When installing a StreamBase 10 node, the 'epadmin install node' command fails reporting this console output:

status (node install): Monitor.MonitorUser - TRACE: epadmin.exe install node nodedirectory=C:\Users\MonitorUser\Documents\release10.2\.nodes nodename=Monitor.MonitorUser buildtype=PRODUCTION 
status (node install): Monitor.MonitorUser -     Installing node
status (node install): Monitor.MonitorUser -            PRODUCTION executables
status (node install): Monitor.MonitorUser -            File shared memory
status (node install): Monitor.MonitorUser -            7 concurrent allocation segments
status (node install): Monitor.MonitorUser -            Host name FZ234HQN
status (node install): Monitor.MonitorUser -            Container tibco/sb
status (node install): Monitor.MonitorUser -            Starting container services
status (node install): Monitor.MonitorUser -     Creating node snapshot after installation failure
status (node install): Monitor.MonitorUser -     Created snapshot archive C:\Users\MonitorUser\Documents\release10.2\.nodes\Monitor.MonitorUser\..\snapshots\Monitor.MonitorUser\Monitor.MonitorUser.2018-08-17-11-27-41.zip
error (node install):  - Unable to the retrieve start-up status from the node: Node cannot perform requested command. Reason: switch notifier not available: not found out after 120 seconds.
failed (node install): returnCode = -1

Found in the node's logs/bootstrap/System_administration.log file, the underlying errors are:

1) 2018-08-17 14:42:25.636000|KVM|WARN |14428|ktvmmgr.cpp(1284)|Bootstrap logging initialization failed: Begin Java Stack Trace:
java.lang.NoClassDefFoundError: ch/qos/logback/core/Context
Caused by: java.lang.ClassNotFoundException: ch.qos.logback.core.Context

2) 2018-08-17 14:42:26.698000|KVM|WARN |14428|exceptions.cpp(305)|Component service loading failed
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory

 

This error is seen when the SLF4J logging libraries have been removed or hidden (by renaming their parent directory path) from the StreamBase Server install, so they cannot be found by the runtime. Restoring the original directory name and rebuilding the application archive for deployment resolves this issue.

The classes referenced in the above errors are specifically found in the libraries:

ch.qos.logback.core.Context
./3rdparty/generic/logback/1.1.7/logback-core-1.1.7.jar: ch/qos/logback/core/Context.class
./distrib/kabira/java/deploy.jar: ch/qos/logback/core/Context.class
./distrib/tibco/dtm/java/bootstrap/com.tibco.ep.dtm.nodeinstall-uber.jar: ch/qos/logback/core/Context.class
./lib/sb-java-tools.jar: ch/qos/logback/core/Context.class

org.slf4j.LoggerFactory
./3rdparty/generic/slf4j-api/1.7.21/slf4j-api-1.7.21.jar: org/slf4j/LoggerFactory.class
./distrib/kabira/java/deploy.jar: org/slf4j/LoggerFactory.class
./distrib/tibco/dtm/java/bootstrap/com.tibco.ep.dtm.nodeinstall-uber.jar: org/slf4j/LoggerFactory.class
./distrib/tibco/sb/java/3rdparty/slf4j-api-1.7.21.jar: org/slf4j/LoggerFactory.class
./lib/sb-java-tools.jar: org/slf4j/LoggerFactory.class

These libraries need to be restored to their normal locations in the server install.

 

Error when logging classes removed from the software install