systemd-tmpfiles won't start Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Ubuntu installed by copying system files does not bootSystemd Mysql won't stopSystemd: How to start/stop services on batterynginx 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-startInstall Redis-Server on Ubuntu 16.04 LTS minimalsystemd won't start service
What LEGO pieces have "real-world" functionality?
Using "nakedly" instead of "with nothing on"
What do you call a plan that's an alternative plan in case your initial plan fails?
How to rotate it perfectly?
How did the aliens keep their waters separated?
I'm thinking of a number
Complexity of many constant time steps with occasional logarithmic steps
Need a suitable toxic chemical for a murder plot in my novel
Estimated State payment too big --> money back; + 2018 Tax Reform
What is the electric potential inside a point charge?
Autumning in love
How is simplicity better than precision and clarity in prose?
Passing functions in C++
Are my PIs rude or am I just being too sensitive?
Classification of bundles, Postnikov towers, obstruction theory, local coefficients
If A makes B more likely then B makes A more likely"
Why does this iterative way of solving of equation work?
Single author papers against my advisor's will?
How to market an anarchic city as a tourism spot to people living in civilized areas?
What to do with post with dry rot?
What was Bilhah and Zilpah's ancestry?
Cold is to Refrigerator as warm is to?
How can I protect witches in combat who wear limited clothing?
What computer would be fastest for Mathematica Home Edition?
systemd-tmpfiles won't start
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Ubuntu installed by copying system files does not bootSystemd Mysql won't stopSystemd: How to start/stop services on batterynginx 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-startInstall 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;
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
add a comment |
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
add a comment |
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
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
1
asked Nov 21 '18 at 11:32
LokiLoki
234
234
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
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.
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 |
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
add a comment |
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.
add a comment |
I was reluctant to the answer from @ivop, but it turned out to solve my problem.
I'm using Arch, and found that my /run/mysqld and /run/httpd directories were not created at boot (thus I had to crank start apache and mariaDB), and that whenever an update took place, I always received the error: "could not create temporary files".
What I don't get is: why, when I did "ls -l /", every file had root ownership (root root). And, after trying @ivop's answer, everything kinda looks the same, but now works.
Am I missing something?
Is there another way to check files ownerships?
Thanks anyway! I'll be vigilant if something stops working from here.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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
);
);
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
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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 |
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.
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 |
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.
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
1061
1061
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 |
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
add a comment |
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
add a comment |
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
It seems it is a bug:
systemd-tmpfiles-setup.service fails on btrfs
answered Nov 24 '18 at 3:59
GannetGannet
1177
1177
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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
514
514
add a comment |
add a comment |
I was reluctant to the answer from @ivop, but it turned out to solve my problem.
I'm using Arch, and found that my /run/mysqld and /run/httpd directories were not created at boot (thus I had to crank start apache and mariaDB), and that whenever an update took place, I always received the error: "could not create temporary files".
What I don't get is: why, when I did "ls -l /", every file had root ownership (root root). And, after trying @ivop's answer, everything kinda looks the same, but now works.
Am I missing something?
Is there another way to check files ownerships?
Thanks anyway! I'll be vigilant if something stops working from here.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I was reluctant to the answer from @ivop, but it turned out to solve my problem.
I'm using Arch, and found that my /run/mysqld and /run/httpd directories were not created at boot (thus I had to crank start apache and mariaDB), and that whenever an update took place, I always received the error: "could not create temporary files".
What I don't get is: why, when I did "ls -l /", every file had root ownership (root root). And, after trying @ivop's answer, everything kinda looks the same, but now works.
Am I missing something?
Is there another way to check files ownerships?
Thanks anyway! I'll be vigilant if something stops working from here.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I was reluctant to the answer from @ivop, but it turned out to solve my problem.
I'm using Arch, and found that my /run/mysqld and /run/httpd directories were not created at boot (thus I had to crank start apache and mariaDB), and that whenever an update took place, I always received the error: "could not create temporary files".
What I don't get is: why, when I did "ls -l /", every file had root ownership (root root). And, after trying @ivop's answer, everything kinda looks the same, but now works.
Am I missing something?
Is there another way to check files ownerships?
Thanks anyway! I'll be vigilant if something stops working from here.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I was reluctant to the answer from @ivop, but it turned out to solve my problem.
I'm using Arch, and found that my /run/mysqld and /run/httpd directories were not created at boot (thus I had to crank start apache and mariaDB), and that whenever an update took place, I always received the error: "could not create temporary files".
What I don't get is: why, when I did "ls -l /", every file had root ownership (root root). And, after trying @ivop's answer, everything kinda looks the same, but now works.
Am I missing something?
Is there another way to check files ownerships?
Thanks anyway! I'll be vigilant if something stops working from here.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 12 mins ago
tulainastulainas
11
11
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
tulainas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
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.
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