bootloogd does'nt work in 9.04

[NoOp]

On 12/18/2009 12:05 PM, Leonard Chatagnier wrote:
> Tom H wrote:
>>>> How to enable boot messages logging?
>>>> Enabling BOOTLOGD in /etc/default/syslogd does'nt work in
>>>> 9.04.
>>>> I'm trying to solve some init scripts upstart problems and
>>>> need a copy of
>>>> all messages sent to the console. Bootlogd seems to be the
>>>> answer but
>>>> apparently the bootlogd program is'nt installed.
>>>> I've seen some workarounds to install it and some comments
>>>> on why it is'nt  installed
>>>> But still I would like to ask all the experts here - what
>>>> would be the best way tol solve
>>>> this problem?
>>>>        
>>    
>>> I think bootlogd has been disabled in Ubuntu for the last
>>> several issues. I have asked about this same problem and AIR,
>>> the only reply was that it was disabled and can't be made to
>>> work.  I would like to get bootlogd working so if you find out
>>> how, please let me and the list know the solution. Regarding
>>> your info needed to troubleshoot, you can probably find all the
>>> boot messages outputs in /var/log/syslog, dmesg and /var/log/messages,
>>> debug and kernel logs. Not a nice solution but most, if not all,
>>> info should be there.
>>>      
>> http://www.linuxquestions.org/questions/linux-general-1/howto-workaround-broken-upstart-boot-logging-746468/
>>
>>    
> All well and good but:  Solution requires compiling and in my opinion, 
> Ubuntu should fix it without requiring non-geek types like me to compile
> a solution for what I have considered normal output for any OS.  There 
> was mention of a non-compiled solution, if I understood correctly,
> from a link withing your reference.  It seems a bootlogd_2.86.02.tar.gz 
> <http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz>was 
> shown in the link by Sergei Ivanov <https://launchpad.net/%7Esvivanov>  
> and I read it all via Ark but
> not any info where to put it or any details of what to do.  So, I didn't 
> feel safe in trying to use the so-called non-compiled solution.  Whether
> Ubuntu uses sysv or upstart, it seems that something in the nature of 
> bootlogd is needed and appropriate to be there. Just my $.02.


Just as an added note: sysvinit-utils (which now includes bootlogd) is
now included in karmic by default (at least on a fresh install test
system).
$ apt-cache policy sysvinit-utils
sysvinit-utils:
  Installed: 2.87dsf-4ubuntu12
  Candidate: 2.87dsf-4ubuntu12
  Version table:
 *** 2.87dsf-4ubuntu12 0
        500 http://archive.ubuntu.com karmic-updates/main Packages
        100 /var/lib/dpkg/status
     2.87dsf-4ubuntu11 0
        500 http://archive.ubuntu.com karmic/main Packages

bootlogd seems to work in karmic (for me) - sample /var/log/boot file
for the 21st:

> Mon Dec 21 10:00:55 2009: ^[[74G[ OK ]init crypto disks...       ^[[80G 
> Mon Dec 21 10:00:58 2009:  * Stopping NTP server ntpd
> Mon Dec 21 10:00:58 2009:  * Restarting OpenBSD Secure Shell server sshd
> Mon Dec 21 10:00:58 2009:  * nmbd is running
> Mon Dec 21 10:01:00 2009:  * Starting NTP server ntpd
> Mon Dec 21 10:21:00 2009:  * Reloading Common Unix Printing System: cupsd       ^[[80G init: rsyslog-kmsg main process (903) killed by TERM signal
> Mon Dec 21 23:06:30 2009: acpid: exiting
> Mon Dec 21 23:06:30 2009: 
> Mon Dec 21 23:06:30 2009: init: Disconnected from system bus
> Mon Dec 21 23:06:30 2009: modem-manager: Caught signal 15, shutting down...
> Mon Dec 21 23:06:31 2009: dhcdbd: Shut down.

Now this system has had the daemon enabled as far back as I can
remember(fiesty I think) & I hadn't bothered to check lately, as I
figured that nothing was working. Anyway, appears that it is.

$ cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes

Edit back to BOOTLOGD_ENABLE=No if you'd like to not have bootlogd run
at startup.

Start the daemon:
$ sudo update-rc.d bootlogd defaults
update-rc.d: warning: bootlogd start runlevel arguments (2 3 4 5) do not
match LSB Default-Start values (S)
update-rc.d: warning: bootlogd stop runlevel arguments (0 1 6) do not
match LSB Default-Stop values (none)
 Adding system startup for /etc/init.d/bootlogd ...
   /etc/rc0.d/K20bootlogd -> ../init.d/bootlogd
   /etc/rc1.d/K20bootlogd -> ../init.d/bootlogd
   /etc/rc6.d/K20bootlogd -> ../init.d/bootlogd
   /etc/rc2.d/S20bootlogd -> ../init.d/bootlogd
   /etc/rc3.d/S20bootlogd -> ../init.d/bootlogd
   /etc/rc4.d/S20bootlogd -> ../init.d/bootlogd
   /etc/rc5.d/S20bootlogd -> ../init.d/bootlogd

Not sure about the warning issues. I already have it running on this
system from previously & the above is the output from the new karmic system.