How to monitor the additional Plesk PHP-FPM services in Watchdog?

Follow

Comments

3 comments

  • Avatar
    b_p

    Marc Vidal Honestly, this is a joke. Multiple PHP versions is a core feature of Plesk and as you already outline in this article, the problem can easily be fixed by Plesk. Is it really too much to expect, that other modules such as watchdog are properly updated when new features are introduced? Ridiculous that we should file a feature request. This is a sloppy implementation that needs to be fixed!

     

    0
    Comment actions Permalink
  • Avatar
    Torsten Homberger (Edited )

    At least there is this easy workaround. Works like a charm! 👌

    0
    Comment actions Permalink
  • Avatar
    b_p

    Marc Vidal so what are the differences between the start and stop commands given in the config file and that need to be entered in the database?

    As /opt/psa/etc/modules/watchdog/monitrc contains the line

    INCLUDE "/opt/psa/etc/modules/watchdog/services.d/*"

    and as the template file gets copied into that location, I would assume that the start and stop commands for the database are not required? Or could they be used to replace parts in the template file? If so, how?

    Also: As this is interesting to monitor additional services, it would really help (and solve vulnerabilities) if the outdated monit version 4.6 (from 2005!!) gets replace with a more recent one (e.g. 5.27). For instance, many new services in Ubuntu do not work with PID files any more (so you would need to check with 'check program <name> with path "/bin/systemctl  --quiet is active servicename.service"' instead of "check process <name> with pidfile <filename>"). However, it seems that version 4.6 does not allow this.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request