Bug #14425
closed
"Max Processes" value is not stored properly when saving on ``system_advanced_admin.php``
Added by M Felden over 1 year ago.
Updated over 1 year ago.
Plus Target Version:
23.05.1
Description
When instance was on 23.01, went to
system_advanced_admin.php and bumped maxprocesses for the web configurator to 4. Applied change. nginx restarted and it reflected 4.
Upgraded to 23.05 REL
Set it back to 2. Saved. nginx restarted and still shows 4.
Whatever value is entered and saved, it will revert to 4.
On another instance it was still on 2 at the time of upgrade to 23.05 and I cannot change it to any other value. It reverts to 2.
Confirmed able to recreate this in 23.05-RELEASE. The <max_procs> value is not updated in the config.xml either.
- Project changed from pfSense Plus to pfSense
- Subject changed from system_advanced_admin.php -> Editing webConfigurator Max Processes reverts to whatever original value was. to "Max Processes" value is not stored properly when saving on ``system_advanced_admin.php``
- Category changed from Web Interface to Web Interface
- Assignee set to Jim Pingle
- Target version set to 2.7.0
- Affected Plus Version deleted (
23.05)
- Plus Target Version set to 23.09
This isn't Plus-specific. Also it appears to stay when saving but reverts when refreshing the page. If the value is not present in the configuration, an empty tag is added on save.
Probably a variable name isn't referenced properly when saving values.
- Status changed from New to Feedback
- % Done changed from 0 to 100
Tested in 23.05 via System Patch. Max Processes variable is now properly updated and shows in the config and the webConfigurator after applying. This can be closed as Resolved.
- Status changed from Feedback to Resolved
- Plus Target Version changed from 23.09 to 23.05.1
- Affected Version set to 2.7.0
Also available in: Atom
PDF
Updated by 
Updated by