Apache Problems after Update 8.1 > 8.1.1

[tglawe]

After the Update on a Debian 3.1 I got a Problem with Apache: It's shutting down regularly.

[Sun Apr 01 11:01:13 2007] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec2)
[Sun Apr 01 11:01:13 2007] [notice] mod_python: Creating 20 session mutexes based on 20 max processes and 0 max threads.
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sun Apr 01 11:01:13 2007] [notice] Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-19 mod_ssl/2.0.54 OpenSSL/0.9.7e mod_perl/1.999.21 Perl/v5.8.4 configured -- resuming normal operations
[Sun Apr 01 11:03:37 2007] [notice] caught SIGTERM, shutting down

Does anybody have a solution to solve it?

 

[Hunne]

I'm having the exact same problem on a 1und1 Suse 9.3 dedicated server.
My log shows the same, got apache running but my plesk control panel is inaccesible.
Please help us swsoft staff!

 

[tglawe]

The server provider's support found the mistake:

Watchdog checked the Apache on a wrong IP.

First solution to prevent: deactivate Watchdog monitoring for the Apache deamon.

This is not a durable solution, but it works.

 

[dasmo]

Has anyone had any luck coming up with a better solution than disabling watchdog? It's a bit dodgy to lose a feature so that apache doesn't crash.

 

[dasmo]

OK. Got it going.


These were the steps I took:

Make sure you have apache monitoring turned on.
tail -f /opt/psa/var/modules/watchdog/log/monit.log
disable watchdog
reenable watchdog

tail will catch something similar to this:
[EST Mar 6 18:42:05] 'apache' failed, cannot open a connection to INET[192.168.1.103:80]

Which in my case was the IP address I set the machine up on (an internal DHCP address, which really makes no sense to me. Shouldn't it just 127?)

I added this as a virtual interface to my 2nd nic (internal network anyway, who cares)

Reenabled watchdog. No issues.

I checked as many different places as I could, but am yet to find where the config for this is stored. If I find it I'll post it here.

 

[benlake]

Monit Config

The monit config file is locate here on Plesk 8.1.1 Linux:

/opt/psa/etc/modules/watchdog/monitrc

I had this issue and the monitrc file was referencing the static IP I had configured for a second interface, simple adjustment.