17.1 Daemon httpstkd Is Unable to Start

The OES Remote Manager daemon httpstkd might be unable to start if the ports it is trying to use are busy. This error is commonly shown by applications when the ports it uses (in this case NRM ports 8008 and 8009) are busy and do not respond. In this situation, you can start httpstkd without needing to reboot the server by modifying the ports used by OES Remote Manager in the /etc/opt/novell/httpstkd.conf file:

  1. Log in to the server as the root user.

  2. Open the /etc/opt/novell/httpstkd.conf file in a text editor.

  3. Change the default ports 8008 and 8009 to other unused ports on the following lines:

    addr 0.0.0.0:8008
    addr 0.0.0.0:8009 keyfile=/etc/opt/novell/httpstkd/server.key 
                      certfile=/etc/opt/novell/httpstkd/server.pem
  4. Save your changes, then close the /etc/opt/novell/httpstkd.conf file.

  5. Open a terminal console, then start the httpstkd daemon by entering:

    rcnovell-httpstkd start