I also have this problem, using a very recent version from git. (see also: http://www.mail-archive.com/samba@lists.samba.org/msg124657.html )
Periodically, winbind seems to simply crash, and getent passwd & other ops (e.g. htop) stall. I'd also be happy to provide any debugging information needed. On Tue, Apr 16, 2013 at 11:29 AM, <sa...@nisx.de> wrote: > Hi, > > I have a problem with winbind, could anyone help me? > > Version: > root@leela:~# samba -V > Version 4.0.5 > root@leela:~# uname -a > Linux leela 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 > x86_64 x86_64 x86_64 GNU/Linux > > - First everything went fine: > root@leela:~# getent passwd > root:x:0:0:root:/root:/bin/bash > [...] > FUTURAMA+Administrator:*:0:513::/home/FUTURAMA/Administrator:/bin/bash > FUTURAMA+svtn:*:1008:513:Thomas Nolte as SV:/home/FUTURAMA/svtn:/bin/bash > > - For example I change a files owner to root: > root@leela:~# chown 0 /opt/samba/var/shares/profiles/svtn/ntuser.dat > > - Everything is still fine: > root@leela:~# ll /opt/samba/var/shares/profiles/svtn/ > insgesamt 3224 > drwxrws--- 33 FUTURAMA+svtn FUTURAMA+gf 4096 Apr 6 13:39 > Anwendungsdaten > [...] > -rw-rw---- 1 root FUTURAMA+gf 3145728 Apr 8 06:54 ntuser.dat > [...] > > - Now changing owner to 3000000 (Buildin/Administrator): > root@leela:~# chown 3000000 /opt/samba/var/shares/profiles/svtn/ntuser.dat > > - It needs many seconds to work. > root@leela:~# ll /opt/samba/var/shares/profiles/svtn/ > insgesamt 3224 > drwxrws--- 33 FUTURAMA+svtn FUTURAMA+gf 4096 Apr 6 13:39 > Anwendungsdaten > [...] > -rw-rw---- 1 3000000 FUTURAMA+gf 3145728 Apr 8 06:54 ntuser.dat > [...] > > - And if I look again, all users shown as numbers, not names: > root@leela:~# ll /opt/samba/var/shares/profiles/svtn/ > insgesamt 3224 > drwxrws--- 33 1008 1016 4096 Apr 6 13:39 Anwendungsdaten > [...] > -rw-rw---- 1 3000000 1016 3145728 Apr 8 06:54 ntuser.dat > [...] > root@leela:~# > > - And now all samba users gone. winbind -u is empty too. > root@leela:~# getent passwd > root:x:0:0:root:/root:/bin/bash > [...] > > - in the logfile I found this: > [2013/04/16 15:44:09, 0] ../lib/util/fault.c:72(fault_report) > =============================================================== > [2013/04/16 15:44:09, 0] ../lib/util/fault.c:73(fault_report) > INTERNAL ERROR: Signal 11 in pid 26194 (4.0.5) > Please read the Trouble-Shooting section of the Samba HOWTO > [2013/04/16 15:44:09, 0] ../lib/util/fault.c:75(fault_report) > =============================================================== > [2013/04/16 15:44:09, 0] ../lib/util/fault.c:144(smb_panic_default) > PANIC: internal error > > - After restart samba > root@leela:~# stop samba4 > root@leela:~# start samba4 > > - Alll users back now... > root@leela:~# getent passwd > root:x:0:0:root:/root:/bin/bash > [...] > FUTURAMA+Administrator:*:0:513::/home/FUTURAMA/Administrator:/bin/bash > FUTURAMA+svtn:*:1008:513:Thomas Nolte as SV:/home/FUTURAMA/svtn:/bin/bash > > Does anyone has an Idea? I've tried an older version (4.0.1) of samba too, > same problem. > > Regards > Thomas Nolte > -- > Nolte Infosysteme, Im Sikfeld 8, 38304 Wolfenbuettel > Tel 05331-946210, Fax 05331-946211, Handy 0170-5508198 > > Computer, Netzwerk, Kommunikation www.nisx.de > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba