*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
On Wed, 2009-08-12 at 10:11 +, Jarl wrote:
> To me it seems like this bug is the one with most details (most
> comments) and most attention (most subscribers).
>
Age of bug, number of comments and most s
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
@ Scott James Remnant
I believe Charles does not need to sending "half a dozen" emails, if he
just get *one* reasonable answer as to why this bug is a duplicate of
bug 328881 and not opposite.
To me it seems
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
On Sun, 2009-08-09 at 10:43 +, Charles Atkinson wrote:
> *** This bug is a duplicate of bug 328881 ***
> https://bugs.launchpad.net/bugs/328881
>
> Thanks Dimitrios Symeonidis
>
> That makes sense.
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
Thanks Dimitrios Symeonidis
That makes sense. If it were applied in this case then this bug report
(with 74 comments) would be the master rather than
https://bugs.launchpad.net/upstart/+bug/328881 (with thre
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
@Charles Atkinson: not necessarily, the idea is that the master bug
should be the one with the most details, or the one that received the
most attention... Often it is the oldest one, but not always.
--
logd
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
This bug report, started on 2007-03-30, has been marked as a duplicate
of https://bugs.launchpad.net/upstart/+bug/328881, started on
2009-02-13.
I understood that later bugs were marked as duplicates of earli
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
The simplest solution I have found, which helped me work out what was
wrong without installing unsupported packages, is to use Ctrl-S to pause
the output and Ctrl-Z to let it start again. Hope it helps
--
lo
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
** Changed in: upstart (Fedora)
Status: In Progress => Won't Fix
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, w
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
Note that bootlogd not working is a different bug on sysvinit (we should
fix that)
** This bug has been marked a duplicate of bug 328881
init: support logging of job output
--
logd not running
https://bu
Hi Jean-Baptiste,
You can force dpkg to overwrite files by adding the --force-overwrite
param to the command to install the bootlogd .deb:
sudo dpkg -i --force-overwrite bootlogd_2.86.02_*.deb
Tested this on jaunty and it produces a nice /var/log/bootmsg file.
Hope this helps,
glitsj16
--
lo
I was happily using bootlogd 2.86.02 until I upgraded to Jaunty: the
package cannot be installed anymore, due to a conflict with initscripts:
Unpacking bootlogd (from .../bootlogd_2.86.02_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/bootlogd_2.86.02_amd64.deb
(--unpack):
trying
On Monday 27 April 2009, Charles Atkinson wrote:
> In bootlogd.c, there is a while loop starting at line 585 and ending at
> line 664. Each iteration it reads from the intercepted console output,
> writes what it gets to the console and either buffers it or writes it to
> logfile. What is the acc
access() is from unistd.h.
Starting at line 250 of /usr/include/unistd.h:
/* Values for the second argument to access.
These may be OR'd together. */
#define R_OK4 /* Test for read permission. */
#define W_OK2 /* Test for write permission. */
#define X_OK
Hello (especially Sergei) :-)
I'm trying to go further, running bootlogd on ubuntu 8.04.02 running in
a VirtualBox virtual machine with / mounted read-only and a writeable
/var/log mounted later. Isn't it always the way -- the code works
perfectly well and then someone shifts the goal posts?!
I
Thanks for the workaround, Sergei. I downloaded, built, and installed
your 2.86.02 package above and got just what I needed. I'm using Hardy.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just wanted to say that I installed Debian 5.0 a month ago and bootlogd
worked perfectly by setting /etc/default/bootlogd to Yes. So, it's very
strange that this seems to be such a large problem on my Ubuntu 8.04
server.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this
I can't make it work even with Sergei Ivanov's patched version. Im
running Ubuntu 8.10 and have set BOOTLOGD_ENABLE=Yes in
/etc/default/bootlogd ... this is a big issue, at least for me... I see
boot scripts failing but can't find out which ones or why...
--
logd not running
https://bugs.launchpa
On Saturday 14 March 2009, Charles Atkinson wrote:
> I expected this change to cause some breakage; perhaps bootlogd depended
> on something set by the earlier boot scripts; why would the package
> designers not start it right at the beginning of the boot process so it
> could capture all the boot
Hello :-)
Subject: bootlogd 2.86.02 boot script link change to capture more boot
messages
Regards the workaround for this bug ('cos it ain't going away any time
soon!).
After installing bootlogd 2.86.02 from the package Sergei attached to
this bug report (thanks Sergei) ...
bootlogd is started
Description:Ubuntu jaunty (development branch)
Release:9.04
confirm, this issue is still present
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I would be very very nice if this issue could be solved.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
It's a big issue for me, especialy on my headless server.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
** Description changed:
- logd is currently not running in feisty; which means both /var/log/boot
- isn't filled AND that output is spat all over the getty by default.
+ /sbin/logd is not started since Gutsy, leading to an empty /var/log/boot
+ file
- Get it enabled again before release, damnit
this bug persists on intrepid ibex
i cannot simply see my boot log (upstream, bootlog or whatever)
dmesg is NOT enough
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Changed in: upstart (Ubuntu)
Status: In Progress => Confirmed
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Kubuntu KDE 3.5.9 Hardy Heron (for pity sake, this has been a problem
since Dapper, or so it seems when reading the Ubuntu Forums)
Bootlog remains empty, as others have stated... even after changing No
to Yes.
The Boot Log in KSystemlog states that there no file 'boot.log' in
/var/log.
Personal
** Changed in: upstart
Status: Fix Released => Won't Fix
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Changed in: upstart
Status: Fix Committed => Fix Released
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Good catch, thats what I meant.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo
Brando shouldn´t u have said 999kb not 999mb as you wrote above. Anybody
having any idea as to whatś happening on this front atm.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
when i place an integer value that is larger then six digits (largest i
can go is 999,999) it compiles fine but just doesnt log anything. first
i tried 1mb and that didnt work so i knocked it down to 999mb and that
didnt work, so i used 999,999 and it worked. im measuring the time based
on the time
> i cant make the buffer big enough to log it all. my boot process takes
> 23 seconds and the biggest buffer that i can get to work is 975kb
> (999,999 bytes) which will only log 18 seconds.
This is a strange constant. The 32-bit integer overflows near 2Gb.
What is wrong with larger values? Doesn'
i cant make the buffer big enough to log it all. my boot process takes
23 seconds and the biggest buffer that i can get to work is 975kb
(999,999 bytes) which will only log 18 seconds. also is there a way to
log the shutdown messages? network manager keeps giving me a lot of
errors but i can never
making some progress, i increased it from 32k to 128k and it now logs 9
seconds. im going to go all out and up it to 1mb and see how that goes.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
thanks, how can i check to see when the script is run?
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
> i installed Sergei's version and it works but it only captures 3 seconds
> of my boot messages, how can i fix this?
Is there a lot of text to capture? If so, it might overflow the internal 32K
buffer.
It is defined on line 52 in bootlogd.c. Try to increase it.
Also, there is a stop-bootlogd sc
i installed Sergei's version and it works but it only captures 3 seconds
of my boot messages, how can i fix this?
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: upstart
Status: Triaged => Fix Committed
** Changed in: upstart (Ubuntu)
Status: Invalid => In Progress
Target: ubuntu-7.04 => None
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
** Changed in: upstart (Fedora)
Status: Unknown => In Progress
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Bug watch added: Red Hat Bugzilla #431117
https://bugzilla.redhat.com/show_bug.cgi?id=431117
** Also affects: upstart (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=431117
Importance: Unknown
Status: Unknown
--
logd not running
https://bugs.launchpad.net/bugs/98955
Y
Hi all,
From whatever little I know of Upstart wasn't it designed to replace sysvinit
in the first place.
Dunno if this is the right thing or not but from what I read it seems to
say that Upstart is not able to play along nicely with logd or vice-
versa.
I don't like the idea of using scripts
> Can you give me layman steps of how to install your package?
This is a Debian source package. It is meant to be installed using
dpkg-related tools, not with "make; make install".
A recipe was there in the post where I announced the package.
Here it is again:
# unpack the source
tar xzvf bootl
Sergei,
Can you give me layman steps of how to install your package?
Thanks.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
p.s. when i run make in the untared dir i get
gcc -Wall -O2 -D_GNU_SOURCE -s -lutil bootlogd.c -o bootlogd
bootlogd.c: In function ‘main’:
bootlogd.c:658: warning: pointer targets in passing argument 2 of ‘writelog’
differ in signedness
should i be concerned about that warning?
--
logd
Hi,
this might help:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/125710/comments/1
(from https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/125710)
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bu
> Bootlogd [...] This is the right tool for the problem "what did that
scrolled-away messages say?".
No Bootlog is really no big issue. It is just helpful for troubleshooting
actual boot problems.
When you see a failed message scoll by just place a link to /sbin/sulogin in
/etc/rcS.d or /etc/rc2
Ok, I see. Well, then this behavior is probably preferred.
Thankyou
2008/1/27, Sergei Ivanov <[EMAIL PROTECTED]>:
>
> > Yes, I sure understand that you don't want to be a maintainer for it,
> that
> > would probably be quite a lot of work. For me the [ok] comes on it's own
> > separate:
> > Sun J
> Yes, I sure understand that you don't want to be a maintainer for it, that
> would probably be quite a lot of work. For me the [ok] comes on it's own
> separate:
> Sun Jan 27 21:52:32 2008: * Starting system message bus dbus
> Sun Jan 27 21:52:32 2008: [ OK ]
>
> Is this intentional? Otherwise
Yes, I sure understand that you don't want to be a maintainer for it, that
would probably be quite a lot of work. For me the [ok] comes on it's own
separate:
Sun Jan 27 21:52:32 2008: * Starting system message bus dbus
Sun Jan 27 21:52:32 2008: [ OK ]
Is this intentional? Otherwise this seems muc
I am not willing to maintain it seriously, it is too system-dependent.
Nevertheless, here is a new version. Changes are:
- Improved logfile formatting.
- The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in
the future.
Again, please do not install it blindly. You cannot be
I hit a fast test and Sergei's version worked nicely.
I'll also try with 2.6.24 later on.
Now I can see bootlog of my headless server.
Hope this will get standalone package in the ubuntu repo.
Thanks, for that!
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug noti
Ok, I see, then you did not forget it after all. :-)
I installed your version, it works nicely for me, and the /var/log/boot file
looks nicer than it did with my old one. Thankyou for this work. Maybe you
could submit this package to getdeb.net for inclusion in their archive,
along with some warni
I did attach it! Maybe launchpad does not allow this via email.
Now I am trying to do this using the web interface.
** Attachment added: "bootlogd_2.86.01.tar.gz (unofficial package)"
http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz
--
logd not running
https://bugs.launchpad.ne
Segei: I think you forgot to attach the actual file. ;-)
Your description of it seems very nice though, I hope they could include
a package like this in the universe. I think many users would appreciate
that possibility. Maybe even a package from you, if you would have the
time to be maintaining i
To tekknokrat. You can try out the attached source package.
This is bootlogd alone, separated from gutsy's sysvinit.
I fixed logging of terminal codes and some other minor issues.
It works for me here (Ubuntu stock kernel, no usplash, no mounting of /var).
You can build and install it with the fo
> I think there is a good reason that they are not using bootlogd by
> default. I think I read somewhere that bootlogd is quite buggy on some
> systems, and it is hard to make it work correctly the way it is
> designed. So the proper fix in the long run would be to redesign it
> completely, as Scot
I think there is a good reason that they are not using bootlogd by
default. I think I read somewhere that bootlogd is quite buggy on some
systems, and it is hard to make it work correctly the way it is
designed. So the proper fix in the long run would be to redesign it
completely, as Scott is inten
I tried the method Pär Lidén explained on gutsy_x64_86.
apt-get source sysvinit
sudo apt-get build-dep sysvinit
cd sysvninit*
debuild -us -uc
sudo cp src/bootlogd /sbin/
(attached bootlogd for gutsy x64 perhaps someone else will have try with
it...)
remove "-c" option in init.d/bootlogd...
whe
I think that using the old bootlogd is the right fix. It seems that
bootlogd and logd can and should coexist on the same system (of course,
if they write to different logfiles). They just serve different
purposes.
Bootlogd is to save everything sent to /dev/console. It does not know
who writes wha
No, it's completely unrelated; logd and bootlogd are completely
different programs with a completely different implementation.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
After looking around, I can see that this bug is very much connected to
bug #94120.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
hello, I have the same problem with the boot logging not working. All
the other log files seem to work fine, but not the one logging consoloe
output during boot.
The most recent data written in /var/log/boot is from 20 april this
year. I guess that's when I upgraded to 7.04. This is a very annoyin
actually, it didn't work, my bad
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Here it's explained how to restart and prepare the bootlogd properly, if this
is what you need:
http://ubuntuforums.org/showpost.php?p=2441664&postcount=17
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which
Not an Ubuntu bug -- it's upstream
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
The logd problem is the way it works (the following is a summary, see
logd(8) for more protocol detail):
Jobs specify "console logged" (once the default) in their definition,
this means that Upstart will open a connection to logd for the job and
bind that socket to the job's standard input/output.
** Changed in: upstart (Ubuntu)
Assignee: Scott James Remnant (keybuk) => (unassigned)
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
Confirming, too, that /var/log/boot is not filled at all after enabling
bootlog - Gutsy amd64
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Confirming that /var/log/boot is still blank in Gutsy after setting
BOOTLOGD_ENABLE to YES.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
Sorry, but man dmesg doesn't hack it :-)
The problem is that, as said elsewhere in the many discussions about
boot-time logging, these messages do not appear in any of the system log
files - /var/log/dmesg included. It's for that reason that I had to
resort to video to capture the messages and be
man dmesg
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same problem here. I eventually used a digital camera to capture all
the console messages during boot. In this case it enabled me to read
the messages, find the underlying problem and fix it. Hardly the best
solution though.
Until there's a proper fix to this "medium" (!!) importance probl
So right now there is zero possibility to find out what happened during
boot? I see messages spewing all over the console, some of them errors
(that I'm trying to work out), how can I get to them?
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because
My understanding from Scott is that it's been disabled intentionally,
due to causing problems with processes holding file descriptors. Those
issues need to be chased down before it can be enabled again.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification
bug is still present in current gutsy.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
** Changed in: upstart (upstream)
Importance: Undecided => Medium
Status: Unconfirmed => Confirmed
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
See what I said, it's purposely disabled for a reason. If a process is
using logd for it's stdout, and logd gets stopped, that process will die
with SIGPIPE
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can cconfirm. that logd is not running after boot on two computers running
7.04.
The command
sudo initctl list
reports
logd (stop) waiting
I've stumbled over this while trying to find out, why a custom daemon I
wanted to get started during boot doesn't get started. After the
syst
Logging stoped just after feisty (sucktsy) update.
The /var/log/boot file was updated the day before the upgrade.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Logd doesn't get started by default or used by default because there is
a bug in it, not just because it isn't started:
25-02-2007 13:43:25 btw, what is the problem with logd?
25-02-2007 13:44:30 kill it, any job with it as stdout ends up dying
mysteriously and silently
--
logd not running
ht
Confirmed here as well, logging hasn't been happening for quite a while
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
I'll confirm. My last recorded /var/log/boot is 13 Feb. I guess that
means that day's updates broke it. Is there a SVN or CVS or something
like that for upstart somewhere to see what changed it?
** Changed in: upstart (Ubuntu)
Status: Unconfirmed => Confirmed
--
logd not running
https:
For what it's worth: same problem here.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
My /var/log/boot contains only "(Nothing has been logged yet.)" and its
datestamp is from early last month, when I installed Feisty.
So I'm also experiencing logd apparently not running.
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification because you are
84 matches
Mail list logo
