Perfect Server CentOS 8, ISPConfig 3.2.6 Anyone seen this email message before? I never have, and I think it may have come from my attempt to import a MySql export from phpmyadmin from one system into my current system - both ISPConfig systems. The import failed with an error message that I quickly forgot because I switched to the command line and imported the database without an issue. I then noticed this in my inbox 30 minutes later. Just curious, haven't dug more into it yet. thanks.
Either apache or nginx on this system may be started and working but the service is not enabled in systemd, so systemctl command does not return it as valid enabled service when ISPConfig queries systemd, use either: systemctl enable httpd or systemctl enable nginx to enable the web server service on Centos, depending on the web server software you use.
thanks for the response. i'm was pretty sure it was enabled, so i ran systemctl with no options, paged down till i found this: Code: httpd.service loaded active running The Apache HTTP Server so i think that means it's already enabled. also, i don't have to start the service manually after a reboot, if that helps verify it.
Ok, then you must check when this issue happens again so we can narrow down which service is causing it. MySQL is not restarted by ispconfig, so it can not cause that error.
Please post the exact lines from the debug log hen this happens. The message indicates that there is a misconfiguration for one of your server services which has no init script set, it might be an additional PHP version.
Many thanks Till for not resting on sundays I had disabled debug logging for fear of performance but I can re-enable it if you'd like? 09.03.2025-08:20 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:21 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:22 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:22 - WARNING - Let's Encrypt SSL Cert for: network.aemtextile.com could not be issued. 09.03.2025-08:22 - WARNING - /bin/certbot certificates --domains network.aemtextile.com --domains www.network.aemtextile.com 09.03.2025-08:23 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:24 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'borg' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'gzip' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'gunzip' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'zip' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'unzip' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'pigz' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'tar' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'bzip2' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'bunzip2' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'xz' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'unxz' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which '7z' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'rar' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'fail2ban-client' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'setquota' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'xfs_quota' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'iptables' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'ip6tables' 2> /dev/null - return code: 0 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'tw_cli' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'hpacucli' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'megacli' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'megacli64' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [system.inc:2440] - safe_exec cmd: which 'arcconf' 2> /dev/null - return code: 1 09.03.2025-08:25 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:26 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:26 - WARNING - No init script, we quit here. 09.03.2025-08:27 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:28 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:29 - DEBUG [cron:129] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock 09.03.2025-08:30 - DEBUG [system.inc:2440] - safe_exec cmd: which 'borg' 2> /dev/null - return code: 0 09.03.2025-08:30 - DEBUG [system.inc:2440] - safe_exec cmd: which 'gzip' 2> /dev/null - return code: 0 09.03.2025-08:30 - DEBUG [system.inc:2440] - safe_exec cmd: which 'gunzip' 2> /dev/null - return code: 0
Ok, this message does not really indicate which services has the problem here. Please unzip and then copy the attached file to /usr/local/ispconfig/server/lib/classes/ folder, it should give an improved and more detailed error message.
ah - finally, it was the apache it was upset about: 10.03.2025-07:19 - WARNING - No init script for: apache2 with action: start and path: /etc/init.d, we quit here. I have systemd with httpd. so no apache2 script anywhere AFAIK..
Yes, this is just a fallback if systemd reports no systemd unit for this service. I guess the underlying issue is that for some reason it tries to use apache2 as service name on your system and not httpd. on Debian and Ubuntu, the service is named apache2. Probably someone hardcoded it in some place. Which ISPConfig function did you use when you received this message?
Just a guess, did you maybe enable System > Server config > Rescue > Enable service monitoring and restart on failure ? If yes, try to disable that. This is a very old function that is usually not used today on ISPConfig systems as there is a better alternative to using Monit.
