Hi rollout fellows
A few edg-gridftp-ls --verbose on directory /var/log of some SEs shows
that indeed gridftp-lcas_lcmaps.log and globus-gridftp.log are not
rotated, sometimes leading to single logs of several tens,
hudreeds and even dozens of megabytes. (I haven't checked quattor
config neither lcfg, this is only related to yaim)
I've added to the logrotate config the following wich seems to operate ok :
/var/log/globus-gridftp.log /var/log/gridftp-lcas_lcmaps.log {
missingok
weekly
create 0644 root root
sharedscripts
postrotate
/sbin/service globus-gridftp restart
endscript
}
-not very comments friendly- ggus ticket 2165
Cheers
David
On Thursday 14 April 2005 11:11, you wrote:
> Hello lcg-rollout,
>
> I've noticed that many log files on my only SL3/lcg-yaim server, the SE in
> classic_SE flavor are not handled by logrotate. The particular case of
> gridftp-lcas_lcmaps.log was what revealed this behaviour :
> in less than a week it growed to around 400Mb.
>
> Hence two questions :
> 1 is it possible to reduce the log level of lcas/lcmaps ? The 400Mb should
> be quite representative of a mid level SE usage by users if I believe what
> I know and what I deduce from their current grid usage and logs. And
> gridftp-lcas_lcmaps.log only contains logs of success (except voms failure
> of course). Are all these logs necessary for security audits ? Am I right
> when I suppose that a single gridftp connexion generates more than 50 lines
> in the log ?
>
>
> 2 Is there a reason why these (globus-gridftp.log, gridftp-lcas_lcmaps.log)
> could not be managed by logrotate ? Is there any pre/post command to run ?
>
> Cheers
> David
|