Issue Apache crashes on every hosting settings change

[Bennyyyy]

I have been having problems with my Plesk server for some time. The server is running on a LXC server in Proxmox. About 4 weeks ago I had a hard disk damage and had to restore the Plesk server. Up to this point everything was running fine. Since the restore, all domains have a 502 Bad Gateway Error every time I change the hosting settings. The Apache server hangs with the status "deactivating". This can be fixed by restarting the Apache server manually or automatically after about 5 minutes. Since restoring the server from a 1:1 backup, features like automatic mail account setup (QR code) are also missing. I can't find the error and I don't understand how there can be changes in a 1:1 backup.

System:
Plesk ObsidiaN
CPU Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz (8 core(s))
RAM 32 GB
Version Plesk Obsidian v18.0.40_build1800220116.00 os_Debian 10.0
OS Debian 10.11

Apache status when hanging

apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─limit_nofile.conf
   Active: deactivating (stop-sigterm) since Sat 2022-02-05 21:00:44 UTC; 53s ago
     Docs: https://httpd.apache.org/docs/2.4/
  Process: 12717 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
  Process: 21572 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS)
  Process: 22337 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
   Memory: 136.6M
   CGroup: /system.slice/apache2.service
           └─21753 /usr/sbin/apache2 -k start

Feb 05 20:34:48 Plesk apachectl[12717]: Setting ulimit failed. See README.Debian for more information.
Feb 05 20:34:48 Plesk systemd[1]: Started The Apache HTTP Server.
Feb 05 21:00:03 Plesk systemd[1]: Reloading The Apache HTTP Server.
Feb 05 21:00:03 Plesk apachectl[21572]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Feb 05 21:00:03 Plesk apachectl[21572]: Setting ulimit failed. See README.Debian for more information.
Feb 05 21:00:04 Plesk systemd[1]: Reloaded The Apache HTTP Server.
Feb 05 21:00:44 Plesk systemd[1]: Stopping The Apache HTTP Server...
Feb 05 21:00:44 Plesk apachectl[22337]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Feb 05 21:00:44 Plesk apachectl[22337]: Setting ulimit failed. See README.Debian for more information.
Feb 05 21:00:44 Plesk apachectl[22337]: httpd (pid 12757?) not running

Apache log when hanging

[ N 2022-02-05 21:14:30.1211 26094/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog...
[ N 2022-02-05 21:14:30.1365 26098/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core...
[ N 2022-02-05 21:14:30.1366 26098/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode.
[ N 2022-02-05 21:14:30.1705 26098/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 26098
[Sat Feb 05 21:14:30.265345 2022] [core:warn] [pid 26084] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Feb 05 21:14:30.279726 2022] [mpm_prefork:notice] [pid 26084] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1d mod_fcgid/2.3.9 Phusion_Passenger/6.0.8 configured -- r$
[Sat Feb 05 21:14:30.279767 2022] [core:notice] [pid 26084] AH00094: Command line: '/usr/sbin/apache2'
[ N 2022-02-05 21:14:32.2309 26098/T5 age/Cor/SecurityUpdateChecker.h:519 ]: Security update check: no update found (next check in 24 hours)

All repair tools have unfortunately brought nothing and also find no errors.

Thanks for any help

 

[Dave W]

A. Nolan you should start your own thread and not jump another users thread.​

 

[Maarten.]

I have been having problems with my Plesk server for some time. The server is running on a LXC server in Proxmox. About 4 weeks ago I had a hard disk damage and had to restore the Plesk server. Up to this point everything was running fine. Since the restore, all domains have a 502 Bad Gateway Error every time I change the hosting settings. The Apache server hangs with the status "deactivating". This can be fixed by restarting the Apache server manually or automatically after about 5 minutes. Since restoring the server from a 1:1 backup, features like automatic mail account setup (QR code) are also missing. I can't find the error and I don't understand how there can be changes in a 1:1 backup.

System:
Plesk ObsidiaN
CPU Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz (8 core(s))
RAM 32 GB
Version Plesk Obsidian v18.0.40_build1800220116.00 os_Debian 10.0
OS Debian 10.11

Apache status when hanging

apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─limit_nofile.conf
   Active: deactivating (stop-sigterm) since Sat 2022-02-05 21:00:44 UTC; 53s ago
     Docs: https://httpd.apache.org/docs/2.4/
  Process: 12717 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
  Process: 21572 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS)
  Process: 22337 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
   Memory: 136.6M
   CGroup: /system.slice/apache2.service
           └─21753 /usr/sbin/apache2 -k start

Feb 05 20:34:48 Plesk apachectl[12717]: Setting ulimit failed. See README.Debian for more information.
Feb 05 20:34:48 Plesk systemd[1]: Started The Apache HTTP Server.
Feb 05 21:00:03 Plesk systemd[1]: Reloading The Apache HTTP Server.
Feb 05 21:00:03 Plesk apachectl[21572]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Feb 05 21:00:03 Plesk apachectl[21572]: Setting ulimit failed. See README.Debian for more information.
Feb 05 21:00:04 Plesk systemd[1]: Reloaded The Apache HTTP Server.
Feb 05 21:00:44 Plesk systemd[1]: Stopping The Apache HTTP Server...
Feb 05 21:00:44 Plesk apachectl[22337]: /usr/sbin/apachectl: 99: ulimit: error setting limit (Operation not permitted)
Feb 05 21:00:44 Plesk apachectl[22337]: Setting ulimit failed. See README.Debian for more information.
Feb 05 21:00:44 Plesk apachectl[22337]: httpd (pid 12757?) not running

Apache log when hanging

[ N 2022-02-05 21:14:30.1211 26094/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog...
[ N 2022-02-05 21:14:30.1365 26098/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core...
[ N 2022-02-05 21:14:30.1366 26098/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode.
[ N 2022-02-05 21:14:30.1705 26098/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 26098
[Sat Feb 05 21:14:30.265345 2022] [core:warn] [pid 26084] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Feb 05 21:14:30.279726 2022] [mpm_prefork:notice] [pid 26084] AH00163: Apache/2.4.38 (Debian) OpenSSL/1.1.1d mod_fcgid/2.3.9 Phusion_Passenger/6.0.8 configured -- r$
[Sat Feb 05 21:14:30.279767 2022] [core:notice] [pid 26084] AH00094: Command line: '/usr/sbin/apache2'
[ N 2022-02-05 21:14:32.2309 26098/T5 age/Cor/SecurityUpdateChecker.h:519 ]: Security update check: no update found (next check in 24 hours)

All repair tools have unfortunately brought nothing and also find no errors.

Thanks for any help

What is the output of this command?

# grep ULIMIT /usr/sbin/apache2ctl

Seems like you're hitting the limits of ulimit:

apache2ctl: 87: ulimit: error setting limit (Operation not permitted)

The server is running fine -- or at least it seems to -- but there's always the following error: apache2/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) It happens ...

serverfault.com

 

[Bitpalast]

In this case probably not. It is not claimed that the limit is exceeded, but that it cannot be set due to a lack of permissions. If the user started Apache with sudo it would work. For some reason after his restore he is lacking some root permissions. The question is how @Bennyyyy has actually done the restore. He says it is a 1:1 copy, but it is probably not, else it would not have changed permissions.