We need to find a possibility to make sure that delayed jobs (rake jobs:work) are securely stopped by the ./stop script. As a minimum, an error message must be displayed.
Full log (prompt shortened, i.e. replaced by $):
$ ./stop
$ ./status
Web Portal (productive on port 3000): stopped
Web Portal (development): running (PID=14447) on port 3001
Delayed Jobs: running (PID=30019)
$ ./status
Web Portal (productive on port 3000): stopped
Web Portal (development): running (PID=14447) on port 3001
Delayed Jobs: running (PID=30019)
Delayed Jobs did not stop for several minutes. Workaround:
$ kill -9 30019
this had killed the process, as we see by trying again:
$ kill -9 30019
-bash: kill: (30019) - No such process
Prio is set to low, since this bug does not impact the service itself. It just adds more work on the operations folks.
We need to find a possibility to make sure that delayed jobs (rake jobs:work) are securely stopped by the ./stop script. As a minimum, an error message must be displayed.
Full log (prompt shortened, i.e. replaced by
$):Delayed Jobs did not stop for several minutes. Workaround:
this had killed the process, as we see by trying again:
Prio is set to low, since this bug does not impact the service itself. It just adds more work on the operations folks.