-
Notifications
You must be signed in to change notification settings - Fork 68
nbproc': undefined method
[]' for nil:NilClass (NoMethodError)
#27
Comments
Just adding a +1 to this issue, as we are also seeing it in out environment. |
I had the same issue, looking at the code it's wanting to parse the nbproc directive from the haproxy.cfg file The stats socket will only work with nbproc 1 as far as i can tell, once you add nbproc 1 to the config file it will resolve this issue. p.s without this directive haproxy defaults to 1 anyway 1.5) Increasing the overall processing powerOn multi-processor systems, it may seem to be a shame to use only one processor, Example :
|
@shaynem we are running into this same issue on the latest (1.3.0) release and we are NOT specifying nbproc. Do you have any recommendations for us? Haproxy version 1.5.2
We also get this error when we try to remove a backend (which is a primary use case for us with haproxyctl).
CC: @mnmexy |
@jayhilden you need to add a socket line to your /etc/haproxy/haproxy.cfg under the global section add something similar to:
|
@lewisst thank you very much, that corrected the first half of the issue issue. Now when I try to reload I get an error surrounding that file (I choose to name it /var/run/haproxy.stat vs admin.sock). It says it's waiting but it never returns. If I run this as root with sudo it works fine. Any advice on this would be much appreciated.
|
We have the same problem:
Results in this error:
|
Changing our configuration to:
Fixed the problem for us. |
Same error here with haproxyctl-1.4.3 and haproxy-1.6.3 It errors out unless nbproc 1 is specified in the global section. Seems like a weird dependency, since nbproc is a rarely used config item, and it's entirely optional. haproxyctl should handle the absence of the non-mandatory nbproc gracefully. Don't error out, just keep working as before. |
+1 |
1 similar comment
👍 |
Hi, with the latest release I get this error when running
sudo service haproxyctl show health
:Everything works fine on 1.3.0, I am using CentOS 6.5.
The text was updated successfully, but these errors were encountered: