27.6.1.2 To Monitor imapd, popd and httpd

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

• Can be monitored with SNMP.

  If you have the SNMP set up, this is a very good way to monitor these processes. See Appendix A, SNMP Support. The server information is in the Network Services Monitoring MIB.

• Check log files.

  Look in the directory msg-svr-base/log/service where service can be http or IMAP or POP. In that directory you will find a number of log files. One filename is the name of the service (imap, pop, http) and the others are the name of the service plus a sequence number and a date concatenated to the service name. For example:

  imap imap.29.1010221593 imap.31.1010394412 imap.33.1010567224

  The file with just the service name is the latest log. The other ones are ordered by the sequence number (here 29, 31, 33) and the one with the highest sequence number is the next newest one. (See Chapter 25, Managing Logging.”)

  If a server was shut down you might see something like this:

  imap.12.1065431243:[07/Oct/2003:01:15:43 -0700] gotmail-2 imapd[20525]: General Warning: Sun Java System Messaging Server IMAP4 6.1 (built Sep 24 2003) shutting down

• Can be checked with counterutil. See 27.8.3 counterutil and counterutil in Sun Java System Messaging Server 6.3 Administration Reference.

• Run the platform-specific command to verify that the imapd, popd and httpd processes are running. For example, in Solaris you can use the ps command and look for imapd, popd and mshttpd.

• You can set alarms for specified server performance thresholds by setting the server response configuration parameters described in 27.8.9.1 Alarm Messages

• See 27.8.1 immonitor-access.