Linux boot error

Question:

When loading Xubuntu 18.04, a red line (FAILED) began to slip. This happens so fast that I had to take a picture of the screen, I did not find it in the logs. I have no problems using the system, but I would like to correct the error.

It says that I should run systemctl status systemd-tmpfiles-setup.service to see the details of the error, and here they are:

● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
   Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-11-24 05:04:49 EET; 2min 24s ago
     Docs: man:tmpfiles.d(5)
           man:systemd-tmpfiles(8)
  Process: 526 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAI
 Main PID: 526 (code=exited, status=1/FAILURE)

Nov 24 05:04:49 MAINFRAME systemd[1]: Starting Create Volatile Files and Directories...
Nov 24 05:04:49 MAINFRAME systemd-tmpfiles[526]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing.
Nov 24 05:04:49 MAINFRAME systemd-tmpfiles[526]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing.
Nov 24 05:04:49 MAINFRAME systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
Nov 24 05:04:49 MAINFRAME systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.
Nov 24 05:04:49 MAINFRAME systemd[1]: Failed to start Create Volatile Files and Directories.

These logs don't tell me much. Probably need to replace symlinks with real paths? But I didn't create these symlinks. You never know what they are for.

UPD: I just went through these paths – /var/lib/colord/icc , /var/lib/systemd/coredump and it turned out that these are ordinary empty folders, not symlinks. So I have no idea what he wants from me.

UPD: Googled this error, here's what I found – it seems like someone managed to solve the same problem with the chown root.root / , but it didn't help me.

Answer:

Problem solved. The reason was that mysql somehow secretly declared itself the owner of the /var/lib folder. I returned the rights to the root and the error is no more.

Scroll to Top