Report this

What is the reason for this report?

Ghost 0.4 Install Problems

Posted on January 15, 2014

I decided to manually install Ghost 0.4. My problem is I get these errors when I run npm install --production. I tried to proceed with the installation but now ghost will not start and my site returns 502 errors. Any idea where the problem is? :)

sqlite3@2.1.19 install /var/www/leoadhemartan.com/public_html/ghost/node_modul es/sqlite3 node build.js

[sqlite3]: Checking for http://node-sqlite3.s3.amazonaws.com/Release/node_sqlite 3-v2.1.a-node-v11-linux-x64.tar.gz [sqlite3]: Error: ENOENT, open ‘/home/tan/tmp/node-sqlite3-Release/node_sqlite3- v2.1.a-node-v11-linux-x64.tar.gz’ npm ERR! sqlite3@2.1.19 install: node build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sqlite3@2.1.19 install script. npm ERR! This is most likely a problem with the sqlite3 package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node build.js npm ERR! You can get their info via: npm ERR! npm owner ls sqlite3 npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.8.0-29-generic npm ERR! command “/usr/bin/node” “/usr/bin/npm” “install” “–production” npm ERR! cwd /var/www/leoadhemartan.com/public_html/ghost npm ERR! node -v v0.10.24 npm ERR! npm -v 1.3.21 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /var/www/leoadhemartan.com/public_html/ghost/npm-debug.log



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Seems to work for me when I rebuild the sqlite3 package from source. <br> <br>sudo npm install sqlite3 --build-from-source <br> <br>Then just run as before: <br> <br>sudo npm install --production <br>sudo npm start

Same problem and none solution above works :-(

I symlinked nodejs to node to get around the naming issue. This is also what Joyent recommends trying. <br> <br>% ln -s /usr/bin/nodejs /usr/bin/node <br> <br>Fixed my issues.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.