question-mark
Stuck on an issue?

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.

Unable to Update Ghost to v0.8.0 on production server

See original GitHub issue

Hello, I have a live blog and I’m unable to update my ghost blog as per the docs.

I tried several combinations of following :

  1. deleting entire core, node_modules and index.js file and replacing it with new ones
  2. using npm cache clean
  3. changing and updating to root level and using the commands as a root user.
  4. changing node version.

But none of them work.

While using 0.12.0, I get following error while installing node

> npm install semver && node -e "require('./core/server/utils/startup-check.js').nodeVersion()"

semver@5.1.0 node_modules/semver

> jsonpath@0.2.2 postinstall /var/www/ghost/node_modules/jsonpath
> node lib/aesprim.js > generated/aesprim-browser.js

Killed

What does Killed mean?

This is what is shown when I type npm start --production

>ghost@0.8.0 start /var/www/ghost
> node index

module.js:338
    throw err;
          ^
Error: Cannot find module 'xmlbuilder'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/var/www/ghost/node_modules/nodemailer/node_modules/aws-sdk/lib/xml/builder.js:2:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/var/www/ghost/node_modules/nodemailer/node_modules/aws-sdk/lib/core.js:42:14)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)

npm ERR! Linux 3.13.0-57-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--production"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! ghost@0.8.0 start: `node index`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the ghost@0.8.0 start script 'node index'.
npm ERR! This is most likely a problem with the ghost package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node index
npm ERR! You can get their info via:
npm ERR!     npm owner ls ghost
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /var/www/ghost/npm-debug.log

And these are contents of /var/www/ghost/npm-debug.log


0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'start',
1 verbose cli   '--production' ]
2 info using npm@1.2.14
3 info using node@v0.10.0
4 verbose read json /var/www/package.json
5 error Error: ENOENT, open '/var/www/package.json'
6 error If you need help, you may report this log at:
6 error     <http://github.com/isaacs/npm/issues>
6 error or email it to:
6 error     <npm-@googlegroups.com>
7 error System Linux 3.13.0-57-generic
8 error command "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--production"
9 error cwd /var/www
10 error node -v v0.10.0
11 error npm -v 1.2.14
12 error path /var/www/package.json
13 error code ENOENT
14 error errno 34
15 verbose exit [ 34, true ]

Update: I get the same issue while installing 0.9.0-beta.2

> ghost@0.9.0-beta.2 preinstall /var/www/ghost
> npm install semver && node -e "require('./core/server/utils/startup-check.js').nodeVersion()"

semver@5.1.0 node_modules/semver
Killed

Thanks

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:15

github_iconTop GitHub Comments

1reaction
prashantsanicommented, Jul 22, 2016

@kevinSuttle try contacting them over slack

https://ghost.org/slack/

And if you find a solution, then add here.

0reactions
prashantsanicommented, Sep 23, 2016

Had A similar issue while reinstalling Ghost on the server. Realised that config.js was corrupt. A simple js lint on config.js would show the error.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Ghost update 3.42.6 -> 4.17.0 failed with "Cannot remove ...
Issue Summary An update of ghost 3.42.6 to 4.17.0 failed with the following error: Cannot remove permission(Add offers) with ...
Read more >
How to update to the latest major version - Ghost
The most common reason for an update failure is running out of memory, so make sure you have enough RAM or swap configured...
Read more >
Package List — Spack 0.20.0.dev0 documentation
Versions: develop, 0.8.0, 0.7.1, 0.7.0, 0.6.0; Build Dependencies: cuda, cmake, ... A package universe and a request to install, remove, or upgrade packages ......
Read more >
npm install errors with Error: ENOENT, chmod - Stack Overflow
When it completed I had node and npm on my path and I was able to run rm -rf ~/.npm npm install -g...
Read more >
Migrate to Ghost 1.x on Azure - Code Design
After the deployment which I did with the provided template, I got Ghost v1.22, so a good opportunity to use the ghost update...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found