Ghost-CLI: Ghost process exited with code: 0

This issue is a

Bug Report
Feature Request

Summary

Debug Information:
    Node Version: v6.11.2
    Ghost-CLI Version: 1.1.2
    Environment: production
    Command: 'ghost start'
Message: Ghost process exited with code: 0
Stack: Error: Ghost process exited with code: 0
    at ChildProcess.cp.on (/usr/local/lib/node_modules/ghost-cli/lib/utils/local-process.js:47:24)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)

Ghost won’t start - just emits this unhelpful error message!

Steps to Reproduce (for a bug report)

Not sure. Usually happens after an upgrade and reboot on the server. NPM packages are rebuilt at the same time but this doesn’t always fix it.

Technical details (will be automatically output by Ghost-CLI if an error occurs):

OS: Ubuntu 16.04
Node Version: 6.11.2
Ghost-CLI Version: 1.1.2
Environment:
Command: sudo -u ghost -H ghost start

Kate Note: Error message should be improved first. Try to improve other error messages as well.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 5
Comments: 18 (4 by maintainers)

Commits related to this issue

fix(local-process): error if content folder owned by other user closes #501 - if the content folder is owned by a separate user, the local process manager will fail - improve local process manager er... — committed to acburdine/Ghost-CLI by acburdine 6 years ago
fix(local-process): error if content folder owned by other user closes #501 - if the content folder is owned by a separate user, the local process manager will fail - improve local process manager er... — committed to acburdine/Ghost-CLI by acburdine 6 years ago
fix(local-process): error if content folder owned by other user closes #501 - if the content folder is owned by a separate user, the local process manager will fail - improve local process manager er... — committed to acburdine/Ghost-CLI by acburdine 6 years ago
fix(local-process): error if content folder owned by other user closes #501 - if the content folder is owned by a separate user, the local process manager will fail - improve local process manager er... — committed to TryGhost/Ghost-CLI by acburdine 6 years ago

Most upvoted comments

@newey01c that appears to be accurate. I had the same issue; cd current && npm rebuild fixed it.

+11

whitfin on Nov 9, 2017

I ran into this today and it was due to my current/ symlink being broken. Running ghost update --force fixed the broken link.

shriker on Jan 4, 2019

This is still an issue when the folder name is changed after initialising

chansecampbell on Nov 13, 2019

I encountered this problem today when I attempted to upgrade Ghost from 2.6.x to 2.8.0 before upgrading Ghost CLI. After trying a few different things, running ghost update --force appears to have solved it.

Worth noting: When I ran ghost update --force the last step said “Restarting Ghost” even though the instance didn’t appear to be running. Might be related.

Debug Info

OS: Microsoft Windows, v10.0.17763
Node Version: v10.14.2
Ghost-CLI Version: 1.9.8
Environment: development
Command: ghost start

pfist on Dec 13, 2018

I have similar issue with the same error message. In my case, when I rename folder name other than “ghost”. When I rename it back to “ghost”, everything goes back to normal.

OS: Mac OS 10.14.1
Node Version: 8.12.0
Ghost-CLI Version: 1.9.8
Environment: Development
Command: ghost start

restuarifp on Dec 7, 2018

@newey01c @togume would both of you be able to try running ghost run (@togume add the --development flag because you’re running it locally) and see if anything is output?

If this happens again too you might try running ghost log just to see if there are any error messages.

I’ll try to add some additional logic in here to output exactly why ghost stopped - although if there is no logging output there’s not much that I can do unfortunately.

acburdine on Oct 18, 2017