Clovertech

Permanently stop monitorD

› Clovertech Forums › Cloverleaf › Permanently stop monitorD

  • Creator
    Topic
  • December 20, 2024 at 12:41 pm #121698
    Jason Russell
    Participant

      I am probably missing something simple here, but I’m trying to remove a site, and I cannot get the monitorD to shut down and stay off. It keeps restarting after a period of time. I’ve checked server admin, site preferences, etc, and am obviously missing a setting. I don’t want to have to kill the process, that will be a last resort, but if that’s going to be the method, that’s what I’ll do. Just want to make sure I’m not missing something.

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • December 20, 2024 at 12:50 pm #121699
        Debbie Davis
        Participant

          I had a similar experience – we found that Global Monitor was set to always restart the monitorD.  Not sure if you have Global Monitor, but if you do you could check that.

        • December 20, 2024 at 1:19 pm #121700
          Jason Russell
          Participant

            I do have GM, that specific site was removed. What process did you follow to make sure GM wasn’t affecting it?

          • December 20, 2024 at 1:35 pm #121701
            Debbie Davis
            Participant

              Its been a few years but I believe it was in  System preferences – MonitorD Auto-Restart Feature:  Disabled

              May not apply if you have already removed the site.

            • December 20, 2024 at 2:14 pm #121702
              Tim Pancost
              Participant

                Have been bitten by this “feature” many times.  As to where it is, Debbie is correct; Preferences tab at the top, System tab at the left, its on the right side of the pane at the top.  Seems to be consistent location, at least between versions 6.1 and 21.1.  Make sure it’s disabled.  First thing I do when installing/upgrading GM, making sure it’s disabled. 🙂  Makes maintenance on the engine a real PITA when it keeps restarting the monitor daemon on you.  We’ve also encountered issues in the past with it creating “ghost” ones, where it thinks it’s down, so it spins up another instance, and so you have duplicates.

                Also, any time you make a change(i.e. to configuration and/or adding/removing a site), I would recommend bouncing the Global Monitor service.  The host server is supposed to be dynamic when it notices a change in the server.ini file, but can’t hurt to bounce that too.

                HTH,

                TIM

                 

                Tim Pancost
                Trinity Health

            • Author
              Replies
            Viewing 3 reply threads
            • You must be logged in to reply to this topic.