I ran tdbtool to check the tdb files while winbind was working properly and they all reported OK. I ran it again after killing winbind, after it crashed, and again they all showed up as being OK.
I was also beginning to think it was a hardware memory fault as we recently added extra RAM to the server. But the Ubuntu server is running as a VM under VMWare ESXi and none of the other VMs (or the hypervisor itself for that matter) on the server are having errors. The physical server itself also uses ECC memory so I would have that would have caught any errors. We'll run a full memory diagnostic on the physical server when we get a chance during the next couple of days. I'm having a little trouble running apport-collect at the moment. I just get connection timed out errors. Googling the issue, it looks like it's because we are behind a proxy (our local squid proxy forwards all traffic to our ISPs proxy). I'll look into running winbind under valgrind. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1100787 Title: Samba 3.6.3 segfault or panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1100787/+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
