syslog is sometimes empty
Bug #1084186 reported by
Paul Larson
This bug report is a duplicate of:
Bug #1210431: syslog stops logging when lxc containers autostart.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
UTAH |
Triaged
|
High
|
Max Brustkern |
Bug Description
I've seen a few cases where the syslog is empty after running a job. For instance:
http://
In this case, "log" was also empty as well, which is likely a contributing factor.
Max also pointed me at http://
Related branches
lp:~doanac/utah/uuid_check_rsyslog
- Andy Doan (community): Needs Resubmitting
-
Diff: 350 lines (+89/-37) (has conflicts)8 files modifiedtemplates/install-commands.jinja2 (+23/-0)
tests/test_rsyslog.py (+34/-11)
utah/config.py (+4/-7)
utah/provisioning/baremetal/bamboofeeder.py (+1/-1)
utah/provisioning/baremetal/cobbler.py (+1/-1)
utah/provisioning/provisioning.py (+0/-12)
utah/provisioning/rsyslog.py (+25/-4)
utah/provisioning/vm.py (+1/-1)
Changed in utah: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in utah: | |
importance: | Medium → High |
assignee: | nobody → Max Brustkern (nuclearbob) |
To post a comment you must log in.
I don't know if this is the same problem, but my /var/log/syslog is empty (in Kubuntu 12.10).