-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solr not reading cores from correct path, solr < 5 #56
Conversation
…s not (re)starting properly.
… is not used in systemd".
This was already fixed in #53, though...? What else is not working anymore? Also, the sleep use is intentional still—on non-systemd systems it's still needed to prevent potential restart failures. And finally—the systemd script for Solr 5+ uses the solr binary and not the init script intentionally. |
…ep as it is not used in systemd"." This reverts commit a9254d6.
@geerlingguy I created an own issue for this now, please see #57 And thanks, I re-added the sleep. |
ExecReload=/bin/kill -s HUP $MAINPID | ||
ExecStop=/bin/kill -s QUIT $MAINPID | ||
PrivateTmp=true | ||
ExecStart=/etc/init.d/solr start |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One problem is I don't think I can guarantee the sysvinit files would always be available on systemd systems. For Solr 6 (and 5, I think, too), the solr -e cloud -noprompt
is the correct way to start the service...
This was fixed in #97 |
Please see details in issue #57 and previous PR #55
For reference, got the updated service unit file value from https://techdetails.agwego.com/2013/06/07/227/
I'm not entirely sure why this works but I guess the service unit file messed up the solr configs somehow.