The .pid file referenced in the "Permission denied" message does not exist.
On Thu, Oct 15, 2020 at 11:01 AM Ryan W <rya...@gmail.com> wrote: > I have been starting solr like so... > > service solr start > > > On Thu, Oct 15, 2020 at 10:31 AM Joe Doupnik <j...@netlab1.net> wrote: > >> Alex has it right. In my environment I created user "solr" in group >> "users". Then I ensured that "solr:user" owns all of Solr's files. In >> addition, I do Solr start/stop with an /etc/init.d script (the Solr >> distribution has the basic one which we can embellish) in which there is >> control line RUNAS="solr". The RUNAS variable is used to properly start >> Solr. >> Thanks, >> Joe D. >> >> On 15/10/2020 15:02, Alexandre Rafalovitch wrote: >> > It sounds like maybe you have started the Solr in a different way than >> > you are restarting it. E.g. maybe you started it manually (bin/solr >> > start, probably as a root) but are trying to restart it via service >> > script. Who owned the .pid file? I am guessing 'root', while the >> > service script probably runs as a different (lower-permission) user. >> > >> > The practical effect of that assumption is that your environmental >> > variables were set differently and various things (e.g. logs) may not >> > be where you expect. >> > >> > The solution is to be consistent in using the service to >> > start/restart/stop your Solr. >> > >> > Regards, >> > Alex. >> > >> > On Thu, 15 Oct 2020 at 09:51, Ryan W <rya...@gmail.com> wrote: >> >> What is my permissions problem here: >> >> >> >> [root@faspbsy0002 bin]# service solr restart >> >> Sending stop command to Solr running on port 8983 ... waiting up to 180 >> >> seconds to allow Jetty process 38947 to stop gracefully. >> >> /opt/solr/bin/solr: line 2125: /opt/solr/bin/solr-8983.pid: Permission >> >> denied >> >> >> >> What is the practical effect if Solr can't write this solr-8983.pid >> file? >> >> What user should own the contents of /opt/solr/bin ? >> >> >> >> Thanks >> >>
