Level 65
Could be that it can't find the file when you redeploy? Since it checks every second.
Jun 22, 2015
8
Level 20
supervisor.sock no such file
I have a Laravel 5.0 app using Forge and Envoyer. I have a beanstalkd queue worker running on forge, mainly for queuing emails. Every now and then (maybe after deploy), I notice my emails are not being sent. When I check the worker status on Forge it says:unix:///var/run/supervisor.sock no such file. So it seems supervisor has stopped running. So then I ssh into the server and run sudo service supervisor start and that seems to start it back up again.
When I check the supervisor.log file, I see this error: worker-12345 (exit status 1; not expected)
Does any know why supervisor would stop running? Do I need to manually run supervisor on every deploy? Any help would be greatly appreciated.
Level 20
@bashy I'm not well versed with this stuff, but that could make sense. Maybe when Envoyer activates the new release during the last step of deployment? If that was the case, you would think more people would have noticed this problem though.
Level 65
Yeah I'm not sure what the cause of it is but reading a few threads on SO come to that conclusion. I've not used supervisord with Forge or deploy system.
Level 20
I have read that it may be a bug with supervisor version 3.0b2. Is there an easy way to update supervisor? I'm having difficulty finding any information on how to update.
Level 65
On Forge it should be as easy as apt-get update && apt-get install supervisor --only-upgrade. If Ubuntu has an updated version, it will update. If not, you will need to wait or build it from source.
Level 5
@Swaz Have you fixed that? I'm not using Forge, but getting the same error.
Level 20
@christophrumpel Sorry, I never looked into it any further. I was just playing around with stuff at the time.
Level 5
Ok thx, then I will open a new thread.
Please or to participate in this conversation.