Vampire a Samba4 domain to Samba3?
timnboys at gmail.com
Fri Mar 18 11:23:43 MDT 2011
Hi, I can help you fix samba4 to work when it locks up, all you have to do
is enter this command: "samba -i -M single -d 20"(which is I do everytime I
start samba4, which starts samba4)(considering that samba4 is in your
path). and if it says it is already running, get the process number that
samba4 is running under, then enter this into your command prompt(which is
shell on linux), "kill samba4processnumber" which you replace
"samba4processnumber" with your samba4 process number which you got by
running the above command("samba -i -M single -d 20") which is assumming
that you have samba4 in your $PATH variable. and then once you issue the
kill command to samba4 then you just start samba4 again, and it will work as
usual(I know this is not the way you would want to do this considering that
you production machines, but it works.)
Please email me back if you have any more problems.
On Fri, Mar 18, 2011 at 9:37 AM, Christian Huldt <christian at solvare.se>wrote:
> Hi Mat
> fre 2011-03-18 klockan 09:47 +0300 skrev Matthieu Patou:
> > On 18/03/2011 05:29, Taylor, Jonn wrote:
> > > On 03/17/2011 05:18 PM, Matthieu Patou wrote:
> > >> Hi Taylor& Christian
> > >>>> The default, ldb.
> > >>>>
> > >>>> I assume we would need to get the dc replication up as a simple
> > >>>> rsync of
> > >>>> (parts of) samba/private wouldn't suffice as replication?
> > >>>>
> > >>>>
> > >>> This is the same problem that I have been having. I was seeming is
> > >>> ldb transactions or samba4 would completely crash. I even sent you
> > >>> and dumps on this problem.
> > >>>
> > >> Well normally the replication for ldb using vampire should just work I
> > >> vampirized a domain one more time with success last days.
> > >>
> > >> Can you resend the logs related to your pb (or point me the message).
> > >> I might have just forget about it !
> > >> Sorry !
> > >>
> > >> Matthieu.
> > >>
> > > Mat, I forwarded you the 2 messages that I sent you.
> > >
> > Yeah got them, at least one didn't ring a bell at all for me so I don't
> > remember reading it ;-(.
> > In order to have a more useful backtrace we need a real dump of samba to
> > see how it was when it crashed.
> > This can be done by adding:
> > panic action = /usr/local/src/samba4/selftest/gdb_backtrace
> I added that, but the problem has come up three times i six months, so I
> can't really say when we get something out...
> We had yet another incident today (before I added the panic action
> unfortunately), the only thing I found in the log was a few entries like
> this (a few entries per machine that lost connectivity to the server
> that is) and not a huge build up om memory usage or anything, I assume
> it was those two samba processes that didn't go away with a simple
> [Fri Mar 18 13:30:06 2011 CET,
> schannel_fetch_session_key_tdb: Failed to find entry with key
More information about the samba-technical