Sentinel does not start completely while waiting on Sonic to load.

  • 7003278
  • 14-May-2009
  • 26-Apr-2012


Novell Sentinel 6.0
Novell Sentinel 6.1


After the initial install of Sentinel including the Communications Server component on a machine that does not have a Graphical User Interface (GUI) Sentinel does not ever accept connections properly.

Searching for listening sockets on TCP port 10012 shows none are listening.

The log files for several Sentinel components indicate that connections to Sonic (over port 10012) are not being accepted.

The directory where Sonic should be installed inside multiple subdirectories is instead nearly empty with only a single 'installer' directory which includes the Sonic installer.

Attempting to install Sonic manually does not complete properly.


The SonicMQ installer fails when there is no graphical environment on the machine where it is installing.  This is a bug in the way the third-party installer uses Java.  There is currently no way to perform the installation using the shipping or an updated version of Java without corrupting the Sonic installation.

Contact Novell Technical Support (NTS) to get access to a"headless" installation of Sonic.  A Service Request for this purpose will be refunded once access to the installer is provided if the problem was resolved by the separate installer.


Reported to Engineering