syslog messages truncated to 256 chars during debian-installer run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BusyBox |
Fix Released
|
Unknown
|
|||
busybox (Ubuntu) |
Fix Released
|
High
|
Adam Stokes | ||
Precise |
Fix Released
|
High
|
Adam Stokes | ||
Quantal |
Fix Released
|
High
|
Adam Stokes | ||
Raring |
Fix Released
|
High
|
Adam Stokes |
Bug Description
[Impact]
Users relying on busybox within their environment and attempting to do any sort of debugging of logs.
[Test Case]
Run the installer, parse logs from syslogd packaged within busybox.
[Regression]
Minimal, only doubling buffer size for syslogd within busybox.
We're seeing syslog messages during installers runs truncated to 256 chars. This is annoying.
Digging into the debian-installer source, its calling /sbin/syslogd from the initrd - this is a busybox binary. In the busybox source, there's a config variable CONFIG_
Can we either -
1. fix busybox to use a dynamic buffer, or
2. bump the config variable up to 1024 or so?
I'm perfectly happy with solution 2 :)
affects: | ubuntu → busybox (Ubuntu) |
tags: | added: lucid precise |
Changed in busybox (Ubuntu Precise): | |
assignee: | nobody → Adam Stokes (adam-stokes) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in busybox (Ubuntu): | |
assignee: | nobody → Adam Stokes (adam-stokes) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in busybox (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.2 |
description: | updated |
Changed in busybox: | |
status: | Unknown → New |
Changed in busybox (Ubuntu Raring): | |
milestone: | none → ubuntu-13.04-beta-1 |
Changed in busybox (Ubuntu Raring): | |
status: | New → In Progress |
importance: | Medium → High |
milestone: | ubuntu-13.04-beta-1 → ubuntu-13.04 |
milestone: | ubuntu-13.04 → ubuntu-13.04-beta-1 |
Changed in busybox (Ubuntu Quantal): | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Adam Stokes (adam-stokes) |
milestone: | none → quantal-updates |
Changed in busybox (Ubuntu Quantal): | |
status: | Triaged → In Progress |
Changed in busybox: | |
status: | New → Fix Committed |
Changed in busybox: | |
status: | Fix Committed → Fix Released |
Reproduction instructions, using the binary itself. archive. ubuntu. com/ubuntu/ dists/precise/ main/installer- amd64/current/ images/ netboot/ netboot. tar.gz Downloads/ netboot. tar.gz ./ubuntu- installer/ amd64/initrd. gz installer/ amd64/initrd. gz | cpio -i sbin/syslogd
# Extract syslogd from the Precise netboot:
wget http://
tar xzf /home/mwharris/
mkdir sbin
gzip -dc ubuntu-
# Run the new syslogd.
sudo stop rsyslog # to free the port
sudo ./sbin/syslogd -n
# Now the busybox syslogd is running.
# Send a long line to syslogd
logger "watch runs command repeatedly, displaying its output and errors (the first screenfull). This allows you to watch the program output change over time. By default, the program is run every 2 seconds; use -n or --interval to specify a different interval. Normally, this interval is interpreted as the amout of time between the completion of one run of command and the beginning of the next run. However, with the -p or --precise option, you can make watch attempt to run command every interval seconds. Try it with ntptime and notice how the fractional seconds stays (nearly) the same, as opposed to normal mode where they continuously increase."
Check /var/log/messages for truncated output.
Another option to reproduce would be to look for a long line generated during install time, but I don't know of one off-hand. We're running puppet during install and it generates some long lines when it errors.