Problem
When Solr fails to start (port 8983 already in use, killed by security software, bind error),
the Control Panel gives no reason — the Solr indicator just isn't green, and the user has no
idea why or where to look. On a fresh install this reads as "the app is broken."
Ask
Surface the failure in the Control Panel: e.g. "Solr failed to start on 8983 — see
logs/solr.log" (and ideally the one-line cause). Turn a silent/greyed indicator into an
actionable message pointing at the log.
Notes
On Windows the log is logs\solr.log under the install root; on *nix similarly. The Control
Panel already tracks service state — this is adding the why when a service doesn't come up.
Most impactful for locked-down institutional machines where 8983 is often blocked or taken.
Problem
When Solr fails to start (port 8983 already in use, killed by security software, bind error),
the Control Panel gives no reason — the Solr indicator just isn't green, and the user has no
idea why or where to look. On a fresh install this reads as "the app is broken."
Ask
Surface the failure in the Control Panel: e.g. "Solr failed to start on 8983 — see
logs/solr.log" (and ideally the one-line cause). Turn a silent/greyed indicator into an
actionable message pointing at the log.
Notes
On Windows the log is
logs\solr.logunder the install root; on *nix similarly. The ControlPanel already tracks service state — this is adding the why when a service doesn't come up.
Most impactful for locked-down institutional machines where 8983 is often blocked or taken.