Hi, after a year I’m back trying to update my blog (
ghost update --v2.28.0) , and I’m kind of stuck now, I installed the latest cli (
sudo npm i -g ghost-cli@latest) and I currently have version 8.9.0 of node using nvm, the update goes fine however when it tries to start the app it keeps looping after it hits an error:
(I also tried with v10.16.2 of node and have the same problem )
I already call the doctor and he couldn’t find anything. The journalctl only says:
ghost_arturofm-com.service: Main process exited, code=exited, status=203/EXEC
Aug 14 23:15:17 ip-172-31-90-86 systemd: ghost_arturofm-com.service: Unit entered failed state.
Aug 14 23:15:17 ip-172-31-90-86 systemd: ghost_arturofm-com.service: Failed with result 'exit-code'.
I found this log:
Systemd process manager has not been set up or is corrupted.
Any idea how to fix it?
I did ghost setup again, to double check the config and that was it, so now it updated it witht the node v10.16.2, now the funny thing is that it deleted all my web content lol
Ok so it doesn’t delete my content… it simply overrides my custom files such as the home page… oh lord… can someone please tell me if it’s necessary to upgrade from 2.5 to 2.28? Is it a major difference?
I’m going back to 2.5, I don’t have time for this… guys this updates are a pain honestly… look at the admin console:
I did this: ghost update --v2.7.1 and it updated it to the latest version instead of that one, looking around I found that the actual command is ``ghost update 2.7.1` anyway… the result is that it updated correctly somehow without any unexpected behaviors… I used v10.16.2 of node
Hi @afern247, sorry to see you’re having trouble. Have you followed the upgrading steps shown here?
If you’re changing Node versions via nvm, that may or may not impact Ghost depending on how you’ve got it setup - so that’s something to watch for.
As for the upgrade, of course upgrading straight from 2.5 to 2.28 should work, but there’s also over 1000 commits and almost 70 versions between those two… and that makes it very hard to keep these big-jump upgrades working.
You definitely don’t need to do the upgrades 1 by 1, but maybe try 2.10, 2.15 etc.
lol that guide has literally no use, it’s only 3 commands, I already went over that if you notice on the post, but thanks. I’ll just wait for a major upgrade 3.0
That sounds reasonable, let me try
Just trying to be helpful @afern247! But pleased that @Hannah was able to give you further assistance
I know, sorry if that sounded bad, I appreciate the help, actually I didn’t know about the rollback command, so I was literally using snapshots of my instance. Thank you
EDIT: This is so weird… I did this:
ghost update --v2.7.1 and it updated it to the latest version instead of that one, looking around I found that the actual command is ``ghost update 2.7.1` anyway… the result is that it updated correctly somehow without any unexpected behaviors… I’m glad I gave it a second try today. Thanks guys
Woop! Sorry you had problems but pleased you’re all up to date now .
PS. Thanks for the “Edit” messages on posts, anyone who stumbles upon them later might benefit from the updated info. However they don’t seem to set off notifications when you edit them, so if you’re looking for a response you might want to make a new reply
That’s fine, I did the edits with the intent of passing on the troubleshooting knowledge