Solved: Backburner 2016 manager issue

Anonymous · ‎05-03-2017

anyone have some idea what these error messages are

2017/05/03 10:38:26 WRN Could not broadcast FIND_SERVERS request on lo: A socket operation was attempted to an unreachable network.

2017/05/03 10:38:26 WRN Could not broadcast DISCOVER_SERVERS request on lo: A socket operation was attempted to an unreachable network.

server seem to connect to the manager ok

although I was seeing some of the servers registering twice

any thoughts here?

please help

adamk · ‎05-03-2017

Haven't seen this error before. But usually when Backburner starts with the network errors - we have to restart ALL machines including the manager. Good Luck!

Alfred.DeFlaminis · ‎05-18-2017

Hello @Anonymous and welcome to the community,

It usually means that backburner is unable to find a route to reach the remote host. Are you able to ping the machines on your network? Is DHCP enabled on your network or do you assign IP's manually? You may have a problem with your TCP/IP settings or configuration, or possibly an A/V is blocking a port or thinks the network isn't friendly. This issue at its' core is likely about IP routing. Are these machine all on the same domain? Subnet properly configured? Thanks for any additional information.

Best Regards,

Alfred.DeFlaminis · ‎05-19-2017

Hello @Anonymous,

I just wanted to follow up here, any progress on this issue?

Best Regards,

simonparish · ‎05-30-2017

After the recent Win10 creators update (May 2017) my Backburner Manager (2017) has been giving me constant warnings.

"WRN Could not broadcast FIND_SERVERS request on lo: A socket operation was attempted to an unreachable network"

"WRN Could not broadcast DISCOVER SERVERS request on lo : A socket operation was attempted to an unreachable network"

My render-slaves successfully register - and perform correctly.

However the Manager continues to spew out DISCOVER_SERVERS warnings.

One odd thing I noticed was that when Manager initially starts it adds a new client on IP 127.0.0.1 to the client list, which is the localhost. Is this correct, as I don't remember seeing it do that before?

Any clues to why it is doing this?

Alfred.DeFlaminis · ‎05-30-2017

Hello @simonparish,

Weird. Everything is working but you're getting those messages anyways? (Am I understanding this correctly?)

When the Anniversary Update came out it reset all kinds of permissions on various areas of windows and there were some problems in Max for a month or so afterwards. This may be a similar situation. I am not a programmer but if the method to communicate outward has changed drastically as a result of the Creator's update that may be another possible cause. In the meanwhile I will start asking questions on my end to see what I can find.

If I misunderstood you and it's not working properly, please answer the same questions as above for me and thanks!

Best Regards,

seda · ‎05-30-2017

Hi @Alfred.DeFlaminis

We are getting the same error on our backburner server. The server log displays the following on start up

.

Wiretap interface connected to the local manager

Could not broadcast FIND_SERVERS servers request on lo: a socket operation was attempted to reach an unreachable network

Could not broadcast DISCOVER_SERVERS servers request on lo: a socket operation was attempted to reach an unreachable network

.

then

Could not broadcast DISCOVER_SERVERS servers request on lo: a socket operation was attempted to reach an unreachable network

about every 2 mins or so.

It seems to be causing a range of issues (from completed render tasks prematurely to 'could not read/write file type' in textures folders). Some renders are rendering fine though.

Other potentially relevent factors:

- new NAS was installed recently

- new NUC was added to the network to run the server

I don't believe the Windows Creators update has been installed on any of our machines.

Any info you have on a potential fix would be much appreciated, it is starting to really mess with our project timelines!

simonparish · ‎05-31-2017

Hi @Alfred.DeFlaminis

It doesn't seem to be effecting my remote rendering, in that my 2 render boxes register OK with the manager, are shown as available in Monitor and can be rendered to using network render (i'm using distributed bucket rendering via Vray but the initial task is off-handed to backburner).

Recourse Files are picked up from a local NAS and the resulting frames are saved back to the NAS no problem.

It doesn't (as yet) seem to be causing any operational problems but obviously something is wrong. I'm pretty sure it only started happening after the anniversary update.

I will check that the render slaves have also been updated to the anniversary edition - the workstation (manager host) is OS version is 1703 build 15063.296

The render slaves don't seem to show the OS version so I 'll do some updating and see what happens.

Alfred.DeFlaminis · ‎05-31-2017

Hello @seda and @simonparish,

I'm currently communicating with QA about this one. This is a new error and I'm trying to hunt down more information. I have a couple questions and thanks for taking the time to answer them.

Are you all on Windows 10?

Creators Update or Anniversary Update?

Was it working before? Or never working?

Anything significant happen around the time this error started to show up?

Best Regards,

Anonymous · ‎05-31-2017

I too have this warning "Could not broadcast DISCOVER_SERVERS servers request on lo: a socket operation was attempted to reach an unreachable network".

Gets printed to manager at regular intervals, but the render jobs seem to be working correctly though.

I'm on Windows 10 creators update.

Don't remember doing any significant changes to the system other than creators update.

I'm not sure when this started, because I haven't used network rendering in a while, but I never got these warnings before the creators update.

Attached a screenshot, the end part of the warning is in Finnish here, but it's the same as above.

Alfred.DeFlaminis · ‎06-01-2017

Thank you for the information @Anonymous,

It seems after every major W10 update that certain permissions, services, etc. get disabled and it's always a guessing game as to which ones were disabled. If you have an IT department I would recommend talking to them about this issue. It's certainly a Windows configuration issue but as of yet I am not sure what service or function affects it. I am looking into WINS and uPNP/Network Discovery as I have a strong feeling it's related but since I can't repro it's a bit of a problem to isolate. Some of my searches are suggesting a problem with TCP/IP configurations or client side system or group policies in Windows. I have posted this question internally to get more suggestions.

Best Regards,

kevin_carrolldesign · ‎06-02-2017

I'm also getting this error in backburner. It happened in bb 2016 version, so installed from 3ds 2017 and still get the error.

I don't have any issue with functionality of backburner, but manager does show these errors.

Incidentally, I am now unable to connect to the license server on first start of 3ds 2017, and can't therefore use it (2016 is fine). I wonder if the problems are related?

I'm using a fresh 1 week old installation of Windows 10 10.0.15063, which I believe is the creators updated version.

Alfred.DeFlaminis · ‎06-02-2017

Thanks for the information @kevin_carrolldesign. I'm working with QA and development to try to repro this problem but so far I don't have anything to share.

The license service for 2016 is shared with 2017 so if one works and not the other then it may be a permissions or firewall issue. Can you check windows firewall for 2017? I did recently get an email about license servers on our end having a hiccup today, it may be just a result of that. I am still waiting on an update with more internally.

Best Regards,

simonparish · ‎06-05-2017

Hi AJ,

Just a bit more info for you. It looks like the Backburner server adds a new client at IP 127.0.0.1

It may be this new client (127.0.0.1) not responding that is creating the "could not DISCOVER_SERVER errors"

From the internet

"127.0.0.1 is the loopback Internet protocol (IP) address also referred to as the localhost. The address is used to establish an IP connection to the same machine or computer being used by the end-user."

Why would backburner be adding the localhost loopback IP as a new client?

If I start the BB server on my workstation I get a successful registration but still get the "could not DISCOVER_SERVER errors" errors.

As a suggestion for future releases it would be very handy to have a copy text feature including into BB to save having to manually type the error messages.

Alfred.DeFlaminis · ‎06-05-2017

Hello @simonparish,

Thank you for the detailed post, you are great! I tested at home this weekend on my laptop and even with BB 2016 it registers the localhost, so I think we can discard that. I have contacted a member of development who think it might be related to multicasting and it's currently being looked into. I wish I had more information but I am working on it. Thanks all for your patience.

Best Regards,

Alfred.DeFlaminis · ‎06-12-2017

Hello all,

I've been trying to repro this for a couple days and I cannot do so. For those who have this issue and cannot use backburner at all, do you all have double entries for the servers in the server list? Right now my best suggestion is to delete the backburner settings and recreate them by starting the program back up afterwards. Path below. Could you please try that for me?

C:\Users\%username%\AppData\Local

If this fails, can you try to uninstall and reinstall backburner? Thanks!

Best Regards,

kevin_carrolldesign · ‎06-13-2017

Backburner does actually work for me - it processes jobs although I'm only using it locally (the server is the same machine that the manager).

I do get the errors in the manager window.

I'm happy to reset settings to see if that makes a difference:

Is it the whole backburner folder within

C:\Users\%username%\AppData\Local ?

About the license issue I mentioned - it must've been on the autodesk end - not a network problem on my end, as its sorted itself now.

Alfred.DeFlaminis · ‎06-13-2017

Hello @kevin_carrolldesign,

If Backburner is still working fine let's not mess with it. I am specifically trying to target those people where it's no longer working. Thank you for the update though and I hope that's not a problem.

There was a license server outage for about an hour a few days ago (or maybe it was almost a week ago) but it's all resolved now. Thank you for your patience.

Best Regards,

guidomanfrotto · ‎06-20-2017

Have anyone figured out what is causing these warnings? Just upgraded the render manager and the slaves to Windows 10 Creators Update and I too started getting these warnings in Backburner Manager. Never seen them before. Everything works as before, I'm able to send and render jobs - just annoying to have these warnings pop up every two minutes. Something is clearly wrong and it seems Creators Update did something to cause the warnings in Manager.

I have tried removing all Backburner rules from the firewall and restarted+added them back to the firewall, but that didn't seem to remove the warnings. I've also tried disabling the firewall alltogether, no dice! Lastly I've tried both the "Disable IPv6" and the "Prefer IPv4 over IPv6" trick mentioned here:

https://forums.autodesk.com/t5/3ds-max-forum/incompatible-adapter-backburner-2017/m-p/7004216/highli...

So, just wanted to check if there's been any progress with finding out what is causing the issue.

Alfred.DeFlaminis · ‎06-20-2017

Hello @guidomanfrotto,

Thanks for the update. The IPv4 workaround for inability to connect is a good one, but this seems to be a base change in how Windows communicates over the network. I'm going to log this into the tracker which will get another more official round of attention on it. The reason I didn't just log it in the first place is because technically Backburner is only supported on Windows 7 and 8 as shown here. I still try to help even when it's not an officially supported OS, but if they change the basis of communications on that OS it may be trickier to resolve.

Best Regards,

Backburner 2016 manager issue

Backburner 2016 manager issue

Forums Links

Post to forums