• 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
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Missing httpd.include after backup / apache restart fails

SherlockH

Basic Pleskian
Although this is an old issue, I think it is worth being reposted:

When using the backup manager to create a complete backup including configuration as well as content, mostly one of the apache restarts for one of the domains fails (there seems to be one restart for each domain?). The particular domain can change randomly each time. The apache error log says: missing httpd.include file in the conf-folder of the domain that is affected. When checking the folder manually the file actually exists and apache can be restarted.

Are there any solution for this very severe bug?

Thanks in advance!
 
PS: Could this be a problem of parallel execution of multiple commands in a multi core environment? Sounds like the Plesk configuration writing process has not finished yet when apache is restarted...
 
New world record: Plesk running for one week without failure!

The only changes we made that may be relevant are:
- Allowed unlimited backup processes (I don't think that this is the reason, because we already tried this before without success)
- Created a reseller account (Would be a weird relationship to the backup problem)
 
Dirty hack

What to do with a buggy piece of (expensive) software that offers zero support and doesn't provide any productive use?

- remove it

If you can't because you already have lots of users and avoid the work of a transfer:

- write some dirty hack to make it work

change these lines of /etc/init.d/apache2:

reload | force-reload)
if ! $APACHE2CTL configtest > /dev/null 2>&1; then
$APACHE2CTL configtest || true
log_end_msg 1
exit 1
fi

to

reload | force-reload)
if ! $APACHE2CTL configtest > /dev/null 2>&1; then
sleep 5
if ! $APACHE2CTL configtest > /dev/null 2>&1; then
$APACHE2CTL configtest || true
log_end_msg 1
exit 1
fi
fi

If plesk has not yet finished writing a specific config file, apache sleeps 5 seconds and tries again...
 
Back
Top