Automatically Starting and Stopping an On-premises Snaplex on Linux

Using the following procedure, Im unable to have the service stop/start [FAILED]. Suggestions?

To add the Snaplex as a Service:

  1. Login to the Linux machine as root.

  2. Create a copy of jcc.sh file as follows:

cp /opt/snaplogic/bin/jcc.sh /etc/init.d/snaplex

echo “export SL_ROOT=/opt/snaplogic” >> /etc/sysconfig/jcc

  1. Add the softlink to chkconfig management as follows:

chkconfig --add snaplex

cat /etc/system-release

CentOS Linux release 7.3.1611 (Core)

service snaplex restart

Restarting snaplex (via systemctl): Job for snaplex.service failed because the control process exited with error code. See “systemctl status snaplex.service” and “journalctl -xe” for details.
[FAILED]

service snaplex status

● snaplex.service - LSB: Starts Java Component Container
Loaded: loaded (/etc/rc.d/init.d/snaplex; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-09-18 22:41:28 UTC; 42s ago
Docs: man:systemd-sysv-generator(8)
Process: 15308 ExecStart=/etc/rc.d/init.d/snaplex start (code=exited, status=3)

Sep 18 22:41:28 dev-gplex02-azr systemd[1]: Starting LSB: Starts Java Component Container…
Sep 18 22:41:28 dev-gplex02-azr snaplex[15308]: Checking for java executable: [ OK ]
Sep 18 22:41:28 dev-gplex02-azr snaplex[15308]: [91B blob data]
Sep 18 22:41:28 dev-gplex02-azr systemd[1]: snaplex.service: control process exited, code=exited status=3
Sep 18 22:41:28 dev-gplex02-azr systemd[1]: Failed to start LSB: Starts Java Component Container.
Sep 18 22:41:28 dev-gplex02-azr systemd[1]: Unit snaplex.service entered failed state.
Sep 18 22:41:28 dev-gplex02-azr systemd[1]: snaplex.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

systemctl is-enabled snaplex

snaplex.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig snaplex --level=5
enabled

BTW, This is my first time looking for support for SnapPlex. Please direct me to a better place to ask questions like this.

The monitor process seems to failing to start due to some configuration error. /opt/snaplogic/run/log/monitor.log would be the log file to check the cause. If that file is not created, then adding an entry

set -x

as the second line in /etc/init.d/snaplex and then doing the service snaplex restart should generate additional logging information on the console.

If that does not help, you can take a tar of the /opt/snaplogic/run/log folder and email to support@snaplogic.com for further help.

Running with invalid version of bash or zip would be one possible cause. /bin/bash --version and /usr/bin/zip --version would indicate the version.