[Bug 350936] Re: Should shut down domains on system shutdown
Tested on 10.04 64bit. Before installing the proposed package, guests' /var/log/dmesg contained this after every time the host was shutdown (either with shutdown command or by pressing power button): [7.316252] EXT3-fs: INFO: recovery required on readonly filesystem. [7.316256] EXT3-fs: write access will be enabled during recovery. [ 36.242794] kjournald starting. Commit interval 5 seconds [ 36.242815] EXT3-fs: recovery complete. And after installing proposed package, guest dmesg contains: [7.101435] kjournald starting. Commit interval 5 seconds [7.101455] EXT3-fs: mounted filesystem with ordered data mode. It gets a thumbs up from me! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/350936 Title: Should shut down domains on system shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 606715] Re: Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid
Can we get this fix backported to Lucid as well? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. https://bugs.launchpad.net/bugs/606715 Title: Logfile defintions wrong after changes to logfile rotation in Ubuntu Lucid -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
Sorry, I forgot to report back about the panics. They were caused by a corrupted XFS filesystem on that server. I haven't had time to do any further testing with my packages since then - I just hacked the shutdown command to do what I needed until I have time to thoroughly test them. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
FWIW, you might want to mark /etc/default/libvirt-bin as a conffile in the libvirt packaging. I think it already is? (dpkg --status libvirt-bin says it is... but I've been changing things all over the place so I might have confused it) Also, it might make more sense to package omit-kvm-vm-pids as part of libvirt instead of a separate package; makes it harder to forget to install it. I'll look into this, it would be nicer. There's already a libvirt-bin.init in the packaging though, so for now I just added a dependency on omit-kvm-vm-pids. Thanks for the '##*/' explanation, google was not at all helpful with that particular search. :) I made another change in addition to yours above. The /lib/init/rw/sendsigs.omit.d/ folder does not exist on my system, so I changed it to /var/run/sendsigs.omit.d/ as mentioned by this bug: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/541512 Also, are these changes based on Lucid packages? The Lucid machine I'm using for testing has a kernel panic on shutdown with the packages from my PPA installed. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 350936] Re: Should shut down domains on system shutdown
@John Morrissey - Nice work on getting this working! I hope you don't mind, I've taken the liberty of packaging all your changes and putting them in a PPA for easier testing. One question on omit-kvm-vm-pids from #51, what does the '##*/' mean toward the end of line 26? -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545683] Re: ignore file missing from logwatch package
I really shouldn't submit bugs so late at night... this is not a bug at all, I had simply put the ignore.conf file in the wrong place. It belongs in /etc/logwatch/conf/ for anyone else who may run into this. ** Changed in: logwatch (Ubuntu) Status: New = Invalid -- ignore file missing from logwatch package https://bugs.launchpad.net/bugs/545683 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545683] [NEW] ignore file missing from logwatch package
Public bug reported: Binary package hint: logwatch Release: 9.10 Logwatch version installed: 7.3.6.cvs20090906-1ubuntu1 The /usr/share/logwatch/scripts/services/ignore script is missing from the Karmic logwatch package. This causes Logwatch to throw an error if ignore.conf has any entries in it. Expected results: Logwatch would send me an email with the lines I configured in ignore.conf. Actual results: I got the following error: Can't open: /usr/share/logwatch/scripts/services/ignore at /usr/sbin/logwatch line 1312 ProblemType: Bug Architecture: amd64 Date: Tue Mar 23 22:06:30 2010 DistroRelease: Ubuntu 9.10 Package: logwatch 7.3.6.cvs20090906-1ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-server SourcePackage: logwatch Uname: Linux 2.6.31-19-server x86_64 ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- ignore file missing from logwatch package https://bugs.launchpad.net/bugs/545683 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 545683] Re: ignore file missing from logwatch package
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41795107/Dependencies.txt -- ignore file missing from logwatch package https://bugs.launchpad.net/bugs/545683 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 453653] Re: [karmic] libvirt fails to list node devices
Sorry, this was my bad... hal is not installed by default on the server flavor and ubuntu-virt-server doesn't bring it in either. I saw libhal1 was installed and assumed that would be enough. Installing hal and rebooting fixed the issue. ** Changed in: libvirt (Ubuntu) Status: Incomplete = Invalid -- [karmic] libvirt fails to list node devices https://bugs.launchpad.net/bugs/453653 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 453653] [NEW] [karmic] libvirt fails to list node devices
Public bug reported: Binary package hint: libvirt-bin Ubuntu release: 9.10 server x86_64 libvirt-bin version: 0.7.0-1ubuntu11 Libvirt is unable to list node devices via virsh or virt-manager add hardware dialog. It looks like libvirt relies on hal for finding devices: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522310 However, hal is being deprecated for Karmic: http://www.ubuntu.com/testing/karmic/beta#hal%20deprecation Steps to reproduce: 1. Install Karmic (I used the beta server cd, then updated to the latest packages) 2. Install ubuntu-virt-server 3. run 'virsh nodedev-list' Expected results: virsh should list devices on the system Actual results: 'virsh noddev-list' outputs an error: error: Failed to count node devices error: this function is not supported by the hypervisor: virNodeNumOfDevices ProblemType: Bug Architecture: amd64 Date: Fri Oct 16 21:52:21 2009 DistroRelease: Ubuntu 9.10 Package: libvirt-bin 0.7.0-1ubuntu11 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.47-server SourcePackage: libvirt Uname: Linux 2.6.31-14-server x86_64 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- [karmic] libvirt fails to list node devices https://bugs.launchpad.net/bugs/453653 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 309632] Re: Unrecognised lines in dpkg output
This patch fixes those unknown lines, as well as capturing re-installed packages and conf file lines that would normally be put in the Unknown lines section. Backported from latest logwatch cvs. ** Attachment added: patch for unknown lines from logwatch.org cvs http://launchpadlibrarian.net/20579327/unknown-lines.patch ** Changed in: logwatch (Ubuntu) Status: New = Confirmed -- Unrecognised lines in dpkg output https://bugs.launchpad.net/bugs/309632 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 309632] Re: Unrecognised lines in dpkg output
I forgot to mention that my patch is for the Hardy version, but the bug occurs in the Jaunty version as well. -- Unrecognised lines in dpkg output https://bugs.launchpad.net/bugs/309632 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 296349] Re: logwatch replaces hostname with number
** Changed in: logwatch (Ubuntu) Status: Fix Released = Confirmed -- logwatch replaces hostname with number https://bugs.launchpad.net/bugs/296349 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 296349] Re: logwatch replaces hostname with number
Logwatch.pl in version 7.3.6.cvs20080702-1ubuntu3 has a typo around line 940: unless ($_ eq hostname} { This causes syntax errors in the rest of the file. The closing bracket for the unless statement should be a ) (parentheses) instead of } (curly bracket). -- logwatch replaces hostname with number https://bugs.launchpad.net/bugs/296349 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 296349] [NEW] logwatch replaces hostname with number
Public bug reported: Binary package hint: logwatch Release: Ubuntu 8.10 Package version: 7.3.6.cvs20080702-1ubuntu2 Expected results: Hostname is displayed in the subject line of Logwatch emails. eg, Logwatch for hostname (Linux) Actual results: If the system's hostname is one of the following keywords, it is replaced with an associated integer: yes = 1 no = 0 true = 1 false = 0 on = 1 off = 0 high = 10 med = 5 medium = 5 low = 0 In my case, the server is called medium (as in small, medium, large), which gets replaced with 5. I've attached a patch for logwatch.pl. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- logwatch replaces hostname with number https://bugs.launchpad.net/bugs/296349 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs