How to fix a broken ghost CMS systemd service?

Developer help Self-hosting
1

Hey guys!

Hope you are doing great.

Lately I’ve been thinking about using Ghost instead of Wordpress for a blog. The editor is much faster compared to gutenberg and you know, ghost has auto image optimizations, integrated SEO and a bunch of really great features.

My issue however is probably my fault. I was changing some settings at config prod json, and after running a “ghost restart” the service doesn’t restart anymore:

704×478 41.6 KB

If I try to run ghost setup linux-user systemd, this is what I receive:

718×222 17.3 KB

I tried to fully delete the systemd service with these commands:

systemctl stop ghost_blog-speedyour-day
systemctl disable  ghost_blog-speedyour-day
rm /etc/systemd/system/ghost_blog-speedyour-day
rm /usr/lib/systemd/system/ghost_blog-speedyour-day
systemctl daemon-reload
systemctl reset-failed

But unfortunately, they didn’t help.

I’am able to start my block with “ghost run” but not with ghost start. The service “ghost_blog-speedyour-day” still exists.

If I try to enable it: systemctl enable ghost_blog-speedyour-day --now

I still can’t manage it with ghost cli.

Ghost doctor says this:

729×442 46.6 KB

To be honest, I don’t understand much about systemd. Do you guys know any way to create the service again?

Thanks!

1 Like
2

Forgot to mention that, but the changes at the config file were related to mail. I just changed it from direct to smtp. I tried to return to direct, but no results. I think it’s unrelated with config file anyway since ghost doctor isn’t saying that it’s config fault

3

Welcome, @aquasp.

Have you tried ghost setup systemd again?

Can you confirm that Ghost was running before changing production.json.conf, and share the file with password etc. redacted.

1 Like
4

Hey, thanks for your reply!

It says that systemd setup was already done :disappointed:

720×218 17.1 KB

This is my current:

  GNU nano 4.8                                                                                   config.production.json                                                                                              
{
  "url": "https://myblog.com",
  "server": {
    "port": 2368,
    "host": "127.0.0.1"
  },
  "database": {
    "client": "mysql",
    "connection": {
      "host": "localhost",
      "user": "ghost-462",
      "password": "mypass",
      "database": "public_html_prod"
    }
  },
"mail": {
  "transport": "direct"
  },
  "logging": {
    "transports": [
      "file",
      "stdout"
    ]
  },
  "process": "systemd",
  "paths": {
    "contentPath": "/home/blogspeed/public_html/content"
  }
}
5

Ok, I think I’m giving up about systemd lol hehehe, always hated him…

Either way, if you have a issue like me and can’t fix systemd, just change to local:

ghost config --process local
ghost restart

Easier, simpler and more stable IMO. Hope Ghost keeps supporting non systemd alternatives

6

@mjw I know that you are probably busy, bust just wanted to tag you to show the “solution” that I found hehe.

7

I found a even better solution!

ghost config --process local
ghost restart
ghost config --process systemd
ghost doctor
(now fix any warning that ghost doctor says)
ghost restart

It’s all good now!