Jetty server not listening on 443 for Satellite Authentication on Windows

  • 7008087
  • 08-Mar-2011
  • 01-Oct-2013

Environment

Novell ZENworks 10 Configuration Management
Novell ZENworks 11 Configuration Management

Situation

After promoting an authentication satellite on Windows, the satellite role in Z-Icon property page shows active but it is not authenticating users and running netstat -na does not show listening on port 443 (or other ZENworks port).
 
zmd-messages.log does not show exception or errors for [AuthSatelliteModule] tags.  What other troubleshooting steps can be used.

Resolution

Troubleshooting:
 
  1. Run zac asr -t all .
  2. Try removing the authentication role, refresh the satellite and re-add the authentication role.
  3. Check whether you can hit the service at https://server:443/CasaAuthTokenSvc/tmp.
  4. Check whether you can hit the service at http://server/zenworks-ping
  5. Confirm that no other web server (for example IIS) is listening on the port.  If it is, the ZENworks port can be changed in the satellite configuration in ZCC.
  6. Check for presence of correct ZENWORKS_HOME\conf\jetty.properties file.
  7. Check for logs in  ZENWORKS_HOME\java\lib\core\configuration directory.   If jetty server can't start properly it will log here.
  8. Compare file structure of ZENWORKS_HOME\java\lib\core\configuration  to a known good working satellite.  Note especially whether the config.ini file exists.  If not, it can be copied from a known good satellite.  This is the error in the jetty log if the config.ini file is missing:

    !ENTRY org.eclipse.osgi 4 0 2013-09-30 21:51:06.802
    !MESSAGE Application error
    !STACK 1
    java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.main(EclipseStarter.java:150)
    at com.novell.zenworks.agent.jettyservice.JettyService.start(JettyService.java:58)
    at com.novell.zenworks.agent.jettyservice.JettyService.serviceStart(JettyService.java:33)

  9. If port 1234 is open, run:
    telnet localhost 1234
    to confirm whether the OSGI service is running.
    type:
    ss
    to list the active modules.  Compare with a known good server.