Hi Anshum Thanks for your response. Yes, we're running Solr standalone
We start Solr as a service. The startup script uses the following to start solr "/usr/local/vufind-5.0/solr/vendor/bin/solr" "$1" -force -p 8080 -s /usr/local/vufind-5.0/solr/vufind -m 4096M -a "-Ddisable.configEdit=true -Dsolr.log=/usr/local/vufind-5.0/solr/vufind/logs/jetty Regards, June -----Original Message----- From: Anshum Gupta <[email protected]> Sent: Thursday, October 13, 2022 12:50 PM To: [email protected] Subject: Re: Solr SSL Troublshooting How are you starting Solr? Seems like you're running it in standalone mode, can you please confirm? On Thu, Oct 13, 2022 at 9:44 AM Rayner, June <[email protected]> wrote: > Hi Jan > > Thanks for your response. With the SSL configured, > > we get an ERR_INVALID_HTTP_RESPONSE error when we access the solr > admin URL in a browser > > with cURL, we get the following > curl localhost:8080/solr/#/dogs/query > curl: (1) Received HTTP/0.9 when not allowed > > There are 2 lines in the solr log that mention the Solr port cat > solr.log | grep 8080 > 2022-10-13 16:32:56.616 INFO (main) [ ] o.a.s.s.SolrDispatchFilter / > __| ___| |_ _ Starting in standalone mode on port 8080 > 2022-10-13 16:32:58.339 INFO (main) [ ] o.e.j.s.AbstractConnector > Started ServerConnector@18245eb0{SSL, (ssl, alpn, h2, http/1.1)}{ > 0.0.0.0:8080} > > These are the last lines in the log itself > 2022-10-13 16:32:59.268 INFO > (searcherExecutor-17-thread-1-processing-x:biblio) [ x:biblio] > o.a.s.c.QuerySenderListener QuerySenderListener done. > 2022-10-13 16:32:59.268 INFO > (searcherExecutor-17-thread-1-processing-x:biblio) [ x:biblio] > o.a.s.h.c.SpellCheckComponent Loading spell index for spellchecker: > default > 2022-10-13 16:32:59.269 INFO > (searcherExecutor-16-thread-1-processing-x:biblio2) [ x:biblio2] > o.a.s.c.S.Request [biblio2] webapp=null path=null > params={q=science+art+business+engineering+history&facet.field=format& > distrib=false&fq=format:book&event=firstSearcher} > hits=0 status=0 QTime=98 > 2022-10-13 16:32:59.269 INFO > (searcherExecutor-16-thread-1-processing-x:biblio2) [ x:biblio2] > o.a.s.c.QuerySenderListener QuerySenderListener done. > 2022-10-13 16:32:59.271 INFO > (searcherExecutor-16-thread-1-processing-x:biblio2) [ x:biblio2] > o.a.s.h.c.SpellCheckComponent Loading spell index for spellchecker: > default > 2022-10-13 16:32:59.301 INFO > (searcherExecutor-17-thread-1-processing-x:biblio) [ x:biblio] > o.a.s.h.c.SpellCheckComponent Loading spell index for spellchecker: > basicSpell > 2022-10-13 16:32:59.304 INFO > (searcherExecutor-16-thread-1-processing-x:biblio2) [ x:biblio2] > o.a.s.h.c.SpellCheckComponent Loading spell index for spellchecker: > basicSpell > 2022-10-13 16:32:59.324 INFO > (searcherExecutor-17-thread-1-processing-x:biblio) [ x:biblio] > o.a.s.c.SolrCore [biblio] Registered new searcher autowarm time: 0 ms > 2022-10-13 16:32:59.328 INFO > (searcherExecutor-16-thread-1-processing-x:biblio2) [ x:biblio2] > o.a.s.c.SolrCore [biblio2] Registered new searcher autowarm time: 0 > ms > > Regards, > > June > > > -----Original Message----- > From: Jan Høydahl <[email protected]> > Sent: Thursday, October 13, 2022 11:36 AM > To: [email protected] > Subject: Re: Solr SSL Troublshooting > > > but we can't access the Solr Admin page. > > > What exactly does this mean? > Do you see the last line Jetty prints out in the log that it is > listening to port 8983? > What happens when you try to connect to the port, with e.g. cURL? > > Jan > > The information contained in this e-mail, and any attachment, is > confidential and is intended solely for the use of the intended recipient. > Access, copying or re-use of the e-mail or any attachment, or any > information contained therein, by any other person is not authorized. > If you are not the intended recipient please return the e-mail to the > sender and delete it from your computer. Although we attempt to sweep > e-mail and attachments for viruses, we do not guarantee that either > are virus-free and accept no liability for any damage sustained as a result > of viruses. > -- Anshum Gupta The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses.
