The after_install script fails when trying to boot solr (sudo -u solr /opt/solr-7.1.0/bin/solr restart -p 8983). Here's how I approached this:
on the server, ran ./solr restart -p 8986 - this raises an error:
Port 8983 is already being used by another process (pid: 22362)
Please choose a different port using the -p option.
changed the port for nyc-councilmatic to 8986 (since I cannot decipher what's using port 8983), and ran ./solr restart -p 8986 - this raises several errors having to do with log permissions, the main one being:
`ERROR: Logs directory /opt/solr-7.1.0/server/logs is not writable. Exiting
the logs are, in fact, readable and writable, so I went ahead and removed those logs
I then ran: sudo -u solr /opt/solr-7.1.0/bin/solr restart -p 8986 - this does not raise an error, but rather:
Waiting up to 180 seconds to see Solr running on port 8986 [|] Still not seeing Solr listening on 8986 after 180 seconds!
I'd like to get this sorted out on the staging site, before we do work for the NYC production site. It would be useful to pair on this with @hancush or @evz.
The
after_installscript fails when trying to boot solr (sudo -u solr /opt/solr-7.1.0/bin/solr restart -p 8983). Here's how I approached this:./solr restart -p 8986- this raises an error:nyc-councilmaticto 8986 (since I cannot decipher what's using port 8983), and ran./solr restart -p 8986- this raises several errors having to do with log permissions, the main one being:sudo -u solr /opt/solr-7.1.0/bin/solr restart -p 8986- this does not raise an error, but rather:One StackOverflow article suggests that this could have something to do with RAM or needing to update Java.
I'd like to get this sorted out on the staging site, before we do work for the NYC production site. It would be useful to pair on this with @hancush or @evz.