systemd Cannot add dependency job for unit cgmanager.service and display-manager.service

rampage

Active Member
Oct 17, 2016
22
2
43
40
systemd Cannot add dependency job for unit cgmanager.service and display-manager.service

Hi, upgrade to the new Virtual Environment 4.4-12/e71b7a74 version and noticed those fail warnings in the system log, should I be worried of those? Not sure if those exists in the old version.

Code:
[    8.894923] systemd[1]: Inserted module 'autofs4'
[    8.937107] systemd[1]: Set hostname to <pve>.
[    9.921501] systemd-sysv-generator[1444]: Ignoring creation of an alias umountiscsi.service for itself
[   11.070958] systemd[1]: Cannot add dependency job for unit cgmanager.service, ignoring: Unit cgmanager.service failed to load: No such file or directory.
[   11.070996] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[   11.071295] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[   11.071347] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[   11.071361] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
 
Last edited:
Hi,

systemd Cannot add dependency job for unit cgmanager.service and display-manager.service

Hi, upgrade to the new Virtual Environment 4.4-12/e71b7a74 version and noticed those fail warnings in the system log, should I be worried of those? Not sure if those exists in the old version.

For cgmanager there is no need to worry, we do not need it anymore and it should get removed by a
Code:
apt-get autoremove

Or use:
Code:
apt remove cgmanager

Code:
[    8.894923]
[   11.070996] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.

This can be seen as systemd noise, its graphical target has a dependency on display-manager.service which would be provided by a desktop environment, which on a Proxmox VE server normally does not exists.
If it really annoys you you could open
/lib/systemd/system/graphical.target
and remove the
Code:
Wants=display-manager.service
line.

But both are not causing any harm.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!