Monday, July 26, 2010
fmadm: logadm: Failed To Rotate Errlog
logadm: Warning: command failed: /bin/sh -c /usr/sbin/fmadm -q rotate errlog && mv /var/fm/fmd/errlog.0- /var/fm/fmd/errlog.0
fmadm: failed to rotate errlog: log file is too busy to rotate (try again later)
fmadm: failed to rotate errlog: log file is too busy to rotate (try again later)
As you can see, fmadm is actually being used to rotate the log "live" (while still in use), but as the error suggests the /var/fm/fmd/ errlog file is in use.
In fact, if this has been going on for more than a few days, you may notice that the file is growing considerably fast (a few bytes per second).
In fact, if this has been going on for more than a few days, you may notice that the file is growing considerably fast (a few bytes per second).
I propose changing the /etc/logadm.conf entry to something along the lines of:
/var/fm/fmd/errlog -M '/usr/sbin/svcadm disable fmd && sleep 15 && mv $file $nfile && /usr/sbin/svcadm enable fmd' -N -P 'Thu Mar 27 10:10:00 2008' -s 10m
Labels:
Logs,
Solaris Fault Managment
No comments:
Post a Comment