Problem

When trying to start Apache Solr 9.7.0 on Windows using either basic start command or cloud example, you might encounter these errors:

1. With basic start (.\solr.cmd start):

Failed to parse command-line arguments due to: Unrecognized option: --max-wait-secs
ERROR: Solr did not start or was not reachable.

2. With cloud example (.\solr.cmd start -e cloud):

Invalid command-line option: --cloud

Environment

• Apache Solr: 9.7.0
• OS: Windows 11
• Java: JDK 17
• Shell: PowerShell (as Administrator)

Problem

When trying to start Apache Solr 9.7.0 on Windows using either basic start command or cloud example, you might encounter these errors:

1. With basic start (.\solr.cmd start):

Failed to parse command-line arguments due to: Unrecognized option: --max-wait-secs
ERROR: Solr did not start or was not reachable.

2. With cloud example (.\solr.cmd start -e cloud):

Invalid command-line option: --cloud

Environment

• Apache Solr: 9.7.0
• OS: Windows 11
• Java: JDK 17
• Shell: PowerShell (as Administrator)

• solr
• startup

Share Improve this question Follow edited Nov 19, 2024 at 11:00 Olaf Kock 48.2k99 gold badges6262 silver badges9191 bronze badges asked Nov 19, 2024 at 8:51 404rorre404rorre 13722 silver badges99 bronze badges 1

• 2 And yet another solr startup bug on Windows... Are there no tests ran on Windows before release ? – Olivier Masseau Commented Nov 30, 2024 at 17:41

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 3

Root Cause

The Windows binary script (solr.cmd) contains inconsistent command switches that don't match what the parser expects. This appears to be a maintenance issue with the Windows scripts in Solr 9.7.0.

Solution

1. Navigate to your Solr installation directory
2. Create a backup of bin\solr.cmd
3. Open bin\solr.cmd in a text editor (like Notepad++ or VS Code)
4. Make these changes:
   • Find --max-wait-secs and replace with -maxWaitSecs
   • Find -cloud and replace with --cloud

Important Notes:

• Only change one occurrence of each parameter
• Don't use "Replace All" as it might affect other correct instances
• Make sure you have backup before editing

After Fix

After applying these fixes, you might see these warnings which can be safely ignored:

WARNING: URLs provided to this tool needn't include Solr's context-root (e.g. "/solr"). 
Such URLs are deprecated and support for them will be removed in a future release. 
Correcting from [http://localhost:8983/solr] to [http://localhost:8983/].

WARNING: A command line option has enabled the Security Manager
WARNING: The Security Manager is deprecated and will be removed in a future release

Verification

After applying the fixes, verify that these commands work:

.\solr.cmd start          # Basic start
.\solr.cmd start -e cloud # Cloud example
.\solr.cmd status         # Status check

Additional Notes

• These fixes are needed even when running PowerShell as Administrator
• The JVM warning about large page memory can be ignored:

  OpenJDK 64-Bit Server VM warning: JVM cannot use large page memory because it does not have enough privilege to lock pages in memory.
  

• This appears to be a Windows-specific issue and doesn't affect Linux/Unix installations

References

• Solr Control Script Reference
• Getting Started Tutorial