• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Forwarded to devs Changing Apache settings from MPM to Prefork and setting a new restart interval after fresh install throws an error message

Bitpalast

Plesk addicted!
Plesk Guru
Username: Peter Debik

TITLE

Changing Apache settings from MPM to Prefork and setting a new restart interval after fresh install throws an error message

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Obsidian 18.0.34, latest MU
CentOS 7.9

PROBLEM DESCRIPTION

Fresh install.
Tools & Settings > Apache Web Server Settings
Change the restart interval to a value like 600 or 900 or similar.
Change MPM from Event to Prefork.
Click "OK"

Result:

Internal error{"formMessages":{"apacheModules":{"apache_modules":{"notInArray":"This option is not supported."}}},"status":"success","statusMessages":[{"class":"","content":"Apache modules configuration was saved.","source":null,"status":"info","title":"Information"}]}

STEPS TO REPRODUCE

Fresh install.
Tools & Settings > Apache Web Server Settings
Change the restart interval to a value like 600 or 900 or similar.
Change MPM from Event to Prefork.
Click "OK"

ACTUAL RESULT

Red box on top of the screen with this content:
Internal error{"formMessages":{"apacheModules":{"apache_modules":{"notInArray":"This option is not supported."}}},"status":"success","statusMessages":[{"class":"","content":"Apache modules configuration was saved.","source":null,"status":"info","title":"Information"}]}

EXPECTED RESULT

No errors.

ANY ADDITIONAL INFORMATION

I have reloaded the same menu item afterwards, and the settings have been applied.
It seems that the changes were applied to the Apache configuration, too.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Hi Peter,
Developers can't reproduce the issue. Access to your server is required.
So, please contact Plesk Support Team.
 
Back
Top