Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fix issue with systemd "failed" state
See original GitHub issueSummary
Right now, Ghost-CLI only has 2 options when it comes to determining the status of a Ghost instance: “running” and “not running”. This has become problematic in the past, because systemd (which is used by default in production on Ubuntu) has the concept of a third state: “failed”. This state occurs whenever the Ghost instance failed to start for a certain reason (e.g. a bad configuration file). Because of this, we currently throw an error when systemd is in state: “failed”.
What I think we should do in the short term is fix the systemd process manager to output a more helpful error message (maybe auto-run journalctl to determine why it’s in a failed state?) and maybe in the future refactor that particular part of the process manager to be able to handle that 3rd state more cleanly.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kirrg001 that sounds like a perfect solution - I’ll work on testing that out this weekend
Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂