[lucid] bootlogd not working (sysvinit) - nothing has been logged yet

[pet]

Binary package hint: sysvinit

i tried to set up the boot logging on feisty

first i enabled in the file : /etc/default/bootlogd (no-->yes)
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=yes

then i turned it also on in the systemsettings.

but /var/log/boot or /var/log/boot.log always shows: "(Nothing has been logged yet.)"

then i tried to install sysvinit with apt-get but this put's me on bash after a restart (no X), and it removes upstart.

regards peter

===================
Notes: unclean install - upgrade form Feisty, through Gutsy to Hardy

And on Jaunty after doing the changes required in /etc/default/booglogd , shutting down the system and restarting it - same message 'Nothing has been logged in yet' in /var/log/boot

[Pev (pevik)]

Well, a bit late, but:

in script which is suppose to start logging daemon is

DAEMON=/sbin/bootlogd
[ -x "$DAEMON" ] || exit 0

So you have to install a package which have file 'sbin/bootlogd'. So run command

apt-get install sysvinit

Pev

[vito (ovitorio)]

Hi, Pev.

I've seen you already placed this "nice" suggestion here:

https://bugs.launchpad.net/upstart/+bug/98955

Apparently you did it without bothering reading full discussion. The problem with your suggestion is that neither Feisty nor Hardy users cannot install sysvinit. There is a known packages conflict there. The installation of sysvinit removes important packages from a system and thus brakes it.

I do not go into details here, since the discussion mentioned above already provides the full info, as well as the only known to me up to date workaround. Though I've not tried it myself yet. But some people did and get positive results.

Again, your advice is harmful and should not be spread so carelessly.

Thank you.

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[vito (ovitorio)]

Teej, does your message mean that these of us who runs Ubuntu 8.04 LTS would stay on cold until the next LTS release? Or are you going to update us as well?

These is a long expected feature. And no changes so far. :-(

Thanks.

[xteejx (xteejx)]

Of course not. The reason we ask this is that the problem may be fixed in a later version, and the fixes may be able to be backported into previous versions, i.e. Hardy, Intrepid, etc. Do you already have backports enabled? If not, can you try enabling it in Software Sources and updating everything fully, and report back if this fixes it. If not, would it be possible to try and reproduce this, as I am unable to reproduce it in Jaunty, it may be due to a specific hardware configuration. Thank you.

[vito (ovitorio)]

Well, Teej,

I've tested it on my Hardy as you suggested after enabling backports and making a full update with it. No changes.

I mean after setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and setting bottlogd to be started at boot time nothing was logged on my machine.

The only thing I can see is the same sacramental phrase:"Nothing has been logged yet."

One more detail if it helps. The Hardy on my laptop is not a clean install but an upgrade from Feisty to Gutsy and then to Hardy.

I have a clean install on my desktop but I'm rather reluctant to use backports on it, since it is my main machine. I may change up my mind if you convince me though. :-) I do not know if it might make any difference.

[xteejx (xteejx)]

Ok, so no fixes for this have been backported. Note: backports are *usually* ok for normal desktop users, I wouldn't advise it for a server install, but a lot of things that work in later versions are pulled back. I am marking this as Low and Confirming it.

[Shirish Agarwal (shirishag75)]

Hi all,
 Doing it on a friend's lappy. Its on jaunty and even after doing the
changes required in /etc/default/booglogd , shutting down the system
and restarting it don't have anything except the same message 'Nothing
has been logged in yet' in /var/log/boot

--
          Regards,
          Shirish Agarwal
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

[xteejx (xteejx)]

Thanks for the update. There should be enough information here for a developer to see where the problem is, so I'm going to mark this as Triaged and let them handle it from here.

[Yosef Karo (yos)]

This issue is affecting me now in karmic and while I was testing lucid. I am having issues at boot up and these logs would be a great help to me to narrow down the problem but these logs continue to remain unavailable.

-Yos

[Paolo Maero (fabrica64)]

bootlogd is simply not started at boot, you have to ad it:
# cd /etc
# ln -s ../init.d/bootlogd S08bootlogd

[George Politis (gpolitis)]

I think this bug is invalid, at least in Lucid. Lucid now includes Plymouth, which logs all console messages into /var/log/boot.log

[DEXTER (mydexterid)]

Debian already solved the issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681639

Please fix it in ubuntu!