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.
A quick note,
You have some parameters here
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...)
Ioda-Net Sàrl www.ioda-net.ch
Bareos Partner, openSUSE Member, fsfe fellowship
GPG KEY : D5C9B751C4653227
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
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.