Bug ID 1218618
Summary systemctl is-system-running - degraded after update
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS openSUSE Tumbleweed
Status NEW
Severity Major
Priority P5 - None
Component Basesystem
Assignee screening-team-bugs@suse.de
Reporter michael.trapp@sap.com
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

Hello,

with the last update on Tumbleweed we've noticed the following issue after
rebooting the server


# systemctl is-system-running
degraded

# systemctl
● systemd-vconsole-setup.service                                               
      loaded failed failed    Virtual Console Setup

# systemctl status systemd-vconsole-setup.service
× systemd-vconsole-setup.service - Virtual Console Setup
     Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service;
static)
     Active: failed (Result: exit-code) since Mon 2024-01-08 12:02:41 CET; 5min
ago
   Duration: 9.112s
       Docs: man:systemd-vconsole-setup.service(8)
             man:vconsole.conf(5)
    Process: 827 ExecStart=/usr/lib/systemd/systemd-vconsole-setup
(code=exited, status=1/FAILURE)
   Main PID: 827 (code=exited, status=1/FAILURE)
        CPU: 10ms

Jan 08 12:02:41 tumbleweed systemd[1]: Starting Virtual Console Setup...
Jan 08 12:02:41 tumbleweed systemd-vconsole-setup[827]: No usable source
console found: Device or resource busy
Jan 08 12:02:41 tumbleweed systemd[1]: systemd-vconsole-setup.service: Main
process exited, code=exited, status=1/FAILURE
Jan 08 12:02:41 tumbleweed systemd[1]: systemd-vconsole-setup.service: Failed
with result 'exit-code'.
Jan 08 12:02:41 tumbleweed systemd[1]: Failed to start Virtual Console Setup.


a journalctl for the service did not provide useful details but a strace in the
service file showed

824   access("/dev/vcs2", F_OK)         = -1 ENOENT (No such file or directory)
824   access("/dev/vcs3", F_OK)         = -1 ENOENT (No such file or directory)
...

The service can be started manually because from the active session we can see

# ls -l /dev/vcs*
crw-rw---- 1 root tty 7,   0 Jan  8 12:18 /dev/vcs
crw-rw---- 1 root tty 7,   1 Jan  8 12:18 /dev/vcs1
crw-rw---- 1 root tty 7,   2 Jan  8 12:18 /dev/vcs2
crw-rw---- 1 root tty 7,   3 Jan  8 12:18 /dev/vcs3
...

# systemctl list-dependencies systemd-vconsole-setup.service
systemd-vconsole-setup.service
● ├─kbdsettings.service
● └─system.slice


Would you please check and fix the issue.

Kind regards
Michael


You are receiving this mail because: