I put a network standalone installation of Octane on a spare desktop that GPU upgrade recently, so as to help with rendering.
I cannot figure out why, but it refuses to see the master.
It is correctly on the network with defined IP address. It can see all machines and network devices like NAS and printer etc.
Try to run Octane NW and the CMD window that pops up shows it trying to connect to master ip address at 0.0.0.0 IP, rather than the 192.168.1.12 where it should be. The other two NW nodes run perfectly.
Same Octane version of course. I've also checked that Octane daemon is set up with same settings prior to running, and that's right too.
I've even tried running CMD line command specifically, telling it the designated master IP address and port - it then lists these as it tries to connect, but then does not complete the connection.
Windows firewall is clear, and is allowing Octane to communicate outwardly etc.
I am really stuck on this node.
Network slave refuses to see master
Moderator: juanjgon
Sorry, for me it is hard to say what could be problem. So you have other network nodes that are working fine, right?
Please, could you enable the logging in Master and Slaves like described here?
viewtopic.php?f=86&t=54503#p285541
Thanks,
-Juanjo
Please, could you enable the logging in Master and Slaves like described here?
viewtopic.php?f=86&t=54503#p285541
Thanks,
-Juanjo
-
BraceMedia
- Posts: 33
- Joined: Thu Dec 04, 2014 1:38 am
Yeah, correct.
I have main master workstation, with LW and Octane license of course; 2 network nodes with Octane slave only, working fine, and was trying to add 3rd node, unsuccessfully.
I'll try to enable those logging tools asap.
Thanks,
Dom
I have main master workstation, with LW and Octane license of course; 2 network nodes with Octane slave only, working fine, and was trying to add 3rd node, unsuccessfully.
I'll try to enable those logging tools asap.
Thanks,
Dom
-
BraceMedia
- Posts: 33
- Joined: Thu Dec 04, 2014 1:38 am
I forgot to mention - before I get to do this logging thing -
When I was attempting to get this working, I had master with LW and Octane running and 2 other NW nodes... as you know already.
On this NW node that the master cannot see and it cannot see the master, if I instead open Octane Standalone on this stuck node, and go to the network rendering settings, it sees the 2 other NW nodes and they are selectable.
So... for some reason it is just refusing to see the master.
I will try to do the logging shortly.
When I was attempting to get this working, I had master with LW and Octane running and 2 other NW nodes... as you know already.
On this NW node that the master cannot see and it cannot see the master, if I instead open Octane Standalone on this stuck node, and go to the network rendering settings, it sees the 2 other NW nodes and they are selectable.
So... for some reason it is just refusing to see the master.
I will try to do the logging shortly.
-
BraceMedia
- Posts: 33
- Joined: Thu Dec 04, 2014 1:38 am
A late response here, but just to let you know - uninstalling v3.03 on the node (finally) and going to 3.06.4 installed fine and the node is seeing the master just fine now. 
-
BraceMedia
- Posts: 33
- Joined: Thu Dec 04, 2014 1:38 am
It wasn't a wrong version.
All master and nodes had the same version. Just that for some reason, one node (when every system was on version 3.03x) would not see the master at all, so that node was useless.
Now with all master and nodes on 3.06, that node is now talking to the master just fine.
All master and nodes had the same version. Just that for some reason, one node (when every system was on version 3.03x) would not see the master at all, so that node was useless.
Now with all master and nodes on 3.06, that node is now talking to the master just fine.