Our websites are currently down. None of our sites on this ISPConfig server are coming up. Our ISPConfig server's /var mount ran low on space due to backups filling the mount. We deleted some of the backups to recover some space and restarted the server. Initialy neither ISPConfig nor websites were coming up. Now, ISPConfig starts but the websites do not giving us the following error: ========================== ========================== "Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.4.29 (Ubuntu) Server at www.networkinaction.com Port 443" ========================== ========================== Checked Apache log but am not seeing anything that's pointing me in the direction for the cause. I will post the Apache log as soon as the server reboots. Trying something else right now. Any help would be greatly appreciated it and thank you in advance.
systemctl list-units --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION ● php7.2-fpm.service loaded failed failed The PHP 7.2 FastCGI Process Manager LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.
I started php7.2-fpm manually from the cli and now the command shows the following but the site loads to an error now. systemctl list-units --state=failed 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.
Ok, so the site developer figured out that there was an issue with the code and why the sites were not coming up after I got php7.2-fpm started. So sites are back up. Now I have to deal with the issue of why php7.2-fpm wasn't starting at boot and why I was able to get it started via the cli. At least things are back up now.
Good to hear things are back up. You could try to simply reboot and see if it still doesn't start up.
Thanks. Exactly what I was planning but have to wait for a time when the site is not being used. Am wondering if the issue discovered by the developer was causing something to trip up and cause the service to fail. Thank you for your help. That command you had me run gave me exactly what I needed to isolate the issue and get things back up. Appreciate your help.
