[Bug 1096491] Re: "etckeeper unclean" is broken
I just ran into this. A better description is that etckeeper unclean is broken when using git. # git status # On branch master nothing to commit (working directory clean) # etckeeper unclean # echo $? 1 Obviously that should return 0. ** Changed in: etckeeper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1096491 Title: "etckeeper unclean" is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1096491/+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 387069] Re: incorrect filesystem permissions prevent nagios command checking from working
Yes, adding www-data to the nagios group is an easy fix. It also carries grave security implications. Use at your own risk. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/387069 Title: incorrect filesystem permissions prevent nagios command checking from working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/387069/+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 849672] Re: make libvirt trivial to backport to lucid
The latest version in oneiric is 0.9.2-4ubuntu13. The latest version you have backported is 0.9.2-4ubuntu6. I was actually trying to make your life easier since your more recent backports have failed to build on lucid and maverick: https://launchpad.net/~ubuntu-virt/+archive/ppa/+packages Seems like if supporting ludic was any sort of priority for developers than making minor changes to current packages to facilitate easier backporting would align with that goal. -- 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/849672 Title: make libvirt trivial to backport to lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/849672/+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 849672] [NEW] make libvirt trivial to backport to lucid
Public bug reported: While libvirt can be backported to natty without changes in order to backport to maverick or lucid requires some minor changes. It would be nice, given how often this package has been updated, to make a no change backport possible, especially for lucid. I have not prepared a debdiff because in my backports I usually simple disable macvtap support as I do not need it however for a proper solution macvtap support should be detected and set in the rules file accordingly. Here are the other changes, from my notes: * control build depends - change cdbs version * control build depends - change python-dev version * control build depends - add python-support * control X-Python-Version from 2.7 to current * rules add DEB_PYTHON_SYSTEM = pysupport * rules macvtap support (as mentioned above) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/849672 Title: make libvirt trivial to backport to lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/849672/+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 794378] [NEW] sync to newer version on libvirt for Ubuntu 11.10
Public bug reported: It would be nice to see 0.9.2 in Ubuntu 11.10 but at the very least it should ship with 0.9.0 which is a significant upgrade from 0.8.8. Debian has backported 0.9.0 to Debian 6 for this reason. 0.9.1 is in Debian unstable. http://packages.debian.org/search?keywords=libvirt- bin&searchon=names&suite=all§ion=all ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- 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/794378 Title: sync to newer version on libvirt for Ubuntu 11.10 -- 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 550409] Re: Slow disk IO for all guests with all disc modes and types.
People should be aware that cache=writeback should only be used if you do not care about the very real possibility of guest disk corruption should the guest or host fail unexpectedly. Given that there is no facility for shutting down guests cleanly on host shutdown one should be very wary of risking their guest data for anything important. -- 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/550409 Title: Slow disk IO for all guests with all disc modes and types. -- 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 714335] Re: KVM SMP Linux Guests Hang
I believe this bug has been affecting me for some time. Just to be clear on my situation: * Host system running Ubuntu 10.04 64-bit * Guest systems running Ubuntu 10.04 64-bit * Guests freeze a large percentage of time, though not always. * They always freeze immediately after the "Freeing initrd memory" line * They work fine if set to "-smp 1" -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/714335 Title: KVM SMP Linux Guests Hang -- 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 691819] [NEW] ntpd stopped working when time server disappeared
Public bug reported: Binary package hint: ntp I have no idea how or when my ntp server got set but I had been noticing for some time that my clock wasn't correct. I finally investigated the problem tonight and found many lines of the following in the daemon.log ntpd_initres[]: host name not found: clock.tricity.wsu.edu /etc/ntp.conf obviously had the following: server clock.tricity.wsu.edu Which I replaced with: server pool.ntp.org My suggestion is that the ntp package should decide on a default ntpserver hostname (pool.ntp.org or ntp.ubuntu.com) and then upgrade people's ntp.conf files to reflect that default. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. https://bugs.launchpad.net/bugs/691819 Title: ntpd stopped working when time server disappeared -- 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 577592] [NEW] qemu-kvm dependencies require X
Public bug reported: Binary package hint: qemu-kvm I've been playing with qemu-kvm on a development server and have been disappointed that the package requires (dpends on) X, SDL, and audio libraries that are not needed on a server. Could these be changed from "depends" to "recommends"? * libasound2 * libpulse0 * libx11-6 * libsdl1.2debian ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- qemu-kvm dependencies require X https://bugs.launchpad.net/bugs/577592 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 539250] [NEW] Windows XP gets access denied when trying to rename folder over smb
Public bug reported: Binary package hint: samba I believe I'm running into this bug on an Ubuntu 9.10 Samba server: https://bugzilla.samba.org/show_bug.cgi?id=6781 Any chance the patch could be applied? ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- Windows XP gets access denied when trying to rename folder over smb https://bugs.launchpad.net/bugs/539250 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 387069] [NEW] incorrect filesystem permissions prevent nagios command checking from working
Public bug reported: Binary package hint: nagios3 Once external command checking has been enabled in nagios.cfg the following error message is reported when attempting to use external commands: --- Error: Could not stat() command file '/var/lib/nagios3/rw/nagios.cmd'! The external command file may be missing, Nagios may not be running, and/or Nagios may not be checking external commands. An error occurred while attempting to commit your command for processing. --- Reported on several websites are the following steps to resolve the problem: --- sudo /etc/init.d/nagios3 stop sudo dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios3/rw sudo dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios3 sudo /etc/init.d/nagios3 start --- These filesystem permissions should be the default unless there is a compelling reason not to or a more secure solution to this problem. Websites offering this solution: --- * http://www.idimmu.net/2009/03/31/Error:-Could-not-stat()-command-file-%27/var/lib/nagios3/rw/nagios.cmd%27! * https://blog.devnu11.net/2008/04/nagios3-debian-etch-pakete/ * http://lars-schenk.com/nagios-commands-via-web-interface-on-debian/446 * http://yesthatworks.blogspot.com/2008/11/error-could-not-stat-command-file_26.html --- ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New ** Tags: nagios server ** Tags added: nagios ** Tags removed: nagio -- incorrect filesystem permissions prevent nagios command checking from working https://bugs.launchpad.net/bugs/387069 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 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 251760] Re: New Dovecot 1.1.x upstream for hardy-backports
** Tags added: email server -- New Dovecot 1.1.x upstream for hardy-backports https://bugs.launchpad.net/bugs/251760 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot 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 120375] Re: cannot boot raid1 with only one disk
No one should be taking any of this personally or feel berated. People should feel free to be honest about their experiences without fear that doing so will drive away people that could be of help in resolving the issues. I've been keeping my mouth shut on this bug for a couple of months and I apologize for being long winded when I finally took the time to post my experiences. Dustin Kirkland, you did not offer to fix this problem in the LTS release. You stated that you would consider it. And that's great, but without any commitment to fix the problem in 8.04 it would be nice to actually be able to offer up a simple solution to the people that come across this page when trying to resolve this bug. I will not unsubscribe from this bug because I know that people will be bit by it again, come to me for help, and I wish to have a good solution for them when they do. I re-read the Code of Conduct and note that being collaborative seems to be at odds with disengaging when one finds the process unpleasant. I certainly respect the right of people to do so but I feel it's a loss to actually making progress on this bug. Granted, I've only been subscribed for 2 months; if I had been subscribed for a year I acknowledge I might feel differently. Since people seem to feel that this hasn't been a friendly exchange I will be happy to buy a drink of choice to: 1) Anyone that comes up with a good solution to this bug for Ubuntu 8.04 and 8.04.1. 2) Anyone who works to get this bug fixed in 8.04.2. 3) Dustin Kirkland and anyone else who makes sure this bug never appears in 8.10. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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 120375] Re: cannot boot raid1 with only one disk
I think it's time for some tough love. No one would be taking the time to comment on this if they didn't want to see Ubuntu Server be a better product. I personally feel this is a significant issue for because it demonstrates Canonical's interest in supporting an LTS release and seriousness about becoming a presence in the server market. I know it can be difficult when people are lambasting a product you've put a lot of time into, believe me, I got more than my fair share of that this week. However, sometimes you have to step back and realize that your product quality has been lower than many people expect and you have to either step up or risk losing more customers. Make no mistake, this bug has lost a lot of sysadmins, some of whom had to fight hard to get Ubuntu onto servers in their workplaces in the first place. I was one of them, and I know a few more personally. I pitched that it made sense to have Ubuntu on the Server because of the benefits of the LTS release, including the longer support time and the large community that contributes to Ubuntu, therefore leading to more bugs being found and resolved. However, I doubt I will be able to propose Ubuntu again until version 10.04. If this bug were to be resolved in 8.04.2 I might at least start pitching it next year, barring any other bugs of this level of severity. To respond to Steve Langasek, while I understand that a lot of these emails are not terribly useful, this bug is exactly what the SRU team is supposed to be addressing. There have been many proposed fixes in this thread and 8 patches uploaded. Do any of them work correctly? Well that is the question, but it's inaccurate to state that this bug does not contain proposed fixes. Furthermore this fits the SRU criteria of being a high impact bug representing a severe regression from earlier versions and one which also may lead to a loss of user data. When the average user is confronted with the initramfs shell during a drive failure I suspect they have the potential to do serious damage to their file systems in an attempt to fix the problem. I don't feel it's possible for me to understate the severity of this bug and how badly sysadmins are going to react when they encounter it or read about it. It is certainly not the kind of bug one can dismiss in an LTS release if LTS is to say anything about quality, and hence suggestions to upgrade to Intrepid, while acceptable to a home user building a server, are not going to be acceptable in the workplace. If this is a market segment that Ubuntu Server is catered to than this issue needs to be addressed. If on the other hand Ubuntu Server is meant merely for enthusiasts with their home file servers than the solution should be to make sure that goal is clearly articulated. To keep us focused on the work at hand and to avail myself of the opportunity that having this number of people working for fix this bug represents I'll say that I've tried a number of solutions on this page but none have been satisfactory. I tried changing the udev rule as suggested above (see Plnt 2007-12-25) but got the same results that have been reported: I can get the system to boot any time the disk is degraded but at the expense that it boots degraded sometimes even when the disks are fine. This is the setting on my remaining Ubuntu servers (which will be migrated to Debian in the near future). This option is suboptimal but better than the default behavior. I would say that the ideal (and expected) behavior is for the system to boot in the case of a degraded array by default, with an option to turn that off if the sysadmin chooses. For those with Ubuntu servers, assuming this never gets fixed, I think an initramfs script (in /etc/initramfs- tools/scripts/) that anyone could copy onto their server might be ideal. Alternatively patching the mdadm udev script to try and start with --no-degraded and on failure use --run might also be an option. I have a server I may be able to user for testing but if anyone has a script to start with that would be great. -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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
