Troubleshooting
Fix Cordis startup failed in DSH
A Cordis startup failed message usually needs the first underlying stack frame, plugin name, and profile context before any fix is safe.
01
Find the first causal error
Read upward from the final startup message and capture the first missing module, invalid configuration, permission failure, or thrown exception.
- Keep the complete stack
- Record the active profile
- Separate warnings from the first fatal error
02
Disable one suspect at a time
Reproduce in a disposable profile and remove only the plugin implicated by the first error. Broad changes hide the cause and make rollback harder.
- Start from the smallest profile
- Restore the same dependency versions
- Re-enable plugins individually
Review sources
Sources help verify current facts. Their inclusion does not imply endorsement of this page.
Cordis startup failed questions
What is Cordis and why does Cordis startup failed appear?
Cordis is the plugin runtime DSH is built on: it loads plugins, wires their dependencies, and starts them. The message means that loading sequence aborted, not that your DSH installation is corrupt.
Which line of the error actually matters?
The first one, not the last. The closing summary line is the least informative part, while the first missing module, invalid config value, or thrown exception above it is what you fix.
How do I find which plugin broke startup?
Start from a minimal profile and re-enable plugins one at a time until it breaks. The plugin named in the first stack frame is the suspect, though a plugin can also fail because something it depends on never loaded.
Can I keep working in the original profile while debugging?
Yes, and you should reproduce in a disposable copy instead. Leaving the original untouched means you can still get work done and can compare a working profile against the broken one.
Why does Cordis startup failed happen only sometimes?
Intermittent failures usually come from network-dependent initialization, a race between plugins, or a lock left behind by a previous crash. Capture the log from a failing run specifically, because a successful run will not show the cause.