# Update to 3.01 and can't \`ghost start\` **URL:** \ **Category:** Developer help\ **Created:** [October 29, 2019, 11:03pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857 "2019-10-29T23:03:40Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![brettdewoody](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/brettdewoody/32/4942_2.png) [@brettdewoody](https://forum.ghost.org/u/brettdewoody)\ **Post date:** [October 29, 2019, 11:03pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/1 "2019-10-29T23:03:40Z")
I tried to update to 3.0.1 but am having issues getting Ghost to start again, using `ghost start`, or `ghost restart`. ```auto ghost start + sudo systemctl is-active ghost_brettdewoody-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 ghost_brettdewoody-com ✔ Validating config ✔ Checking folder permissions ✔ Checking file permissions ✔ Checking content folder ownership ✔ Checking memory availability + sudo systemctl start ghost_brettdewoody-com + sudo systemctl stop ghost_brettdewoody-com ✖ Starting Ghost A GhostError occurred. Message: Could not communicate with Ghost Suggestion: journalctl -u ghost_brettdewoody-com -n 50 ``` The logs a series of these: ```auto ghost_brettdewoody-com.service: Service hold-off time over, scheduling restart. Stopped Ghost systemd service for blog: brettdewoody-com. Started Ghost systemd service for blog: brettdewoody-com. ghost_brettdewoody-com.service: Main process exited, code=exited, status=203/EXEC ghost_brettdewoody-com.service: Unit entered failed state. ghost_brettdewoody-com.service: Failed with result 'exit-code'. ``` I have also updated Node to 10.13.9 recently. Here’s the path to Node and Ghost: 1. /home/brettdewoody/.nvm/versions/node/v10.13.0/bin/node 2. /home/brettdewoody/.nvm/versions/node/v10.13.0/bin/ghost Debug Information: OS: Ubuntu, v16.04 Node Version: v10.13.0 Ghost-CLI Version: 1.12.0 Environment: production Command: ‘ghost start’ Contents of ghost\_brettdewoody-com.service: ```auto [Unit] Description=Ghost systemd service for blog: brettdewoody-com Documentation=https://docs.ghost.org [Service] Type=simple WorkingDirectory=/var/www/ghost User=107 Environment="NODE_ENV=production" ExecStart=/home/brettdewoody/.nvm/versions/node/v10.13.0/bin/node /home/brettdewoody/.nvm/versions/node/v10.13.0/bin/ghost Restart=always [Install] WantedBy=multi-user.target ``` I’ve read through some of the similar issues and tried their solutions, but am still getting the same error. Any other things I should try? ---
**Author:** ![vikaspotluri123](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/vikaspotluri123/32/24_2.png) [@vikaspotluri123](https://forum.ghost.org/u/vikaspotluri123)\ **Post date:** [October 30, 2019, 2:36am UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/2 "2019-10-30T02:36:59Z")
You might try `ghost run` to see if there are any error codes that are being spit out ---
**Author:** ![brettdewoody](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/brettdewoody/32/4942_2.png) [@brettdewoody](https://forum.ghost.org/u/brettdewoody)\ **Post date:** [October 30, 2019, 8:39am UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/3 "2019-10-30T08:39:34Z")
`ghost run` eventually starts up, with this: ```auto [2019-10-30 08:12:34] INFO Ghost is running in production... [2019-10-30 08:12:34] INFO Your site is now available on https://brettdewoody.com/ [2019-10-30 08:12:34] INFO Ctrl+C to shut down [2019-10-30 08:12:34] WARN Can't connect to the bootstrap socket (localhost 8000) ECONNREFUSED [2019-10-30 08:12:34] WARN Tries: 0 [2019-10-30 08:12:34] WARN Retrying... [2019-10-30 08:12:34] WARN Can't connect to the bootstrap socket (localhost 8000) ECONNREFUSED [2019-10-30 08:12:34] WARN Tries: 1 [2019-10-30 08:12:34] WARN Retrying... [2019-10-30 08:12:34] WARN Can't connect to the bootstrap socket (localhost 8000) ECONNREFUSED [2019-10-30 08:12:34] WARN Tries: 2 [2019-10-30 08:12:34] WARN Retrying... [2019-10-30 08:12:35] WARN Can't connect to the bootstrap socket (localhost 8000) ECONNREFUSED [2019-10-30 08:12:35] INFO Ghost boot 6.082s [2019-10-30 08:13:11] WARN {{#get}} helper took 476ms to complete {{#get}} helper took 476ms to complete Error ID: 1d6bfbc0-faed-11e9-877d-9d8d002d155a Error Code: SLOW_GET_HELPER Details: api: v3.[object Object].browse apiOptions: order: count.posts desc include: count.posts limit: 5 returnedRows: 4 [2019-10-30 08:13:11] WARN {{#get}} helper took 485ms to complete {{#get}} helper took 485ms to complete Error ID: 1d6c9800-faed-11e9-877d-9d8d002d155a Error Code: SLOW_GET_HELPER Details: api: v3.[object Object].browse apiOptions: limit: 3 returnedRows: 3 [2019-10-30 08:13:11] INFO "GET /favicon.png" 200 123ms ... ``` ---
**Author:** ![naz](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/naz/32/30666_2.png) [@naz](https://forum.ghost.org/u/naz)\ **Post date:** [October 30, 2019, 11:15am UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/4 "2019-10-30T11:15:05Z")
This line is most likely the reason for the problem: `WARN Can't connect to the bootstrap socket (localhost 8000) ECONNREFUSED` Something is holding up the `:8000` port. Can you check what process is doing that by running`lsof -i:8000`? ---
**Author:** ![brettdewoody](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/brettdewoody/32/4942_2.png) [@brettdewoody](https://forum.ghost.org/u/brettdewoody)\ **Post date:** [October 30, 2019, 12:57pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/5 "2019-10-30T12:57:39Z")
Checking the process on port 8000 results in nothing. ---
**Author:** ![chriskrycho](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/chriskrycho/32/3939_2.png) [@chriskrycho](https://forum.ghost.org/u/chriskrycho)\ **Post date:** [November 2, 2019, 6:11pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/6 "2019-11-02T18:11:28Z")
FWIW, I ran into the same and I _think_ it’s a case of a particularly misleading error message from systemctl, plus an opportunity to surface that output better from Ghost perhaps. If you run the command directly (where `` is the name you’d see in the output of `ghost start`): ```sh $ sudo systemctl start ``` In my case, this gave the _actual_ error: > **Warning:** The unit file, source configuration file or drop-ins of ghost\_krycho-com-1.service changed on disk. Run ‘systemctl daemon-reload’ to reload units. (Note that because of the configuration, you actually need to run `sudo systemctl daemon-reload`; otherwise you’re apt to see errors like “The name org.freedesktop.PolicyKit1 was not provided by any .service files”.) After running `sudo systemctl daemon-reload`, try running `ghost start` again. In my case at least, this solved the problem. As far as I can tell, this happens if Ghost updates the service definition (`/system/files/.system`) but doesn’t (successfully) reload the `systemctl` daemon. You’ll see the same if you for some reason need to edit that file to specify a different node or Ghost binary path and fail to restart it manually yourself. ---
**Author:** ![brettdewoody](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/brettdewoody/32/4942_2.png) [@brettdewoody](https://forum.ghost.org/u/brettdewoody)\ **Post date:** [November 2, 2019, 11:37pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/7 "2019-11-02T23:37:15Z")
Thanks @chriskrycho, your post eventually led me to a solution. Posting here for others. 1. Remove or rename the `/system/files/[sitename].service file 2. Run `ghost setup systemd` 3. Run `ghost start` ---
**Author:** ![simzen85](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/simzen85/32/7020_2.png) [@simzen85](https://forum.ghost.org/u/simzen85)\ **Post date:** [March 27, 2020, 4:09am UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/8 "2020-03-27T04:09:08Z")
Thanks. Your suggestion worked for me ---
**Author:** ![ssmulders](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/ssmulders/32/7034_2.png) [@ssmulders](https://forum.ghost.org/u/ssmulders)\ **Post date:** [March 27, 2020, 7:19pm UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/9 "2020-03-27T19:19:05Z")
My hero 😄 Thanks for sharing! What a hair puller. Happened to me when I started copying dirs around. ---
**Author:** ![kevmille](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kevmille/32/12888_2.png) [@kevmille](https://forum.ghost.org/u/kevmille)\ **Post date:** [July 17, 2022, 3:40am UTC](https://forum.ghost.org/t/update-to-3-01-and-cant-ghost-start/9857/10 "2022-07-17T03:40:24Z")
I had a similar error. **ghost doctor** was no help so I decided to try **ghost setup**. Re-entered the mysql information and then my site started up again. I got this error after trying to add a domain to my Ghost instance. The add failed because it already existed in /etc/nginx/sites-available. I hope this helps some.