[opensuse] Why is /var/log/boot.msg not written to with systemd?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk7SyywACgkQtTMYHG2NR9Xr9gCfUspXFgAfJoRm5DweoOMsr3Lk 9iEAniAB9V3w1WyzV6g2+Db+WP2RPn+X =4/Jh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Nov 28, 2011 at 12:43:33AM +0100, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug,
I see this as a bug. But hey, that what systemd is for. ;)
is it logged somewhere else?
All you have is the output of the dmesg command. Please check bugzilla if this is already reportted. If you have to report it please assign it to Frederic. Thanks. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-11-28 01:15, Lars Müller wrote:
On Mon, Nov 28, 2011 at 12:43:33AM +0100, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug,
I see this as a bug. But hey, that what systemd is for. ;)
Grrrr! :-)
is it logged somewhere else?
All you have is the output of the dmesg command.
Please check bugzilla if this is already reportted. If you have to report it please assign it to Frederic.
As far as I can see, no it wasn't reported. Did so. But there are more than 10 "Frederic", bugzilla tells me. Bug 732933 - systemd does not write to /var/log/boot.msg - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk7S2ecACgkQtTMYHG2NR9VLhwCgiL9NkdFOiVOyee+IhcvZNEg9 YW8AoJjMmrdJhkf9w/JcA5oZ/DBULQZi =66Na -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/11/11 20:43, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
Not a bug, you have to use dmesg, it has to be documented somewhere I think though. (bye bye old tools) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 27 November 2011 22:04:31 Cristian =?ISO-8859-1?Q?Rodr=EDguez?= wrote:
On 27/11/11 20:43, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
Not a bug, you have to use dmesg, it has to be documented somewhere I think though. (bye bye old tools)
That is an incredibly serious bug, which will make supporting and debugging a system that much more difficult. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-11-28 02:04, Cristian Rodríguez wrote:
On 27/11/11 20:43, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
Not a bug, you have to use dmesg, it has to be documented somewhere I think though. (bye bye old tools)
No no, that is absurd. Linux is supposed to log everything. dmesg is volatile. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk7S4M0ACgkQtTMYHG2NR9X83gCfcJiBqJe3VIeOaICYh13f7PZq fFsAoI6JRF/XqB8mPkebrzLbDndwWCyz =9Fn5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/11/11 22:15, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-28 02:04, Cristian Rodríguez wrote:
On 27/11/11 20:43, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
Not a bug, you have to use dmesg, it has to be documented somewhere I think though. (bye bye old tools)
No no, that is absurd. Linux is supposed to log everything. dmesg is volatile.
/var/log/messages will rotate at your discretion, not volatile (by default weekly and keeps 4 weeks of backlogs) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
mine does ??? ~ > l /var/log/boot* -rw-r----- 1 root root 0 Sep 7 08:53 /var/log/boot.log -rw-r--r-- 1 root root 111400 Nov 23 20:51 /var/log/boot.msg -rw-r--r-- 1 root root 102529 Nov 15 16:45 /var/log/boot.omsg but istr that systemd would not replace sysvinit by upgrade/zypper dup which I did to reach 12.1 (from 11.4/tumbleweed). I do have systemd rather than sysvinit but have noticed no problems. Postfix, nfs, spamd, sshd, and other all start on boot, at least I haven't had call to start anything by hand :^). gud luk, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-11-28 02:49, Cristian Rodríguez wrote:
/var/log/messages will rotate at your discretion, not volatile (by default weekly and keeps 4 weeks of backlogs)
AFAIK this file does not contain the boot log. If it does you would have told me so at the beginning... - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk7S7xQACgkQtTMYHG2NR9V3pwCgihyJfQNlL33Yx9TTa84vJZmH /qMAniorMZ9cjVk+NezUnIMYiEDg4753 =Teuc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/11/11 23:16, Carlos E. R. wrote:
AFAIK this file does not contain the boot log. If it does you would have told me so at the beginning...
All messages all logged to syslog.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 27/11/11 23:16, Carlos E. R. wrote:
AFAIK this file does not contain the boot log. If it does you would have told me so at the beginning...
All messages all logged to syslog..
Except for output from init-scripts. Bug#732353 -- Per Jessen, Zürich (4.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 28 November 2011 01:49:28 Cristian Rodríguez wrote:
On 27/11/11 22:15, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-11-28 02:04, Cristian Rodríguez wrote:
On 27/11/11 20:43, Carlos E. R. wrote:
Why is /var/log/boot.msg not written to with systemd? Is it a bug, is it logged somewhere else?
Not a bug, you have to use dmesg, it has to be documented somewhere I think though. (bye bye old tools)
No no, that is absurd. Linux is supposed to log everything. dmesg is volatile.
/var/log/messages will rotate at your discretion, not volatile (by default weekly and keeps 4 weeks of backlogs)
A Huge BUG This systend thing looks like it is going to need to be killed off . I have not said much so far on this but from what i am see so far systemd is a pile of junk yes devs hope you are reading this JUNK got back to school and start again you are heading the windows way . Why people have this stupid fasination with quick boot i will never know nad after all that is what this is about trying to force unwanted / unneeded on us the users . Right now Opensuse needs someone at the helm that has the balls to say get on yer bike to the dangerous distro distroying junk like systemd and this silly idea of moving the filing system layout around to ONE big bin dir not good not healthy all in all very bad for the distro .. This is NOT Redhat stop sucking up to their butts Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.10-0.4-desktop KDE Development Platform: 4.6.5 (4.6.5) "release 7" 07:50 up 1 day 4:11, 4 users, load average: 0.20, 0.22, 0.15 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 28 November 2011, Per Jessen wrote:
Cristian Rodríguez wrote:
On 27/11/11 23:16, Carlos E. R. wrote:
AFAIK this file does not contain the boot log. If it does you would have told me so at the beginning...
All messages all logged to syslog..
Except for output from init-scripts. Bug#732353
Are kernel messages at boot time still logged completely or also missed? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Nov 28, 2011 at 01:46:31AM +0100, Carlos E. R. wrote: [ 8< ]
As far as I can see, no it wasn't reported. Did so. But there are more than 10 "Frederic", bugzilla tells me.
Federic Crozat, who does all the systemd stuff.
Bug 732933 - systemd does not write to /var/log/boot.msg
Thx. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-11-28 10:08, Rüdiger Meier wrote:
On Monday 28 November 2011, Per Jessen wrote:
Cristian Rodríguez wrote:
On 27/11/11 23:16, Carlos E. R. wrote:
AFAIK this file does not contain the boot log. If it does you would have told me so at the beginning...
Mi initial question asked if the boot messages were logged somewhere else. Apparently they are.
All messages all logged to syslog..
Except for output from init-scripts. Bug#732353
Are kernel messages at boot time still logged completely or also missed?
I see there are a lot of messages in the messages log file that previously (ie, systemv) were not:
Nov 27 23:45:45 Elanor kernel: [ 0.000000] Initializing cgroup subsys cpuset Nov 27 23:45:45 Elanor kernel: [ 0.000000] Initializing cgroup subsys cpu Nov 27 23:45:45 Elanor kernel: [ 0.000000] Linux version 3.1.0-1.2-desktop (geeko@buildhost) (gcc version 4.6.2 (SUSE Linux) ) #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) Nov 27 23:45:45 Elanor kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/f1dad273-43f7-4908-8b87-9d1e127d1a8b resume=/dev/disk/by-label/Swap splash=verbose quiet vga=0x317 Nov 27 23:45:45 Elanor kernel: [ 0.000000] Disabled fast string operations Nov 27 23:45:45 Elanor kernel: [ 0.000000] BIOS-provided physical RAM map: Nov 27 23:45:45 Elanor kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable) Nov 27 23:45:45 Elanor kernel: [ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
that I believe are the kernel boot messages. I'm not sure I like them there. However, I'm trying to see why the network is reported as failed, when it is working, and only seeing this:
Nov 27 23:45:46 Elanor systemd[1]: NetworkManager.service: control process exited, code=exited status=1 Nov 27 23:45:46 Elanor systemd[1]: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Nov 27 23:45:46 Elanor systemd[1]: Unit NetworkManager.service entered failed state. ... Nov 27 23:45:48 Elanor network[944]: Setting up (localfs) network interfaces: Nov 27 23:45:49 Elanor network[944]: lo Nov 27 23:45:49 Elanor ifup: lo Nov 27 23:45:49 Elanor ifup: lo Nov 27 23:45:49 Elanor ifup: IP address: 127.0.0.1/8 Nov 27 23:45:49 Elanor network[944]: lo IP address: 127.0.0.1/8 ... Nov 27 23:45:50 Elanor network[944]: ..done eth0 device: Intel Corporation 82545EM Gigabit Ethernet Co
which does not explain it. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk7TawEACgkQtTMYHG2NR9X0ZQCfWYPMmsqgMTtlawX50hyUbDSS WJ8AnArGnhG9H21B9jvxSuJkoJdLniq3 =1qi8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, November 28, 2011 07:58:51 AM Peter Nikolic wrote: ...
Why people have this stupid fasination with quick boot i will never know
Fast boot is just side effect of having smarter way to start computer and if that is all you know about systemd then I'm not surprised with the rest of your comment. Systemd is here to stay as it makes sysadmins life easier. You should see comments by people that make for living administering systems. That Fedora guy came first on idea is not very affirmative for openSUSE as leader in a new trends, but, as usually, openSUSE has tradition in something else, making new trends polished, easy to swallow. To close the case: Complaining and calling the names will not help to polish openSUSE. Reporting problems will.
Pete .
-- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-11-28 at 01:46 +0100, Carlos E. R. wrote:
Bug 732933 - systemd does not write to /var/log/boot.msg
WONTFIX “won't fix, /var/log/boot.msg is not supported by systemd.” :-( - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk7hXPEACgkQtTMYHG2NR9X0KgCfZaJLnwDYc400pIZXhS2+svLa aM4AoJMYbCjifu7KwGOzM3qdXMDBp6Lj =w169 -----END PGP SIGNATURE-----
On 08/12/11 21:57, Carlos E. R. wrote:
WONTFIX
“won't fix, /var/log/boot.msg is not supported by systemd.”
:-(
it told you so ;) it is not a bug! early boot information can be found in /var/log/messages and in the future you will likely be able ask journald about it too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Anders Johansson -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Lars Müller -
Patrick Shanahan -
Per Jessen -
Peter Nikolic -
Rajko M. -
Rüdiger Meier