• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Apache will not start - missing httpd config file

permaculturegeek

New Pleskian
Hi,
Having noticed my server was down (plesk 10.4.4. with automatic updates) I restarted httpd but get this error:
Could not open configuration file /usr/local/psa/admin/conf/generated/14798242210.11559000_server.include: No such file or directory
With only shell access, how do I get plesk to regenerate its config files? All the individual site files with that timestamp are present.
 
looking back, I missed an email related to the most recent site I added:
Generating new Apache configuration on host <servername> failed because the following error(s) occurred:

httpd: Syntax error on line 221 of /etc/httpd/conf/httpd.conf: Syntax error on line 8 of /etc/httpd/conf.d/zz010_psa_
httpd.conf: Syntax error on line 34 of /usr/local/psa/admin/conf/vhosts_bootstrap.conf: Could not open configuration file /var/www/vhosts/dev.bouncy.co.nz/conf/14731477770.42866700_httpd.include: No such file or directory

Please fix error(s) in templates of Apache configuration and retry generating the configuration file.

- so in more detail, 1) How do I fix the missing file? (will putting an empty file there suffice?)
2) How do I trigger generation from ssh?
 
Hi permaculturegeek,

1) How do I fix the missing file? (will putting an empty file there suffice?)
Pls. delete the file "zz010_psa_httpd.conf" ( or rename it, if you would like to keep a backup, to for example "zz010_psa_httpd.conf.backup" ) and recreate the webserver - configuration files with the command: /usr/local/psa/admin/bin/httpdmng --reconfigure-all

2) How do I trigger generation from ssh?
Pls. see possible command options for the "httpdmng" - utility with:

/usr/local/psa/admin/bin/httpdmng --help
 
Ok, I tried that and the configuration failed, once again with the error that the file /var/www/vhosts/dev.bouncy.co.nz/conf/14731477770.42866700_httpd.include is missing. In fact the folder /var/www/vhosts/dev.bouncy.co.nz/ is empty.

Note that the site dev.bouncy.co.nz actually resides at /var/www/vhosts/bouncy.co.nz/casper/ (Manual install of Wordpress there). The client is happy to delete that site (hardly any work done on it) if it can get their other sites working again. Can that be done by ssh, or does Plesk use a database?
 
Last edited:
Hi permaculturegeek,

The client is happy to delete that site
No need to delete anything... the content of a (sub)domain itself is never the root cause of an issue/error/problem, when generating webserver configuration files. ;)

Recommended commands over ssh:
Code:
touch /var/www/vhosts/dev.bouncy.co.nz/conf/14731477770.42866700_httpd.include
/usr/local/psa/admin/bin/httpdmng --reconfigure-domain bouncy.co.nz


If this didn't solve your issue, pls. consider to use your "bootstrapper repair" option:

/usr/local/psa/bootstrapper/ppXX.X.XX-bootstrapper/bootstrapper.sh repair
( where XX.X.XX is the actual existent bootstrapper - version on your server - use "ls -lah /usr/local/psa/bootstrapper" to list the correct folder name )
 
Last edited by a moderator:
looking back, I missed an email related to the most recent site I added:
Generating new Apache configuration on host <servername> failed because the following error(s) occurred:

httpd: Syntax error on line 221 of /etc/httpd/conf/httpd.conf: Syntax error on line 8 of /etc/httpd/conf.d/zz010_psa_
httpd.conf: Syntax error on line 34 of /usr/local/psa/admin/conf/vhosts_bootstrap.conf: Could not open configuration file /var/www/vhosts/dev.bouncy.co.nz/conf/14731477770.42866700_httpd.include: No such file or directory

Please fix error(s) in templates of Apache configuration and retry generating the configuration file.

- so in more detail, 1) How do I fix the missing file? (will putting an empty file there suffice?)
2) How do I trigger generation from ssh?
Hi permaculturegeek,


No need to delete anything... the content of a (sub)domain itself is never the root cause of an issue/error/problem, when generating webserver configuration files. ;)

Recommended commands over ssh:
Code:
touch /var/www/vhosts/dev.bouncy.co.nz/conf/14731477770.42866700_httpd.include
/usr/local/psa/admin/bin/httpdmng --reconfigure-domain bouncy.co.nz

Thanks - the above worked with the addition of having to create phantom log files in the dev.bouncy.co.nz folder
 
Back
Top