The runacct procedure can fail for a variety of reasons, the most common of which are /var running out of space and a corrupted wtmp file. If the activeMMDD file exists, check it first for error messages. If the active file and lock files exist, check fd2log for any mysterious messages. The following is a list of error messages produced by runacct and recommended recovery actions for each situation.
ERROR: locks found, run aborted
The files lock and lock1 were found. These files must be removed before runacct can restart. Either two processes are trying to run runacct simultaneously or the last runacct aborted abnormally without cleaning up the locks. Fheck the fd2log for messages.
ERROR: acctg already run for date: check /var/adm/acct/nite/lastdate
The date in lastdate and today's date are the same. Remove lastdate.
ERROR: turnacct switch returned rc=?
Check the integrity of turnacct and accton. The accton program must be owned by root and have the setuid bit set.
File setups have probably already run. Check the status of the files; then run setups manually, if necessary.
already exists, run setup manually
/var/adm/wtmp has already been copied to /var/adm/acct/nite/wtmp.MMDD
ERROR: wtmpfix errors see /var/adm/acct/nite/wtmperror
wtmpfix detected a corrupted wtmp file. Use fwtmp to correct the corrupted file.
ERROR: invalid state, check /var/adm/acct/nite/statefile
The file statefile is probably corrupted. Check statefile and read active before restarting.