HTTPD Stops When Apache Update Available

T

TheTool

Verified User
Joined
Feb 24, 2023
Messages
7
This has been occurring for a couple of years and it's very annoying because my sites are down until the issue is resolved. It only occurs when DA has an update for Apache. To resolve, I either need to rebuild Apache or install the update. I have no idea why it happens nor how to fix it. Is DA trying to automatically install the update and it fails? Below is the apache error log. Does anyone have any idea?

[Fri Feb 21 00:10:27.576100 2025] [mpm_event:notice] [pid 579:tid 579] AH00493: SIGUSR1 received. Doing graceful restart
[Fri Feb 21 00:10:27.718416 2025] [ssl:warn] [pid 579:tid 579] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 21 00:10:27.718895 2025] [ssl:warn] [pid 579:tid 579] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 21 00:10:27.719216 2025] [lbmethod_heartbeat:notice] [pid 579:tid 579] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 21 00:10:27.719755 2025] [mpm_event:notice] [pid 579:tid 579] AH00489: Apache/2.4.63 (Unix) OpenSSL/1.1.1k configured -- resuming normal operations
[Fri Feb 21 00:10:27.719764 2025] [core:notice] [pid 579:tid 579] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 21 00:11:27.663686 2025] [mpm_event:notice] [pid 579:tid 579] AH00493: SIGUSR1 received. Doing graceful restart
[Fri Feb 21 00:11:27.778881 2025] [ssl:warn] [pid 579:tid 579] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 21 00:11:27.779397 2025] [ssl:warn] [pid 579:tid 579] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Fri Feb 21 00:11:27.779626 2025] [lbmethod_heartbeat:notice] [pid 579:tid 579] AH02282: No slotmem from mod_heartmonitor
[Fri Feb 21 00:11:27.780237 2025] [mpm_event:notice] [pid 579:tid 579] AH00489: Apache/2.4.63 (Unix) OpenSSL/1.1.1k configured -- resuming normal operations
[Fri Feb 21 00:11:27.780246 2025] [core:notice] [pid 579:tid 579] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Feb 21 00:21:14.841652 2025] [mpm_event:notice] [pid 579:tid 579] AH00492: caught SIGWINCH, shutting down gracefully
Click to expand...
 
Hello,

The provided logs do not provide any insight. You might disable auto-updates on the server, and stick to manual updates only.
 
Hello,

Thanks for the reply. That's what I don't understand, I do install updates manually. Is there a setting I am missing?
 
If Apache does not stop because of failed upgrade, then it is not clear why it stops. If it's not clear why it stops, we have no solution to suggest.
 
Okay. I just noticed that "autopatch" was not in /usr/local/directadmin/conf/directadmin.conf so I added it and set it to 0. We'll see what happens.
 
What has it to do with Apache malfunction? autopatch=1 - Controls whether Directadmin same version hot-fix updates is enabled (1) or disabled (0).

From what I've got got from your posts, is that Apache on your server goes down by itself, even without(?) an attempt from DirectAdmin to update it.

I would assume the following scenario:

1. DirectAdmin auto updates itself and rewrites configs of Apache without taking an attempt to upgrade it or failing to upgrade Apache
2. You connect to the server and re-install Apache, then the service goes back online.

Is everything correct? Or do I miss? If this is the case, then you need to run:

Code: 
apachectl -t

and/or

Code: 
systemctl status httpd

of course if it is a matter if the service being down, but not other case.
 
Well I don't know what DirectAdmin is doing but yes, that is what's occurring.

Is there another setting that controls the server updates? Like I said, I run those updates manually already.

Edit: Seems the only way to auto update the server is to run a cron which I don't have.
 
Last edited:
You must log in or register to reply here.
Back
Top