haproxy broken after update to 2.8.0: nbproc is not supported any more...
-
Any idea howto fix that after update to 2.8.0.dev?
haproxy: startup error output!: [NOTICE] (59986) : haproxy version is 2.8.1-a90123a[NOTICE] (59986) : path to executable is /usr/local/sbin/haproxy[ALERT] (59986) : config : parsing [/var/etc/haproxy/haproxy.cfg:8] : nbproc is not supported any more since HAProxy 2.5. Threads will automatically be used on multi-processor machines if available.[ALERT] (59986) : config : Error(s) found in configuration file : /var/etc/haproxy/haproxy.cfg[ALERT] (59986) : config : Fatal errors found in configuration.
Can I downgrade manual!? How?
Rgards,
Christian
-
Error
because the
nbproc
config parameter is now deprecated. see nbprocquick 'n' dirty fix:
vi /usr/local/pkg/haproxy/haproxy.inc
around L1564 add a check and only write
nbproc
if the value entered is >1:if ($a_global['nbproc'] > 1) { fwrite ($fd, "\tnbproc\t\t\t{$numprocs}\n"); } $numthread = $a_global['nbthread'] ? $a_global['nbthread'] : "1";
than, just leave it blank and resave in the GUI
-
-
-
I had to apply this by hand, shoule alredy merged...?
Strange....https://github.com/pfsense/FreeBSD-ports/pull/1153
-
after update to the current version this evening I get the following error message.
-
I have the same error…
-
@RMB Dito. We have to wait ...
-
I'm also facing the same issue on haproxy stable.
-
At the end I installed 2.7.0 again and replayed the config.
Something went wrong as I was on the dev branch. The not initiated auto switching to 2.8.0.dev. seemed to make trouble.
Now on 2.7.0-RELEASE and installed haproxy 0.61_11 all is working.Regards,
Christian
-
-
@eduardomozart said in haproxy broken after update to 2.8.0: nbproc is not supported any more...:
pkg install pfSense-pkg-haproxy-devel
Great, just updatet the HAPROXY and the same happened again!
Your two lines fixed it, thank you very very much!
Regards,
Christian
-
I got the same error. I should have known better then to install without seeing if the upgrade is broken out of the gate. Lesson learned.
-
having the same issue, work around:
-
ssh to pfsense
-
edit /var/etc/haproxy/haproxy.cfg and delete the line "nbproc 1"
-
run haproxy from command line: haproxy -f /var/etc/haproxy/haproxy.cfg
-
-
@nartn said in HAProxy 0.62_1 Error after update:
having the same issue, work around:
-
ssh to pfsense
-
edit /var/etc/haproxy/haproxy.cfg and delete the line "nbproc 1"
-
run haproxy from command line: haproxy -f /var/etc/haproxy/haproxy.cfg
I can confirm this works. I initially went to Diagnostics->Edit File, manually made the edit there and tried to restart HAProxy from the GUI. That failed. So I did as you mentioned and that worked! Thank you!
For those that do not want to SSH, you can do it from the pfSense GUI by going to Diagnostics->Edit File, make the change manually, then go to Diagnostics->Command Prompt and run: haproxy -f /var/etc/haproxy/haproxy.cfg
-
-
@eduardomozart You can do the same thing via the package manager to install the dev version. Same thing happened to the pfsense plus version today.
Adding the dev version fixed it.
-
@Darkk I was facing the issue stated at https://forum.netgate.com/topic/180409/can-t-update-pfsense-or-install-packages/ so I was unable to install packages from webUI but was able to install them through CLI.
-
If you don't want to edit anything you can install the dev version which will fix this issue. You don't need to uninstall the standard version as it will replace it with the dev during install.
EDIT: I am running pfsense plus version 23.05.1-RELEASE (amd64) so it might be different on 2.7.
-
@eduardomozart said in haproxy broken after update to 2.8.0: nbproc is not supported any more...:
@Darkk I was facing the issue stated at https://forum.netgate.com/topic/180409/can-t-update-pfsense-or-install-packages/ so I was unable to install packages from webUI but was able to install them through CLI.
Ok, there might be some differences because I am running the pfsense plus version 23.05.1-RELEASE (amd64) .
-
What is nbproc 1?
I feel iffy editing without knowing the full impact. Im glad there’s a fix. Would prefer a package fix of course