How to install marklogic on rocky linux 8 or 9?

I’ve successfully installed MarkLogic on Rocky Linux 8 within WSL, but I’m encountering an issue while attempting to start the MarkLogic server. The error message displayed is “Failed to start LSB: MarkLogic Server.” I’m seeking guidance on how to resolve this issue.

Additionally, I tried installing MarkLogic on Rocky Linux 9. During the installation process, I encountered the following errors:

ln: failed to create symbolic link ‘/etc/rc.d/rc2.d/S85MarkLogic’: No such file or directory
ln: failed to create symbolic link ‘/etc/rc.d/rc3.d/S85MarkLogic’: No such file or directory
ln: failed to create symbolic link ‘/etc/rc.d/rc4.d/S85MarkLogic’: No such file or directory
ln: failed to create symbolic link ‘/etc/rc.d/rc5.d/S85MarkLogic’: No such file or directory
ln: failed to create symbolic link ‘/etc/rc.d/rc1.d/K15MarkLogic’: No such file or directory
ln: failed to create symbolic link ‘/etc/rc.d/rc6.d/K15MarkLogic’: No such file or directory
warning: %post(MarkLogic-10.0-9.4.x86_64) scriptlet failed, exit status 1

Error in POSTIN scriptlet in rpm package MarkLogic

After completing the installation despite these errors, I noticed that the MarkLogic service is not visible when using systemctl. Attempting to start the MarkLogic service yields the error “Failed to start MarkLogic.service: Unit MarkLogic.service not found.”

I’m reaching out to the community for assistance in resolving these issues. Any guidance or insights would be greatly appreciated. Thank you in advance for your help!

  1. Check Logs: Look into the system logs to find more detailed error messages that could help identify the root cause of the failure. You can check the logs using the journalctl command:

bashCopy code

journalctl -xe
  1. Dependency Issues: Ensure that all the required dependencies for MarkLogic are installed on your Rocky Linux system. This could include Java and other required libraries.
  2. Permissions: Make sure that the user running the MarkLogic service has the necessary permissions to access the MarkLogic installation directory and other required files.
  3. Configuration: Double-check the MarkLogic configuration files to ensure that the paths and settings are correctly configured.
  4. Service Start: Instead of relying on LSB scripts, try starting the MarkLogic service using the following command:

bashCopy code

sudo systemctl start MarkLogic

If this command doesn’t work, check if there’s an actual MarkLogic.service file in the /etc/systemd/system/ directory.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.