I have multiple instances of Ghost running on a DigitalOcean Droplet. When going through the backup process, I was unable to backup the sites because they weren’t running. When I tried to start the sites, I received this error. This same error prevents start, backup, and update. I even attempted to …

The problem was finally resolved by creating a snapshot of the DigitalOcean Droplet of the backup when I had all the sites working. I used that snapshot to create a new Droplet. I waited for the DNS to resolve, then ran ghost ls and it showed that all the sites were running. stephen@bau:/var/www/st…

Can you run ghost doctor or ghost setup systemd?

Here is the output from ghost doctor: stephen@builders:~$ cd /var/www/stephenbau.com stephen@builders:/var/www/stephenbau.com$ ghost doctor Love open source? We’re hiring Node.js Engineers to work on Ghost full-time. https://careers.ghost.org/product-engineer-node-js ✔ Checking system Node.js ve…

Here is the output from ghost setup systemd: stephen@builders:/var/www/stephenbau.com$ ghost setup systemd Love open source? We’re hiring Node.js Engineers to work on Ghost full-time. https://careers.ghost.org/product-engineer-node-js Systemd service has already been set up. Skipping Systemd se…

I have several sites running on this server. I was trying to update Ubuntu for Ghost 5.0. I gave up on reviving my old sites, because I was intending to create a new instance running Ghost 5.0. I should have created a new droplet, but my intention was to update all the sites to 5.0 and things failed…

You need to update to the latest V4 first, and make sure Node is compatible with Ghost 4.19.1, i.e., 14.16.1. [image] Supported node versions for self-hosted installs of Ghost Self-hosted installs of Ghost are recommended to use the supported node versions to ensure you don't run into a…

I tried to follow the downgrade instructions, but that did not seem to make a difference. I have gone back to the oldest available backup to see if that helps. The first ghost ls returned a status of running for all domains. stephen@builders:~$ ghost ls + sudo systemctl is-active ghost_builderscol…

Have you tried ghost setup systemd or ghost setup linux-user systemd for those sites?

Yes, I tried both. stephen@builders:/var/www/designadmin.com$ ghost start + sudo systemctl is-active ghost_designadmin-com ✔ Checking system Node.js version - found v14.16.1 ✔ Ensuring user is not logged in as ghost user ✔ Checking if logged in user is directory owner ✔ Checking current folder per…

After running that, did you try to start Ghost? You could also check the startup status with systemctl list-unit-files --type=service --state=enabled. Are all sites listed? Is vendor enabled for each? And finally, the output from ls -Flai /lib/systemd/system/ghost* will tell you which user runs ea…

SystemError occurred when running ghost start: “Systemd process manager has not been set up or is corrupted.”

Developer help

bauhouse June 7, 2022, 8:12pm 10

I suspect this is a MySQL database issue with this solution.

Topic		Replies	Views
Failed to start Ghost systemd service Developer help	5	3061	June 26, 2023
Tried to update Ghost and everything is broken :( Self-hosting	52	1000	May 16, 2024
Upgrade to Ghost v4, but a lot of 503 error Developer help	31	6511	July 7, 2021
Dont start after update Self-hosting	17	586	August 30, 2023
Upgrade to v5.72.0 - Systemd process manager has not been set up or is corrupted Self-hosting	8	383	November 8, 2023

SystemError occurred when running ghost start: “Systemd process manager has not been set up or is corrupted.”

Related topics