Posted by ckosloff on September 13, 2014 at 2:49pm
I am continuously getting 502 nginx errors when working on modules, enabling/disabling, updating, etc.
I just ran update barracuda up-stable and octopus up-stable all both, to no avail.
In hostmaster I flushed all caches and ran helath check without major issues reported, I just have to install some minor updates to some modules.
Any idea what is causing these errors?

Comments
I did have this problem for a
I did have this problem for a brief time after updating to 2.3.0, but I had a custom vhost which was using port-based php-fpm socket. See https://github.com/omega8cc/boa/commit/bc9968e92e77e28cf6b492c629827720a... for more info. If you have those, you need to change them.
You can then try restarting the nginx and php-fpm services, that should help.
Thanks ar-jan. I had done
Thanks ar-jan.
I had done some research before posting on this issue and found the fpm issue.
I cannot solve it, since my VM only has vanilla Debian 7 + backports and then the BOA install, will have to wait until Monday to find out how the underlying server, running on CentOS, is configured, but my hunch is that there is no custom config for fpm there either.
Also, I had restarted the whole VM from out-of-band vncviewer console, but issue is still there.
Will post findings on Monday.
502 Errors as well
Yeah, I just stabled up from a vanilla Debian BOA 2.2.9 to 2.3.0 and now I am getting random 502 errors. I am running on VMware with 16GB RAM and 2vCPU cores and no traffic. Very few modules enabled. Was going to wait a day or so to see if anyone else was experiencing the same problem.
Peace,
Michael Clendening
It is a known regression
Introduced in this commit: https://github.com/omega8cc/boa/commit/dc9f79d414beef55b5fb947b7fd2d0f54...
Fixed in this commit:
https://github.com/omega8cc/boa/commit/4539d5552f62f2822f729d74808add07b...
To apply a hot fix replace /var/xdrago/proc_num_ctrl.cgi on your system with https://raw.githubusercontent.com/omega8cc/boa/2.3.x-dev/aegir/tools/sys...
BOA-2.3.1 just released
Fixes this problem.