Went through and updated "all" my ISPConfig servers and all are working fine after update except one. Once a day, of course in the middle of the night, one of them goes haywire and can't seem to recover. All I do to fix the issue is to login and start Apache since it won't start form ISPconfig recovery This morning it started at 6.27 AM with this from the cron.log Code: Thu Jan 20 06:27:06 CET 2022 sh: -c: line 0: syntax error near unexpected token `&&' Thu Jan 20 06:27:06 CET 2022 sh: -c: line 0: ` && (sleep 3; kill $!; sleep 2; kill -9 $!) &> /dev/null' Thu Jan 20 06:27:06 CET 2022 PHP Warning: exec(): Cannot execute a blank command in /usr/local/ispconfig/server/mods-available/rescue_core_module.inc.php on line 478 Thu Jan 20 06:27:06 CET 2022 finished server.php. Thu Jan 20 06:28:01 CET 2022 sh: -c: line 0: syntax error near unexpected token `&&' Thu Jan 20 06:28:01 CET 2022 sh: -c: line 0: ` && (sleep 3; kill $!; sleep 2; kill -9 $!) &> /dev/null' Thu Jan 20 06:28:01 CET 2022 PHP Warning: exec(): Cannot execute a blank command in /usr/local/ispconfig/server/mods-available/rescue_core_module.inc.php on line 478 Thu Jan 20 06:28:01 CET 2022 finished server.php. Thu Jan 20 06:29:01 CET 2022 sh: -c: line 0: syntax error near unexpected token `&&' Thu Jan 20 06:29:01 CET 2022 sh: -c: line 0: ` && (sleep 3; kill $!; sleep 2; kill -9 $!) &> /dev/null' Thu Jan 20 06:29:01 CET 2022 PHP Warning: exec(): Cannot execute a blank command in /usr/local/ispconfig/server/mods-available/rescue_core_module.inc.php on line 478 Thu Jan 20 06:29:01 CET 2022 finished server.php. Thu Jan 20 06:30:01 CET 2022 ipcrm: not enough arguments Thu Jan 20 06:30:01 CET 2022 Thu Jan 20 06:30:01 CET 2022 Usage: Thu Jan 20 06:30:01 CET 2022 ipcrm [options] Thu Jan 20 06:30:01 CET 2022 ipcrm shm|msg|sem <id>... Thu Jan 20 06:30:01 CET 2022 Thu Jan 20 06:30:01 CET 2022 Remove certain IPC resources. Thu Jan 20 06:30:01 CET 2022 Thu Jan 20 06:30:01 CET 2022 Options: Thu Jan 20 06:30:01 CET 2022 -m, --shmem-id <id> remove shared memory segment by id Thu Jan 20 06:30:01 CET 2022 -M, --shmem-key <key> remove shared memory segment by key Thu Jan 20 06:30:01 CET 2022 -q, --queue-id <id> remove message queue by id Thu Jan 20 06:30:01 CET 2022 -Q, --queue-key <key> remove message queue by key Thu Jan 20 06:30:01 CET 2022 -s, --semaphore-id <id> remove semaphore by id Thu Jan 20 06:30:01 CET 2022 -S, --semaphore-key <key> remove semaphore by key Thu Jan 20 06:30:01 CET 2022 -a, --all[=shm|msg|sem] remove all (in the specified category) Thu Jan 20 06:30:01 CET 2022 -v, --verbose explain what is being done Thu Jan 20 06:30:01 CET 2022 Thu Jan 20 06:30:01 CET 2022 -h, --help display this help and exit Thu Jan 20 06:30:01 CET 2022 -V, --version output version information and exit Thu Jan 20 06:30:01 CET 2022 Thu Jan 20 06:30:01 CET 2022 For more details see ipcrm(1). Thu Jan 20 06:30:02 CET 2022 sh: -c: line 0: syntax error near unexpected token `&&' Thu Jan 20 06:30:02 CET 2022 sh: -c: line 0: ` && (sleep 3; kill $!; sleep 2; kill -9 $!) &> /dev/null' Thu Jan 20 06:30:02 CET 2022 PHP Warning: exec(): Cannot execute a blank command in /usr/local/ispconfig/server/mods-available/rescue_core_module.inc.php on line 478 Thu Jan 20 06:30:02 CET 2022 finished server.php. and a bit later it also adds Code: Thu Jan 20 06:32:01 CET 2022 20.01.2022-06:32 - ERROR - httpd is down! Rescue will not help! And that keeps going until I restart apache2 and then all is fine, for what it seems, about 24 hours and then it goes again (this is day 2 of the same and I did some updates to the system and ispconfig_update 2 days ago) Any ideas? Debian 9 + Apache 2
I haven't exactly figured out what made this happen and only at 6:27 every morning. I did put in a scheduled restart of the apache2 service at 6.30 today after it went haywire again (quick and dirty I know) but figured I should test it and see what happened in the logs at the time.. found some *** Error in `/usr/sbin/apache2': double free or corruption (!prev): 0x0000563a280888f0 *** which in the subsequent things pointed to libphp7.4.so so I tried reinstalling it but didn't do much so I dis a a2enmod (again) and remove php8.0 that was also as a module /etc/apache2/mods-enabled and tried again and no segfaults this time. I'll report back tomorrow after 6.30 am and let you know if it went bonkers again or not.
