Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Normal boot on a vagrant vbox machine produces 26 critical error entries in journal #70

Closed
crawford opened this issue Jul 11, 2014 · 11 comments
Closed

Normal boot on a vagrant vbox machine produces 26 critical error entries in journal #70

crawford opened this issue Jul 11, 2014 · 11 comments
Labels
area/stability closed/rejected component/distro kind/cleanup priority/P2 team/os

Comments

@crawford
Copy link
Contributor

Originally filed in https://github.com/coreos/init/issues/117.

None of these errors appear to be significant since the machine boots and runs without any obvious issues. It would likely be best to at least document the fact that they are not an issue if you can't inhibit them.

Jul 11 19:52:16 localhost kernel: tsc: Fast TSC calibration failed
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'tty' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'uucp' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'kmem' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'video' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'audio' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'lp' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'disk' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: IMPORT{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'tty' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'uucp' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'kmem' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'video' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'audio' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'lp' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: specified group 'disk' unknown
Jul 11 19:52:16 localhost systemd-udevd[152]: IMPORT{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Jul 11 19:52:17 localhost kernel: piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
Jul 11 19:52:18 localhost systemd-tmpfiles[321]: /sysroot/lib is not the right symlinks.
Jul 11 19:52:19 localhost systemd-tmpfiles[321]: /sysroot/lib is not the right symlinks.
Jul 11 19:52:19 localhost systemd-udevd[376]: IMPORT{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Jul 11 19:52:20 localhost systemd-tmpfiles[412]: /lib is not the right symlinks.
Jul 11 19:52:22 localhost systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Jul 11 19:52:23 core-03 systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Jul 11 19:52:24 core-03 systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Jul 11 19:53:06 core-03 systemd-udevd[376]: IMPORT{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
@crawford crawford added the os label Jul 11, 2014
@josh-padnick
Copy link

I am still seeing several non-critical errors in journalctl on a fresh boot as well. Here are some samples:

Dec 10 22:32:36 core-01 systemd[1]: Starting Network Service...
Dec 10 22:32:36 core-01 systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Dec 10 22:32:36 core-01 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s8          : gained carrier
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s3          : gained carrier
Dec 10 22:32:36 core-01 systemd-networkd[808]: lo              : gained carrier
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s3          : link configured
Dec 10 22:32:36 core-01 systemd-networkd[808]: lo              : link configured
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s3          : DHCPv4 address 10.0.2.15/24 via 10.0.2.2
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s8          : link configured
Dec 10 22:32:36 core-01 systemd-networkd[808]: enp0s3          : link configured
Dec 10 22:32:36 core-01 systemd[1]: Started Network Service.
...
Dec 10 22:32:36 core-01 systemd[1]: Startup finished in 412ms (kernel) + 1.579s (initrd) + 6.591s (userspace) = 8.583s.
Dec 10 22:32:36 core-01 sudo[832]: core : TTY=unknown ; PWD=/home/core ; USER=root ; COMMAND=/bin/bash -l
Dec 10 22:32:36 core-01 sudo[837]: core : TTY=unknown ; PWD=/home/core ; USER=root ; COMMAND=/bin/bash -l
Dec 10 22:32:36 core-01 systemd[1]: Starting system-user\x2dcloudinit.slice.
...
Dec 10 22:32:36 core-01 systemd[1]: Starting etcd...
Dec 10 22:32:36 core-01 systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument
Dec 10 22:32:36 core-01 systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Dec 10 22:32:36 core-01 systemd[1]: Started etcd.
...
Dec 10 22:33:16 core-01 systemd-udevd[403]: IMPORT{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15

@andreas-venturini
Copy link

Just adding to this (note the last line below)

coreos0 ~ $ sudo journalctl -b
[...]
Jan 02 02:07:52 localhost systemd[1]: systemd 218 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Jan 02 02:07:52 localhost systemd[1]: Detected virtualization 'vmware'.
Jan 02 02:07:52 localhost systemd[1]: Detected architecture 'x86-64'.
Jan 02 02:07:52 localhost systemd[1]: Running with unpopulated /etc.
Jan 02 02:07:52 localhost systemd[1]: Initializing machine ID from random generator.
Jan 02 02:07:52 localhost systemd[1]: Populated /etc with preset unit settings.
Jan 02 02:07:53 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 02 02:07:53 localhost systemd[1]: Started Create Static Device Nodes in /dev.
Jan 02 02:07:53 localhost systemd[1]: Starting Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Reached target Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Started udev Coldplug all Devices.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Wait for Complete Device Initialization...
Jan 02 02:07:53 localhost systemd[1]: Started Flush Journal to Persistent Storage.
Jan 02 02:07:53 localhost systemd[1]: Started Rebuild Hardware Database.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Kernel Device Manager...
Jan 02 02:07:53 localhost systemd-udevd[416]: starting version 218
Jan 02 02:07:53 localhost systemd-udevd[416]: RUN{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Jan 02 02:07:52 localhost systemd[1]: systemd 218 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Jan 02 02:07:52 localhost systemd[1]: Detected virtualization 'vmware'.
Jan 02 02:07:52 localhost systemd[1]: Detected architecture 'x86-64'.
Jan 02 02:07:52 localhost systemd[1]: Running with unpopulated /etc.
Jan 02 02:07:52 localhost systemd[1]: Initializing machine ID from random generator.
Jan 02 02:07:52 localhost systemd[1]: Populated /etc with preset unit settings.
Jan 02 02:07:53 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 02 02:07:53 localhost systemd[1]: Started Create Static Device Nodes in /dev.
Jan 02 02:07:53 localhost systemd[1]: Starting Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Reached target Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Started udev Coldplug all Devices.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Wait for Complete Device Initialization...
Jan 02 02:07:53 localhost systemd[1]: Started Flush Journal to Persistent Storage.
Jan 02 02:07:53 localhost systemd[1]: Started Rebuild Hardware Database.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Kernel Device Manager...
Jan 02 02:07:53 localhost systemd-udevd[416]: starting version 218
Jan 02 02:07:53 localhost systemd-udevd[416]: RUN{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Jan 02 02:07:52 localhost systemd[1]: systemd 218 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Jan 02 02:07:52 localhost systemd[1]: Detected virtualization 'vmware'.
Jan 02 02:07:52 localhost systemd[1]: Detected architecture 'x86-64'.
Jan 02 02:07:52 localhost systemd[1]: Running with unpopulated /etc.
Jan 02 02:07:52 localhost systemd[1]: Initializing machine ID from random generator.
Jan 02 02:07:52 localhost systemd[1]: Populated /etc with preset unit settings.
Jan 02 02:07:53 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Jan 02 02:07:53 localhost systemd[1]: Started Create Static Device Nodes in /dev.
Jan 02 02:07:53 localhost systemd[1]: Starting Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Reached target Local File Systems (Pre).
Jan 02 02:07:53 localhost systemd[1]: Started udev Coldplug all Devices.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Wait for Complete Device Initialization...
Jan 02 02:07:53 localhost systemd[1]: Started Flush Journal to Persistent Storage.
Jan 02 02:07:53 localhost systemd[1]: Started Rebuild Hardware Database.
Jan 02 02:07:53 localhost systemd[1]: Starting udev Kernel Device Manager...
Jan 02 02:07:53 localhost systemd-udevd[416]: starting version 218
Jan 02 02:07:53 localhost systemd-udevd[416]: RUN{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15

@psi-4ward
Copy link

also have
systemd-udevd[500]: RUN{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15

@LoicMahieu
Copy link 

Mar 04 09:16:02 localhost systemd-journal[432]: Runtime journal is using 8.0M (max allowed 197.8M, trying to leave 296.7M free of 1.9G available → current limit 197.8M).
Mar 04 09:16:02 localhost systemd-journal[432]: Permanent journal is using 8.7M (max allowed 216.2M, trying to leave 324.3M free of 1.8G available → current limit 216.2M).
Mar 04 09:16:02 localhost systemd-journal[432]: Time spent on flushing to /var is 1.562ms for 2 entries.
Mar 04 09:16:02 localhost systemd-journald[96]: Received SIGTERM from PID 1 (systemd).
Mar 04 09:16:02 localhost systemd-journal[432]: Journal started
Mar 04 09:15:58 localhost systemd[1]: systemd 218 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP -GCRYPT -GNUTLS -ACL -XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Mar 04 09:15:58 localhost systemd[1]: Detected virtualization 'kvm'.
Mar 04 09:15:58 localhost systemd[1]: Detected architecture 'x86-64'.
Mar 04 09:15:58 localhost systemd[1]: Running with unpopulated /etc.
Mar 04 09:15:58 localhost systemd[1]: Initializing machine ID from KVM UUID.
Mar 04 09:16:00 localhost systemd[1]: Populated /etc with preset unit settings.
Mar 04 09:16:02 localhost systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 04 09:16:02 localhost systemd[1]: Started Create Static Device Nodes in /dev.
Mar 04 09:16:02 localhost systemd[1]: Starting Local File Systems (Pre).
Mar 04 09:16:02 localhost systemd[1]: Reached target Local File Systems (Pre).
Mar 04 09:16:02 localhost systemd[1]: Started Flush Journal to Persistent Storage.
Mar 04 09:16:03 localhost systemd[1]: Started Rebuild Hardware Database.
Mar 04 09:16:03 localhost systemd[1]: Starting udev Kernel Device Manager...
Mar 04 09:16:03 localhost systemd-udevd[444]: starting version 218
Mar 04 09:16:03 localhost systemd-udevd[444]: RUN{builtin}: 'uaccess' unknown /usr/lib64/udev/rules.d/73-seat-late.rules:15
Mar 04 09:16:03 localhost systemd[1]: Started udev Kernel Device Manager.
Mar 04 09:16:04 localhost systemd[1]: Found device QEMU_HARDDISK OEM.
Mar 04 09:16:04 localhost systemd[1]: Mounting /usr/share/oem...
Mar 04 09:16:04 localhost kernel: EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: commit=600
Mar 04 09:16:04 localhost systemd[1]: Mounted /usr/share/oem.
Mar 04 09:16:04 localhost systemd[1]: Starting Rebuild Dynamic Linker Cache...
Mar 04 09:16:05 localhost systemd[1]: Started udev Wait for Complete Device Initialization.
Mar 04 09:16:05 localhost systemd[1]: Starting Activation of LVM2 logical volumes...
Mar 04 09:16:05 localhost lvm[475]: No volume groups found
Mar 04 09:16:06 localhost systemd[1]: Started Activation of LVM2 logical volumes.
Mar 04 09:16:06 localhost systemd[1]: Starting Encrypted Volumes.
Mar 04 09:16:06 localhost systemd[1]: Reached target Encrypted Volumes.
Mar 04 09:16:06 localhost systemd[1]: Starting Activation of LVM2 logical volumes...
Mar 04 09:16:06 localhost lvm[477]: No volume groups found
Mar 04 09:16:06 localhost systemd[1]: Started Activation of LVM2 logical volumes.
Mar 04 09:16:06 localhost systemd[1]: Starting Local File Systems.
Mar 04 09:16:06 localhost systemd[1]: Reached target Local File Systems.
Mar 04 09:16:06 localhost systemd[1]: Starting Rebuild Journal Catalog...
Mar 04 09:16:06 localhost systemd[1]: Starting Create missing system files...
Mar 04 09:16:06 localhost systemd[1]: Started Commit a transient machine-id on disk.
Mar 04 09:16:06 localhost systemd[1]: Starting Create Volatile Files and Directories...
Mar 04 09:16:06 localhost systemd[1]: Starting Activation of LVM2 logical volumes...
Mar 04 09:16:06 localhost systemd[1]: Started Rebuild Journal Catalog.
Mar 04 09:16:06 localhost systemd[1]: Started Create missing system files.
Mar 04 09:16:06 localhost lvm[485]: No volume groups found
Mar 04 09:16:06 localhost systemd[1]: Started Activation of LVM2 logical volumes.
Mar 04 09:16:06 localhost systemd[1]: Started Create Volatile Files and Directories.
Mar 04 09:16:06 localhost systemd[1]: Starting Clean up broken links in /etc/ssl/certs...
Mar 04 09:16:06 localhost systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Mar 04 09:16:06 localhost systemd[1]: Starting Remote File Systems.
Mar 04 09:16:06 localhost systemd[1]: Reached target Remote File Systems.
Mar 04 09:16:06 localhost systemd[1]: Started Update UTMP about System Boot/Shutdown.
Mar 04 09:16:06 localhost systemd[1]: Started Clean up broken links in /etc/ssl/certs.

@Vishant0031
Copy link

On coreos 633.1.0 stable; systemd services are not starting and the journalctl logs.
failed to set memory.limit_in_bytes on invalid argument

@slallema
Copy link

slallema commented May 4, 2015

I had that problem with 668.2.0 alpha and solved it by removing rootfstype=btrfsfrom the kernel command line. Apparently the writable fs is achieved with tmpfs now.

@crawford crawford mentioned this issue Sep 23, 2015
Closed
@crawford crawford mentioned this issue Feb 25, 2016
Closed
@simonvanderveldt
Copy link

simonvanderveldt commented Dec 20, 2016 •
edited

@crawford @urzds FYI the issue with 73-seat-late.rules is this one systemd/systemd#4107
Is there a specific reason ACL/libacl is disabled for CoreOS's systemd build?

@marineam
Copy link

marineam commented Dec 20, 2016 via email

@simonvanderveldt
Copy link

simonvanderveldt commented Dec 20, 2016 •
edited

@marineam thanks for the response.
Whilst I'm not really familiar with all the details a quick search gave me this page https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/ which describes what it does an how it works.

Basically it's an action that gets triggered by udev based on on tags that are already set on devices from another rules file (70-uaccess.rules) that sets up ACLs for devices for the current user.

Now in how much trouble you are if this doesn't work I don't know, though it seems reasonable to expect that in some cases some devices, especially on bare metal when plugging something in, will be inaccessible to the active user.

@marineam
Copy link

@simonvanderveldt possibly, though it would only be applicable to a user logging into the console which isn't a common use for coreos beyond debugging. That said there's probably no real advantage to leaving it off either so turning on the USE flag should be fine.

@bgilbert
Copy link
Contributor

Thank you for reporting this issue. Unfortunately, we don't think we'll end up addressing it in Container Linux.

We're now working on Fedora CoreOS, the successor to Container Linux, and we expect most major development to occur there instead. Meanwhile, Container Linux will be fully maintained into 2020 but won't see many new features. We appreciate your taking the time to report this issue and we're sorry that we won't be able to address it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/stability closed/rejected component/distro kind/cleanup priority/P2 team/os
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@marineam @simonvanderveldt @bgilbert @crawford @LoicMahieu @psi-4ward @slallema @josh-padnick @andreas-venturini @Vishant0031