Novell Home

My Favorites

Close

Please to see your favorites.

Sentinel not starting after upgrading to 7.1

This document (7012946) is provided subject to the disclaimer at the end of this document.

Environment

NetIQ Sentinel 7.1 Sentinel Server

Situation

During an upgrade of a Sentinel 7.0.x appliance to 7.1 using zypper patch the message that the database upgraded successfully plus a few more messages went by and then the update broke out to a prompt, not indicating if the update succeeded.  Upon restarting the server, Sentinel will not start properly and has become unusable.

The server0.0.log has the following Severe errors and a telling INFO error: failed to bind to server socket.

 

Wed Jul 24 01:09:43 CEST 2013|SEVERE|Container Startup Thread|com.esecurity.common.communication.Communicator.loadConfiguration
 java.lang.RuntimeException: java.lang.NullPointerException
 at com.esecurity.common.communication.Communicator.loadStrategy(Communicator.java:349)
  at com.esecurity.common.communication.Communicator.loadConfiguration(Communicator.java:601)
  at com.esecurity.common.communication.Communicator.loadConfigurationWithRetry(Communicator.java:393)
  at com.esecurity.common.communication.Communicator.initialize(Communicator.java:751)
  at com.esecurity.common.communication.Communicator.createCommunicator(Communicator.java:157)
  at com.esecurity.common.communication.Communicator.getInstance(Communicator.java:143)
  at com.esecurity.common.communication.Communicator.getInstance(Communicator.java:123)
  at com.esecurity.common.communication.Communicator.getInstance(Communicator.java:85)
  at esecurity.base.subscription.SubscriptionManager.registerWithCommunicator(SubscriptionManager.java:258)
  at esecurity.base.subscription.SubscriptionManager.subscribe(SubscriptionManager.java:172)
  at esecurity.base.subscription.SubscriptionManager.subscribe(SubscriptionManager.java:108)
  at com.esecurity.workflow.server.WorkflowServerComponent.componentActivated(WorkflowServerComponent.java:75)
  at esecurity.base.ccs.BasicComponent.activate(BasicComponent.java:241)
  at esecurity.base.ccs.proxy.ComponentElementProxy.activate(ComponentElementProxy.java:141)
  at esecurity.base.ccs.proxy.ComponentElementProxy.changeChildrenStatus(ComponentElementProxy.java:213)
  at esecurity.base.ccs.proxy.ComponentElementProxy.activate(ComponentElementProxy.java:134)
  at esecurity.base.ccs.proxy.ComponentElementProxy.componentStateChange(ComponentElementProxy.java:121)
  at esecurity.base.ccs.services.ComponentListenerSupport.fireListenerChange(ComponentListenerSupport.java:74)
  at esecurity.base.ccs.services.ComponentListenerSupport.fireListenerChange(ComponentListenerSupport.java:55)
  at esecurity.base.ccs.services.ComponentServices.activateAllComponents(ComponentServices.java:73)
  at esecurity.base.ccs.proxy.ContainerProxy.activateContainer(ContainerProxy.java:61)
  at esecurity.util.service.ContainerService$1.run(ContainerService.java:82)
  at java.lang.Thread.run(Unknown Source)
 Caused by: java.lang.NullPointerException
  at com.esecurity.common.communication.strategy.jmsstrategy.activemq.ActiveMQTopicConnection.startReconnecting(ActiveMQTopicConnection.java:150)
  at com.esecurity.common.communication.strategy.jmsstrategy.activemq.ActiveMQStrategy.initConnections(ActiveMQStrategy.java:212)
  at com.esecurity.common.communication.strategy.jmsstrategy.activemq.ActiveMQStrategy.initialize(ActiveMQStrategy.java:184)
  at com.esecurity.common.communication.Communicator.loadStrategy(Communicator.java:340)
  ... 22 more


Wed Jul 24 01:09:54 CEST 2013|SEVERE|Container Startup Thread|com.esecurity.common.communication.strategy.jmsstrategy.TopicConnection.doConnect
 Failed to connect to Broker.; Exception Could not create Transport. Reason: javax.jms.JMSException: Could not create Transport. Reason: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext; javax.jms.JMSException; ; Caused by BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext;
java.lang.IllegalStateException;


Wed Jul 24 01:09:48 CEST 2013|INFO|Container Startup Thread|esecurity.base.util.JavaLoggingLog4jAppender.append
 Failed to start Apache ActiveMQ (localhost, ID:sentibsl02.eu.jeta.aero-60566-1374620909524-0:16). Reason: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: ssl://[::]:61616?maximumConnections=12090&transport.enabledCipherSuites=SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA due to: java.net.SocketException: Protocol family unavailable

Resolution

1. open an ssh connection to the sentinel box
2. login as root
3. type yast network
4. When yast2 opens the network card should be highlighted, hit enter to go to network settings.
5. hit the tab key to select overview and arrow left to global options.
6. Enable IPv6 and save settings.
7. Reboot the server.

Cause

This is caused due to IPv6 not being enabled.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7012946
  • Creation Date:25-JUL-13
  • Modified Date:08-AUG-13
    • NetIQSentinel

Did this document solve your problem? Provide Feedback