Dont start after update

Hello, i install update 5.36.0 version and i have started ghost, but not started.

ghost start

Love open source? We’re hiring JavaScript Engineers to work on Ghost full-time.
https://careers.ghost.org


+ sudo systemctl is-active ghost_mysite-org-ua
✔ Checking system Node.js version - found v16.18.1
✔ 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_mysite-org-ua
✔ Validating config
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking memory availability
✔ Checking binary dependencies
✔ Checking systemd unit file
✔ Checking systemd node version - found v16.18.1
✖ Starting Ghost: mysite-org-ua
A SystemError occurred.

Message: Systemd process manager has not been set up or is corrupted.
Help: Run ghost setup linux-user systemd and try again.

Debug Information:
    OS: Ubuntu, v22.04.1 LTS
    Node Version: v16.18.1
    Ghost Version: 5.36.0
    Ghost-CLI Version: 1.24.0
    Environment: production
    Command: 'ghost start'

Try running ghost doctor to check your system for known issues.

You can always refer to https://ghost.org/docs/ghost-cli/ for troubleshooting.

Did you try this? And, taken a look at the logs?

Yes, i give this and where find logs?

ghost doctor

Love open source? We’re hiring JavaScript Engineers to work on Ghost full-time.
https://careers.ghost.org


✔ Checking system Node.js version - found v16.18.1
✔ Checking logged in user
✔ Ensuring user is not logged in as ghost user
✔ Checking if logged in user is directory owner
✔ Checking current folder permissions
✔ Checking system compatibility
✔ Checking for a MySQL installation
+ sudo systemctl is-active ghost_mysite-org-ua
? Sudo Password [hidden]
✔ Validating config
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking memory availability
✔ Checking binary dependencies
✔ Checking free space
✔ Checking systemd unit file
✔ Checking systemd node version - found v16.18.1

How do I fix it so that it starts up?

Navigate to the content folder of your site, and you’ll see the logs directory.

I went in, but there is only the log from the ghost run command

Run ghost setup linux-user systemd and try again.

ghost setup linux-user systemd

Love open source? We’re hiring JavaScript Engineers to work on Ghost full-time.

Systemd service has already been set up. Skipping Systemd setup
:information_source: Setting up Systemd [skipped]

after this command ghost start the same thing comes up

Okay, I need additional information about your system. What is the host, and how did you install Ghost?

Host is ukraine.com.ua, system Ubuntu 20.04, I don’t know how they installed it, they asked me to update it, and I know they didn’t use a docker to install it. I updated it, but I can’t launch it.

Was the site working before you updated it?

Please share the output from ghost ls and that the result from typing groups includes sudo.

Everything was working before the update,

This give ghost ls

Love open source? We’re hiring JavaScript Engineers to work on Ghost full-time.
https://careers.ghost.org

+ sudo systemctl is-active ghost_resistance-org-ua
┌───────────────────┬──────────────┬─────────┬─────────┬─────┬──────┬─────────────────┐
│ Name              │ Location     │ Version │ Status  │ URL │ Port │ Process Manager │
├───────────────────┼──────────────┼─────────┼─────────┼─────┼──────┼─────────────────┤
│ mysite-org-ua │ /var/www/res │ 5.36.0  │ stopped │ n/a │ n/a  │ n/a             │

You didn’t answer my question about permissions: it’s not evident if you have complete access to your hosting.

Nonetheless, the next step I’d take is to check the logs, i.e., journalctl -g, for the Ghost systemd service. To find the correct service name, you may need to take a look at /lib/systemd/system/. The service will start with ghost_ and match the name from ghost ls.

If you’re uncertain how to use journalctl, then you’ll need to find out by doing a web search.

journalctl -g

Mar 02 18:10:23 vps-42028 kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Mar 02 18:10:23 vps-42028 systemd[1]: Reached target Preparation for Local File Systems.
Mar 02 18:10:25 vps-42028 systemd[1]: Reached target Preparation for Network.
Mar 02 18:10:39 vps-42028 systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) bein>
Mar 02 18:10:39 vps-42028 systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) bei>
Mar 02 18:10:39 vps-42028 systemd[1]: Condition check resulted in Timer to automatically fetch and run repair assertions being skipped.
Mar 02 18:10:39 vps-42028 systemd[1]: Started Ubuntu Advantage Timer for running repeated jobs.
Mar 02 18:10:39 vps-42028 systemd[1]: Reached target Preparation for Remote File Systems.
Mar 02 18:10:39 vps-42028 systemd[1]: Starting LSB: automatic crash report generation...
Mar 02 18:10:39 vps-42028 systemd[1]: Condition check resulted in Automatically repair incorrect owner/permissions on core devices being skip>
Mar 02 18:10:39 vps-42028 apport[663]:  * Starting automatic crash report generation: apport
Mar 02 18:10:39 vps-42028 systemd[1]: Reached target Preparation for Logins.
Mar 02 18:10:39 vps-42028 systemd[1]: Started LSB: automatic crash report generation.
Mar 02 18:10:58 vps-42028 systemd[1]: ghost_mysite-org-ua.service: Start request repeated too quickly.
Mar 02 18:17:01 vps-42028 CRON[1817]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

All that came out this command to me, I had to run it from a super user, also in the folder that you said - the service is

I did it, I don’t know how, but I did it. I tried a random method and it run

The -g option needs to be followed by the search string.

What did you do? Providing the steps may help other users… and what you did is recorded in .bash_history.

I did not write any commands other than the restart command, when I have free time I will write more about how I fixed it

have the same issue, and can’t fix it