OPNsense Forum

Archive => 22.7 Legacy Series => Topic started by: meyergru on July 28, 2022, 04:56:05 pm

Title: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: meyergru on July 28, 2022, 04:56:05 pm

Seems I go first here...

Upgraded a few systems from 22.1.10 to 22.7 with only a few errors from HAproxy which like depreciation warnings because of the new PHP version - no worries, HAproxy works as before.

Good work!

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: schnerring on July 28, 2022, 06:59:57 pm

I follwed the popular HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating (https://forum.opnsense.org/index.php?topic=23339.0) tutorial.

Some PHP errors are reported by OPNsense:

Code: [Select]

[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $expression follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 147
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $testType follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 176
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $type follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 176
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $address follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 204
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $port follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 204
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $mode follows optional parameter $description in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 204
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $name follows optional parameter $enabled in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 230
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $mode follows optional parameter $enabled in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 230
[28-Jul-2022 16:47:15 Etc/UTC] PHP Deprecated:  Required parameter $algorithm follows optional parameter $enabled in /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php on line 230

Those probably are the same errors you're seeing. But it still works!

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: schnerring on July 28, 2022, 07:39:17 pm

A PR has already been merged to fix the issue. (https://github.com/opnsense/plugins/pull/3043) So all we have to do is wait for a new haproxy release.

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: deeler on July 29, 2022, 07:45:39 am

I have these errors to, but also HAproxy not working

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: deeler on July 29, 2022, 07:46:50 am

this is the error seen on the GUI:

Code: [Select]

An API exception occurred
/usr/local/opnsense/mvc/app/controllers/OPNsense/Base/ApiControllerBase.php:159: Error at /usr/local/opnsense/mvc/app/models/OPNsense/HAProxy/HAProxy.php:147 - Required parameter $expression follows optional parameter $description (errno=8192)
after clicking 'OK' the pages still show, but all config is empty

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: Re4mstr on July 29, 2022, 08:04:05 am

I have the exact issue.

Except for HAproxy, everything works..

Title: Re: Upgrade from 22.1.10 went fine, apart from HAproxy warnings
Post by: peysche on January 06, 2023, 04:31:55 pm

Hi,

I upgradet a old System this Days to 22.7_10.2.

HAProxy Seams to work fine, but as soon as i add a new Condition or Rule they will not get written into /usr/local/etc/haproxy.conf.staging or /usr/local/etc/haproxy.conf


I can not see anything pointing to an error in logs or config validation.

Existing Rules/Conditions can be modified, and are written into the config for HAProxy.


Did someone have the same experience ?


My workaround currently is to mod the config Files manually.

Thx
Peysche