Monitoring stored

stored performs a variety of important tasks such as deadlock and transaction operations of the message database, enforcing aging policies, and expunging and erasing messages stored on disk. If stored stops running, the messaging server will eventually run into problems. If stored doesn’t start when start-msg is run, no other processes will start. For more information about stored see stored in Sun Java System Messaging Server 6 2005Q4 Administration Reference.

Symptoms of stored Problems

There are no outward symptoms.

To Monitor stored

• Check that the stored process is running. stored creates and updates a pid file in msg_svr_base/config called pidfile.store. The pid file shows an init state when recovering and a ready state when ready. For example:

  231: cat pidfile.store 28250 ready

  The number on the first line is the process ID of stored.

  232: ps -eaf | grep stored inetuser 28250 1 0 Jan 05 ? 8:44 /opt/SUNWmsgsr/lib/stored -d

• Check for log file build up in msg_svr_base/store/mboxlist. Note that not every log file build up is caused by direct stored problems. Log files may also build up if imapd dies or there is a database problem.

• Check the timestamp on the following files in msg_svr_base/config:

  stored.ckp - Touched when attempt at checkpointing is made. Should get time stamped every 1 minute stored.lcu - Touched at every db log cleanup. Should get time stamped every 5 minutes stored.per - Touched at every spawn of peruser db writeout. Should get time stamped every 60 minutes

• Check for stored messages in the default log file msg_svr_base/log/default/default

• Can be monitored with watcher and msprobe. See Automatic Restart of Failed or Unresponsive Services and Monitoring Using msprobe and watcher Functions.