So I put together a second node.
Actually I pretty much destroyed and rebuilt two computers today so that my workstation has an 8 core.
Node one I left in tact with it’s existing 8 core.
And I grabbed all the internals of the old workstation and that became my second node. So nothings changed apart from I kept 32GB RAM in my workstation and put two new 8GB modules in the node.
Anyway - I’ve been battling away for hours trying to get DBR and backburner working on this new node.
Everthing installed fine on the new workstation, but the node fails with DBR. Server also fails to open on this node but manager and monitor are ok. I’ve reinstalled it again with no joy.
Communication between new Workstation and the old node is fine but here’s the mr error which doesnt really tell me a lot.
[size=1]
MSG 0.0 274 MB warn 012229: could not connect to host:port RENDER02:7518 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (IPv6)
MSG 0.0 274 MB warn 012229: could not connect to host:port RENDER02:7518 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (IPv4)
[/size][size=1]MSG 0.0 274 MB error 011228: mi_msg_connect: failed to create active socket
MSG 0.0 274 MB error 011706: cannot add host RENDER02:7518
[/size][size=1]MSG 0.0 274 MB warn 012229: could not connect to host:port RENDER02:7001 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (IPv6)
MSG 0.0 274 MB warn 012229: could not connect to host:port RENDER02:7001 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (IPv4)
[/size][size=1][/size]
Any ideas? I think it must be user error.