systemd-tmpfiles won't startUbuntu installed by copying system files does not bootSystemd Mysql won't stopnginx won't start at boot using systemdUbuntu 16.04 freezing randomly [suspect- Visual Studio Code]130+% CPU usage /lib/systemd/systemd-timesyncdHow to start setxkbmap with systemdSystemd x.timer refusing to startsystemd units won't auto-startSystemd won't turn numlock offInstall Redis-Server on Ubuntu 16.04 LTS minimalsystemd won't start service
How to sort human readable size
How useful is the GRE Exam?
How did the European Union reach the figure of 3% as a maximum allowed deficit?
Interview was just a one hour panel. Got an offer the next day; do I accept or is this a red flag?
Is my research statement supposed to lead to papers in top journals?
New Site Design!
How could I create a situation in which a PC has to make a saving throw or be forced to pet a dog?
Manager wants to hire me; HR does not. How to proceed?
How to prevent cables getting intertwined
Digital signature that is only verifiable by one specific person
Leaving job close to major deadlines
Have Steve Rogers (Captain America) and a young Erik Lehnsherr (Magneto) interacted during WWII?
Lead the way to this Literary Knight to its final “DESTINATION”
At what temperature should the earth be cooked to prevent human infection?
What is the precise meaning of "подсел на мак"?
High-end PC graphics circa 1990?
Using roof rails to set up hammock
Why do you need to heat the pan before heating the olive oil?
Why are almost all the people in this orchestra recording wearing headphones with one ear on and one ear off?
Is it a bad idea to have a pen name with only an initial for a surname?
Do my partner and son need an SSN to be dependents on my taxes?
How to search for Android apps without ads?
What could be the physiological mechanism for a biological Geiger counter?
How do credit card companies know what type of business I'm paying for?
systemd-tmpfiles won't start
Ubuntu installed by copying system files does not bootSystemd Mysql won't stopnginx won't start at boot using systemdUbuntu 16.04 freezing randomly [suspect- Visual Studio Code]130+% CPU usage /lib/systemd/systemd-timesyncdHow to start setxkbmap with systemdSystemd x.timer refusing to startsystemd units won't auto-startSystemd won't turn numlock offInstall Redis-Server on Ubuntu 16.04 LTS minimalsystemd won't start service
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
4
After last update there is become a problem: systemd-tmpfiles not starts (so there is no temp dirs and some services can't be started).
root@myserver:/# journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Ср 2018-11-21 01:00:51 MSK, end at Ср 2018-11-21 11:45:01 MSK. --
ноя 21 01:01:04 myserver systemd[1]: Starting Create Volatile Files and Directories...
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/sendsigs.omit.d, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/subsys, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache/man, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/php, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/rpcbind.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/portmap.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/samba, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/screen, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sshd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo/ts, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/nologin, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/user, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/utmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/ask-password, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/seats, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/sessions, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/users, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/machines, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/shutdown, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/links, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/leases, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/wtmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/btmp, refusing.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
ноя 21 01:01:04 myserver systemd[1]: Failed to start Create Volatile Files and Directories.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
I was trying to run separate config files
root@myserver:/# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Unsafe symlinks encountered in /var/run/sshd, refusing.
/var/run/sshd is empty. There is no symlinks at all.
I've no idea what its means and how to fix it. Any advice are welcome.
root@myserver:/# uname -a
Linux myserver 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
16.04 systemd
edited Nov 24 '18 at 4:17
muru
1
asked Nov 21 '18 at 11:32
LokiLoki
234
add a comment |
4
After last update there is become a problem: systemd-tmpfiles not starts (so there is no temp dirs and some services can't be started).
root@myserver:/# journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Ср 2018-11-21 01:00:51 MSK, end at Ср 2018-11-21 11:45:01 MSK. --
ноя 21 01:01:04 myserver systemd[1]: Starting Create Volatile Files and Directories...
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/sendsigs.omit.d, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/subsys, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache/man, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/php, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/rpcbind.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/portmap.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/samba, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/screen, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sshd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo/ts, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/nologin, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/user, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/utmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/ask-password, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/seats, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/sessions, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/users, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/machines, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/shutdown, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/links, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/leases, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/wtmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/btmp, refusing.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
ноя 21 01:01:04 myserver systemd[1]: Failed to start Create Volatile Files and Directories.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
I was trying to run separate config files
root@myserver:/# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Unsafe symlinks encountered in /var/run/sshd, refusing.
/var/run/sshd is empty. There is no symlinks at all.
I've no idea what its means and how to fix it. Any advice are welcome.
root@myserver:/# uname -a
Linux myserver 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
16.04 systemd
edited Nov 24 '18 at 4:17
muru
1
asked Nov 21 '18 at 11:32
LokiLoki
234
add a comment |
4
4
4
1
After last update there is become a problem: systemd-tmpfiles not starts (so there is no temp dirs and some services can't be started).
root@myserver:/# journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Ср 2018-11-21 01:00:51 MSK, end at Ср 2018-11-21 11:45:01 MSK. --
ноя 21 01:01:04 myserver systemd[1]: Starting Create Volatile Files and Directories...
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/sendsigs.omit.d, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/subsys, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache/man, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/php, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/rpcbind.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/portmap.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/samba, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/screen, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sshd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo/ts, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/nologin, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/user, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/utmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/ask-password, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/seats, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/sessions, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/users, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/machines, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/shutdown, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/links, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/leases, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/wtmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/btmp, refusing.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
ноя 21 01:01:04 myserver systemd[1]: Failed to start Create Volatile Files and Directories.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
I was trying to run separate config files
root@myserver:/# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Unsafe symlinks encountered in /var/run/sshd, refusing.
/var/run/sshd is empty. There is no symlinks at all.
I've no idea what its means and how to fix it. Any advice are welcome.
root@myserver:/# uname -a
Linux myserver 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
16.04 systemd
edited Nov 24 '18 at 4:17
muru
1
asked Nov 21 '18 at 11:32
LokiLoki
234
After last update there is become a problem: systemd-tmpfiles not starts (so there is no temp dirs and some services can't be started).
root@myserver:/# journalctl -b 0 -u systemd-tmpfiles-setup.service
-- Logs begin at Ср 2018-11-21 01:00:51 MSK, end at Ср 2018-11-21 11:45:01 MSK. --
ноя 21 01:01:04 myserver systemd[1]: Starting Create Volatile Files and Directories...
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/sendsigs.omit.d, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/subsys, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lock/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/lvm, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/cache/man, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/php, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/rpcbind.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/rpcbind/portmap.xdr, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/samba, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/screen, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sshd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/run/sudo/ts, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/nologin, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/user, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/utmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/ask-password, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/seats, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/sessions, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/users, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/machines, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/shutdown, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/links, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/systemd/netif/leases, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /run/log, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/wtmp, refusing.
ноя 21 01:01:04 myserver systemd-tmpfiles[1040]: Unsafe symlinks encountered in /var/log/btmp, refusing.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
ноя 21 01:01:04 myserver systemd[1]: Failed to start Create Volatile Files and Directories.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state.
ноя 21 01:01:04 myserver systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
I was trying to run separate config files
root@myserver:/# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Unsafe symlinks encountered in /var/run/sshd, refusing.
/var/run/sshd is empty. There is no symlinks at all.
I've no idea what its means and how to fix it. Any advice are welcome.
root@myserver:/# uname -a
Linux myserver 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
16.04 systemd
16.04 systemd
edited Nov 24 '18 at 4:17
muru
1
asked Nov 21 '18 at 11:32
LokiLoki
234
edited Nov 24 '18 at 4:17
muru
1
asked Nov 21 '18 at 11:32
LokiLoki
234
edited Nov 24 '18 at 4:17
muru
1
edited Nov 24 '18 at 4:17
muru
1
edited Nov 24 '18 at 4:17
muru
1
1
asked Nov 21 '18 at 11:32
LokiLoki
234
asked Nov 21 '18 at 11:32
LokiLoki
234
asked Nov 21 '18 at 11:32
LokiLoki
234
234
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
11
I had exactly the same problem today on my workstation - ubuntu 18.04.1.
Finally (searching systemd source code) I have figured, that somehow
my root folder = / ownership had been changed to me - the only user.
Simple chown root.root / solved the problem :)
... after some 2 hours of searching.
answered Nov 21 '18 at 12:33
ivopivop
12612
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running thechowncommand? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to rundpkg --configure -ato fix, which returnedSetting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusingthen cascaded failures after that. This fixed that and I was successfully able to re-run thedpkgcommand to complete the upgrade
– ardila
Nov 26 '18 at 13:42
add a comment |
1
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1328
add a comment |
1
Encountered this problem as well.
To add to the answer above, you need to make sure that the whole path belongs to root, not just /. Somehow my /var folder got the owner of mysql (good job, mysql), and sshd was trying to create /var/run/sshd, which failed.
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094776%2fsystemd-tmpfiles-wont-start%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
11
I had exactly the same problem today on my workstation - ubuntu 18.04.1.
Finally (searching systemd source code) I have figured, that somehow
my root folder = / ownership had been changed to me - the only user.
Simple chown root.root / solved the problem :)
... after some 2 hours of searching.
answered Nov 21 '18 at 12:33
ivopivop
12612
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running thechowncommand? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to rundpkg --configure -ato fix, which returnedSetting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusingthen cascaded failures after that. This fixed that and I was successfully able to re-run thedpkgcommand to complete the upgrade
– ardila
Nov 26 '18 at 13:42
add a comment |
11
I had exactly the same problem today on my workstation - ubuntu 18.04.1.
Finally (searching systemd source code) I have figured, that somehow
my root folder = / ownership had been changed to me - the only user.
Simple chown root.root / solved the problem :)
... after some 2 hours of searching.
answered Nov 21 '18 at 12:33
ivopivop
12612
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running thechowncommand? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to rundpkg --configure -ato fix, which returnedSetting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusingthen cascaded failures after that. This fixed that and I was successfully able to re-run thedpkgcommand to complete the upgrade
– ardila
Nov 26 '18 at 13:42
add a comment |
11
11
11
I had exactly the same problem today on my workstation - ubuntu 18.04.1.
Finally (searching systemd source code) I have figured, that somehow
my root folder = / ownership had been changed to me - the only user.
Simple chown root.root / solved the problem :)
... after some 2 hours of searching.
answered Nov 21 '18 at 12:33
ivopivop
12612
I had exactly the same problem today on my workstation - ubuntu 18.04.1.
Finally (searching systemd source code) I have figured, that somehow
my root folder = / ownership had been changed to me - the only user.
Simple chown root.root / solved the problem :)
... after some 2 hours of searching.
answered Nov 21 '18 at 12:33
ivopivop
12612
answered Nov 21 '18 at 12:33
ivopivop
12612
answered Nov 21 '18 at 12:33
ivopivop
12612
answered Nov 21 '18 at 12:33
ivopivop
12612
12612
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running thechowncommand? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to rundpkg --configure -ato fix, which returnedSetting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusingthen cascaded failures after that. This fixed that and I was successfully able to re-run thedpkgcommand to complete the upgrade
– ardila
Nov 26 '18 at 13:42
add a comment |
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running thechowncommand? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to rundpkg --configure -ato fix, which returnedSetting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusingthen cascaded failures after that. This fixed that and I was successfully able to re-run thedpkgcommand to complete the upgrade
– ardila
Nov 26 '18 at 13:42
1
1
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Wow! Amazing! I didn't even think to dig in this direction.
– Loki
Nov 21 '18 at 12:47
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
Really troublesome that something would change ownership of the root directory... And that this would happen to more than one of you. Did you end up figuring out what changed those permissions in this way???
– filbranden
Nov 22 '18 at 19:05
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
No, I did not. Actually I do nothing special on that machine as root = ubuntu upgrades. Very rarely something else. So I suspect some package update. In apt history there is only one package installed previous day (no updates): synology-note-station:amd64. But I did the same on another (practically the same) machine - no problems :(
– ivop
Nov 24 '18 at 6:28
Thanks for this. Noob question: Is there any side-effect to running the
chown command? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to run dpkg --configure -a to fix, which returned Setting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusing then cascaded failures after that. This fixed that and I was successfully able to re-run the dpkg command to complete the upgrade– ardila
Nov 26 '18 at 13:42
Thanks for this. Noob question: Is there any side-effect to running the
chown command? Do I need to clean anything up or revert any ownership afterwards? In case it helps someone, this happened to me during an upgrade from 17.10 to 18.04, where it said that systemd wasn't configured. It said I needed to run dpkg --configure -a to fix, which returned Setting up systemd (237-3ubuntu10.9) ... Unsafe symlinks encountered in /var/log/journal, refusing then cascaded failures after that. This fixed that and I was successfully able to re-run the dpkg command to complete the upgrade– ardila
Nov 26 '18 at 13:42
add a comment |
1
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1328
add a comment |
1
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1328
add a comment |
1
1
1
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1328
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1328
answered Nov 24 '18 at 3:59
GannetGannet
1328
answered Nov 24 '18 at 3:59
GannetGannet
1328
answered Nov 24 '18 at 3:59
GannetGannet
1328
1328
add a comment |
add a comment |
1
Encountered this problem as well.
To add to the answer above, you need to make sure that the whole path belongs to root, not just /. Somehow my /var folder got the owner of mysql (good job, mysql), and sshd was trying to create /var/run/sshd, which failed.
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
add a comment |
1
Encountered this problem as well.
To add to the answer above, you need to make sure that the whole path belongs to root, not just /. Somehow my /var folder got the owner of mysql (good job, mysql), and sshd was trying to create /var/run/sshd, which failed.
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
add a comment |
1
1
1
Encountered this problem as well.
To add to the answer above, you need to make sure that the whole path belongs to root, not just /. Somehow my /var folder got the owner of mysql (good job, mysql), and sshd was trying to create /var/run/sshd, which failed.
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
Encountered this problem as well.
To add to the answer above, you need to make sure that the whole path belongs to root, not just /. Somehow my /var folder got the owner of mysql (good job, mysql), and sshd was trying to create /var/run/sshd, which failed.
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
answered Nov 25 '18 at 0:44
Michael KimMichael Kim
1514
1514
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094776%2fsystemd-tmpfiles-wont-start%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
