janhoy commented on PR #1223:
URL: https://github.com/apache/solr/pull/1223#issuecomment-1349704824

   I reproduced this locally in Docker:
   
   ```bash
   docker run --rm -ti apache/solr-nightly:10.0.0-SNAPSHOT bash
   Unable to find image 'apache/solr-nightly:10.0.0-SNAPSHOT' locally
   10.0.0-SNAPSHOT: Pulling from apache/solr-nightly
   Digest: 
sha256:df810e8fc7b81238f1339a9267ab3e0689a9295cb031776e8a8c9c5ba68dbdd3
   Status: Downloaded newer image for apache/solr-nightly:10.0.0-SNAPSHOT
   WARNING: The requested image's platform (linux/amd64) does not match the 
detected host platform (linux/arm64/v8) and no specific platform was requested
   solr@00c425e5b1ca:/opt/solr-10.0.0-SNAPSHOT$ solr start -p 7000
   Java 17 detected. Enabled workaround for SOLR-16463
   Waiting up to 180 seconds to see Solr running on port 7000 [-]  
   Started Solr server on port 7000 (pid=127). Happy searching!
   
   solr@00c425e5b1ca:/opt/solr-10.0.0-SNAPSHOT$ solr stop -V -p 7000
   Using Solr root directory: /opt/solr
   Using Java: /opt/java/openjdk/bin/java
   openjdk version "17.0.5" 2022-10-18
   OpenJDK Runtime Environment Temurin-17.0.5+8 (build 17.0.5+8)
   OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (build 17.0.5+8, mixed mode, 
sharing)
   Sending stop command to Solr running on port 7000 ... waiting up to 180 
seconds to allow Jetty process 127 to stop gracefully.
   Solr process 127 is still running; jattach threaddumping it now.
   Could not start attach mechanism: No such file or directory
   Solr process 127 is still running; forcefully killing it now.
   Killed process 127
   solr@00c425e5b1ca:/opt/solr-10.0.0-SNAPSHOT$ 
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to