Samba coredump after update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Whooeeee... I've been fudging with this problem for a while without making headway...

A couple days ago I ran an update on a FC5 Xen Dom0 and all the corresponding FC5
DomU's. I didn't notice anything until I rebooted. At that point, Samba stopped
working completely and coredumps every couple minutes.

Kernel is 2.6.17-1.2187_FC5xenU
Samba is samba-3.0.23c-1.fc5

/var/log/messages is filled with:
Nov 22 16:26:12 xm-fc5-001 smbd[6174]: [2006/11/22 16:26:12, 0]
lib/util.c:smb_panic(1614)
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:   PANIC (pid 6174): internal error
Nov 22 16:26:12 xm-fc5-001 smbd[6174]: [2006/11/22 16:26:12, 0]
lib/util.c:log_stack_trace(1721)
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:   BACKTRACE: 20 stack frames:
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:    #0 smbd(log_stack_trace+0x2d) [0x78d8ad]
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:    #1 smbd(smb_panic+0x5d) [0x78d9dd]
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:    #2 smbd [0x77951a]
Nov 22 16:26:12 xm-fc5-001 smbd[6174]:    #3 [0xdde420]
Nov 22 16:26:13 xm-fc5-001 smbd[6174]:    #4
/lib/i686/nosegneg/libc.so.6(__strdup+0x1f) [0x98c5d3]
Nov 22 16:26:13 xm-fc5-001 smbd[6174]:    #5 /lib/libnsl.so.1(nis_list+0x5d2)
[0x18eb5f]
Nov 22 16:26:13 xm-fc5-001 smbd[6174]:    #6
/lib/libnss_nisplus.so.2(_nss_nisplus_setnetgrent+0x8f) [0x2e262e]

I've tried rolling back to the previous kernels in both Dom0 and DomU, but I'm not
certain if it's in any way related to Xen.

There are also multiple instances of:
Nov 22 03:52:32 xm-fc5-001 init: Id "co" respawning too fast: disabled for 5 minutes

I don't see anything in inittab or my runscripts.

Bugzilla show some Samba client issues with the .2200 kernel, but nothing

I saw this, but it appears to be SELinux related. SELinux is disabled in my machine:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192557

Others appear to be client related, whereas I'm trying to export a share to XP systems.

BTW, this will also bluescreen XP machines pretty consistently. If you attempt to
map/browse the broken CIFS share, after around six attempts XP (SP2, Media Center)
will bluescreen.

-- 
* The Digital Hermit   http://www.digitalhermit.com
* Unix and Linux Solutions   kwan@xxxxxxxxxxxxxxxxx

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux