I have tried downgrading to 3.4, and I get the same (or very similar) issue - core dump when I try to connect.
Is Samba 3.4/3.5 just broken on FreeBSD 7.2 amd64? That seems crazy... I would go back to 3.3, but it's an unsupported version and not available in ports anymore ): On Thu, Sep 8, 2011 at 10:38 PM, John W <[email protected]> wrote: > A little more investigation seems to indicate that the gencache.tdb > error is actually not the issue. > In fact, I removed the file (since it is not necessary for operation), > and still got a core dump. > > So it looks like the reinit_after_fork() is the real problem. > But no clue why that would be happening. > > Any ideas? > Here's my uname -a: > > FreeBSD <myhostname-redacted> 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri > May 1 07:18:07 UTC 2009 > [email protected]:/usr/obj/usr/src/sys/GENERIC amd64 > > -John > > > On Thu, Sep 8, 2011 at 10:33 PM, John W <[email protected]> wrote: >> Ok, after looking at some logs, it turns out samba is dumping core ): >> >> Does anyone know what might be the cause of this? >> It seems related to my gencache.tdb file, but no idea what's going on really. >> >> log tail: >> >> [2011/09/08 22:29:41, 0] lib/util_tdb.c:tdb_log(682) >> tdb(/var/db/samba/gencache.tdb): tdb_reopen: file dev/inode has changed! >> [2011/09/08 22:29:41, 0] lib/util.c:reinit_after_fork(1054) >> tdb_reopen_all failed. >> [2011/09/08 22:29:41, 0] smbd/server.c:open_sockets_smbd(773) >> reinit_after_fork() failed >> [2011/09/08 22:29:41, 0] lib/util.c:smb_panic(1673) >> PANIC (pid 86439): reinit_after_fork() failed >> [2011/09/08 22:29:41, 0] lib/util.c:log_stack_trace(1777) >> BACKTRACE: 0 stack frames: >> [2011/09/08 22:29:41, 0] lib/fault.c:dump_core(231) >> dumping core in /var/log/samba/cores/smbd >> >> >> >> >> On Thu, Sep 8, 2011 at 9:53 PM, John W <[email protected]> wrote: >>> Hi, >>> >>> I recently updated my Samba from 3.3 to 3.5, and while that worked >>> fine, I can no longer access my shares - it asks for a password, which >>> fails even if I do enter a correct one. >>> >>> Here is one of my shares - very simple, I think: >>> >>> [myshare] >>> comment = My Share >>> path = /path/to/myshare >>> public = yes >>> read only = yes >>> writable = no >>> browseable = yes >>> printable = no >>> guest ok = yes >>> >>> At the top of my file, I have defined: >>> >>> guest account = smbguest >>> >>> Which is an account I created. >>> >>> Are there any gotchas when switching from 3.3 to 3.5 that might explain >>> this? >>> >>> Everything was working fine before. >>> >>> I have tried from both a WinXP machine and from smbclient, and neither >>> succeeds. >>> In the smbclient version, it asks for the password of the current >>> logged in user, and if I enter that password, I still get failure >>> (NT_STATUS_PIPE_BROKEN). >>> >>> >>> Any ideas? >>> >>> Thanks >>> -John >>> >> > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
