• 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 The same procedure every night - the configuration files are gone

TK79

New Pleskian
Hi Plesk-Fans,

since ~14 days I've got the problem of loosing my web server configuration files every night (~ 4:00).
I think a Plesk process does something wrong that causes this.

Every morning I get an email from Plesk with this text:

Unable to generate the web server configuration file on the host <server03.drehpunkt.info> because of the following errors:

Template_Exception: 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: Could not open configuration file /etc/httpd/conf/plesk.conf.d/forwarding/last_httpd.conf: No such file or directory

file: /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php
line: 75
code: 0

Please resolve the errors in web server configuration templates and generate the file again.



In Plesk itself I can see this message:

upload_2019-10-31_15-53-39.png

I tried to find some solutions in this forum, but I was not able to fix this issue.

Ths "Webserver Configurtions Troubleshooter" shows issues, but the "Check configuration" shows that everything is fine:

upload_2019-10-31_15-56-41.png

upload_2019-10-31_15-59-52.png


With the option "Rebuild broken" I can fix the issue ... until tomorrow.

upload_2019-10-31_16-7-41.png


Does somebody has an idea what could cause this problem and how I can fix this?


Best wishes,

Tino
 
* push *

I still have the problems, I tried to solve the issues with the manual repair tool kit, but that does not work.
Does nobody has any idea? :-(
 
Try to fix it with

# plesk bin repair --update-vhosts-structure

Also, I'd suggest you check that there is a lack of write access to the file /etc/httpd/conf/plesk.conf.d/forwarding/last_httpd.conf or related directories.
 
Hello @IgorG

I've tried this:

[root@XXXXX~]# plesk bin repair --update-vhosts-structure
The structure of the home directory was successfully updated on virtual hosts.


But that solved not my problem. :-(
After the "plesk bin rapair" I tried to do again "plesk repair web", but that does also not fixed my issues.


[root@XXXXX~]# plesk repair web

Checking Plesk version .............................................. [OK]

Checking for custom configuration templates ......................... [OK]

Checking the JkWorkersFile directive in the Apache configuration .... [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object
................................................................... [OK]

Checking the configuration of Apache modules ........................ [OK]

Checking web server configuration

Reinstall SSL/TLS certificates and set the default certificate for all IP addresses? [Y/n] Y
Reinstalling SSL/TLS certificates ............................... [OK]
Applying the default SSL/TLS certificate to all IP addresses .... [OK]

File not found: xxx.info.conf
File not found: xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.mobi.conf
File not found: xxx.mobi.conf
File not found: xxx.xxx.mobi.conf
File not found: xxx.xxx.mobi.conf
File not found: xxx.xxx.mobi.conf
File not found: xxx.xxx.mobi.conf
File not found: xxx.net.conf
File not found: xxx.de.conf
File not found: xxx-xxx.net.conf
File not found: xxx.xxx-xxx.net.conf
File not found: xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx-xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.de.conf
File not found: xxx-xxx-xxx.net.conf
File not found: xxx.net.conf
File not found: xxx-xxx.de.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.info.conf
File not found: xxx-xxx.de.conf
File not found: xxx-xxx.de.conf
File not found: _.xxx.de.conf
File not found: xxx-xxx.de.conf
File not found: xxx.xxx.net.conf
File not found: xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.support.conf
File not found: xxx.energy.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.support.conf
File not found: xxx.xxx-xxx.de.conf
File not found: xxx.xxx-xxx.de.conf
File not found: xxx.xxx-xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.support.conf
File not found: xxx.eu.conf
File not found: xxx.de.conf
File not found: xxx.fail.conf
File not found: xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.de.conf
File not found: xxx.xxx.net.conf
File not found: xxx.de.conf
File not found: xxx-xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.org.conf
File not found: xxx.xxx.org.conf
File not found: xxx.de.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.net.conf
File not found: xxx.international.conf
File not found: xxx.de.conf
File not found: xxx.com.conf
File not found: xxx.news.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx-xxx-xxx.eu.conf
File not found: xxx.app.conf
File not found: xxx-xxx.xxx.de.conf
File not found: xxx.eu.conf
File not found: xxx.town.conf
File not found: xxx.li.conf
File not found: xxx.li.conf
File not found: xxx-xxx.de.conf
File not found: xxx-xxx.de.conf
File not found: xxx.xxx.eu.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: _.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.net.conf
File not found: xxx.xxx.info.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf
File not found: xxx.xxx.de.conf ............................ [ERROR]

Repair web server configuration for all domains? [Y/n] Y
Repairing web server configuration for all domains. This aspect
can be used with individual domains ("plesk repair web
example.com"), and on the server level ("plesk repair web") ..... [FIXED]

Repair server-wide configuration parameters for web servers? [Y/n] Y
Repairing server-wide configuration parameters for web servers .. [OK]

Update the file of sharing passwords and permissions of users according to actual information? [Y/n] Y
Updating the file of sharing passwords and permissions of users
according to actual information ................................. [OK]

Checking the usage of PHP handlers .................................. [OK]

Error messages: 1; Warnings: 0; Errors resolved: 1

The tool says "fixed", but nothing was fixed. :-(

/Tino
 
[root@XXX~]# ls -l /etc/httpd/conf/plesk.conf.d/forwarding/last_httpd.conf
lrwxrwxrwx 1 root root 19 Sep 28 23:57 /etc/httpd/conf/plesk.conf.d/forwarding/last_httpd.conf -> xxx.de_httpd.conf

I think it's red because the /etc/httpd/conf/plesk.conf.d/forwarding/last_httpd.conf is a symbolic link and the domain configuration file does not exist.
 
[root@XXX~]# ls -l /etc/httpd/conf/plesk.conf.d/forwarding/
total 0
lrwxrwxrwx 1 root root 19 Sep 28 23:57 last_httpd.conf -> h4n54.de_httpd.conf
 
[root@XXX~]# ls -l /etc/httpd/conf/plesk.conf.d/
total 56
drwxr-xr-x 2 root root 4096 Nov 10 18:17 forwarding
drwxr-xr-x 2 root root 4096 Nov 1 09:26 ip_default
-rw------- 1 root apache 1 Oct 29 23:53 modsecurity.conf
-rw------- 1 root apache 1 Oct 17 23:15 modsecurity.conf.bak
-rw-r--r-- 1 root root 2558 Nov 1 09:27 roundcube.htaccess.inc
-rw------- 1 root apache 4959 Nov 9 22:00 server.conf
-rw------- 1 root apache 4959 Nov 9 22:00 server.conf.bak
drwxr-xr-x 2 root root 4096 Nov 9 21:58 vhosts
drwxr-xr-x 2 root root 12288 Nov 9 22:01 webmails
drwxr-xr-x 2 root root 4096 Nov 1 09:26 wildcards
 
It's interesting that the directories have the "root" user and group permission.
Is that normal?
 
Hi,

today the Plesk support told me that there are several issues with "ImunifyAV" that can be installed as extension.

upload_2019-11-11_22-57-44.png


Now I've uninstalled this extension and I'm waiting for tomorrow if my problem is solved.

Press your thumbs, please! :mad:


Regards

Tino
 
It's interesting that the directories have the "root" user and group permission.
Is that normal?
Yes, it is ok. On my test server I see the same:

# ls -l /etc/httpd/conf/plesk.conf.d/
total 40
drwxr-xr-x 2 root root 4096 Nov 7 19:29 forwarding
drwxr-xr-x 2 root root 4096 Nov 7 19:29 ip_default
-rw-r--r-- 1 root root 2558 Nov 7 19:29 roundcube.htaccess.inc
-rw------- 1 root apache 4603 Nov 12 04:59 server.conf
-rw------- 1 root apache 4603 Nov 12 04:59 server.conf.bak
drwxr-xr-x 2 root root 4096 Nov 12 09:12 vhosts
drwxr-xr-x 2 root root 4096 Nov 12 09:12 webmails
drwxr-xr-x 2 root root 4096 Nov 7 19:29 wildcards

If problem still actual I'd suggest you contact Plesk Support Team. Investigation directly on your server is required.
 
Hello Friends,

the Plesk Support found some suspicious errors on my server that were probably caused by an incorrect automatic update/upgrade of Plesk.

The main causing error was the file /usr/local/psa/admin/plib/Template/Writer/Webserver/Abstract.php. It was a wrong file version of an older Plesk, so the configuration files could not be written during the maintenance process.

The support replaced it with an actual version of the installed Plesk version and now everything works.

I don't know how to solve this topic yourself ... I think if somebody has this problem somebody should give him this file via this forum.


Best regards

Tino
 
Back
Top