"Waiting for unicorn to reload", then update stops


(DiscourseMetrics.com) #1

I’m getting these messages when updating:

and then the update stops with the error message in the header.

Any ideas? :slight_smile:


(Florian) #2

Last time when this happened, I needed to

cd /var/discourse
./launcher rebuild app

(DiscourseMetrics.com) #3

Thanks! Will give that a try :slight_smile:


(DiscourseMetrics.com) #4

Rebuilding worked, but I still get the same error afterwards when updating using the web UI.


#5

I’ve had this but did not need to rebuild. It had apparently updated though this was not reflected on the web UI progress. Waiting a while and then opening the upgrade screen again confirmed that despite the odd visual behaviour, Discourse had updated.


(Alan Tan) #6

This is odd, do you see anything if you do ./launcher logs app?


(DiscourseMetrics.com) #7

This is the last I see in the logs:

[Wed Nov  7 21:34:09 UTC 2018] Run reload cmd: sv reload nginx
warning: nginx: unable to open supervise/ok: file does not exist
[Wed Nov  7 21:34:09 UTC 2018] Reload error for :
Started runsvdir, PID is 326
ok: run: redis: (pid 337) 0s
ok: run: postgres: (pid 342) 0s
rsyslogd: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
rsyslogd: imklog: cannot open kernel log (/proc/kmsg): Operation not permitted.
rsyslogd: activation of module imklog failed [v8.16.0 try http://www.rsyslog.com/e/2145 ]
rsyslogd: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
supervisor pid: 338 unicorn pid: 378
(338) Reloading unicorn (378)
(338) Waiting for new unicorn master pid... 18109
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Waiting for new unicorn workers under 18109 to start up...
(338) Old pid is: 378 New pid is: 18109

(Alan Tan) #8

Ah I found the problem, when the script encounters an error it logs to STDERR which goes to nowhere right now. I fixed it so that we publish the errors to the client too.