Restarting the runacct Command

Prerequisites

1. You must have the accounting system installed.
2. You must have root user or adm group authority.

   Note: The runacct command can fail for a variety of reasons, most commonly because the system goes down, the /usr file system runs out of space, or the /var/adm/wtmp file has records with inconsistent date stamps.

Procedure

If the runacct command is unsuccessful, do the following:

1. Check the /var/adm/acct/nite/active mmdd file for error messages.
2. If both the active file and lock files exist in acct/nite, check the accterr file, where error messages are redirected when the cron daemon calls the runacct command.
3. Perform any actions needed to eliminate errors.
4. Restart the runacct command.
5. To restart the runacct command for a specific date, enter the following:

   nohup runacct 0601 2>> \
   /var/adm/acct/nite/accterr &

   This restarts the runacct program for June 1 (0601). The runacct program reads the /var/adm/acct/nite/statefile file to find out with which state to begin. All standard error output is appended to the /var/adm/acct/nite/accterr file.
6. To restart the runacct program at a specified state, for example, the MERGE state, enter the following:

   nohup runacct 0601 MERGE 2>> \
   /var/adm/acct/nite/accterr &