Hello, I suspect the init script has the wrong SELinux context. This issue seems to describe exactly what you’re seeing:
https://github.com/geerlingguy/ansible-role-solr/issues/142 However, as Dimitri already suggested, I’d recommend switching to a native systemd service for Solr instead of relying on the old init script. Kind regards Umut Saribiyik Gadsby, Eric T. via users <[email protected]> schrieb am Mo., 1. Dez. 2025, 19:49: > It’s running from system d so I assume the system is running the process > as root. If I add .sh to the end of the script and running it via sudo it > fires right up but will not reload from System d. > > *From: *Johnnie Adams <[email protected]> > *Date: *Monday, December 1, 2025 at 1:45 PM > *To: *[email protected] <[email protected]> > *Cc: *Gadsby, Eric T. <[email protected]> > *Subject: *Re: Problems with Solr starting as a service on Rocky 9.5 > > [ *CAUTION*: This email is from outside of TU. Use caution before > clicking links or opening attachments. If suspicious, report to > [email protected]. ] > Silly question--what user are you operating as? > > On Mon, Dec 1, 2025 at 12:42 PM Gadsby, Eric T. via users < > [email protected]> wrote: > > Dear Friends, > > Good afternoon. We are spinning up Solr on a Rocky 9.5 machine and can’t > get the init service to start. We get the following error: > > "× solr.service - LSB: Controls Apache Solr as a Service > Loaded: loaded (/etc/rc.d/init.d/solr; generated) > Active: failed (Result: exit-code) since Mon 2025-12-01 13:21:28 EST; > 6min ago > Docs: man:systemd-sysv-generator(8) > CPU: 2ms > Dec 01 13:21:28 aspace systemd[1]: Starting LSB: Controls Apache Solr as a > Service... > Dec 01 13:21:28 aspace solr[808]: /etc/rc.d/init.d/solr: line 75: > /usr/bin/su: Permission denied > Dec 01 13:21:28 aspace systemd[1]: solr.service: Control process exited, > code=exited, status=126/n/a > Dec 01 13:21:28 aspace systemd[1]: solr.service: Failed with result > 'exit-code'. > Dec 01 13:21:28 aspace systemd[1]: Failed to start LSB: Controls Apache > Solr as a Service.” > > We installed using the provided script and other then that hasn’t made any > changes. Any and all ideas would be appreciated. Thanks in advance! > > > > > > *[image: Towson University logo] <http://www.towson.edu/>* > > *Eric T. Gadsby* > > *Pronouns: he/him/his* > > IT Operations Specialist | Library IT, Albert S. Cook Library > > *—* > > P: 410-704-3340 > *[email protected] <[email protected]>* | > *www.towson.edu/https://libraries.towson.edu > <https://libraries.towson.edu/>* > > *—* > > Confidentiality Notice: This message may contain information that is > confidential, privileged, proprietary, or otherwise legally exempt from > disclosure. If you are not the intended recipient, you are notified that > you are not authorized to read, print, copy or disseminate this message, > any part of it, or any attachments. If this message has been sent to you in > error, please notify the sender by replying to this transmission, or by > calling Library IT, Albert S. Cook Library at 410-704-3340 . > > > > > > -- > John Adams > Senior Linux/Middleware Administrator | Information Technology Services > +1-501-916-3010 | [email protected] | http://ualr.edu/itservices > *UA Little Rock* > > Reminder: IT Services will never ask for your password over the phone or > in an email. Always be suspicious of requests for personal information that > come via email, even from known contacts. For more information or to > report suspicious email, visit IT Security > <http://ualr.edu/itservices/security/>. >
