[Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot
Also, once I have installed the update on the DNS server, if I run apt- get update it queries TYPE62321 record. 22-Mar-2017 06:04:37.406 queries: info: client 127.0.0.1#38103 (gb.archive.ubuntu.com.comlaude.lon2): query: gb.archive.ubuntu.com.comlaude.lon2 IN TYPE62321 + (127.0.0.1) This server is also an apt-cacher server, if i restart apt-cacher, then it queries A records correctly again. 22-Mar-2017 06:05:37.426 queries: info: client 127.0.0.1#52629 (gb.archive.ubuntu.com): query: gb.archive.ubuntu.com IN A + (127.0.0.1) Again, the question is what else needs to be restarted? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: glibc update caused NSS ABI break To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot
To add to that, I just manually updated another running webserver, and boom. The apache+php webserver uses DNS to resolve the database server, which it can no longer do after the update, bringing the site down. It sends these incorrect TYPE62321 DNS queries to our DNS server. 22-Mar-2017 05:33:01.205 queries: info: client 172.16.x.x#59821 (mysql.internal.domain): query: mysql.internal.domain IN TYPE62321 + (172.16.x.x) In this case, restarting apache2 clears the issue. I don't know if anything else also needs restarting (so i did a reboot after to be sure). If it helps, I also have traditional resolv.conf instead of resolvconf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: Ubuntu 14.04 broken during PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot
Just like my earlier comment, this _fix_ *broke* a running system after it was automatically applied. Start-Date: 2017-03-22 04:17:12 Commandline: /usr/bin/unattended-upgrade Upgrade: libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), locales:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), libc-bin:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), multiarch-support:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7) End-Date: 2017-03-22 04:17:34 Immediately after that, the system is no longer able to resolve names. On my DNS server, I can see this is sending queries of TYPE62321 instead of A 22-Mar-2017 04:17:30.407 queries: info: client 172.16.x.x#63762 (host.interna.domain): query: host.interna.domain IN TYPE62321 + (172.16.1.10) A reboot clears the issue, but the point is that applying the update is still a "critical" bug because it breaks [some] running systems. In this case, the system is running apache+php. It might be that it only effects certain things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: Ubuntu 14.04 broken during PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674532] Re: Ubuntu 14.04 broken during PXE boot
Hi To extend the info on this one: unattended-upgrades updated this package today, and caused the same issue for me, causing servers to stop resolving DNS internally. Rebooting after installing resolved the issue, suggesting the update itself is fine, but the process of updating breaks resolution. After updating a server (without reboot), the internal DNS servers received odd queries of type TYPE20736 (no idea what that is) 21-Mar-2017 10:38:49.627 queries: info: client 172.16.x.x#49803 (host.internal.domain): query: host.internal.domain IN TYPE20736 + (172.16.x.x) After rebooting said server, it starts querying normal type A records again. I also run some authoritative DNS servers, and have seen the same query type from the public - suggesting that other servers out in the wild are experiencing the same issue! 21-Mar-2017 14:22:22.578 queries: client x.x.x.x#43836 (www.domain.com): query: www.domain.com IN TYPE20736 - (x.x.x.x) I realize this is not directly related to the subject of this bug, but I think its relevant. Cheers, Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674532 Title: Ubuntu 14.04 broken during PXE boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1674532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 309776] Re: jaunty xorg 100% cpu usage
Same thing here with Mobile GM965/GL960 on Sony Vaio; however, I have just cycled between Gnome and KDE a few times, and the problem only seems to exists in GNOME (every time). My xorg.conf is clean (dpkg-reconfigure) and compiz is disabled, though it was working fine (didn't hang my machine) Attached is a Diff between the Xorg.0.log between Gnome/Kde ** Attachment added: Xorg.0.log.diff http://launchpadlibrarian.net/21472874/Xorg.0.log.diff -- jaunty xorg 100% cpu usage https://bugs.launchpad.net/bugs/309776 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 309776] Re: jaunty xorg 100% cpu usage
After a cold boot, it has cleared for a while. when it happens again i will try that too. -- jaunty xorg 100% cpu usage https://bugs.launchpad.net/bugs/309776 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231888] Re: switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB)
I may also point out, that the uk layout was set during install (i assume) or at least before i touched it. Somebody on ubuntu-uk mentioned trying gb instead, and that does work. I have attached the log for that too, in case its helpful. ** Attachment added: Xorg.0.log_gb http://launchpadlibrarian.net/14640893/Xorg.0.log_gb -- switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB) https://bugs.launchpad.net/bugs/231888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231888] Re: switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB)
... and here is when i have commented out the line, and all is working cheers ** Attachment added: Xorg.0.log_working http://launchpadlibrarian.net/14640835/Xorg.0.log_working -- switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB) https://bugs.launchpad.net/bugs/231888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231888] Re: switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB)
Attached is Xorg log when the line is not commented out (and CTRL+ALT+Fn doesn't work). ** Attachment added: Xorg.0.log_not http://launchpadlibrarian.net/14640825/Xorg.0.log_not -- switching to tty fails on a Sony Vaio (Intel 965/Core 2 Duo/2GB) https://bugs.launchpad.net/bugs/231888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231888] [NEW] switching to tty
Public bug reported: Binary package hint: xserver-xorg-core Hi I have looked at a few other bugs which seem similar, but not the same - and I have a work-around for the following. I am running Kubuntu 8.04 (went from Alpha-5 to Final, then reinstalled) on a Sony Vaio (Intel 965/Core 2 Duo/2GB). Switching (CTRL+ALT+F1 etc) to terminals didn't work (no flashing screen, nothing - and in konsole: it would just print P on the screen.). After messing around (and some assistance from ubuntu-uk), I found i needed to disable the keyboard model in xorg.conf and set it up and KDE's regional settings. Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc105 # Option XkbLayout uk EndSection Not such a high priority, but perhaps needs attention. P.S. Many other bugs/comments relating to this issue mention video drivers - but using using the 'vesa' driver as apposed to 'intel' made no difference. Thanks ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- switching to tty https://bugs.launchpad.net/bugs/231888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 214669] [NEW] apt-get update/grub menu.lst
Public bug reported: Hi I am not sure this really counts as a bug, but i have just done an apt- get upgrade on my 8.04 Beta i386-server When it came to the Kernel update, it asked about the menu.lst: should it keep the current version or install the package maintainers version. I have not manually edited the menu.lst since install (theres no dual boot or anything). If i had selected keep the current version it would not have added the new kernel to the menu.lst. I can confirm this as a diff on the previous and new version showed that that was the only change. Like i say, not really a bug - but i don't think it should ask you as some may panic and keep the current version (as I normally would with something like postfix or bind) The update was from 2.6.24-12-server to 2.6.24-15-server Cheers, thedarkwinter ** Affects: ubuntu Importance: Undecided Status: New -- apt-get update/grub menu.lst https://bugs.launchpad.net/bugs/214669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128714] Re: Screen resolition changes after fullscreen mode
hi sorry, i was on holiday. just tried it, and messed around with the video settings, and it doesn't happen (even using opengl)??? ... this may sound weird, i don't know if there has been an updated nvidia driver in the last few weeks but its not happening on any of the others now ??? Is there a way i can check to see whats updates have been applied? cheers, tdw -- Screen resolition changes after fullscreen mode https://bugs.launchpad.net/bugs/128714 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128714] Re: Screen resolition changes after fullscreen mode
Okay i've played around a bit with the two drivers. Frozen bubble does not cause a problem with nv or nvidia driver Most of those games (3d) dont work with the nv driver so i couldn't test, but i have tested some more games on nvidia Lincity/Nexuiz/Open Arena/Wormux/Assault Cube/Ultimate Stunts/GL-117 all did not cause the problem. The only one i've found that i can add the the above list is Warcraft 3 (Wine again). Anything more i can do? -- Screen resolition changes after fullscreen mode https://bugs.launchpad.net/bugs/128714 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128714] Screen resolition changes after fullscreen mode
Public bug reported: After going into fullscreen mode (usually in games, if not always?) the screen resolution in kde changes: Low priority I am running Kubuntu 7.04 (i386), NVidia proprietary driver on a 6800. (AMD X2 based) My default resolution is 1152x864. After playing a game, regardless of the resolution in the game (tried 800 - 1280) and exiting, i return to the desktop in 1024x768. When going to the system settings it still says its in 1152. To fix the problem i have to change the resolution to 1024, and then back to 1152. This occurs when playing: PlaneShift (native) RegNum(native) Doom2 (doomsday engine) W-o-Warcraft (Wine) ... and more ** Affects: Ubuntu Importance: Undecided Status: New -- Screen resolition changes after fullscreen mode https://bugs.launchpad.net/bugs/128714 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61231] Kernel reverted to 386 version
Public bug reported: Binary package hint: linux-image-2.6-amd64-generic Hi Firstly Im running AMD64 (6.06) installed from the AMD64 Desktop CD. Im not entirely sure how this happened, i just noticed this morning when the automatic updates came up, there was an update kernel to 386, so i did the uname -r thing, and i am currently running 386 version(!?!), and doing a search in synaptic for linux image it doesn't even give me the amd64-generic package to select. Yesterday it came up with a kernel update but i didn't really look at what it was, i just let it install. Dont know if thats helpful at all to you... Michael ** Affects: linux-meta (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Kernel reverted to 386 version https://launchpad.net/bugs/61231 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 16824] Re: incorrect groot setting after installation
Just to add my 2 cents!! My system is AMD64 (more detail prob not relevant as i have had the same problem on two different AMD64 motherboards) HDD config: 2 HDD: 1 SATA2, 1 IDE As SATA is faster than IDE i have used it as my primary drive, and disabled the IDE drive in the CMOS so that windows recognized the SATA2 is HD0 at boot-time. When installing ubuntu (5.10 and 6.06) it installs everything in the right place etc, but detects the SATA2 as HD1 and the IDE as HD0, and therefore the grub menu.lst uses ROOT(HD1,x) instead of (HD0,x). This is very simple to fix manually, but whenever there is a Kernel update, debconf(?) rewrites the menu.lst file back to (HD1,x). For whats its worth: FilesystemSize Used Avail Use% Mounted on /dev/sda9 29G 2.8G 25G 10% / varrun 1014M 104K 1014M 1% /var/run varlock 1014M 4.0K 1014M 1% /var/lock udev 1014M 124K 1014M 1% /dev devshm 1014M 0 1014M 0% /dev/shm lrm 1014M 19M 996M 2% /lib/modules/2.6.15-26-386/volatile /dev/sda8 17G 395M 16G 3% /home /dev/sda1 40G 14G 26G 34% /media/c-drive /dev/sda5 143G 65G 78G 46% /media/d-drive /dev/hdc1 56G 30G 27G 53% /media/music /dev/hdc2 56G 24G 33G 43% /media/video I'm not a very advanced user, so forgive some of my more assumptive comments! 1 Last note, when i install SuSE 10 on the same system - grub worked without a problem. Michael -- incorrect groot setting after installation https://launchpad.net/bugs/16824 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
