HP StorageWorks Scalable File Share - Manual (Page 288)

Troubleshooting 9–64
When the resynchronization is complete, the
/proc/mdstat
command indicates this, as shown in
the following example:
sfs> show log facility=storage && age < "5m"
.
.
.
2004/11/02 10:56:41 storage n south2: mds8: /proc/mdstat:
md0 : active raid1 sdc[1] sdb[0]
10485504 blocks [2/2] [UU]
.
.
.
9.36 System log files
The following log files are present on each server and may be useful:
• Configuration system:
/var/log/configd/configd.log
• Power management:
/var/log/powerd/powerd.log
This file is rotated when it reaches 8MB—the previous log is then compressed in
gzip
format and
renamed
powerd.log.bak.gz
.
The following log file is generated by the administration service and is only present on the administration
or MDS servers:
•
/var/log/hpls_admin
This file contains the start action return codes of the various services started by the administration
service. The file is truncated each time the administration service starts.
9.37 Administration service restarts every one minute (attempting to start
the evlogd daemon)
The event log daemon (
evlogd
) crashes if the
/var/hpls/evlog/eventlog
event log file on the server
running the administration service (either the administration server or MDS server) grows to more than 2GB.
When this happens, the administration service restarts every one minute, attempting to start the
evlogd
daemon.
By default, a
cron
command runs at 2 a.m. (0200 hours) every day and purges all events that are more
than 30 days old from the event log. However, this may not be enough to ensure that the event log file
remains less than 2GB.
If you find that the event log is getting large (for example, greater than 1GB), purge unnecessary events
from the log. The following are examples of how to purge some of the less useful events from the log. These
commands must be run on the server where the administration service is running:
# evlogmgr -c ’data contains "dhcpd"’
# evlogmgr -c ’data contains "duplicate events"’
# evlogmgr -c ’data contains "CROND"’
If the event log is already at 2GB, it is likely that you will not be able to purge events from the log. In this
case, rename the existing event log, as shown in the following example:
# mv /var/hpls/evlog/eventlog /var/hpls/evlog/eventlog.toobig
When you have done this, the administration service will automatically start the event logger within one
minute.