# Upgrade to v5.72.0 - Systemd process manager has not been set up or is corrupted

**URL:** <https://forum.ghost.org/t/upgrade-to-v5-72-0-systemd-process-manager-has-not-been-set-up-or-is-corrupted/42483>\
**Category:** Self-hosting\
**Created:** [November 6, 2023, 5:57am UTC](https://forum.ghost.org/t/upgrade-to-v5-72-0-systemd-process-manager-has-not-been-set-up-or-is-corrupted/42483 "2023-11-06T05:57:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jeff](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jeff/32/4900_2.png) [@jeff](https://forum.ghost.org/u/jeff)\
**Post date:** [November 6, 2023, 7:22am UTC](https://forum.ghost.org/t/upgrade-to-v5-72-0-systemd-process-manager-has-not-been-set-up-or-is-corrupted/42483/5 "2023-11-06T07:22:45Z")

</div>

So I found the `migrations_lock` table and updated the lock to `0` as per [Migration lock after updating Ghost - #4 by KeenenCharles](https://forum.ghost.org/t/migration-lock-after-updating-ghost/5625/4) - but when I `sudo systemctl restart ghost_jaguart-tech` the **MigrationsLock** error recurrs, and the database has been updated to `1` again…

I also tried `ghost update --rollback` - which fails with permissions because the Ghost logs are owned by Ghost rather than normal user. Opened the permissions on the logs - but --rollback fails at the `systemctl stop` stage.

`ghost update --force` says it has succeeded, but `systemctl start` and while it thinks its running, syslog says:

```
{
   message: {
     statusCode: 500,
     errorType: 'InternalServerError',
     level: 'critical',
     message: "Ghost was able to start, but errored during boot with: EACCES: permission denied, open '/var/www/www.jaguart.tech/content/data/the-art-of-jagu.ghost.2023-11-06-07-08-11.json'",
     id: '3ee655f0-7c73-11ee-bf5e-7d632264e5ee',
     name: 'InternalServerError',
     code: 'EACCES',
     property: null,
     redirect: null,
     hideStack: false,
     errno: -13,
     syscall: 'open',
     path: '/var/www/www.jaguart.tech/content/data/the-art-of-jagu.ghost.2023-11-06-07-08-11.json'
   }
}

```

The file that is is unable to open does not exist - it has the MigrationsLock timestamp in it’s name. So at a guess, the reinstall even with --force is missing a step…

Not sure what to try next - any help appreciated.

---

_[View the full topic](https://forum.ghost.org/t/upgrade-to-v5-72-0-systemd-process-manager-has-not-been-set-up-or-is-corrupted/42483)._
