SAP Hybris commerce indexing

[dnguyen_31]

Hello Gurus,

I am getting the following errors in SAP Hybris Commerce suite while indexing product.

Indexing finished successfully07.08.2018 14:37:41: ERROR: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: https://10.100.1.132:8983/solr 07.08.2018 14:37:41: ERROR: Executing indexer worker as an admin user failed:

Your help is greatly appreciate it, David

[dnguyen_31]

Additional Error when starting the solr server on port 8983

E:\Hybris66\hybris\bin\ext-commerce\solrserver\resources\solr\bin>solr start -p 8983

ERROR: Process 416 is already listening on port 8983. If this is Solr, please st op it first before starting (or use restart). If this is not Solr, then please c hoose a different port using -p PORT

E:\Hybris66\hybris\bin\ext-commerce\solrserver\resources\solr\bin>

[dnguyen_31]

Thank you Saurabh, I am not able to accessed the https://10.100.1.132:8983/solr or localhost:8983. It looks like the tomcat server is occupying the 8983 port. Th Error below:

Found Solr process 416 running on port 8983

ERROR: Failed to get system information from http://localhost:8983/solr due to: org.apache.http.client.ClientProtocolException: Expected JSON response from serv er but received:

HTTP ERROR: 503

Problem accessing /solr/admin/info/system. Reason:

    Service Unavailable

---

Typically, this indicates a problem with the Solr server; check the Solr server logs for more information.

E:\Hybris66\hybris\bin\ext-commerce\solrserver\resources\solr\bin>

[Former Member]

Additionally, can you check if you can access the url https://10.100.1.132:8983/solr via browser. If not then your application might also not be able to connect to this url.

If you can connect to this url via browser but your application gives you this error, try to run solr on localhost and see if your application can connect.

Let me know how you go.

[Former Member]

Try to restart solr server. it may fix this issue

[dnguyen_31]

Hi Ashok, I have tried to restart the solr, but the issue still persist.

Thanks David