[Bug 571572] [NEW] krb5 prefers the reverse pointer no matter what for locating service tickets.
Public bug reported:
I'm trying to upgrade workstations to lucid an fails to access our
kerberos enabled websites. It reveals that the krb5 implementation in
lucid now tries to resolve the reverse dns and aquire a tikket for
service/reverse dns instead of service/what the user typed in the
first place.
The latter behavior is what the MS environment does and is what Ubuntu
has done (i think) until Lucid. A diff of the sourcecode from hardy
revealse that we now hint the getaddrinfo with AI_CANONNAME which it
didnt before.
Applying below patch enables the old behaviour.
--- krb5-1.8.1+dfsg/src/lib/krb5/os/sn2princ.c.orig 2010-04-29
09:04:11.401567914 +0200
+++ krb5-1.8.1+dfsg/src/lib/krb5/os/sn2princ.c 2010-04-29 09:04:21.762191834
+0200
@@ -112,7 +112,7 @@
memset(hints, 0, sizeof(hints));
hints.ai_family = AF_INET;
-hints.ai_flags = AI_CANONNAME;
+//hints.ai_flags = AI_CANONNAME;
try_getaddrinfo_again:
err = getaddrinfo(hostname, 0, hints, ai);
if (err) {
** Affects: krb5 (Ubuntu)
Importance: Undecided
Status: New
--
krb5 prefers the reverse pointer no matter what for locating service tickets.
https://bugs.launchpad.net/bugs/571572
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Since the problem is in the clientside kerberos libraries it affects all kerberos enabled stuff. -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Tried.. had that before.. but doesn't work any more. (and isn't documented in man krb5.conf either). -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Hi Sam. I agree.. the current behaviors seems to be excactly what is in the code and in the documentation. Never the less it is a change from earlier versions of Ubuntu and a change that makes Ubuntu + Firefox work in a different way than MS Windows + MSIE (negoiating different tickets), thus breaking Single Signon in typical Kerberos enabled environments.. our is a corporate one with Active Directory as Kerbereos and both MS IIS and Ubuntu Apache + mod_auth_kerb on the serverside. Used to work.. lucid breaks it.. As far as I can tell, the change snug in between MIT kerberos 1.6 and 1.8 . Jesper -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
I agree that it is a partial workaround.. it fixes the Ubuntu/Firefox + apache combination. But without changing the same thing for all the IIS servers it would still render my Ubuntu/Firefox + IIS SSO broken. Since I only administrate the Linux stuff, and the other side genereally are very reluctant to do change to only fit linux, then patching it locally is much more doable in my environment. Anyway, now the bug is at least here to document it for other people hitting the same wall. Jesper -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 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 571572] [NEW] krb5 prefers the reverse pointer no matter what for locating service tickets.
Public bug reported:
I'm trying to upgrade workstations to lucid an fails to access our
kerberos enabled websites. It reveals that the krb5 implementation in
lucid now tries to resolve the reverse dns and aquire a tikket for
service/reverse dns instead of service/what the user typed in the
first place.
The latter behavior is what the MS environment does and is what Ubuntu
has done (i think) until Lucid. A diff of the sourcecode from hardy
revealse that we now hint the getaddrinfo with AI_CANONNAME which it
didnt before.
Applying below patch enables the old behaviour.
--- krb5-1.8.1+dfsg/src/lib/krb5/os/sn2princ.c.orig 2010-04-29
09:04:11.401567914 +0200
+++ krb5-1.8.1+dfsg/src/lib/krb5/os/sn2princ.c 2010-04-29 09:04:21.762191834
+0200
@@ -112,7 +112,7 @@
memset(hints, 0, sizeof(hints));
hints.ai_family = AF_INET;
-hints.ai_flags = AI_CANONNAME;
+//hints.ai_flags = AI_CANONNAME;
try_getaddrinfo_again:
err = getaddrinfo(hostname, 0, hints, ai);
if (err) {
** Affects: krb5 (Ubuntu)
Importance: Undecided
Status: New
--
krb5 prefers the reverse pointer no matter what for locating service tickets.
https://bugs.launchpad.net/bugs/571572
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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Since the problem is in the clientside kerberos libraries it affects all kerberos enabled stuff. -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Tried.. had that before.. but doesn't work any more. (and isn't documented in man krb5.conf either). -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Hi Sam. I agree.. the current behaviors seems to be excactly what is in the code and in the documentation. Never the less it is a change from earlier versions of Ubuntu and a change that makes Ubuntu + Firefox work in a different way than MS Windows + MSIE (negoiating different tickets), thus breaking Single Signon in typical Kerberos enabled environments.. our is a corporate one with Active Directory as Kerbereos and both MS IIS and Ubuntu Apache + mod_auth_kerb on the serverside. Used to work.. lucid breaks it.. As far as I can tell, the change snug in between MIT kerberos 1.6 and 1.8 . Jesper -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
Hi Russ. I cannot say anything about what other are experiencing.. but in our setup we haven't put the final hostname in the keytab (and neither did the guys that only cared about MSIE+IIS). And all Ubuntu releases (from around Dapper) and up and until Lucid has worked for us. So seen from an Ubuntu perspective, this is a regression.. wether or not it is desired to fix it I dont know? But I guess until Windows changes behaviour (thus all the configuration of the Windows servers), I'll have to maintain this patch locally for our installation. An it is a fair assumption to say that our setup is fairly standard. Would a patch that makes the behaviour configurable be acceptable? Jesper -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 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 571572] Re: krb5 prefers the reverse pointer no matter what for locating service tickets.
I agree that it is a partial workaround.. it fixes the Ubuntu/Firefox + apache combination. But without changing the same thing for all the IIS servers it would still render my Ubuntu/Firefox + IIS SSO broken. Since I only administrate the Linux stuff, and the other side genereally are very reluctant to do change to only fit linux, then patching it locally is much more doable in my environment. Anyway, now the bug is at least here to document it for other people hitting the same wall. Jesper -- krb5 prefers the reverse pointer no matter what for locating service tickets. https://bugs.launchpad.net/bugs/571572 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 28380] Re: Autofs fails to update /net with new shares from server
Hi Dave Thank you for finally attending to the bug. Well since the problem now persists in all official releases of Ubuntu as of now, allthough fixed in the current development branch, dont you think it is a bit premature to close the bug. Even as invalid since fixed is what you actually are doing. As far as I know autofs is a part of main in all distributions done. Jesper ** Changed in: autofs (Ubuntu) Status: Incomplete = Confirmed -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- 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 28380] Re: Autofs fails to update /net with new shares from server
Hi Dave Thank you for finally attending to the bug. Well since the problem now persists in all official releases of Ubuntu as of now, allthough fixed in the current development branch, dont you think it is a bit premature to close the bug. Even as invalid since fixed is what you actually are doing. As far as I know autofs is a part of main in all distributions done. Jesper ** Changed in: autofs (Ubuntu) Status: Incomplete = Confirmed -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28380] Re: Autofs fails to update /net with new shares from server
It is really dissapointing .. but there has been posted an awfull lot of automated crap in this bug, by people who either: * Didnt read the initial bug or * Did try out the steps to reproduce Even though it can be done on any installation, just going ahead using the five points above. The problem is (AFAIK) reproducible on any version of Ubuntu going from, dapper and up til today, since you still ship autofs4 and not autofs5 as default. Autofs5 has been released for two years by now. Sensible answers to this bug would have been stuff like: * We dont care about autofs, even though we ship it in main * We cannot reproduce the bug using above steps. (No-one has even claimed that they have tried so far). .. and a lot of other constructive feedback. .. I just tried on Karmic and the problem is still there, allthough it might have been slightly better, since the problem is only occouring if someone actively uses the mountpoint. .. once again (karmic test). $ sudo apt-get install nfs-kernel-server autofs $ edit /etc/auto.master and enable /net $ sudo /etc/init.d/autofs restart $ mkdir /tmp/test1 /tmp/test2 $ edit /etc/exports and insert /tmp/test1 *(ro,no_subtree_check) $ sudo exportfs -a $ showmount -e localhost Export list for localhost: /tmp/test1 * $ cd /net/localhost/tmp; ls test1 $ edit /etc/exports and insert /tmp/test2 *(ro,no_subtree_check) $ sudo exportfs -a $ sudo /etc/init.d/autofs reload Reloading automounter: checking for changes ... Reloading automounter map for: /net $ ls test1 $ # Here we should have seen test2 .. $ ls /net/localhost/tmp/ test1 $ # Here it should have been again. The fix is to ship autofs5 .. not 4.. 4 years, 10 semi-auto generated messages from people systems.. and the fix is even posted in the comments and still no actions. Jesper -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. -- 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 28380] Re: Autofs fails to update /net with new shares from server
It is really dissapointing .. but there has been posted an awfull lot of automated crap in this bug, by people who either: * Didnt read the initial bug or * Did try out the steps to reproduce Even though it can be done on any installation, just going ahead using the five points above. The problem is (AFAIK) reproducible on any version of Ubuntu going from, dapper and up til today, since you still ship autofs4 and not autofs5 as default. Autofs5 has been released for two years by now. Sensible answers to this bug would have been stuff like: * We dont care about autofs, even though we ship it in main * We cannot reproduce the bug using above steps. (No-one has even claimed that they have tried so far). .. and a lot of other constructive feedback. .. I just tried on Karmic and the problem is still there, allthough it might have been slightly better, since the problem is only occouring if someone actively uses the mountpoint. .. once again (karmic test). $ sudo apt-get install nfs-kernel-server autofs $ edit /etc/auto.master and enable /net $ sudo /etc/init.d/autofs restart $ mkdir /tmp/test1 /tmp/test2 $ edit /etc/exports and insert /tmp/test1 *(ro,no_subtree_check) $ sudo exportfs -a $ showmount -e localhost Export list for localhost: /tmp/test1 * $ cd /net/localhost/tmp; ls test1 $ edit /etc/exports and insert /tmp/test2 *(ro,no_subtree_check) $ sudo exportfs -a $ sudo /etc/init.d/autofs reload Reloading automounter: checking for changes ... Reloading automounter map for: /net $ ls test1 $ # Here we should have seen test2 .. $ ls /net/localhost/tmp/ test1 $ # Here it should have been again. The fix is to ship autofs5 .. not 4.. 4 years, 10 semi-auto generated messages from people systems.. and the fix is even posted in the comments and still no actions. Jesper -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291070] [NEW] snmp crash at bootup
Public bug reported: Ubuntu Hardy amd64 with all patches. Sometimes when snmpd starts it dies with: [ 374.996791] snmpd[8897] trap divide error rip:7ffd4be9dc2c rsp:7fff54832550 error:0 Other times it is: [5631127.259786] snmpd[27035]: segfault at 7f5160145000 ip 7f51600ded00 sp 7fff68d3d2d8 error 4 in libnetsnmp.so.15.1.0[7f51600b4000+91000] [5631275.353511] snmpd[28154]: segfault at 7f194383e000 ip 7f19437d7d00 sp 7fff4c435a88 error 4 in libnetsnmp.so.15.1.0[7f19437ad000+91000] [5631416.563465] snmpd[28931]: segfault at 7f5495451000 ip 7f54953ead00 sp 7fff9e048698 error 4 in libnetsnmp.so.15.1.0[7f54953c+91000] [5631501.448326] snmpd[29144]: segfault at 7f2b6fa6b000 ip 7f2b6fa04d00 sp 7fff78662728 error 4 in libnetsnmp.so.15.1.0[7f2b6f9da000+91000] [5631587.790769] snmpd[29770]: segfault at 7f19565b5000 ip 7f195654ed00 sp 7fff5f1ae818 error 4 in libnetsnmp.so.15.1.0[7f1956524000+91000] [5634535.721029] snmpd[5779]: segfault at 7fde3d4c ip 7fde3d459d00 sp 7fff460b7728 error 4 in libnetsnmp.so.15.1.0[7fde3d42f000+91000] [5646356.761825] snmpd[2423]: segfault at 7fdd5769a000 ip 7fdd57633d00 sp 7fff602918f8 error 4 in libnetsnmp.so.15.1.0[7fdd57609000+91000] [5646839.929888] snmpd[3663]: segfault at 7f39ca774000 ip 7f39ca70dd00 sp 7fffd336d718 error 4 in libnetsnmp.so.15.1.0[7f39ca6e3000+91000] [5650509.728074] snmpd[14482]: segfault at 816000 ip 7f550e2acd00 sp 7fff16f0b578 error 4 in libnetsnmp.so.15.1.0[7f550e282000+91000] [5701859.034895] snmpd[18370]: segfault at 814000 ip 7f84ace5cd00 sp 7fffb5abd128 error 4 in libnetsnmp.so.15.1.0[7f84ace32000+91000] [5736108.873400] snmpd[13268]: segfault at 812000 ip 7f25d8918d00 sp 7fffe1577588 error 4 in libnetsnmp.so.15.1.0[7f25d88ee000+91000] Running it a second time may bring it up. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- snmp crash at bootup https://bugs.launchpad.net/bugs/291070 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp 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 291070] [NEW] snmp crash at bootup
Public bug reported: Ubuntu Hardy amd64 with all patches. Sometimes when snmpd starts it dies with: [ 374.996791] snmpd[8897] trap divide error rip:7ffd4be9dc2c rsp:7fff54832550 error:0 Other times it is: [5631127.259786] snmpd[27035]: segfault at 7f5160145000 ip 7f51600ded00 sp 7fff68d3d2d8 error 4 in libnetsnmp.so.15.1.0[7f51600b4000+91000] [5631275.353511] snmpd[28154]: segfault at 7f194383e000 ip 7f19437d7d00 sp 7fff4c435a88 error 4 in libnetsnmp.so.15.1.0[7f19437ad000+91000] [5631416.563465] snmpd[28931]: segfault at 7f5495451000 ip 7f54953ead00 sp 7fff9e048698 error 4 in libnetsnmp.so.15.1.0[7f54953c+91000] [5631501.448326] snmpd[29144]: segfault at 7f2b6fa6b000 ip 7f2b6fa04d00 sp 7fff78662728 error 4 in libnetsnmp.so.15.1.0[7f2b6f9da000+91000] [5631587.790769] snmpd[29770]: segfault at 7f19565b5000 ip 7f195654ed00 sp 7fff5f1ae818 error 4 in libnetsnmp.so.15.1.0[7f1956524000+91000] [5634535.721029] snmpd[5779]: segfault at 7fde3d4c ip 7fde3d459d00 sp 7fff460b7728 error 4 in libnetsnmp.so.15.1.0[7fde3d42f000+91000] [5646356.761825] snmpd[2423]: segfault at 7fdd5769a000 ip 7fdd57633d00 sp 7fff602918f8 error 4 in libnetsnmp.so.15.1.0[7fdd57609000+91000] [5646839.929888] snmpd[3663]: segfault at 7f39ca774000 ip 7f39ca70dd00 sp 7fffd336d718 error 4 in libnetsnmp.so.15.1.0[7f39ca6e3000+91000] [5650509.728074] snmpd[14482]: segfault at 816000 ip 7f550e2acd00 sp 7fff16f0b578 error 4 in libnetsnmp.so.15.1.0[7f550e282000+91000] [5701859.034895] snmpd[18370]: segfault at 814000 ip 7f84ace5cd00 sp 7fffb5abd128 error 4 in libnetsnmp.so.15.1.0[7f84ace32000+91000] [5736108.873400] snmpd[13268]: segfault at 812000 ip 7f25d8918d00 sp 7fffe1577588 error 4 in libnetsnmp.so.15.1.0[7f25d88ee000+91000] Running it a second time may bring it up. ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: New -- snmp crash at bootup https://bugs.launchpad.net/bugs/291070 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 231746] Re: kernel crash in iov_iter_advance (caused by nfs-kernel-server)
We're also seing this kernel bug in relation to NFS .. (not using XEN at all); Aug 4 14:56:00 ko kernel: [263156.166854] PGD 8063 PUD 9063 PMD 0 Aug 4 14:56:00 ko kernel: [263156.166905] CPU 2 Aug 4 14:56:00 ko kernel: [263156.166926] Modules linked in: nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc autofs4 iptable_filter ip_tables x_ tables parport_pc lp parport loop joydev ipv6 psmouse evdev serio_raw pcspkr jedec_probe cfi_probe gen_probe mtd chipreg map_funcs i2c_nforce2 i2c_c ore button shpchp pci_hotplug k8temp ext3 jbd mbcache pata_amd pata_acpi sr_mod cdrom usb_storage libusual usbhid hid sg sd_mod mptsas mptscsih mptb ase scsi_transport_sas qla2xxx scsi_transport_fc e1000 scsi_tgt ata_generic ehci_hcd ohci_hcd libata scsi_mod usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse Aug 4 14:56:00 ko kernel: [263156.167218] Pid: 7150, comm: nfsd Not tainted 2.6.24-19-server #1 Aug 4 14:56:00 ko kernel: [263156.167246] RIP: 0010:[iov_iter_advance+0x66/0x80] [iov_iter_advance+0x66/0x80] iov_iter_advance+0x66/0x80 Aug 4 14:56:00 ko kernel: [263156.167292] RSP: 0018:8101fa8478e8 EFLAGS: 00010246 Aug 4 14:56:00 ko kernel: [263156.167317] RAX: RBX: 1000 RCX: Aug 4 14:56:00 ko kernel: [263156.167360] RDX: RSI: 1000 RDI: 8101fa847980 Aug 4 14:56:00 ko kernel: [263156.167402] RBP: 1000 R08: R09: Aug 4 14:56:00 ko kernel: [263156.167444] R10: 81000400 R11: R12: 0005ba1f8000 Aug 4 14:56:00 ko kernel: [263156.167487] R13: 1000 R14: 8101760241d8 R15: Aug 4 14:56:00 ko kernel: [263156.167530] FS: 7f9a5e8106e0() GS:8101fb042380() knlGS: Aug 4 14:56:00 ko kernel: [263156.167574] CS: 0010 DS: ES: CR0: 8005003b Aug 4 14:56:00 ko kernel: [263156.167600] CR2: 81000408 CR3: 55597000 CR4: 06e0 Aug 4 14:56:00 ko kernel: [263156.167643] DR0: DR1: DR2: Aug 4 14:56:00 ko kernel: [263156.167686] DR3: DR6: 0ff0 DR7: 0400 Aug 4 14:56:00 ko kernel: [263156.167730] Process nfsd (pid: 7150, threadinfo 8101fa846000, task 8101fb8947e0) Aug 4 14:56:00 ko kernel: [263156.167774] Stack: 80286a9e 8101e8df4600 81033ec88680 0001 Aug 4 14:56:00 ko kernel: [263156.167823] 8101fa847b90 0005ba0f9000 8101fa847b10 8101e8df4600 Aug 4 14:56:00 ko kernel: [263156.167871] 8101760241d8 882559a0 8101760240c8 882559a0 Aug 4 14:56:00 ko kernel: [263156.167903] Call Trace: Aug 4 14:56:00 ko kernel: [263156.167940] [generic_file_buffered_write+0x1de/0x6b0] generic_file_buffered_write+0x1de/0x6b0 Aug 4 14:56:00 ko kernel: [263156.167979] [__generic_file_aio_write_nolock+0x24f/0x400] __generic_file_aio_write_nolock+0x24f/0x400 Aug 4 14:56:00 ko kernel: [263156.168028] [ext3:generic_file_aio_write+0x64/0x450] generic_file_aio_write+0x64/0xd0 Aug 4 14:56:00 ko kernel: [263156.168069] [ext3:ext3_file_write+0x23/0xc0] :ext3:ext3_file_write+0x23/0xc0 Aug 4 14:56:00 ko kernel: [263156.168100] [ext3:ext3_file_write+0x0/0xc0] :ext3:ext3_file_write+0x0/0xc0 Aug 4 14:56:00 ko kernel: [263156.168129] [do_sync_readv_writev+0xcb/0x110] do_sync_readv_writev+0xcb/0x110 Aug 4 14:56:00 ko kernel: [263156.168161] [__alloc_pages+0x9d/0x3d0] __alloc_pages+0x9d/0x3d0 Aug 4 14:56:00 ko kernel: [263156.168189] [80254260] autoremove_wake_function+0x0/0x30 Aug 4 14:56:00 ko kernel: [263156.168222] [ext3:__get_free_pages+0x1b/0x1320] __get_free_pages+0x1b/0x40 Aug 4 14:56:00 ko kernel: [263156.168251] [do_readv_writev+0xfd/0x230] do_readv_writev+0xfd/0x230 Aug 4 14:56:00 ko kernel: [263156.168293] [8843c9e2] :nfsd:nfsd_setuser+0x82/0x1f0 Aug 4 14:56:00 ko kernel: [263156.168327] [88434f6c] :nfsd:nfsd_setuser_and_check_port+0x5c/0x70 Aug 4 14:56:00 ko kernel: [263156.168379] [88436790] :nfsd:nfsd_vfs_write+0xf0/0x3d0 Aug 4 14:56:00 ko kernel: [263156.168410] [__dentry_open+0x1a7/0x200] __dentry_open+0x1a7/0x200 Aug 4 14:56:00 ko kernel: [263156.168443] [88436fbc] :nfsd:nfsd_open+0x12c/0x1e0 Aug 4 14:56:00 ko kernel: [263156.168477] [8843731d] :nfsd:nfsd_write+0x10d/0x120 Aug 4 14:56:00 ko kernel: [263156.168512] [8843f86b] :nfsd:nfsd3_proc_write+0x10b/0x160 Aug 4 14:56:00 ko kernel: [263156.168547] [88432271] :nfsd:nfsd_dispatch+0xb1/0x240 Aug 4 14:56:00 ko kernel: [263156.168597] [8838bdad] :sunrpc:svc_process+0x47d/0x7e0 Aug 4 14:56:00 ko kernel: [263156.168627] [802362c0] default_wake_function+0x0/0x10 Aug 4 14:56:00 ko kernel: [263156.168658] [__down_read+0x12/0xb1] __down_read+0x12/0xb1 Aug 4 14:56:00 ko kernel: [263156.168689]
[Bug 214810] Re: Kernel Panic due to null pointer dereference in do_add_mount()
I can reproduce it on a 7.10 system: May 19 16:02:51 node15 kernel: [2059317.829560] PGD efe18067 PUD efe19067 PMD 0 May 19 16:02:51 node15 kernel: [2059317.922748] CPU 1 May 19 16:02:51 node15 kernel: [2059317.948928] Modules linked in: nfs lockd sunrpc autofs4 ipv6 usbhid hid uhci_hcd ehci_hcd usbk bd fuse parport_pc lp parport af_packet i2c_amd756 i2c_core amd_rng serio_raw pcspkr shpchp psmouse pci_hotplug k8temp evdev ext3 jbd mbcache sg sd_mod ide_cd cdrom ata_generic libata floppy tg3 mptspi mptscsih mptbase scsi_transport_spi scsi_mod ohci_hcd usbc ore amd74xx ide_core thermal processor fan capability commoncap May 19 16:02:51 node15 kernel: [2059318.394824] Pid: 22862, comm: mount.nfs Not tainted 2.6.22-14-generic #1 May 19 16:02:51 node15 kernel: [2059318.477001] RIP: 0010:[graft_tree+76/304] [graft_tree+76/304] graft_tree+0x4c/0x130 May 19 16:02:51 node15 kernel: [2059318.573826] RSP: 0018:8100ccf55c48 EFLAGS: 00010246 May 19 16:02:51 node15 kernel: [2059318.639381] RAX: 8100bb90f4e0 RBX: ffec RCX: May 19 16:02:51 node15 kernel: [2059318.726753] RDX: 8100bc60f100 RSI: 8100ccf55e58 RDI: 81001b04ae00 May 19 16:02:51 node15 kernel: [2059318.814124] RBP: 81001b04ae00 R08: R09: 8100ee6f6980 May 19 16:02:51 node15 kernel: [2059318.901493] R10: 1785c20a R11: 0007 R12: 8100ccf55e58 May 19 16:02:51 node15 kernel: [2059318.988864] R13: R14: 000b R15: 000b May 19 16:02:51 node15 kernel: [2059319.076237] FS: 2b2f50a1e6e0() GS:8100faab7180() knlGS:f7d616b0 May 19 16:02:51 node15 kernel: [2059319.175036] CS: 0010 DS: ES: CR0: 8005003b May 19 16:02:51 node15 kernel: [2059319.245784] CR2: 00b2 CR3: c45b CR4: 06e0 May 19 16:02:51 node15 kernel: [2059319.333156] Process mount.nfs (pid: 22862, threadinfo 8100ccf54000, task 8100facdb4a0) May 19 16:02:51 node15 kernel: [2059319.438187] Stack: 8100ccf55e58 8100ccf55e60 81001b04ae00 802b1fa0 May 19 16:02:51 node15 kernel: [2059319.536468] 0006 1b04ae00 8100e22d5000 8100e22d4000 May 19 16:02:51 node15 kernel: [2059319.627371] 8100e00be000 802b3271 0010 May 19 16:02:51 node15 kernel: [2059319.716092] Call Trace: May 19 16:02:51 node15 kernel: [2059319.749550] [do_add_mount+160/352] do_add_mount+0xa0/0x160 May 19 16:02:51 node15 kernel: [2059319.816142] [do_mount+1329/2000] do_mount+0x531/0x7d0 May 19 16:02:51 node15 kernel: [2059319.879618] [__handle_mm_fault+1985/2912] __handle_mm_fault+0x7c1/0xb60 May 19 16:02:51 node15 kernel: [2059319.952451] [autoremove_wake_function+0/48] autoremove_wake_function+0x0/0x30 May 19 16:02:51 node15 kernel: [2059320.029428] [__up_read+33/176] __up_read+0x21/0xb0 May 19 16:02:51 node15 kernel: [2059320.091866] [do_page_fault+971/2160] do_page_fault+0x3cb/0x870 May 19 16:02:51 node15 kernel: [2059320.160540] [zone_statistics+125/128] zone_statistics+0x7d/0x80 May 19 16:02:51 node15 kernel: [2059320.229212] [error_exit+0/132] error_exit+0x0/0x84 May 19 16:02:51 node15 kernel: [2059320.291648] [copy_mount_options+273/384] copy_mount_options+0x111/0x180 May 19 16:02:51 node15 kernel: [2059320.365513] [sys_mount+155/256] sys_mount+0x9b/0x100 May 19 16:02:51 node15 kernel: [2059320.428990] [system_call+126/131] system_call+0x7e/0x83 May 19 16:02:51 node15 kernel: [2059320.493504] May 19 16:02:51 node15 kernel: [2059320.513341] May 19 16:02:51 node15 kernel: [2059320.513342] Code: 0f b7 81 b2 00 00 00 25 00 f0 00 00 3d 00 40 00 00 48 8b 47 May 19 16:02:51 node15 kernel: [2059320.692552] RSP 8100ccf55c48 Happens during mount.nfs from the automounter (we dont manually mount any NFS shares). I did get 2 of them since yesterday. -- Kernel Panic due to null pointer dereference in do_add_mount() https://bugs.launchpad.net/bugs/214810 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 181996] Re: NFS server: lockd: server not responding
Well.. since the problem only is present on a gutsy kernel.. it is quite obvious that you can reproduce on the hardy kernel. The patch above is from the patch-stream between gutsy and hardy. Jesper -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 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 227848] [NEW] boot order wrong for iscsi
Public bug reported: Binary package hint: open-iscsi The boot order is still wrong in some cases for iscsi. iscsi probably waits for networking to start (due to upstart and dependencies) but it does not wait long enough, so link are available before. Trace from bootup: [EMAIL PROTECTED]:~# dmesg | perl -ane 'print if $_ =~ /(eth|bond|iscsi)/i; ' [ 145.733504] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection [ 146.052622] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection [ 146.372001] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection [ 146.701361] e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection [ 154.506735] Driver 'sd' needs updating - please use bus_type methods [ 154.506382] Driver 'sr' needs updating - please use bus_type methods [ 163.088171] eth4: NIU Ethernet 00:14:4f:bb:23:a8 [ 163.088176] eth4: Port type[XMAC] mode[10G:FIBER] XCVR[XPCS] phy[xgf] [ 164.305607] eth5: NIU Ethernet 00:14:4f:bb:23:a9 [ 164.305611] eth5: Port type[XMAC] mode[10G:FIBER] XCVR[XPCS] phy[xgf] [ 165.450618] Loading iSCSI transport class v2.0-724. [ 165.461844] iscsi: registered transport (tcp) [ 165.505437] iscsi: registered transport (iser) [ 169.129554] Ethernet Channel Bonding Driver: v3.2.3 (December 6, 2007) [ 169.129563] bonding: MII link monitoring set to 100 ms [ 169.297933] e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 169.321894] bonding: bond0: enslaving eth0 as a backup interface with an up link. [ 169.447624] e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 169.461239] bonding: bond0: enslaving eth1 as a backup interface with an up link. [ 169.597327] e1000: eth2: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 169.610971] bonding: bond0: enslaving eth2 as a backup interface with an up link. [ 169.747033] e1000: eth3: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 169.760631] bonding: bond0: enslaving eth3 as a backup interface with an up link. [ 170.102554] ADDRCONF(NETDEV_UP): bond0: link is not ready [ 177.340214] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 188.001939] bond0: no IPv6 routers present So the iscsi is tried to start at 165 and first at 177 the link is ready. ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- boot order wrong for iscsi https://bugs.launchpad.net/bugs/227848 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 214476] Re: open-iscsi fails to install
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present in hardy (just hit it) Jesper -- open-iscsi fails to install https://bugs.launchpad.net/bugs/214476 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi 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 214476] Re: open-iscsi fails to install
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present in hardy (just hit it) Jesper -- open-iscsi fails to install https://bugs.launchpad.net/bugs/214476 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi 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 214476] Re: open-iscsi fails to install
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present in hardy (just hit it) Jesper -- open-iscsi fails to install https://bugs.launchpad.net/bugs/214476 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 214476] Re: open-iscsi fails to install
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present in hardy (just hit it) Jesper -- open-iscsi fails to install https://bugs.launchpad.net/bugs/214476 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 223759] Re: ifupdown integration broken
I've now tried it from hardy-proposed, and can confirm that it works excellent. Jesper -- ifupdown integration broken https://bugs.launchpad.net/bugs/223759 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 218215] Re: Module iscsi_tcp not included in linux-image
I can confirm, both the bug in hardy, and the fix in proposed-updates. The Hardy iSCSI installation is useless until this has been fixed. -- Module iscsi_tcp not included in linux-image https://bugs.launchpad.net/bugs/218215 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 223759] Re: ifupdown integration broken
No. I integrated the changes from the diff manually on my system. (They were very trivial). Jesper -- ifupdown integration broken https://bugs.launchpad.net/bugs/223759 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 223759] Re: ifupdown integration broken
I can confirm both bug and fix. This is vital, it breaks networking on any server running with bonded network interfaces. .. worked flawless in hardy-1 Another change that seems to be releated. Symbolik names in /etc/modprobe.d/options doesnt work any more: May 1 22:02:33 hest kernel: [ 175.644153] bonding: Error: Invalid bonding mode 802.3ad options bond0 mode=4 miimon=100 # Apparently 802.3ad doesnt work any more (worked in hardy-1) # options bond0 mode=802.3ad miimon=100 Jesper -- ifupdown integration broken https://bugs.launchpad.net/bugs/223759 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 181996] Re: NFS server: lockd: server not responding
SRU is a StableReleaseUpdate .. thats described in the links above. The process to get fixes pushed to a stable release. -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 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 181996] Re: NFS server: lockd: server not responding
Changing to Confirmed.. as Described by Leann Ogasawara when the patches are confirmed to work on a gutsy system. ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Won't Fix = Confirmed -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 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 181996] Re: NFS server: lockd: server not responding
I can confirm that the above 2 patches solves the problem. The problem is really grave.. making the NFS-server in gutsy rarely usable. The locking problem occoured about every second day here.. I applied the patch over a week ago and hasn't seen the problem since. Jesper -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 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 181996] Re: NFS server: lockd: server not responding
Leann Ogasawara: Should we provide more to get a SRU for this bug in gutsy? Jesper -- NFS server: lockd: server not responding https://bugs.launchpad.net/bugs/181996 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 28380] Re: Autofs fails to update /net with new shares from server
Problem reproducible on gutsy .. according to the autofs-list autofs5 should be used (currently released). ** Changed in: autofs (Ubuntu) Status: Incomplete = New -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 28380] Re: Autofs fails to update /net with new shares from server
Hi Mathias. May I ask why you marked it as incomplete? I'm willing to provide whatever more information needed, but nothing is asked for in the bug and the problem is a real PITA when having a large NFS based network. Jesper Mathias Gug wrote: ** Changed in: autofs (Ubuntu) Status: New = Incomplete -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192080] [NEW] shutdown fails.. nfs
Public bug reported: Binary package hint: open-iscsi Hi. A server with iscsi may look like this: ls /etc/rc0.d/K* lrwxrwxrwx 1 0 0 17 Nov 23 09:02 K09apache2 - ../init.d/apache2 lrwxrwxrwx 1 0 0 16 Nov 7 11:12 K19autofs - ../init.d/autofs lrwxrwxrwx 1 0 0 24 Nov 7 11:23 K19postgresql-8.1 - ../init.d/postgresql-8.1 lrwxrwxrwx 1 0 0 24 Nov 23 10:36 K19postgresql-8.2 - ../init.d/postgresql-8.2 lrwxrwxrwx 1 0 0 28 Nov 7 11:22 K20nagios-nrpe-server - ../init.d/nagios-nrpe-server lrwxrwxrwx 1 0 0 20 Jan 17 20:15 K20open-iscsi - ../init.d/open-iscsi lrwxrwxrwx 1 0 0 17 Nov 7 11:22 K20postfix - ../init.d/postfix lrwxrwxrwx 1 0 0 20 Nov 7 10:58 K25hwclock.sh - ../init.d/hwclock.sh lrwxrwxrwx 1 0 0 20 Nov 7 11:50 K50alsa-utils - ../init.d/alsa-utils lrwxrwxrwx 1 0 0 20 Nov 7 11:23 K79nfs-common - ../init.d/nfs-common lrwxrwxrwx 1 0 0 27 Dec 4 11:07 K80nfs-kernel-server - ../init.d/nfs-kernel-server lrwxrwxrwx 1 0 0 19 Nov 7 11:22 K91bacula-fd - ../init.d/bacula-fd Which is bad.. if you have nfs exported our iscsi-volume. Then shutdown will fail due to the try to get open-iscsi stopped before the users of the disk is stopped. So nfs should be shut down much earlier in the process or open-iscsi much later. (i suggest the latter) sorta like mv K20open-iscsi S50open-iscsi ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- shutdown fails.. nfs https://bugs.launchpad.net/bugs/192080 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 192081] [NEW] startup iscsi at boot
Public bug reported: Binary package hint: open-iscsi Startup iscsi at boot happens to late.. open-iscsi should start rigtht after networking and before any applications are being startet. mv rc2.d/S20open-iscsi rcS.d/S41open-iscsi This fix doesnt make checkfs work. Jesper ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- startup iscsi at boot https://bugs.launchpad.net/bugs/192081 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 192158] Re: iscsi checkfs and mount
making moutnall.sh adhere to _netdev option. ** Attachment added: mountall.sh.patch http://launchpadlibrarian.net/11991161/mountall.sh.patch -- iscsi checkfs and mount https://bugs.launchpad.net/bugs/192158 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 192158] Re: iscsi checkfs and mount
For making checkfs.sh adhere to _netdev option ** Attachment added: checkfs patch http://launchpadlibrarian.net/11991156/checkfs.patch -- iscsi checkfs and mount https://bugs.launchpad.net/bugs/192158 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 192158] [NEW] iscsi checkfs and mount
Public bug reported: Binary package hint: open-iscsi When using the _netdev mount-option, fsck at boottime /etc/init.d/checkfs.sh and mount /etc/init.d/mountall.sh should avoid the device since those scripts are run before the network is available. Attached patches makes both checkfs.sh and mountall.sh aviod filesystem with the _netdev option. ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- iscsi checkfs and mount https://bugs.launchpad.net/bugs/192158 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 192158] Re: iscsi checkfs and mount
Added patches to checkfs.sh and mountall.sh for _netdev later in the bootprocess .. after open-iscsi has been started but before applications that use the device starts. ** Attachment added: checkfs-netdev.sh http://launchpadlibrarian.net/11991843/checkfs-netdev.sh -- iscsi checkfs and mount https://bugs.launchpad.net/bugs/192158 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 192158] Re: iscsi checkfs and mount
Same for mountall ** Attachment added: mountall-netdev.sh http://launchpadlibrarian.net/11991846/mountall-netdev.sh -- iscsi checkfs and mount https://bugs.launchpad.net/bugs/192158 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 185987] Re: Program not utillizing the CPU fully
** Attachment added: Screenshot of top http://launchpadlibrarian.net/11568383/Screenshot-1.png -- Program not utillizing the CPU fully https://bugs.launchpad.net/bugs/185987 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 185987] [NEW] Program not utillizing the CPU fully
Public bug reported: Binary package hint: linux-image-2.6.20-16-generic Sometimes (not particular reprodusable) we have jobs like the one on the screenshot allocated on our compute cluster. This jobs is not utillizing the CPU's as it should. 2 individual processes on a 2-CPU machine leaves 1 x 100% cpu and about 50% idle CPU. The cluster is Ubuntu Feisty 7.04 machines with: [EMAIL PROTECTED]:~$ uname -a Linux node04 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 7.04 Release:7.04 Codename: feisty [EMAIL PROTECTED]:~$ uname -a Linux node04 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 244 stepping: 10 cpu MHz : 1794.886 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips: 3595.24 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 5 model name : AMD Opteron(tm) Processor 244 stepping: 10 cpu MHz : 1794.886 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow bogomips: 3589.83 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: New -- Program not utillizing the CPU fully https://bugs.launchpad.net/bugs/185987 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 28380] Re: Autofs fails to update /net with new shares from server
Søren. No It was not accessible. Problem easily reproducible on feisty -- Autofs fails to update /net with new shares from server https://bugs.launchpad.net/bugs/28380 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134205] 2.2.0 released
Public bug reported: Binary package hint: bacula 2.2.0 has been released. ** Affects: bacula (Ubuntu) Importance: Undecided Status: New -- 2.2.0 released https://bugs.launchpad.net/bugs/134205 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 105648] Re: nis client fails to start at bootup
There is no log-messages about ypbind in syslog (neither when it tries to start during bootup or when it is started subsequently) -- nis client fails to start at bootup https://bugs.launchpad.net/bugs/105648 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105927] X is strange when shifting from X to console and back.
Public bug reported: On an Amd64 system upgraded from edgy to feisty, switching from X to console, makes the display act strange when shifting back. The LCD- monitor seems to be initialized wrong and is flicking in the view. The screen isn''t correctly redrawn either. Restarting X does not solve the problem but a complete reboot does bring X up correctly. # lspci | grep Gra 00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82Q963/Q965 Integrated Graphics Controller (rev 02) Xorg.0.log attached. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- X is strange when shifting from X to console and back. https://bugs.launchpad.net/bugs/105927 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105927] Re: X is strange when shifting from X to console and back.
Xorg.0.log attached ** Attachment added: Xorg.0.log http://librarian.launchpad.net/7301575/Xorg.0.log -- X is strange when shifting from X to console and back. https://bugs.launchpad.net/bugs/105927 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105648] Re: nis client fails to start at bootup
Strange.. Now I removed it from rc.local and it works fine. It must somehow be related to the other stuff of configuration on the system and/or the packages updated during the last 24 hours in feisty. It works now. $ nm-tool NetworkManager Tool State: connected print_devices(): didn't get a reply from NetworkManager. There are no available network devices. ... which probably is correct due to what I read in the other bugs? -- nis client fails to start at bootup https://bugs.launchpad.net/bugs/105648 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105648] Re: nis client fails to start at bootup
Ok.. bug found .. but no soloution. The problem only occours when an dhcp-adresse is assigned. Then does # nm-tool NetworkManager Tool get_nm_state(): didn't get a reply from NetworkManager. NetworkManager appears not to be running (could not get its state). instead of in the above situation where it was configured with a static ip-adress. Jesper -- nis client fails to start at bootup https://bugs.launchpad.net/bugs/105648 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105648] nis client fails to start at bootup
Public bug reported: Binary package hint: nis On an amd64 edgy upgraded to Feisty the nis client fails to start at bootup. Subsequently starting it by doing an /etc/init.d/nis start, brings it up just fine. ** Affects: nis (Ubuntu) Importance: Undecided Status: Unconfirmed -- nis client fails to start at bootup https://bugs.launchpad.net/bugs/105648 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 105651] nis client fails to start due to dbus stuff
Public bug reported: Binary package hint: nis On an edgy/amd64 system upgraded to feisty the nis client fails to start due to something with dbus. Setting $YPBINDOPTS=-no-dbus in /etc/default/nis solves this problem but the default configuration of the nis-client was broken. ** Affects: nis (Ubuntu) Importance: Undecided Status: Unconfirmed -- nis client fails to start due to dbus stuff https://bugs.launchpad.net/bugs/105651 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 28380] Re: Autofs fails to update /net with new shares from server
The problem still persists on edgy -- Autofs fails to update /net with new shares from server https://launchpad.net/bugs/28380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69836] Thinkpad X30 (prism 2.5) wireless card fails to work.
Public bug reported: Just opgraded my Thinkpad X30 from dapper to edgy and the wireless card failes to work. iwconfig doesnt report any wireless extentions on the card. Booting back into the old 2.6.15-27-686 makes it work again. lspci output: $ 01:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01) There is a thread here about apparently the excact same problem: http://ubuntuforums.org/showthread.php?p=168 ** Affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Thinkpad X30 (prism 2.5) wireless card fails to work. https://launchpad.net/bugs/69836 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68704] Re: bcm43xx in edgy doesn't connect to AP anymore
The module loads automatically: $ lsmod | grep bcm bcm43xx 124436 0 ieee80211softmac 30720 1 bcm43xx ieee80211 33608 2 bcm43xx,ieee80211softmac From dmesg: [17179589.724000] ieee80211_crypt: registered algorithm 'NULL' [17179589.756000] ieee80211: 802.11 data/management/control stack, git-1.1.13 [17179589.756000] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketreno @linux.intel.com [17179589.848000] bcm43xx driver $ iwconfig eth1 IEEE 802.11b/g ESSID:off/any Nickname:Broadcom 4311 Mode:Managed Frequency=2.484 GHz Access Point: Invalid Bit Rate=1 Mb/s Tx-Power=18 dBm RTS thr:off Fragment thr:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 But: $ sudo iwlist eth1 scanning eth1 No scan results (even tried iwconfig eth1 rate 11M as suggested on the wiki) -- bcm43xx in edgy doesn't connect to AP anymore https://launchpad.net/bugs/68704 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68704] Re: bcm43xx in edgy doesn't connect to AP anymore
The module loads automatically: $ lsmod | grep bcm bcm43xx 124436 0 ieee80211softmac 30720 1 bcm43xx ieee80211 33608 2 bcm43xx,ieee80211softmac From dmesg: [17179589.724000] ieee80211_crypt: registered algorithm 'NULL' [17179589.756000] ieee80211: 802.11 data/management/control stack, git-1.1.13 [17179589.756000] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketreno @linux.intel.com [17179589.848000] bcm43xx driver $ iwconfig eth1 IEEE 802.11b/g ESSID:off/any Nickname:Broadcom 4311 Mode:Managed Frequency=2.484 GHz Access Point: Invalid Bit Rate=1 Mb/s Tx-Power=18 dBm RTS thr:off Fragment thr:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 But: $ sudo iwlist eth1 scanning eth1 No scan results (even tried iwconfig eth1 rate 11M as suggested on the wiki) -- bcm43xx in edgy doesn't connect to AP anymore https://launchpad.net/bugs/68704 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68683] Re: Edgy doesn't let me switch to console
I can confirm that I miss the console on an Dell Inspiron 6400.. the screens are blank. Disabling splash form the kernel-boot-commandline give them back. Clean Edgy install. -- Edgy doesn't let me switch to console https://launchpad.net/bugs/68683 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68704] Re: bcm43xx in edgy doesn't connect to AP anymore
I have the same behaviour on a fresh Edgy installation on an Dell Inspiron 6400 (sometimes I get a lockup) but mostly I can only view the accesspoints, but not assosiate with them. The firmware has been installed using bcm43xx-fwcutter and the script coming in that package. -- bcm43xx in edgy doesn't connect to AP anymore https://launchpad.net/bugs/68704 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52260] Re: Kernel does not detect all luns.
Now I've tried the above suggestion, it does not seem to solve anything on Ubuntu.. I've tried adding it: 1) In the /etc/modprobe.d and reconfiguring initrd 2) Adding it on the commandline to the kernel boot parameters. 3) Even tried the old scsi_max_luns the same way. The aic7xxx module gives this output: Jul 11 08:06:20 atlas kernel: [ 100.649227] aic7xxx: Unknown parameter `max_luns' I've tried the same process on the scsi_mod-module .. as tha IBM article suggests. Thus it seems as it has been renamed again or there is another parameter that interfers with this setup. Dmesg from scsi1 the problematic controller.. [ 115.757774] scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 [ 115.75] Adaptec 29160 Ultra160 SCSI adapter [ 115.757778] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs [ 115.757780] [ 115.758171] Vendor: Zero-D X Model: -3i Rev: 0001 [ 115.758179] Type: Direct-Access ANSI SCSI revision: 03 [ 115.758188] scsi1:A:0:0: Tagged Queuing enabled. Depth 8 [ 115.758197] target1:0:0: Beginning Domain Validation [ 115.759090] target1:0:0: wide asynchronous [ 115.759722] target1:0:0: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31) [ 115.772156] target1:0:0: Domain Validation skipping write tests [ 115.772159] target1:0:0: Ending Domain Validation [ 115.772312] SCSI device sdb: 4294950912 512-byte hdwr sectors (2199015 MB) [ 115.772483] SCSI device sdb: drive cache: write back [ 115.772638] SCSI device sdb: 4294950912 512-byte hdwr sectors (2199015 MB) [ 115.772795] SCSI device sdb: drive cache: write back [ 115.772798] sdb: sdb1 [ 115.773159] sd 1:0:0:0: Attached scsi disk sdb [ 115.773267] scsi: host 1 channel 0 id 0 lun 0x0200080c0400 has a LUN larger than currently supported. [ 115.773273] scsi: host 1 channel 0 id 0 lun 0xff01 has a LUN larger than currently supported. [ 115.773494] scsi: host 1 channel 0 id 0 lun808529923 has a LUN larger than allowed by the host adapter [ 115.773879] scsi: host 1 channel 0 id 0 lun3078 has a LUN larger than allowed by the host adapter Jesper -- Kernel does not detect all luns. https://launchpad.net/bugs/52260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52609] Ubuntu standard depends on openssh-client not a meta-package for ssh
Public bug reported: ubuntu-standard depends on openssh-client.. thus using Ubuntu in a kerberos setup where ssh-krb5 is needed, ubuntu-standard will be force off the system. ** Affects: ubuntu-meta (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Ubuntu standard depends on openssh-client not a meta-package for ssh https://launchpad.net/bugs/52609 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52260] Kernel does not detect all luns.
Public bug reported: Binary package hint: linux-amd64-server Using an Adaptec SCSI controller on a external raid disk, that supplies 2 luns on same SCSI-id, Ubuntu does not automatically detect the second lun. Running the command: echo scsi add-single-device 1 0 0 1 /proc/scsi/scsi brings the device back up. This seems to be related to the aic7xxx scsi-driver since the qlogic ql2300 driver works in a similar setup. According to this: http://publib.boulder.ibm.com/infocenter/dsichelp/ds8000ic/index.jsp?topic=/com.ibm.storage.ssic.help.doc/f2c_linuxlunconfig_2hsaga.html putting max_luns=128 in modules.conf should help, but that doesnt change the situation for ubuntu. ** Affects: linux-meta (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Kernel does not detect all luns. https://launchpad.net/bugs/52260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
