On Wed, Apr 10, 2013 at 09:26:45PM -0500, Nick Semenkovich wrote:
I just had samba4 (git 69b3d19 from yesterday) crash while logging in as
administrator.
The login stalled, and on the samba4 AD DC, winbind stopped responding --
getent passwd stopped showing the domain entries, and commands
Is there any way we can get a backtrace from this? Also,
which platform are you running on? invalid opcode, that
kindof sounds like a compiler bug. I know that usually all
compiler bugs turn out to be just plain program defects,
so would it be possible that you run it under valgrind, just
to
I just had samba4 (git 69b3d19 from yesterday) crash while logging in as
administrator.
The login stalled, and on the samba4 AD DC, winbind stopped responding --
getent passwd stopped showing the domain entries, and commands that
showed some samba users (e.g. ls in a directory with domain owners,
Hi Amir,
this is a known and fixed issue in Samba 3.6.6.
It was known as Bug 9004 https://bugzilla.samba.org/show_bug.cgi?id=9004
and has been fixed by
o Andreas Schneider a...@samba.org
* BUG 8944 and 8567: Don't lookup the system user in pdb.
Do you need a patch for 3.6.1?
As far as I
Any idea what's going on here? I've installed samba's debug symbols hoping
to catch more if this happens again.
Samba domain member server (where the crash happened):
Samba: 3.4.7
Ubuntu: 10.04.4 LTS
Samba DC:
Samba: 3.6.6
Ubuntu: Quantal 12.10
[Thread debugging using libthread_db enabled]
Hello, i've migrate my domain samba-3.0.22-1 on old server (centos 4.3) to
samba-3.0.23c-2.el5.2.0.2 on new server (Centos 5.0). i'm use OpenLdap to
users accounts and computers accounts.
Procedure :
- stop old PDC;
- copy smb.conf and secrets.tdb on new server;
- start new PDC;
On the new
