Thanks for checking it out! The patch does work for my repeat, but I still think it's a regression in robustness compared to using a URL as it relies on PID files. Also it doesn't work if running with a non-loopback bind: set SOLR_HOST_BIND=10.0.x.x set SOLR_HOST_ADVERTISE=myhost.example.com solr-10.0.0-slim\bin\solr.cmd start --user-managed -p 8981 Waiting up to 180 seconds to see Solr running on port 8981 ERROR: Solr at http://localhost:8981/solr did not come online within 180 seconds! ERROR: Solr did not start or was not reachable. Check the logs for errors. Note: It also shows a warning about using deprecated “host” instead of “solr.host.advertise”, probably a midflight collision between https://issues.apache.org/jira/browse/SOLR-15442 and https://issues.apache.org/jira/browse/SOLR-17864 where the latter should have used “solr.host.advertise” in EnvToSyspropMappings.properties (as “host” was deprecated 8 days before in DeprecatedSystemPropertyMappings.properties). This worked before: set SOLR_HOST=myhost.example.com set SOLR_JETTY_HOST=10.0.x.x solr-9.10.1-slim\bin\solr.cmd start -p 8981 Waiting up to 180 seconds to see Solr running on port 8981 Started Solr server on port 8981. Happy searching! It correctly passes --solr-url http://myhost.example.com:8981 to the status tool. I have requested Jira access in the self-serve portal to be able to file tickets. Yours, Mikael
On Wed, Aug 5, 2026, at 01:28, Jan Høydahl wrote: > Michael, > > Would you be able to test this patched solr.cmd script > <https://raw.githubusercontent.com/janhoy/solr/375b5be8fb3c2e796f79826d89985fda3614585a/solr/bin/solr.cmd> > found in a WIP PR <https://github.com/apache/solr/pull/4710>.? > I don't posess a Windows system so I'm not able to easily test myself. > > Jan > >> 5. aug. 2026 kl. 01:15 skrev Jan Høydahl <[email protected]>: >> >> Hi >> >> Thanks for reporring. This definitely looks like a bug, would you be able to >> open a JIRA issue for tracking it? >> >> Jan >> >>> 4. aug. 2026 kl. 16:36 skrev Mikael Sterner <[email protected]>: >>> >>> Hi! >>> >>> When using the Solr Control Script to start Solr 10.0.0 on Windows in User >>> Managed mode, it checks the status of all currently running Solr instances: >>> >>> solr-10.0.0-slim\bin\solr.cmd start --user-managed -p 8981 >>> Waiting up to 180 seconds to see Solr running on port 8981 >>> Started Solr server on port 8981. Happy searching! >>> >>> solr-10.0.0-slim\bin\solr.cmd start --user-managed -p 8982 >>> Waiting up to 180 seconds to see Solr running on port 8981 >>> Started Solr server on port 8981. Happy searching! >>> Waiting up to 180 seconds to see Solr running on port 8982 >>> Started Solr server on port 8982. Happy searching! >>> >>> >>> In Solr 9.10.1 it only waits for the specified Solr instance: >>> >>> solr-9.10.1-slim\bin\solr.cmd start -p 8981 >>> Waiting up to 180 seconds to see Solr running on port 8981 >>> Started Solr server on port 8981. Happy searching! >>> >>> solr-9.10.1-slim\bin\solr.cmd start -p 8982 >>> Waiting up to 180 seconds to see Solr running on port 8982 >>> Started Solr server on port 8982. Happy searching! >>> >>> >>> If this behavior is not intentional, it seems like a regression from >>> https://issues.apache.org/jira/browse/SOLR-17685, where the “simplified” >>> solr.cmd script no longer passes in --solr-url to the status tool: >>> https://github.com/apache/solr/pull/3223/changes#diff-118de7ae5d9fc032e479321cb4d3ee62ceb68e9f3c845292b44c5e14c0f769cfL1178 >>> (This makes it fall back to waiting for all Solr instances found in the >>> PID directory.) >>> >>> Yours, >>> Mikael Sterner
