• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Watchdog can't monitor apache server

N

nk111

Guest
Watchdog doesn't seem to be able to monitor my apache server. I alway get those messages which say "your webserver is down" and "webserver released from monitoring" even if the apache runs fine...

I'm using psa v8.6.0_build86080822.20 os_Ubuntu 6.06

I searched around in the forums but did not find a solution until now.

I guess this could be the reason:
here is a part of the file /opt/psa/etc/modules/watchdog/monitrc

Code:
# Apache
check process apache
        with pidfile "/var/run/apache2.pid"
        start = "/opt/psa/admin/bin/websrvmng --start"
        stop = "/opt/psa/admin/bin/websrvmng --stop"
        if failed host 192.168.0.181 port 80 send "GET / HTTP/1.1\r\nHost: 192.168.0.181\r\n\r\n" expect "HTTP/1\.[01x] [1-4][0-9]{2} .*\r\n" with timeout 5 seconds then restart
        if 5 restarts within 5 cycles then timeout
        every 1 cycles
        mode active

It seems like watchdog tries to monitor the apache server on an internal ip where apache is not listening.
Here is a snippet of /opt/psa/etc/modules/watchdog/monitrc.tpl :

Code:
# Apache
check process apache
        with pidfile "/var/run/apache2.pid"
        start = "<apache_start>"
        stop = "<apache_stop>"
        if failed host <default_apache_ip> port 80 send "GET / HTTP/1.1\r\nHost: <default_apache_ip>\r\n\r\n" expect "HTTP/1\.[01x] [1-4][0-9]{2} .*\r\n" with timeout <apache_connection_timeout> seconds then restart
        if <apache_timeout_restarts> restarts within <apache_timeout_cycles> cycles then timeout
        every <apache_cycles> cycles
        mode <apache_mode>

So it looks like default_apache_ip is a wrong one in my installation.

In the control panel under server / ip addresses I have 2 ip addresses listet. The external one which is assigned to my only customer and all domains and those internal one which is in the monitrc file too. This second one shows a red exclamation mark and is NOT the standard ip. But I cant delete it. When I try to delete this ip I get "access denied".

I even deleted and re-installed the watchdog module - I still have this wrong ip in the monitrc file.

Any ideas?

nico
 
YES! Solved...

I found this solution:
http://kb.swsoft.com/en/2149

to delete the old not working ip... Then I deleted the watchdog module and re-installed it. After that, the monitc file now holds the correct ip and service state is "running".

maybe this helps
 
Ever since upgrading, this also is an issue with my server. Watchdog says Apache is constantly down when it is running fine.

So this must be a bug right?
 
Back
Top