Many things can cause the Makeworld service to fail to start including, but not limited to:
1.) A corrupt persist file
2.) A corrupt queue file
3.) The lock not being released for the Makeworld service
1.) First start by navigating to where the persist file is located within the core-shell:
/opt/syslog-ng/var
*NOTE* If you cannot enter the core-shell please follow the instructions in the following KB article to regain access to the core-shell: How-to Enter Failing Core-Shell
2.) Rename the current persist file in the above directory which will be named syslog-ng.persist
3.) Next, navigate to the following location where the lock files may be present:
/opt/ssb/var/lock
4.) Remove the xml, xml.critical, ps_make_world, and config locks, if present, using the following command:
rm xml xml.critical ps_make_world config
5.) Reset the failed flags within the System Control daemon:
systemctl reset-failed
6.) Restart the makeworld service using the following command:
systemctl restart makeworld
7.) The Syslog-ng Store Box should now be up and running as expected. Please try accessing the WebUI.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center