eduardo at November 21st, 2015 18:03 — #1
Currently I am getting the Signaling webhook to create site message when trying to create my first self-hosting site. And it just sits there, nothing happens. Nothing created in my buckets, although I do see site and login info added to my Firebase.
I did some digging around and when I run
sudo supervisorctl status I get this:
beanstalk FATAL Exited too quickly (process log may have details)
build_worker RUNNING pid 19641, uptime 0:13:56
command_delegator RUNNING pid 19627, uptime 0:13:57
create_worker RUNNING pid 19607, uptime 0:13:58
invite_worker RUNNING pid 19636, uptime 0:13:56
reaper RUNNING pid 19618, uptime 0:13:57
webhook_server RUNNING pid 19608, uptime 0:13:58
Also when I run: sudo supervisorctl restart all
beanstalk: ERROR (abnormal termination)
So the issue seems to be beanstalk Does anyone know what causes this? and more importantly, how to fix it?
eduardo at November 24th, 2015 00:34 — #2
Since you guys know about self-hosting, do you have any ideas what may cause this issue? I tried reinstalling Beanstalk and the problem is still there.
budparr at November 24th, 2015 08:24 — #3
Unfortunately, not, though the first thing comes to mind is if you installed with the right permissions. The docs are pretty good on this process, but you have to make sure you're following them explicitly.
dkenzik at November 24th, 2015 11:17 — #4
@Eduardo - Not sure what that's about. Do check permissions, though. And I agree with @budparr in that you must follow the instructions carefully.
niketgupta at June 29th, 2016 08:50 — #5
Facing same issue can anyone suggest a solution for the same
ruben at August 18th, 2016 16:54 — #6
Following the self hosting instructions, the
supervisorctl setup is powered by
webhook.conf. In that file, you see that the
beanstalk program maps to the command
beanstalkd -b /var/beanstalk.
On your compute instance, try running the command and see what error you get. You can also add the verbose flag (
-V) to get more information (
beanstalkd -V -b /var/beanstalk). This might give you some hints about why the status of the process is
I just ran into this myself, and somehow there was already a
beanstalk instance running on the same port. I was getting this message:
beanstalkd: net.c:125 in make_server_socket: bind(): Address already in use. Since the process that was already being run was not one managed by
supervisorctl, I decided to kill the current process that was running, and restart all
To find out the process ID, I used
netstat to see what process was using the default
beanstalkd port (11300). Running
sudo netstat -tulnp revealed that process ID 356 was already using port 113000. The process ID on your compute instance will likely be different, just look for the row whose
Local Address ends with
:113000. Then scan over to the end of the row, and find the
PID value for the row. Thats the process ID. Then you can use the command
sudo kill 356, replacing the
356 with the your process ID.
Once the process that was taking up your
beanstalk port is killed, try running
sudo supervisorctl restart all again and check the status via
sudo supervisorctl status.
I had the same happening with the
webhook_server process, and the same solution fixed it.
Hope that helps!
eduardo at August 20th, 2016 22:15 — #7
Thanks @ruben but I've moved on. As much as I liked WH, it seems like it's not going anywhere. Also even when you self-host it seems you still depend on other services (including WH servers) and that is just too risky for me. But thank you for the reply anyways, I am sure it might help someone else.
Best of luck!