Skip to main content
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

You need to provide the service file that you wrote, please edit your original question with this. (Should have been a comment but I don't have the permission).

The base issue is that your service file has created a loop in desired startup order. Example: systemd wants to start a first, then b, then c, but a wants to start after c. I would suspect that the two guilty lines are the BindsTo and After, since it makes it part of the same service that it wants to wait on.

However, you can follow this answerthis answer with cvol.service replaced with your [email protected]. Relevant command: systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After [email protected]

Descriptions for keywords can be found here

You need to provide the service file that you wrote, please edit your original question with this. (Should have been a comment but I don't have the permission).

The base issue is that your service file has created a loop in desired startup order. Example: systemd wants to start a first, then b, then c, but a wants to start after c. I would suspect that the two guilty lines are the BindsTo and After, since it makes it part of the same service that it wants to wait on.

However, you can follow this answer with cvol.service replaced with your [email protected]. Relevant command: systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After [email protected]

Descriptions for keywords can be found here

You need to provide the service file that you wrote, please edit your original question with this. (Should have been a comment but I don't have the permission).

The base issue is that your service file has created a loop in desired startup order. Example: systemd wants to start a first, then b, then c, but a wants to start after c. I would suspect that the two guilty lines are the BindsTo and After, since it makes it part of the same service that it wants to wait on.

However, you can follow this answer with cvol.service replaced with your [email protected]. Relevant command: systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After [email protected]

Descriptions for keywords can be found here

Source Link
D.S
  • 562
  • 4
  • 9

You need to provide the service file that you wrote, please edit your original question with this. (Should have been a comment but I don't have the permission).

The base issue is that your service file has created a loop in desired startup order. Example: systemd wants to start a first, then b, then c, but a wants to start after c. I would suspect that the two guilty lines are the BindsTo and After, since it makes it part of the same service that it wants to wait on.

However, you can follow this answer with cvol.service replaced with your [email protected]. Relevant command: systemctl show -p Requires,Wants,Requisite,BindsTo,PartOf,Before,After [email protected]

Descriptions for keywords can be found here