SSL cache messages

This topic contains error messages that might result due to caching problems and provides a solution to help you troubleshoot the problem.


The following messages are displayed due to caching problems:

  • SSL0600E: Unable to connect to session ID cache

    • Reason: The server cannot connect to the Session ID caching daemon.

    • Solution: Verify that the daemon successfully started.

  • SSL0601E: Session ID cache daemon process <process-id> exited with exit code <exit-code>; restarting

    • Reason: If the value of <exit-code> is 0, the session ID cache daemon (sidd) received the SIGTERM signal. Other exit codes are not expected. Sidd automatically restarted.

    • Solution: If the value of <exit-code> is 0 and IBM HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send SIGTERM to sidd.

  • SSL0602E: Session ID cache daemon process <process-id> exited with terminating signal <signal-number>; restarting

    • Reason: The session ID cache daemon (sidd) received a signal other than SIGTERM was received by the session ID cache daemon (sidd), which caused it to exit. Sidd automatically restarted.

    • Solution: If the value of <exit-code> is 0 and IBM HTTP Server did not stop or restart, verify that locally installed CGI scripts, scheduled operating system tasks, or other monitoring software cannot send the signal to sidd.

  • SSL0603E: Session ID cache daemon process <process-id> exited with exit code<exit-code>; not restarting; check sidd configuration or enable sidd error log with SSLCacheErrorLog

    • Reason: The session ID cache daemon (sidd) did not initialize. The following possible exit code values might be displayed:

      Value Reason
      2 Log files could not be opened. The SSLCacheTraceLog or the SSLCacheErrorLog directive is not valid.
      3 The AF_UNIX socket cannot be initialized. Use the SSLCachePortFilename directive to specify a different socket for the session ID cache daemon.
      4 Sidd cannot switch to the configured user and group. Verify the values for the user and group directives.

    • Solution: Provide a valid value for the directives and restart IBM HTTP Server.