Video Screencast Help

Legacy daemons with dynamic logging levels

Created: 24 Sep 2012 | 2 comments
John_Nardello's picture
2 Agree
0 Disagree
+2 2 Votes
Login to vote

I'd like to not have to cycle daemons/services ever again in order to enable higher (or lower) verbosity logging. It's bad enough doing this on a Media Server but having to take down the entire Master just to capture logs has a huge impact on our customer SLAs. The legacy daemons should be smart enough by this point to be sent the equivalent of a HUP and modify their log level accordingly.

Comments 2 CommentsJump to latest comment

Dyneshia's picture

The only log you are required to restart services is bprd.  For the rest, you can run the following instead of restarting services.

bin/admincmd/bprdreq -rereadconfig

Login to vote
John_Nardello's picture

If that was the only one that had to get cycled, I'd just run "bprdreq -terminate" and then restart it. =) But it seems like every time I call in with an issue Support tells me I need to cycle daemons to enable a more verbose log.

So either it's still an issue, or their script is in need of an update. Thoughts on which ?

- "Your backups are only as good as your restores."

Login to vote