On the JSA Event Processor, system notifications may report that the scaserver service has failed to start successfully.

Notification:

Process monitor: Application has failed to start up multiple times.

Payload info:

May 28 10:16:00 127.0.0.1 [ProcessMonitor] com.q1labs.hostcontext.processmonitor.ProcessManager: [ERROR] [NOT:0150114103][<EP_IP_Address>/- -] [-/- -]Process scaserver has failed to start for 15328 intervals. Continuing to try to start...

The following messages can be found in the /var/log/messages file.

May 28 17:38:18 HOSTNAME systemd[1]: Starting scaserver daemon...
May 28 17:38:18 HOSTNAME scaserver[50023]: [scaserver_update_settings.sh] Updating /store/dca//server.ini threads value to 51
May 28 17:38:18 HOSTNAME  scaserver[50023]: [scaserver_update_settings.sh] Updating /store/dca/dca/init/dca_license/dca_license_settings_user.txt with console address localhost
May 28 17:38:18 HOSTNAME scaserver[50023]: [scaserver_update_settings.sh] Updating /store/dca/dca/init/dca_update/dca_update_settings_user.txt with console address localhost
May 28 17:38:18 HOSTNAME scaserver[50023]: [scaserver_update_settings.sh] /store/dca/dca/init/dca_ipr/db/fdb6_00000000.fdb is NOT empty
May 28 17:38:18 HOSTNAME scaserver[50023]: [scaserver_update_settings.sh] /store/dca/dca/init/dca_urlclassification/db/fdb6_00000000.fdb is NOT empty
May 28 17:38:18 HOSTNAME scaserver[50023]: [scaserver_update_settings.sh] /store/dca/dca/init/dca_wac/db/fdb6_00000000.fdb is NOT empty
May 28 17:38:18 HOSTNAME systemd[1]: Started scaserver daemon.
May 28 17:38:18 HOSTNAME scaserver[50408]: SERVER_INI=server.ini
May 28 17:38:18 HOSTNAME scaserver[50408]: Error reading server.ini. Exiting.
May 28 17:38:18 HOSTNAME systemd[1]: scaserver.service: main process exited, code=exited, status=1/FAILURE
May 28 17:38:18 HOSTNAME systemd[1]: Unit scaserver.service entered failed state.
May 28 17:38:18 HOSTNAME systemd[1]: scaserver.service failed.

As a result, the scaserver service repeatedly attempts to start and eventually triggers a system notification indicating multiple startup failures.

The scaserver daemon may fail to start if the server.ini file is empty or improperly configured. This file is typically located at:

/store/dca/server.ini

Follow these steps to restore a valid server .ini file and restart the service.

1. SSH to the affected node and check the contents of server.init: 

cat /store/dca/server.ini

If the file is empty, corrupted or contains invalid configuration values, it is likely the cause of the issue.

3. If the file is empty or malformed, move it to a backup location:

mv /store/dca/server.ini /store/jsa_support/

4. Then, copy the server.ini from the console to the affected node This can be done using scp.

First you need to exit from the affected node and from the console, run this command:

scp /store/dca/server.ini root@affected_node_IP:/store/dca/

5. Then, ssh to the affected node again:

ssh affected_node_IP

6. and restart scaserver:

systemctl restart scaserver

The service should now be running normally, and the startup failure notifications should no longer be generated.