6.1.2 Monitor Daemon Starts itself

This topic has 3 replies, 2 voices, and was last updated 7 years, 3 months ago by Todd Horst.

Creator

Topic
September 20, 2017 at 6:59 pm #55501
Todd Horst
Participant
It used to be that if you stopped the monitor daemon it would stay down until you open up the net monitor or started it manually.

However, in 6.1.2 it appears that the monitor daemon starts itself up after about 5 seconds.

1) Can anyone confirm this is happening to them?

2) In what version was this change made?

3) How is this happening? Is there a process that is monitoring all monitor daemons?
Creator

Topic

Viewing 2 reply threads

Author

Replies
- September 25, 2017 at 5:59 pm #85566
  Todd Horst
  Participant
  It turns out that global monitor starts up a monitor daemon (Assuming its set to do so).
  
  this setting is in preferences > system
- September 25, 2017 at 7:43 pm #85567
  Robert Milfajt
  Participant
  Now that explains some things… Thank you for finding that out.
  
  Want to add that again, based on settings, global monitor will run hcidbdump -r -C to get message counts for some widget. Which may conflict randomly with your own recovery dB queries. Moreover, as this is how I found this out, if your site has a large number of messages in recovery dB due to some problem, your chance of encountering this is much greater! 😯
  
  Robert Milfajt
  Northwestern Medicine
  Chicago, IL
- September 25, 2017 at 8:49 pm #85568
  Todd Horst
  Participant
  Yes, to be fair, I had my own system in place that queried the DB more frequently and ended up causing more issues. When we went to global monitor we saw a reduction in errors.
  
  I think this highlights the need for Cloverleaf to move to a more robust default db structure.
  
  I also want to play with the execution user, which is a parameter on a lot of commands, to see if that improves the situation.
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.