On Tuesday 07 October 2014 10.30:03 Philipp Storz wrote: > Hello Bruno, > > very good that you want to debug on windows. > > You are lucky, because we now have windows debug packages that will install > the windows sourcecode > along with the binaries and instal binaries with debug information. > > You find them in the windows/debug download folder > for example here: > > http://download.bareos.org/bareos/release/14.2/windows/debug/ > > So please install the software from a windows debug package including the > sourcecode. > > > Then you need a gdb on windows which you can install via mingw-builds: > > http://sourceforge.net/projects/mingwbuilds/files/mingw-builds-install/mingw-builds-install.exe/download > > Select during install: > > Architecture -> x64 > Threads -> posix > Exception -> sjlj > Build Revision -> (newest) > > > After installation, we have a menu entry: Start -> All Programs -> > MinGW-Builds... -> Run terminal > > Here you can then use gdb to debug the daemons, e.g. > > gdb c:/path/to/bareos/bareos-fd.exe > > # then you have to tell gdb where the sourcecode is located with the > directory command > > dir c:/bareos-xxxxx/srv > > # then you can start the binary with > > run -d300 -f > > > Now you have a "normal" gdb session. > > You should of course run everything with administrator rights, and do not > forget to shutdown the > services first before you start the debug session. > > Good luck! > > > > Am 06.10.2014 13:56, schrieb Bruno Friedmann: > > Hello backup'ers > > > > I've setup and running one of my bareos systems on a pure ipv6 network > > (you need correct resolution, firewall rules etc) > > > > mostly restricting FD,DIR,SD with configuration like this > > > > DIRAddresses = { > > ipv6 = { addr = :: ; port = 9101 } > > # ipv4 = { addr = 0.0.0.0; port = 9101 } > > } > > > > everything is working well under Linux > > > > but now I've to integrate a windows 8.1 64bits client. > > I've applied the same trick for the sd and the bareos-fd.exe seems to start > > correctly > > > > netstat -tan under windows show the daemon listening only on ipv6 > > Connexion actives > > > > Proto Adresse locale Adresse distante État État > > de déchargement > > > > TCP 0.0.0.0:135 0.0.0.0:0 LISTENING > > InHost > > TCP 0.0.0.0:445 0.0.0.0:0 LISTENING > > InHost > > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING > > InHost > > TCP [::]:135 [::]:0 LISTENING > > InHost > > TCP [::]:445 [::]:0 LISTENING > > InHost > > TCP [::]:3389 [::]:0 LISTENING > > InHost > > TCP [::]:9102 [::]:0 LISTENING > > InHost > > > > but if I try to connect with the director or bareos-tray-monitor then I got > > only > > TCP [2001:41d0:2:f1de::55:aa44]:9102 > > [2001:41d0:2:f1de::ff:3c90]:33452 ESTABLISHED InHost > > and bareos-fd start to use 50% (2 full cpu) > > > > And no connections are made ... > > > > look like a crash with ipv6 > > > > If I filter to use only ipv4 the daemon work just prooving the setup is > > right. > > > > How is it possible to debug this nasty crap? > > > > > > >
ok thanks will try that tonight even if administrator right start to means nothing under 8,1 :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
