Hi list, on my TW systems, there is a boot.log created that catches the on-screen messages from the boot process. I have now some Leap 15.2 systems, and there I don't have those. Is there a way to enable this?
On 13/04/2021 13.40, Peter Suetterlin wrote:
Hi list,
on my TW systems, there is a boot.log created that catches the on-screen messages from the boot process.
I have now some Leap 15.2 systems, and there I don't have those. Is there a way to enable this?
boot.log is created by the plymouth boot thing. But you should be able to see those messages in the journal or syslog - although there is some problem in 15.2 where syslog doesn't. I have not studied why yet. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
boot.log is created by the plymouth boot thing.
:( That one isn't installed (the machine is a server somewhere in a corner...) Indeed the first message in the boot.logs is [ OK ] Started Show Plymouth Boot Screen.
But you should be able to see those messages in the journal or syslog - although there is some problem in 15.2 where syslog doesn't. I have not studied why yet.
Journalctl doen't list those (for me, or am I missing some option switch?), and there's no extra syslog, only the journalctl one. Thanks!
On 13/04/2021 14.12, Peter Suetterlin wrote:
Carlos E. R. wrote:
boot.log is created by the plymouth boot thing.
:( That one isn't installed (the machine is a server somewhere in a corner...) Indeed the first message in the boot.logs is [ OK ] Started Show Plymouth Boot Screen.
Yep.
But you should be able to see those messages in the journal or syslog - although there is some problem in 15.2 where syslog doesn't. I have not studied why yet.
Journalctl doen't list those (for me, or am I missing some option switch?),
No, they should be there. journalctl -b should start the display at the boot of the current session. If the directory "/var/log/journal/" exists, then it will preserve previous sessions.
and there's no extra syslog, only the journalctl one.
Syslog has to be installed separately. I recommend "rsyslogd" -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
Journalctl doen't list those (for me, or am I missing some option switch?),
No, they should be there.
journalctl -b
Just for clarity: boot.log (as created by plymouth) does not contain the kernel messages, but those messages printed on the terminal during the system startup, like [ OK ] Reached target Initrd Root Device. (Of course, especially the fail messages are of interest there.) I cannot see those in the journalctl output. At least not on the Leap machine. Strange enough, I see comparable output on a Tumbleweed machine, coming from systemd: Mar 27 10:42:16 speedy systemd[1]: Reached target Initrd Root File System. Maybe a difference coming from older systemd?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-04-14 at 14:00 +0100, Peter Suetterlin wrote:
Carlos E. R. wrote:
Journalctl doen't list those (for me, or am I missing some option switch?),
No, they should be there.
journalctl -b
Just for clarity: boot.log (as created by plymouth) does not contain the kernel messages, but those messages printed on the terminal during the system startup, like [ OK ] Reached target Initrd Root Device.
Ah.
(Of course, especially the fail messages are of interest there.)
For that, I have: /etc/systemd/system/helloworld.service: Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target [Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld [Install] WantedBy=multi-user.target WantedBy=graphical.target and /root/ThingsNeededForBoot/helloworld has: #!/bin/bash echo echo "-----" echo systemctl --failed --no-pager if [ $? -eq 0 ] ; then cat /root/ThingsNeededForBoot/hal9.au > /dev/audio 2> /dev/null & /usr/bin/logger -t Mine -p daemon.info "Saying hello world." else echo echo "Something failed!" play -q /root/ThingsNeededForBoot/abitsilly.wav /usr/bin/logger -t Mine -p daemon.info "Something failed on boot." fi The sound thing fails, but the part of interest for you is the running of "systemctl --failed --no-pager", that prints on vttty1.
I cannot see those in the journalctl output. At least not on the Leap machine. Strange enough, I see comparable output on a Tumbleweed machine, coming from systemd: Mar 27 10:42:16 speedy systemd[1]: Reached target Initrd Root File System.
Maybe a difference coming from older systemd?
Dunno... - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHb1ERwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+XkAnieZ+o5GRs9kaStomT/G rzT2UsHBAKCDlZR56i+JOTs8DTVej5CTBOkFeA== =8yLI -----END PGP SIGNATURE-----
Carlos E. R. wrote:
On Wednesday, 2021-04-14 at 14:00 +0100, Peter Suetterlin wrote:
Journalctl doen't list those (for me, or am I missing some option switch?),
and /root/ThingsNeededForBoot/helloworld has:
#!/bin/bash echo echo "-----" echo
systemctl --failed --no-pager
Aah. Likely, that is the "option" I wasn't aware of :D
Peter Suetterlin wrote:
Hi list,
on my TW systems, there is a boot.log created that catches the on-screen messages from the boot process.
I have now some Leap 15.2 systems, and there I don't have those.
may be /var/log/boot.msg ? -- Per Jessen, Zürich (6.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there... But there seems to be a package blog-plymouth: The Blogd daemon can be used as a replacement for Plymouth in situations where a splash screen and/or usage of a frame buffer is unwanted.... That one will also copy the log to /var/log/boot.log However, it claims to be a 'plymouth agent', but installing it does not pull any plymouth packages in.... I'll see how it goes. I don't (like to) boot that machine too often :P
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd. -- Per Jessen, Zürich (9.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
s/systemd/syslog-service/ Maybe check that you have that klog.service installed. tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2021-04-11 17:25:49 CEST; 1 day 21h ago Process: 1123 ExecStart=/bin/sh -c test -c /dev/tty10 && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 || : (code=exited, status=0/SUCCESS) Process: 1122 ExecStart=/bin/sh -c test -s /dev/shm/initrd.msg && /bin/cat /dev/shm/initrd.msg >> /var/log/boot.msg || : (code=exited, status=0/SUCCESS) Process: 1120 ExecStart=/bin/sh -c /bin/dmesg -r > /var/log/boot.msg (code=exited, status=0/SUCCESS) Process: 1118 ExecStart=/bin/sh -c test -s /var/log/boot.msg && /bin/mv -f /var/log/boot.msg /var/log/boot.omsg || : (code=exited, status=0/SUCCESS) Main PID: 1123 (code=exited, status=0/SUCCESS) Tasks: 0 CGroup: /system.slice/klog.service Apr 11 17:25:48 tattoo2 systemd[1]: Starting Early Kernel Boot Messages... Apr 11 17:25:49 tattoo2 systemd[1]: Started Early Kernel Boot Messages. -- Per Jessen, Zürich (8.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead) Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
Peter Suetterlin wrote:
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead)
Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
I did notice it was also disabled on an old 13.2 system of my own. If I were you, I would be very tempted to just enable it. -- Per Jessen, Zürich (8.7°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland.
On Wed, 14 Apr 2021 13:36:43 +0200 Per Jessen <per@computer.org> wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead)
Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
I did notice it was also disabled on an old 13.2 system of my own. If I were you, I would be very tempted to just enable it.
Note that klog.service and klogd.service are not the same! And have different descriptions.
On Wed, 14 Apr 2021 21:23:22 +0100 Dave Howorth <dave@howorth.org.uk> wrote:
On Wed, 14 Apr 2021 13:36:43 +0200 Per Jessen <per@computer.org> wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead)
Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
I did notice it was also disabled on an old 13.2 system of my own. If I were you, I would be very tempted to just enable it.
Note that klog.service and klogd.service are not the same! And have different descriptions.
# systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset> Active: active (exited) since Wed 2021-03-17 14:30:08 GMT; 4 weeks 0 days ago Main PID: 1179 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/klog.service Mar 17 14:30:08 acer-suse systemd[1]: Starting Early Kernel Boot Messages... Mar 17 14:30:08 acer-suse systemd[1]: Started Early Kernel Boot Messages. # systemctl status klogd ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor pres> Active: inactive (dead)
Dave Howorth wrote:
On Wed, 14 Apr 2021 13:36:43 +0200 Per Jessen <per@computer.org> wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead)
Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
I did notice it was also disabled on an old 13.2 system of my own. If I were you, I would be very tempted to just enable it.
Note that klog.service and klogd.service are not the same!
Very good point! I did not spot that. -- Per Jessen, Zürich (1.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-04-14 at 12:12 +0100, Peter Suetterlin wrote:
Per Jessen wrote:
Maybe check that you have that klog.service installed.
tattoo2:/var/log # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled)
Interesting, mine says ● klogd.service - System Kernel Logging Service Loaded: loaded (/usr/lib/systemd/system/klogd.service; disabled; vendor preset: disabled) Active: inactive (dead)
Telcontar:~ # systemctl status klog ● klog.service - Early Kernel Boot Messages Loaded: loaded (/usr/lib/systemd/system/klog.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2021-04-11 11:40:27 CEST; 3 days ago Process: 1488 ExecStart=/bin/sh -c test -c /dev/tty10 && /usr/sbin/klogconsole $KLOGCONSOLE_PARAMS -r10 || : (code=exited, status=0/SUCCESS) Process: 1487 ExecStart=/bin/sh -c test -s /dev/shm/initrd.msg && /bin/cat /dev/shm/initrd.msg >> /var/log/boot.msg || : (code=exited, status=0/SUCCESS) Process: 1485 ExecStart=/bin/sh -c /bin/dmesg -r > /var/log/boot.msg (code=exited, status=0/SUCCESS) Process: 1471 ExecStart=/bin/sh -c test -s /var/log/boot.msg && /bin/mv -f /var/log/boot.msg /var/log/boot.omsg || : (code=exited, status=0/SUCCESS) Main PID: 1488 (code=exited, status=0/SUCCESS) Tasks: 0 CGroup: /system.slice/klog.service Apr 11 11:40:27 Telcontar systemd[1]: Starting Early Kernel Boot Messages... Apr 11 11:40:27 Telcontar systemd[1]: Started Early Kernel Boot Messages. Telcontar:~ #
Not sure why it's preset: disabled here. Maybe because it's an upgrade from an old 42.3? But there are no conflicts from rpmconfigcheck...
Mine is also an upgrade from 42.3. How can I find when the service was enabled? There would be a symnlink :-? Yes, there is: cer@Telcontar:~> ll --full-time /etc/systemd/system/basic.target.wants/klog.service lrwxrwxrwx 1 root root 36 2019-01-07 16:18:05.151420453 +0100 /etc/systemd/system/basic.target.wants/klog.service -> /usr/lib/systemd/system/klog.service cer@Telcontar:~> Machine upgrade from 42.3 to 15.0 started at 2019-01-07 15:22:12+01:00, finished 2019-01-07 17:41:57+01:00. It fits. But then it was set automatically, a manual change by me would happen later. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHbUlxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVo6MAnA+Um4rjCUl+EpKFYlIF NX9QSlljAKCP7JP1q6DsKWsr/pcqHXtKiWEE4Q== =xcjC -----END PGP SIGNATURE-----
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-) -- Per Jessen, Zürich (7.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
In SysV init days, the script was 'boot.klog'. On my 10.3 machine, it is dated 2007. office64:/etc/init.d # l boot.klog -rwxr-xr-x 1 root root 1723 Jun 20 2007 boot.klog* -- Per Jessen, Zürich (8.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here. I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth. I don't know what writes them now, but it is not plymouth as I don't have it. cer@Telcontar:~> rpm -qa | grep -i plym cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I guess you don't have syslog installed. -- Per Jessen, Zürich (1.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
On 13/04/2021 23.32, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote: > > may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I guess you don't have syslog installed.
I certainly do. I have rsyslog installed. I always do. But you misunderstand, or I failed to explain well enough. I'll try again. Those two files went missing, but they reappeared. I don't know when, but my backups of august 2019 show them (15.0). I was not expecting them back, I stopped looking for them for years. My guess is they went on Leap 42.x. I will have to investigate on a virtual machine. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 13.04.2021 23:38, Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth.
This is /var/log/boot.log, not "boot log". "boot log" is too ambiguous.
I don't know what writes them now, but it is not plymouth as I don't have it.
If "them" refers to /var/log/boot.(o)msg - service klog.service which is part of syslog-service.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <8fdca991-468c-4c16-5bee-eb13c6a98cda@Telcontar.valinor> On Wednesday, 2021-04-14 at 08:08 +0300, Andrei Borzenkov wrote:
On 13.04.2021 23:38, Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote: > > may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth.
This is /var/log/boot.log, not "boot log". "boot log" is too ambiguous.
Intentionally :-) Not sure of the actual file name. cer@Telcontar:~> l /var/log/ | grep boot - -rw-r--r-- 1 root root 16675 Jun 10 2013 boot.log - -rw-r--r-- 1 root root 97668 Apr 11 11:40 boot.msg - -rw-r--r-- 1 root root 97709 Apr 10 22:19 boot.omsg cer@Telcontar:~>
I don't know what writes them now, but it is not plymouth as I don't have it.
If "them" refers to /var/log/boot.(o)msg - service klog.service which is part of syslog-service.
Yes, I know that now. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHbVaxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVTJkAn3/4mFe0MPl3T9FqQ6hY dKy1ZuruAKCMRuRviVodnM/GrvdDZh8sv14T2g== =zjw0 -----END PGP SIGNATURE-----
On 2021/04/13 22:38:07 +0200, Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote:
may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth. I don't know what writes them now, but it is not plymouth as I don't have it.
cer@Telcontar:~> rpm -qa | grep -i plym cer@Telcontar:~>
Maybe it is the blogd from blog package :) it is a dropin replacement for plymouth but without graphical splash screen and with working serial console support. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
Dr. Werner Fink wrote:
Maybe it is the blogd from blog package :) it is a dropin replacement for plymouth but without graphical splash screen and with working serial console support.
The package is actually named blog-plymouth, see my other post. I've installed it, but not yet booted since.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-04-14 at 10:13 +0200, Dr. Werner Fink wrote:
On 2021/04/13 22:38:07 +0200, Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote: > > may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth. I don't know what writes them now, but it is not plymouth as I don't have it.
cer@Telcontar:~> rpm -qa | grep -i plym cer@Telcontar:~>
Maybe it is the blogd from blog package :) it is a dropin replacement for plymouth but without graphical splash screen and with working serial console support.
cer@Telcontar:~> rpm -q blog blog-2.18-lp152.6.6.x86_64 cer@Telcontar:~> Curious, I do have it installed. News to me. What runs it? But the boot log comes from service klog. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHbWmxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVXJsAnivmpbTWeBRzH7HWXWuO YbDFTaZ/AJ9RHVgh6/rwvuCtxETvS7ro0Op/bw== =4MxI -----END PGP SIGNATURE-----
On 2021/04/14 13:48:43 +0200, Carlos E. R. wrote:
Maybe it is the blogd from blog package :) it is a dropin replacement for plymouth but without graphical splash screen and with working serial console support.
cer@Telcontar:~> rpm -q blog blog-2.18-lp152.6.6.x86_64 cer@Telcontar:~>
Curious, I do have it installed. News to me.
What runs it?
This package has two parts blog-plymouth to replace plymouth, that is provide all services even for dracut initrd, and blog which provides the daemon started within initrd. This daemon can switch root to survive switch from initrd to new root (done with the help of blog-switch-root.service). After /var/log becomes writable blogd move the old /var/log/boot.log to /var/log/boot.old and writes out the new /var/log/boot.log. After boot has finished the blogd gets stopped ... btw. on shutdown it will be finally restarted and then blogd appendes as long as possible to /var/log/boot.log. Werner
But the boot log comes from service klog.
This servive does move /var/log/boot.msg to /var/log/boot.omsg and then writes out /var/log/boot.msg as oneshot at boot. Only kernel messages can be found. Beside this console log level and log console is set. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
Dr. Werner Fink wrote:
But the boot log comes from service klog.
This servive does move /var/log/boot.msg to /var/log/boot.omsg and then writes out /var/log/boot.msg as oneshot at boot. Only kernel messages can be found. Beside this console log level and log console is set.
So this would only be a duplicate of what I get via journalctl, yes? Then there's no need to enable this....
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2021-04-14 at 14:54 +0200, Dr. Werner Fink wrote:
On 2021/04/14 13:48:43 +0200, Carlos E. R. wrote:
Maybe it is the blogd from blog package :) it is a dropin replacement for plymouth but without graphical splash screen and with working serial console support.
cer@Telcontar:~> rpm -q blog blog-2.18-lp152.6.6.x86_64 cer@Telcontar:~>
Curious, I do have it installed. News to me.
What runs it?
This package has two parts blog-plymouth to replace plymouth, that is provide all services even for dracut initrd, and blog which provides the daemon started within initrd. This daemon can switch root to survive switch from initrd to new root (done with the help of blog-switch-root.service). After /var/log becomes writable blogd move the old /var/log/boot.log to /var/log/boot.old and writes out the new /var/log/boot.log. After boot has finished the blogd gets stopped ... btw. on shutdown it will be finally restarted and then blogd appendes as long as possible to /var/log/boot.log. Werner
But the boot log comes from service klog.
This servive does move /var/log/boot.msg to /var/log/boot.omsg and then writes out /var/log/boot.msg as oneshot at boot. Only kernel messages can be found. Beside this console log level and log console is set.
I noticed "/etc/systemd/system/bootmsg.service" (a symlink to /usr/lib/systemd/system/klog.service), from package syslog-service-2.0-lp152.4.7.noarch: # /lib/systemd/system/klog.service # # This file is part of package systemd. # # Copyright (c) 2011 SuSE LINUX Products GmbH, Germany. # Author: Werner Fink # Please send feedback to http://www.suse.de/feedback # # Description: # # Create the well known /var/log/boot.msg # By using dmesg(1) the normal kernel and boot messages handled # by systemd will not disappear. The character device /dev/tty10 # will be created by udevd and therefore should exists only if # virtual consoles are available. ... So there are several components that may write the "boot log" file. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHb2Lhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVwc4AnjsDyLxYvDfQkAIuHqDO W455vXbBAJ4vXTkx8AE9xQoMD/YKU0HZllvkrg== =Lcql -----END PGP SIGNATURE-----
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Dave Howorth -
Dr. Werner Fink -
Per Jessen -
Peter Suetterlin