Re: [bareos-devel] Re: Windows FD IPv6
On Wednesday, 12 October 2016 17:06:08 UTC+1, Bruno Friedmann wrote: > On mercredi, 12 octobre 2016 00.52:49 h CEST Dane Elwell wrote: > > On Tuesday, 11 October 2016 20:33:09 UTC+1, Bruno Friedmann wrote: > > > I believe for the moment this bug is stucked. > > > Someone needs to be able to provide a trace which is always > > > overcomplicated > > > under windows :-) > > > > > > Are you able to ? if yes please post result in the bugtracker. > > > > Hi Bruno, > > > > We have access to Windows developers who might be able to get this > > information, however can you clarify what you mean by a trace? If you can > > point us in the right direction we'll try and get the data you need. > > > > This bug is currently stopping a significant rollout of BareOS across our > > Windows systems, so any assistance you can provide would be helpful. > > > > Regards > > > > Dane > > A quick note, > > You have some parameters here > http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-36800027.10 > > and I would at least start the windows fd daemon with a -d 200 included in > its > service file to see if there's some elements > > You should obtain log in %programdata%\bareos normally (I don't have access > to > a windows plateform until next saturday). > > I know some tools exists under windows to trace what file sockets and ports > an > exe is using. > > I would also check if the problem is not linked to ipv6 privacy, network > connection going in with the public address and then output going on one of > private ipv6 ... (easy to setup under linux, don't know how to do that > quickly > under MS os...) > > > -- > > Bruno Friedmann > Ioda-Net Sàrl www.ioda-net.ch > Bareos Partner, openSUSE Member, fsfe fellowship > GPG KEY : D5C9B751C4653227 > irc: tigerfoot > > openSUSE Tumbleweed > Linux 4.7.6-1-default x86_64 GNU/Linux, nvidia: 367.44 > Qt: 5.7.0, KDE Frameworks: 5.26.0, Plasma: 5.8.0, kmail2 5.3.0 (QtWebEngine) Hi Bruno, I've provided traces for IPv6 and IPv4 at the bug tracker: https://bugs.bareos.org/view.php?id=477 Kind regards, Lee -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-devel] Re: Windows FD IPv6
Am 11.10.2016 um 17:49 schrieb leespottisw...@gmail.com: > On Tuesday, 11 October 2016 15:34:42 UTC+1, leespot...@gmail.com wrote: >> Hi, >> >> I am currently experiencing an issue identical to the one described within >> bug report: https://bugs.bareos.org/view.php?id=477 >> >> I have attempted to debug this, but this is completely outside my area of >> expertise - I was wondering whether anyone else has either worked around >> this issue, or can point me in the right direction? >> >> I am considering reverting back to IPv4, however IPv6 would be preferable. >> >> Lee > > Hi, > > It would appear that I may be experiencing the bug introduced between Bacula > 5.2.6 - 5.2.9: > https://sourceforge.net/p/bacula/mailman/message/29461163/ I assume the bug mentioned there as not related to this problem here. Bareos has been forked from bacula-5.2.13 and also the problem here is only with Windows. -- Jörg Steffens joerg.steff...@bareos.com Bareos GmbH & Co. KGPhone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-devel] Re: Windows FD IPv6
On mercredi, 12 octobre 2016 00.52:49 h CEST Dane Elwell wrote: > On Tuesday, 11 October 2016 20:33:09 UTC+1, Bruno Friedmann wrote: > > I believe for the moment this bug is stucked. > > Someone needs to be able to provide a trace which is always > > overcomplicated > > under windows :-) > > > > Are you able to ? if yes please post result in the bugtracker. > > Hi Bruno, > > We have access to Windows developers who might be able to get this > information, however can you clarify what you mean by a trace? If you can > point us in the right direction we'll try and get the data you need. > > This bug is currently stopping a significant rollout of BareOS across our > Windows systems, so any assistance you can provide would be helpful. > > Regards > > Dane A quick note, You have some parameters here http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-36800027.10 and I would at least start the windows fd daemon with a -d 200 included in its service file to see if there's some elements You should obtain log in %programdata%\bareos normally (I don't have access to a windows plateform until next saturday). I know some tools exists under windows to trace what file sockets and ports an exe is using. I would also check if the problem is not linked to ipv6 privacy, network connection going in with the public address and then output going on one of private ipv6 ... (easy to setup under linux, don't know how to do that quickly under MS os...) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.7.6-1-default x86_64 GNU/Linux, nvidia: 367.44 Qt: 5.7.0, KDE Frameworks: 5.26.0, Plasma: 5.8.0, kmail2 5.3.0 (QtWebEngine) -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-devel] Re: Windows FD IPv6
On Tuesday, 11 October 2016 20:33:09 UTC+1, Bruno Friedmann wrote: > > I believe for the moment this bug is stucked. > Someone needs to be able to provide a trace which is always overcomplicated > under windows :-) > > Are you able to ? if yes please post result in the bugtracker. Hi Bruno, We have access to Windows developers who might be able to get this information, however can you clarify what you mean by a trace? If you can point us in the right direction we'll try and get the data you need. This bug is currently stopping a significant rollout of BareOS across our Windows systems, so any assistance you can provide would be helpful. Regards Dane -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-devel] Re: Windows FD IPv6
On mardi, 11 octobre 2016 08.49:23 h CEST leespottisw...@gmail.com wrote: > On Tuesday, 11 October 2016 15:34:42 UTC+1, leespot...@gmail.com wrote: > > Hi, > > > > I am currently experiencing an issue identical to the one described within > > bug report: https://bugs.bareos.org/view.php?id=477 > > > > I have attempted to debug this, but this is completely outside my area of > > expertise - I was wondering whether anyone else has either worked around > > this issue, or can point me in the right direction? > > > > I am considering reverting back to IPv4, however IPv6 would be preferable. > > > > Lee I believe for the moment this bug is stucked. Someone needs to be able to provide a trace which is always overcomplicated under windows :-) Are you able to ? if yes please post result in the bugtracker. > > Hi, > > It would appear that I may be experiencing the bug introduced between Bacula > 5.2.6 - 5.2.9: https://sourceforge.net/p/bacula/mailman/message/29461163/ > > Could you please let me know whether the Bareos client is also affected by > this? > > Cheers, > Lee This bug was addressed in 5.2.10, and also fixed in bareos. The truth is somewhere else. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.7.6-1-default x86_64 GNU/Linux, nvidia: 367.44 Qt: 5.7.0, KDE Frameworks: 5.26.0, Plasma: 5.8.0, kmail2 5.3.0 (QtWebEngine) -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-devel] Re: Windows FD IPv6
On Tuesday, 11 October 2016 15:34:42 UTC+1, leespot...@gmail.com wrote: > Hi, > > I am currently experiencing an issue identical to the one described within > bug report: https://bugs.bareos.org/view.php?id=477 > > I have attempted to debug this, but this is completely outside my area of > expertise - I was wondering whether anyone else has either worked around this > issue, or can point me in the right direction? > > I am considering reverting back to IPv4, however IPv6 would be preferable. > > Lee Hi, It would appear that I may be experiencing the bug introduced between Bacula 5.2.6 - 5.2.9: https://sourceforge.net/p/bacula/mailman/message/29461163/ Could you please let me know whether the Bareos client is also affected by this? Cheers, Lee -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
