Existing Fault Conditions Not Displayed

If you are aware that a server is in a fault condition, but there is no indicator of this fault condition in the browser interface, you might need to restart the Solaris sysevent daemon (syseventd) on the server.

The following explanation applies only to servers with version 4, update 5, or earlier versions of the software.

The reason this might occur is that /opt might not be part of the root file system on the server. If this is the case, the Solaris sysevent daemon (syseventd) starts before /opt is available when the server is rebooted. Because /opt is unavailable to the daemon upon rebooting, the daemon cannot find some of the SUNWsamfs binaries that are required for the SAM-QFS Manager software to report recent fault conditions or to send Recovery Point Interrupted or File System Overflow notifications.

To address this issue, perform the following:

  1. After rebooting the server, log in to the server as root.

  2. Type the following at the command prompt:

    # pkill -HUP syseventd

    The Solaris sysevent daemon is restarted. The daemon can now find the required SUNWsamfs binaries.