LuxCoreRender Forums

I'm getting this error with BlendLuxCore-v2.3:

File "/home/leo/.config/blender/2.82/scripts/addons/BlendLuxCore/bin/pyluxcoretools.zip/pyluxcoretools/renderfarm/renderfarmjobsingleimage.py", line 393, in NodeThread
nodeSocket.connect((self.renderFarmNode.address, self.renderFarmNode.port))

I'm very far to be an expert with networking, my setup is very simple

It consists of 2 PCs linked by an ethernet cable setted up with what I think is a static IPs configuration

Remote desktop works fine to control the Windows machine via Remmina with these settings

I'm running the LuxCore NetConsole on the Ubuntu machine

Running up the NetNode on Windows it is added to the NetConsole list

Starting a job I'm getting the above error

You should post the complete error. Do you have some kind of firewall active ?

Thank you very much Dade,

I think this was the complete error:

Node thread started
timed out
Traceback (most recent call last):
File "/home/leo/.config/blender/2.82/scripts/addons/BlendLuxCore/bin/pyluxcoretools.zip/pyluxcoretools/renderfarm/renderfarmjobsingleimage.py", line 393, in NodeThread
nodeSocket.connect((self.renderFarmNode.address, self.renderFarmNode.port))
socket.timeout: timed out
Node thread done
Retrying node: 192.168.1.1:18018

I've checked the Windows 10 firewall and enabled pyluxcoretool.exe to pass through

No firewalls active on the Ubuntu machine as I understand (ufw status: inactive)

Now it is stuck before starting to render

On the NetConsole:

LuxCore 2.3
NetBeaconReceiver thread started.
Discovered new node: 192.168.1.1:18018
Creating single image render farm job: /home/leo/Documents/LuxCore/NetworkCache/LuxCore2.1Benchmark_LuxCore/00001.bcf
New render farm job: /home/leo/Documents/LuxCore/NetworkCache/LuxCore2.1Benchmark_LuxCore/00001.bcf
Job file md5: bcdb427ab152e7a287f02c955c74da1d
Previous scene MD5: bcdb427ab152e7a287f02c955c74da1d
Current scene MD5: bcdb427ab152e7a287f02c955c74da1d
/home/leo/Documents/LuxCore/NetworkCache/LuxCore2.1Benchmark_LuxCore/00001-netrendering exists and is valid. Continue the rendering
Merging all previous films
-------------------------------------------------------
Job started: /home/leo/Documents/LuxCore/NetworkCache/LuxCore2.1Benchmark_LuxCore/00001.bcf
-------------------------------------------------------
Node thread started
Film merge thread started
Remote node has the same pyluxcore verison
Sending file: /home/leo/Documents/LuxCore/NetworkCache/LuxCore2.1Benchmark_LuxCore/00001.bcf
Transfered 32.01 Mbytes in 00:00:00 (114.02 Mbytes/sec)
Sending seed: 10
Waiting for node rendering start


And the NetNode:

LuxCore 2.3
Waiting for configuration...
Started
NetBeaconSender thread started.
Waiting for a new connection
Received connection from: ('192.168.1.2', 58718)
Remote pyluxcore version: 2.3
Local pyluxcore version: 2.3
Receiving RenderConfig serialized file: renderfarmnode-aba59288-869e-4edb-88cb-babeea898720.bcf
Receiving file: renderfarmnode-aba59288-869e-4edb-88cb-babeea898720.bcf
Transfered 32.01 Mbytes in 00:00:00 (104.92 Mbytes/sec)
Receiving RenderConfig serialized MD5: bcdb427ab152e7a287f02c955c74da1d
Received seed: 10
Reading RenderConfig serialized file: renderfarmnode-aba59288-869e-4edb-88cb-babeea898720.bcf
[SDL][14.438] Loading serialized mesh: Mesh_Plane__013140281056706568000
[SDL][14.453] Loading serialized mesh: Mesh_Box057140281056268808000
[SDL][14.453] Loading serialized mesh: Mesh_Box057140281056268808001
...
[SDL][15.235] Loading serialized mesh: Curve_Plane__021140281056717320000

It's also showing a -Waiting for a new connection- message on the NetNode window frame

Ok, so you don't get the error anymore

There has been some report of freezes when lunching network rendering from Blender while it works fine as stand alone: viewtopic.php?f=4&t=2037#p21966

Are you lunching the rendering from Blender or from command line ?

So, the first error is not happening anymore since I've allowed pyluxcoretool.exe to pass through the firewall on Windows 10

Running the console on Windows seems to work fine if the Ubuntu node is set up with the right host and broadcast IPs

I've just thrown half a render on cpu (no openCL) without splitting workloads and it was going ok

The opposite way, running the console on Ubuntu, the Windows node keeps getting stuck

I'm running all of this from GUIs

Ok, I think I get it now

The issue happens when the LuxCore NetNode is loaded up from Blender's GUI on Windows

It all seems to work fine if the Windows node is being run instead by using the pyluxcoretools executable from the Blender addons folder

3DLV wrote: ↑Wed May 27, 2020 6:34 pm Ok, I think I get it now

The issue happens when the LuxCore NetNode is loaded up from Blender's GUI on Windows

It all seems to work fine if the Windows node is being run instead by using the pyluxcoretools executable from the Blender addons folder

Have you installed Blender with admin rights so it (and pyluxcoretools) can not write in its directory ? It may explain the problem (network rendering requires to create several temporary files).

Sorry, I´m not sure, I think it is

I'm just unzipping Blender, moving it to my Program Files folder and launching it from a shortcut