On 3/17/22 07:22, Solange Silva Ajuria wrote:
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
This would seem to indicate that the techproducts index doesn't exist.
The fact that you got a 404 means something is listening on the port.
According to the official installation documentation
/etc/default/solr.in.sh
SOLR_HOST="172.16.100.75"
The SOLR_HOST variable doesn't affect Solr's network operation. It
determines what name a SolrCloud system will use when it registers
itself in the zookeeper database.
Solr versions up through 8.x will listen on all network interfaces.
When Solr 9.0 is released, it will only listen on 127.0.0.1. You can
get the old behavior of listening on all interfaces on a 9.x version by
setting the SOLR_JETTY_HOST variable to 0.0.0.0 in solr.in.sh or
solr.in.cmd.
WARNING: Starting Solr as the root user is a security risk and not considered
best practice. Exiting.
Please consult the Reference Guide. To override this check, start
with argument '-force'
That's the relevant error from when you tried to start the cloud example.
You tried to start Solr as root. The start script detected this and
refused to start. As far as I know it won't be possible to start the
cloud example as root because a -force parameter on the main script
execution will not be transferred to the later calls that start the
individual Solr instances in the example.
Change the ownership on the extracted files and run the command as a
regular user, not root.
Thanks,
Shawn
