1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Watchdog plesk apache monitoring fc7 only

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by 105547111, May 9, 2010.

  1. 105547111

    105547111 Silver Pleskian

    32
    30%
    Joined:
    Jul 13, 2006
    Messages:
    643
    Likes Received:
    2
    Hi IgorG,

    I know that FC7 is not supported by the vendor, but on plesk 9.5.2 watchdog now thinks httpd is not running.

    I restarted httpd it's the same.

    Note for developers, F11 is not effected it's running perfectly, so this is only a F7 issue so it's not at all priority.
     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,564
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Did you tried to perform checking according to section for Apache from /usr/local/psa/etc/modules/watchdog/monitrc ?
    Also do you have any useful related logs from /usr/local/psa/var/modules/watchdog/log/ ?
     
  3. 105547111

    105547111 Silver Pleskian

    32
    30%
    Joined:
    Jul 13, 2006
    Messages:
    643
    Likes Received:
    2
    Hi IgorG,

    Sorry for the delay only had time on the weekend to look at this server.

    [root@server ~]# /etc/init.d/httpd status
    httpd (pid 22858 22857 22844 22796 22780 22742 22707 22706 22695 22619 22609 22608 22607 22606 22605 22604 22603 22602 22601 22599) is running...
    [root@server ~]#

    Here is the monit.log:
    [EST May 16 10:30:24] 'plesk_apache' process PID changed to 23484
    [EST May 16 10:30:25] 'apache' failed, cannot open a connection to INET[172.16.0.1:80]
    [EST May 16 10:30:25] 'apache' trying to restart
    [EST May 16 10:30:25] 'apache' stop: /usr/local/psa/admin/bin/websrvmng
    [EST May 16 10:30:26] 'apache' start: /usr/local/psa/admin/bin/websrvmng
    [EST May 16 10:30:26] 'bind' PID has not changed


    Why the 172.16.0.1:80 that is wrong, the IP address is not on the server at all. Its got 3 IPs all public address space.


    Then check apache:

    [root@server ~]# /usr/local/psa/admin/bin/websrvmng --status
    is running
    [root@server ~]#
     
  4. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,564
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Did you checked this IP in /usr/local/psa/etc/modules/watchdog/monitrc ? Just specify correct IP there.
     
  5. 105547111

    105547111 Silver Pleskian

    32
    30%
    Joined:
    Jul 13, 2006
    Messages:
    643
    Likes Received:
    2
    I don't have the 172.16.0.1 is not on the server, I even checked the SQL database the IP is not there.

    I think it's failing as it thinks it's running on this IP which it's not.

    The correct IPs are 3 of 208.x.x.x

    Any idea what config file it's stored in that watchdog is checking against?

    Apache is obviously running and it is on the websites hosted.
     
  6. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,564
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    On my test Plesk environment I see following in file /usr/local/psa/etc/modules/watchdog/monitrc:

    As you can see there is specified IP 10.55.62.17 for port 80 checking.
    My question - do you have any IP there?
     
  7. 105547111

    105547111 Silver Pleskian

    32
    30%
    Joined:
    Jul 13, 2006
    Messages:
    643
    Likes Received:
    2
    Hi IgorG

    Thanks again for your help. No I only see one ip for the apache section and that is 208.109.x.x

    There is not a single 172.x address in the file so I can't understand where that is coming from.

    Any other files that watchdog uses for monitoring?

    Apache is definately running on port 80.

    It looks like it's picking up the old 172.x ip from the psa-VPN that's been removed.

    But that is nothing to do with port 80 anyway, and it's gone both the package and database has not got that ip.

    Should try yum remove psa-watchdog and reinstall it?
     
  8. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,564
    Likes Received:
    1,243
    Location:
    Novosibirsk, Russia
    Try remove it with
    and then install it back with autoinstaller.
     
  9. 105547111

    105547111 Silver Pleskian

    32
    30%
    Joined:
    Jul 13, 2006
    Messages:
    643
    Likes Received:
    2
    Hi IgorG,

    Removing and reinstalling watchdog fixed the issue. It must have happened onnthe 9.5.1 to 9.5.2 update as that is when it insisted apache was not monitored as it failed starting too many times.

    Weird how that IP showed up, but was not in the monitrc file at all.

    Anyhow it's fixed thanks again!
     
Loading...