Troubleshooting
Problem
In some scenarios, the scaserver daemon might fail to start, causing the service to enter a failed state. The following error messages are observed in the system logs:
systemd[1]: Starting scaserver daemon...
scaserver[274027]: [scaserver_update_settings.sh] Updating /store/dca//server.ini threads value to 45
scaserver[274027]: [scaserver_update_settings.sh] Updating /store/dca/dca/init/dca_license/dca_license_settings_user.txt with console address localhost
scaserver[274027]: [scaserver_update_settings.sh] Updating /store/dca/dca/init/dca_update/dca_update_settings_user.txt with console address localhost
systemd[1]: Started scaserver daemon.
scaserver[274550]: SERVER_INI=server.ini
scaserver[274550]: Error reading server.ini. Exiting.
systemd[1]: scaserver.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit scaserver.service entered failed state.
systemd[1]: scaserver.service failed.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtdAAA","label":"Upgrade"}],"ARM Case Number":"TS019191333","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.0;7.1.0;7.2.0;7.2.2;7.2.3;7.2.4;7.2.5;7.2.6;7.2.7;7.2.8;7.3.0;7.3.1;7.3.2;7.3.3;7.4.0;7.4.1;7.4.2;7.4.3;7.5.0"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
10 June 2025
UID
ibm17234599