After update ghost don't start


#1

Hi,

after update ghost-cli and after ghost to the latest versione.
Ghost don’t start when i try ‘ghost start’
I get this error:

Debug Information:
    OS: Ubuntu, v18.04
    Node Version: v8.11.4
    Ghost-CLI Version: 1.9.8
    Environment: production
    Command: 'ghost start'
Message: Could not communicate with Ghost
Suggestion: journalctl -u ghostname-com -n 50
Stack: Error: Could not communicate with Ghost
    at Server.server.close (/usr/lib/node_modules/ghost-cli/lib/utils/port-polling.js:56:20)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:106:13)
    at Server.emit (events.js:208:7)
    at emitCloseNT (net.js:1659:8)
    at _combinedTickCallback (internal/process/next_tick.js:135:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

My configuration:
Ghost-CLI version: 1.9.8
Ghost version: 2.10.1
If I try to start ghost with ‘sudo systemctl start ghostname-com’
I get
‘Failed to start ghostname-com.service: Unit ghostname-com.service not found.’

And I can’t go back with the update I get error here too.

Anyone can help?

Thanks Mik


#2

Can you please try again, and if it doesn’t work, run the suggested debug command?

The output from that should contain more details of the error.


#3
user@ghostinstall:/var/www/ghostinstall.com/html/blog$ ghost start                                                                                                                                                                     + sudo systemctl is-active ghost_miklaboratoty-com
✔ Ensuring user is not logged in as ghost user
✔ Checking if logged in user is directory owner
✔ Checking current folder permissions
+ sudo systemctl is-active ghostname-com
✔ Validating config
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking content folder ownership
✔ Checking memory availability
+ sudo systemctl start ghostname-com
+ sudo systemctl stop ghostname-com
✖ Starting Ghost
A GhostError occurred.


Message: Could not communicate with Ghost
Suggestion: journalctl -u ghostname-com -n 50

Debug Information:
    OS: Ubuntu, v18.04
    Node Version: v8.15.0
    Ghost-CLI Version: 1.9.8
    Environment: production
    Command: 'ghost start'

Additional log info available in: /home/user/.ghost/logs/ghost-cli-debug-2019-01-11T11_48_43_458Z.log

Try running ghost doctor to check your system for known issues.

You can always refer to https://docs.ghost.org/docs/troubleshooting#section-cli-errors for troubleshooting.
user@ghostinstall:/var/www/ghostinstall.com/html/blog$ sudo journalctl -u ghostname-com -n 50
-- Logs begin at Tue 2018-11-13 02:53:31 CET, end at Fri 2019-01-11 12:49:16 CET
-- No entries --

#4

Any ideas?


#5

I have the same error and have to revert back to previous version, the error message is:

Message: Cannot read property ‘engine’ of undefined

the journalctl shows:

Jan 15 11:13:12 haper node[19044]: TypeError: Cannot read property 'engine' of undefined
Jan 15 11:13:12 haper node[19044]:     at Resources._initResourceConfig (/var/www/html/blog/blog/versions/2.10.1/core/server/services/url/Resources.js:48:68)
Jan 15 11:13:12 haper node[19044]:     at Resources.fetchResources (/var/www/html/blog/blog/versions/2.10.1/core/server/services/url/Resources.js:55:14)
Jan 15 11:13:12 haper node[19044]:     at emitNone (events.js:106:13)
Jan 15 11:13:12 haper node[19044]:     at EventRegistry.emit (events.js:208:7)
Jan 15 11:13:12 haper node[19044]:     at settings.init.then.then.then (/var/www/html/blog/blog/versions/2.10.1/core/server/index.js:108:31)
Jan 15 11:13:12 haper node[19044]:     at tryCatcher (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/util.js:16:23)
Jan 15 11:13:12 haper node[19044]:     at Promise._settlePromiseFromHandler (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/promise.js:512:31)
Jan 15 11:13:12 haper node[19044]:     at Promise._settlePromise (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/promise.js:569:18)
Jan 15 11:13:12 haper node[19044]:     at Promise._settlePromise0 (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/promise.js:614:10)
Jan 15 11:13:12 haper node[19044]:     at Promise._settlePromises (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/promise.js:694:18)
Jan 15 11:13:12 haper node[19044]:     at _drainQueueStep (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/async.js:138:12)
Jan 15 11:13:12 haper node[19044]:     at _drainQueue (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/async.js:131:9)
Jan 15 11:13:12 haper node[19044]:     at Async._drainQueues (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/async.js:147:5)
Jan 15 11:13:12 haper node[19044]:     at Immediate.Async.drainQueues (/var/www/html/blog/blog/versions/2.10.1/node_modules/bluebird/js/release/async.js:17:14)
Jan 15 11:13:12 haper node[19044]:     at runCallback (timers.js:810:20)
Jan 15 11:13:12 haper node[19044]:     at tryOnImmediate (timers.js:768:5)
Jan 15 11:13:12 haper node[19044]:     at processImmediate [as _immediateCallback] (timers.js:745:5)

#6

Got the same error while installing a fresh instance.

Additional info for our use case:

  • We are not installing Nginx and MySQL because we have them external.

Reverting to 2.9.1 which is our current instance does seem to work.


#7

Update 2.11.0 creates the same error for me so no answer to the above and no solution in the latest update.

I wonder if this is related:

web@haper:/var/www/html/blog/blog$ sudo npm install -g ghost-cli@latest
npm WARN deprecated cross-spawn-async@2.2.5: cross-spawn no longer requires a build toolchain, use it instead
/usr/local/bin/ghost -> /usr/local/lib/node_modules/ghost-cli/bin/ghost
+ ghost-cli@1.9.9
updated 1 package in 4.665s 

web@haper:/var/www/html/blog/blog$ ghost -v
Ghost-CLI version: 1.9.8
Ghost version: 2.9.1 (at /var/www/html/blog/blog)

In other words ghost-cli is not updated