[Bug 1435823] Re: Disappearing /var/run/mysqld causes mysqld to fail after reboot
Hi, I am not an expert,so I do'nt know how to apply the Bruno's fix When I start mysql I get: Sep 11 11:08:52 serv mysql[25802]: Checking for tables which need an up...e Sep 11 11:08:52 serv mysql[25802]: not closed cleanly.. Hint: Some lines were ellipsized, use -l to show in full. I understand I have to Create a newfile /etc/tmpfiles.d/mysql.conf: What does it mean " d /var/run/mysqld 0755 mysql mysql - " ? Delete? Thank You to all mysql experts that can solve this question. Yours Sincerely, Alex -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1435823 Title: Disappearing /var/run/mysqld causes mysqld to fail after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435823/+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 1092243] [NEW] /etc/init.d/bind9: 92: [: pid:: unexpected operator
Public bug reported: god@world:~$ uname -a Linux world 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux god@world:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise god@world:~$ apt-cache policy bind9 bind9: Установлен: 1:9.8.1.dfsg.P1-4ubuntu0.5 Кандидат: 1:9.8.1.dfsg.P1-4ubuntu0.5 Таблица версий: *** 1:9.8.1.dfsg.P1-4ubuntu0.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.8.1.dfsg.P1-4 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I did it like this: god@world:~$ sudo /etc/init.d/bind9 restart [sudo] password for it-orion: * Stopping domain name service... bind9 /etc/init.d/bind9: 92: [: pid:: unexpected operator ...done. * Starting domain name service... bind9 ...done. With help of guys from li...@conference.jabber.ru we solved this bug: god@world:~$ sudo nano /etc/init.d/bind9 -if [ -n $pid ]; then + if [ -n $pid ]; then I hope it helps for you all. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Description changed: god@world:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise god@world:~$ apt-cache policy bind9 bind9: - Установлен: 1:9.8.1.dfsg.P1-4ubuntu0.5 - Кандидат: 1:9.8.1.dfsg.P1-4ubuntu0.5 - Таблица версий: - *** 1:9.8.1.dfsg.P1-4ubuntu0.5 0 - 500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages - 100 /var/lib/dpkg/status - 1:9.8.1.dfsg.P1-4 0 - 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages + Установлен: 1:9.8.1.dfsg.P1-4ubuntu0.5 + Кандидат: 1:9.8.1.dfsg.P1-4ubuntu0.5 + Таблица версий: + *** 1:9.8.1.dfsg.P1-4ubuntu0.5 0 + 500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages + 100 /var/lib/dpkg/status + 1:9.8.1.dfsg.P1-4 0 + 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I did it like this: god@world:~$ sudo /etc/init.d/bind9 restart - [sudo] password for it-orion: - * Stopping domain name service... bind9 + [sudo] password for it-orion: + * Stopping domain name service... bind9 /etc/init.d/bind9: 92: [: pid:: unexpected operator -...done. - * Starting domain name service... bind9 -...done. + ...done. + * Starting domain name service... bind9 + ...done. - With help of guys from li...@conference.jabber.ru we solve this bug: + With help of guys from li...@conference.jabber.ru we solved this bug: god@world:~$ sudo nano /etc/init.d/bind9 -if [ -n $pid ]; then + if [ -n $pid ]; then I hope it helps for you all. ** Description changed: + god@world:~$ uname -a + Linux world 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux + god@world:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise god@world:~$ apt-cache policy bind9 bind9: Установлен: 1:9.8.1.dfsg.P1-4ubuntu0.5 Кандидат: 1:9.8.1.dfsg.P1-4ubuntu0.5 Таблица версий: *** 1:9.8.1.dfsg.P1-4ubuntu0.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.8.1.dfsg.P1-4 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages I did it like this: god@world:~$ sudo /etc/init.d/bind9 restart [sudo] password for it-orion: * Stopping domain name service... bind9 /etc/init.d/bind9: 92: [: pid:: unexpected operator ...done. * Starting domain name service... bind9 ...done. With help of guys from li...@conference.jabber.ru we solved this bug: god@world:~$ sudo nano /etc/init.d/bind9 -if [ -n $pid ]; then + if [ -n $pid ]; then I hope it helps for you all. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1092243 Title: /etc/init.d/bind9: 92: [: pid:: unexpected operator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1092243/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Blueprint servercloud-p-virtio-device-driver] Providing VirtIO device driver for other OS
Blueprint changed by Al Stone: Whiteboard changed: This doesn't need a discussion, just us to do it. -robbie.w Work Items: [ahs3] build the latest virtio drivers: DONE [ahs3] request built driver signing (and wait): DONE - [ahs3] package and test signed drivers: INPROGRESS - [ahs3] release signed and packaged drivers: BLOCKED + [ahs3] package and test signed drivers: DONE + [ahs3] release signed and packaged drivers: DONE [mahmoh] test released signed and packaged drivers: BLOCKED -- Providing VirtIO device driver for other OS https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-virtio-device-driver -- 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 835766] [NEW] package dhcp3-client 3.1.3-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script killed by signal (Segmentation fault)
Public bug reported: I was installing 10.04 and then ran the update manager, that is when the bug happened. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: dhcp3-client 3.1.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Sat Aug 27 19:59:37 2011 DhclientLeases: ErrorMessage: subprocess installed post-installation script killed by signal (Segmentation fault) InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-33-generic root=UUID=b30a90bd-ddf8-427f-a629-8ba4b1412bb8 ro quiet splash SourcePackage: dhcp3 Title: package dhcp3-client 3.1.3-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script killed by signal (Segmentation fault) ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/835766 Title: package dhcp3-client 3.1.3-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script killed by signal (Segmentation fault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/835766/+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 835766] Re: package dhcp3-client 3.1.3-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script killed by signal (Segmentation fault)
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/835766 Title: package dhcp3-client 3.1.3-2ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script killed by signal (Segmentation fault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/835766/+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
[Blueprint server-o-windows-paravirtual-drivers] Packaging of Windows Guest Paravirtual Drivers
Blueprint changed by Al Stone: Whiteboard changed: Problems: - PV Drivers cannot be installed on an exhisting or pre-installed Win VM - Red Hat PV Drivers are signed and allow install on exhisting guests, drivers must be signed to be installed (initial) for 2008/Win 7 - Signed drivers can be installed but are not supported by Microsoft unless WHQLed (MS Certiified and couter-signed) - RH owns copyright, and while it remains GPL2, they could fork it any time, leaving us responsible for bugfixes. == Questions == - Is there an outside source for these drivers? - WHQL support boundries? - Who will own/maintain and run the certification tests on LTS releases the drivers once signed/WHQLed? - Partner or Multiverse == Drivers == - SCSI (2x/3x speed increase) - Network (decrease latency but may be flaky) - Serial (used?) - Balloon (unknown/untested) Priorities: 1) SCSI, 2) Network (if not flaky), 3) Baloon, 4) Serial, 1) 2008 R2 SP1/Win 7, 2) everything else Work Items: - [ahs3] Build the latest drivers from the latest source: TODO + [ahs3] Build the latest drivers from the latest source: DONE (see +https://launchpad.net/kvm-guest-drivers-windows for downloads) [markashtonb] Find out if we want to sign, WHQL, support (possibly code updates), Logo, assign build/test responsibilities for driver updates/LTS releases: TODO [mahmoh] Get input on release(s) to certify from hallyn (target latest LTS + latest Natty): DONE - - per hallyn, 10.04.02 and 11.04 64 bit server releases (ISOs, no updates, June) - should be good + - per hallyn, 10.04.02 and 11.04 64 bit server releases (ISOs, no updates, June) - should be good [mahmoh] Test the drivers as possible - 1) 2008 R2/SCSI on LTS, 2) Natty? : TODO Compare driver performance to existing WHQLed performance (wishlist): TODO -- Packaging of Windows Guest Paravirtual Drivers https://blueprints.launchpad.net/ubuntu/+spec/server-o-windows-paravirtual-drivers -- 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
Invitation to ubuntu-server declined by zulcss
Hello Ubuntu Server Team, Chuck Short (zulcss) has declined the invitation to make Ubuntu Server Team (ubuntu-server) a member of UBUNTU - AL (linux-traipu). https://launchpad.net/~linux-traipu -- 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 513273] Re: kvm with -vga std is broken since karmic
I care about this bug and I can test against bochs within 24 hours. I should be using vgabios 0.6b and whatever bochs is current in Ubuntu, right? -- kvm with -vga std is broken since karmic https://bugs.launchpad.net/bugs/513273 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 513273] Re: kvm with -vga std is broken since karmic
Using the vgabios from Dustin's PPA, bochs from Ubuntu (I'm running a 10.4 beta, so that's 2.4.2-1ubuntu1), and the guest OS is a Debian 3.0 image from Bochs' Sourceforge page. I can run X11 at 1024x768, 24-bit color. Can't get any higher, but that's as likely a guest-OS limitation as anything (anyone trying to run GUI systems in Bochs is a severe masochist). Mode switching, grayscale modes, text-graphics mode all worked smoothly. Also, kvm-qemu (from the command-line) is back to working (guest OS here is Win7). I can get up to 1600x1200 there, switched between all modes from 800x600 to 1600x1200 with no problems. If there are any specific tests that need to be run I'd be glad to give 'em a whack. -- kvm with -vga std is broken since karmic https://bugs.launchpad.net/bugs/513273 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 224791] Re: nut upsmon not observing it's config file
OK, I think I have a plausible hypothesis for my experience and a configuration change that makes the annoying WALL messages go away. First, although my battery is at 100% when I check is--and so the low battery message seems wrong, there is something else going on. I have a couple of things attached to the APC UPS and ups.load is very high. I have the sense that when ups.load crossed over from the 60% area into the 70% area a low battery condition was communicated to upsmon. If this hypothesis is correct, this may be just a design characteristic, not a driver bug. Second, upsmon seems to have some defaults that I didn't understand. I had commented out my normal LOWBATT configuration (NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC) to try to kill the WALL messages. That didn't work. What I ended up doing was setting LOWBATT to NOTIFYFLAG LOWBATT SYSLOG. This seems to have worked. There are now lowbatt messages in syslog, but no WALL messages. So, the upshot of all this is that I think I should withdraw the bug report. Sorry for sharing my learning experience with you. -- al -- nut upsmon not observing it's config file https://bugs.launchpad.net/bugs/224791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut 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 224791] Re: nut upsmon not observing it's config file
** Attachment added: upsmon.conf http://launchpadlibrarian.net/14047343/upsmon.conf -- nut upsmon not observing it's config file https://bugs.launchpad.net/bugs/224791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut 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
Re: [Bug 222761] Re: [SRU] upsd doesn't start NOT 221737
On Tue, 2008-04-29 at 07:41 +, Martin Pitt wrote: Chuck, that looks much better already. However, the changelog says nut group, whereas the patch puts the nut user into dialout. Which one is right and intended? This comment suggests that a fix to the problem is adding the user nut to the group dialout. Do I understand correctly? I had done this already to handle permissions on the port my UPS was attached to. That is, the owner.group for /dev/ttyS0 is root.dialout and so to get nut to work one has to do an adduser nut dialout. Doing an adduser nut nut, which fixes the problem, seems to me to be a hack, not a proper fix. I ask again, when the code was built, was the argument -with-user=nut given to configure? -- [SRU] upsd doesn't start NOT 221737 https://bugs.launchpad.net/bugs/222761 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut 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
