On Fri, Oct 22, 2010 at 04:46:58PM -0400, Nate Coraor wrote:
Ry4an Brase wrote:
I set up logrotate on our production galaxy instance here, but after moving the file Galaxy (or more likely paste I imagine) doesn't re-open the log file. Is there some post-rotate action I can set in my logrotate command to let galaxy know that I pulled the logging rug out from under it? On apache this would be a SIGHUP, but some daemons use SIGUSRs of various flavors.
Unfortunately, the only way to reopen the log right now is to restart the process entirely. Galaxy does need a means to reload the config and reopen logs without restarting, but it doesn't have it right now.
Yeah reloading config is hard, but re-opening logs is easy. Perhaps I can tackle the later (certainly not the former).
How are others handling logs that grow without bounds?
I also use log rotation, although on Solaris, so with logadm.
So you have logadm restart galaxy, or just run the rotate "manually" as part of startups? -- Ry4an Brase 612-626-6575 Software Developer Application Development University of Minnesota Supercomputing Institute http://www.msi.umn.edu