live Installer may rotate syslog during install and copy only a portion to /target/var/log/installer/syslog

Bug #296129 reported by Joel Ebel
2
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Medium
Unassigned
Precise
Won't Fix
Medium
Unassigned

Bug Description

The Ubuntu Live CD includes the sysklogd package, which is used for logging the install to /var/log/syslog. The syslog is copied to /target/var/log/installer/syslog at the end of installation. The sysklogd package installs a syslog rotation script into /etc/cron.weekly/sysklogd which runs at 6:47 AM on Sunday. If an install happens to span across this time, then the log gets rotated during the install. As a result, the syslog that gets copied to /target/var/log/installer/syslog doesn't contain the entire installer log.

I'm seeing this in the intrepid installer. It may exist in previous versions, but I didn't check. I'm not certain what component to file the bug under, since it's a file from the sysklogd package that's causing the problem, but the problem is specific only to the install cd.

To reproduce, run an install when the computer's clock is going to pass 6:47 AM on a sunday morning and observe the log file after the install finishes. One would expect the see the entire installer log, but in fact only sees the portion that occured after log rotation.

I propose that the live cd either does not rotate logs, or that log rotation be disabled during an installation.

TEST CASE
1) Boot Live CD to Try Ubuntu
2) Adjust Date one day into the future
3) Execute 'sudo /etc/cron.daily/logrotate'
4) Observe 2 syslog files in /var/log/

Tags: testcase
Revision history for this message
Joel Ebel (jbebel) wrote :

As stated in the description, I don't believe this should be targeted to the sysklogd source package, as it's not a bug in sysklogd. It's a bug in the Live CD, but I don't know what component in launchpad is responsible for that.

Revision history for this message
Joel Ebel (jbebel) wrote :

Moving to ubiquity package since I think that's a better place to start.

Revision history for this message
Colin Watson (cjwatson) wrote :

(We don't use the ubiquity upstream project for bug tracking, only the ubiquity package in Ubuntu, so I'm marking the upstream task Invalid.)

Changed in ubiquity:
status: New → Invalid
Revision history for this message
Colin Watson (cjwatson) wrote :

I agree that this would be a very good thing to fix; I've observed it impeding my ability to diagnose bugs several times. The package that governs live CD startup is casper.

affects: ubiquity (Ubuntu) → casper (Ubuntu)
Changed in casper (Ubuntu):
importance: Undecided → High
status: New → Triaged
description: updated
tags: added: testcase
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Looking at all the open ubiquity bug attachments about 32 of them contain a log file with rsyslog being restarted in them.

tags: added: rls-p-tracking
Changed in casper (Ubuntu Precise):
importance: High → Medium
Steve Langasek (vorlon)
tags: removed: rls-p-tracking
Revision history for this message
Stéphane Graber (stgraber) wrote :

Moving back to ubiquity as we don't want to rotate logs for persistent sessions.
Instead ubiquity should stop logrorate before installing and start it again afterwards, easiest way to achieve this is to remove the executable bit from the logrotate binary.

no longer affects: ubiquity
affects: casper (Ubuntu) → ubiquity (Ubuntu)
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in ubiquity (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in ubiquity (Ubuntu Precise):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.