# Dietpi Services not starting
**URL:** https://dietpi.com/forum/t/dietpi-services-not-starting/2966
**Category:** Troubleshooting
**Created:** [20 February 2019 09:08 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966 "2019-02-20T09:08:35Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@WilburWalsh](https://dietpi.com/forum/u/WilburWalsh)
#### Post date: [20 February 2019 09:08 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/1 "2019-02-20T09:08:35Z")
Hi,
recently I noticed that sometimes after booting my Raspberry not all of the Dietpi Services are starting, I assume it’s all the postboot services, see this screenshot:
At first I felt this only happens if I login via ssh directly after reboot, but this seems not to be the cause.
I already tried to find a hint by looking at the journalctl output and other log files, but could not find an error. Any ideas, where to search?
---
### Author:  [@WilburWalsh](https://dietpi.com/forum/u/WilburWalsh)
#### Post date: [21 February 2019 12:12 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/2 "2019-02-21T12:12:20Z")
Update:
I digged into the journal messages and compared a successful with an unsuccessful boot. Seems the problem is somehow related to Systemd and/or Plymouth.
I can see that plymouth-quit-wait.service is started, because it says:
```nohighlight
Starting Hold until boot process finishes up...
```
but plymouth-quit.service, which also should be started, is not. There is no
```nohighlight
Starting Terminate Plymouth Boot Screen...
```
as in the successful start’s journal.
So it waits for plymouth to finish, without asking it to stop. Thus, target Multi-User System is not reached, and dietpi-postboot is not started. I have no access to a system to test right now, but will check if a manual start/restart of plymouth-quit.service forces to other services to follow.
I found a couple of similar problems when googling it, but no good explanation or solution so far. So still, any hint would be appreciated 🙂
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 February 2019 21:48 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/3 "2019-02-21T21:48:03Z")
Can you please try to edit /etc/systemd/system/dietpi-postboot.service and remove multi-user.target from the After= line?
Then systemctl daemon-reload an check on next reboot.
---
### Author:  [@pecan\_pie](https://dietpi.com/forum/u/pecan_pie)
#### Post date: [21 February 2019 23:23 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/4 "2019-02-21T23:23:36Z")
> [@](#):
>
> Can you please try to edit /etc/systemd/system/dietpi-postboot.service and remove multi-user.target from the After= line?
> Then systemctl daemon-reload an check on next reboot.
This worked for me, thanks!
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [21 February 2019 23:26 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/5 "2019-02-21T23:26:19Z")
Okay, glad to here. This is already patched for DietPi v6.22 as well.
---
### Author:  [@WilburWalsh](https://dietpi.com/forum/u/WilburWalsh)
#### Post date: [22 February 2019 09:47 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/6 "2019-02-22T09:47:05Z")
In the last few days every boot went fine, and I was wondering how that happened… I had switched to the dev branch in the meantime, with the already updated dietpi-postboot.service 😃
So obviously no more problems now, thanks!
---
### Author:  [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [22 February 2019 17:16 UTC](https://dietpi.com/forum/t/dietpi-services-not-starting/2966/7 "2019-02-22T17:16:04Z")
Okay, just keep in mind that the dev branch indeed is under development and not tested throughout. But current stage at least does not contain some unfinished things, should work fine.