get IP backburner server

[themaxxer]

hi all

I need some advice from pro's, but it's not vray related.
I have several renderslaves which are virtualized and start their system from an image (vhd) over the network, very complicated setup, but it worked well. so now the problem...
the backburner server. with version 2014 of backburner it was no problem, but with version 2016 it is. the server (2014) always filled in the IP address of related computer right, but with version 2016 it fills in (servername) "localhost" and not its IP address anymore. also if you delete the backburner.xml and restart it fills in "localhost" before it was the IP address. now the problem begins with the manager, because all renderslaves have the same name and it's impossible to work with it.
is it possible to set the backburner.xml to get the ip, or is there a way to write a script to get the IP and write it into the backburner.xml (servername)?

I need a workaround so I am pleased to get some ideas. thanks a lot.

best regards
themaxxer

[DanielBrew]

If you can remote desktop on to each of the render servers and type ipconfig into the command prompt it will tell you the ip address. Then you could try entering it manually into backburner server.

[themaxxer]

yes i know that... thanks, but I would like to have a automatic version, i have over 20 slaves, so this way is very time consuming and I have to make it every time I start all 20 servers...

[DanielBrew]

Sorry, I understand now, the server name gets reset because the servers boot from an image.

[themaxxer]

exactly, sorry for my bad explanation...

[DanielBrew]

It's strange that localhost doesn't work for you in Max 2016:

If you edit the backburner.xml on the image by removing servername, serverMAC and description lines:

<ServerSettings>
        <ManagerName>10.10.16.2</ManagerName>
        <AutoSearch>0</AutoSearch>
</ServerSettings>

These line will be rebuilt when Backburner is run and backburner should connect to the manager specified.

[themaxxer]

hm... strange. why does it work for you... my manager is reconnecting a lot http://c2n.me/3ostNbS.png
the names of the renderslaves are right, but if I want to monitor them only one is idle and green the others are grayed out... http://c2n.me/3osunsI.png
that's becuase I tought there is something wrong because with backburner 2014 I had no problems...

thanks for your help and effort

best regards
themaxxer

[themaxxer]

...and my backburner.xml looks exactly like yours, so the server GUI hast to fill in it every time it starts...

[DanielBrew]

If you are using a firewall maybe you should check that the ports are open for Backburner 2016. We have had a few problems this year with Windows Firewall closing ports after security updates and we definitely had to delete Backburner from the exceptions list and add it again after moving to 2016. The ports need to be opened on both the server and the manager otherwise the traffic is one way otherwise the servers to continually connect then disconnect. We use Windows Group Policy to configure our firewall.

[themaxxer]

hm... my windows firewall is off on the server where the manager is running...

[DanielBrew]

If you look at the server's properties in Queue Monitor do they have different IP addresses and handles?

[themaxxer]

no it's messed up, renderslave 10 has the IP from renderslave 1 and so on, and there's only one visible in the monitor at the time. so there is a problem.

[DanielBrew]

It looks like the problem is with the virtualization not backburner. Do all the virtual machines have the same IP addresses and MAC addresses?

[themaxxer]

no it's BB, because ReFaMo works like a charme and all slaves has an IP. http://c2n.me/3otpJMd.png

[DanielBrew]

Is the IP address that backburner sees one of those listed in the screenshot of your last post or is it the IP address of the server hosting the virtual machines?