Blender Foundation: Blender 2.x BF release: Detail: 25671 Network Render freezes/blocks blender

Log In
New Account

[#25671] Network Render freezes/blocks blender

Date:
2011-01-16 21:53 Priority:
3

State:
Closed

Submitted by:
Agustin benavidez (agus3d) Assigned to:
Martin Poirier (theeth)

Category:
Scripts Status:
Fixed / Closed

Relates to: Duplicates:

Patches:

Summary:
Network Render freezes/blocks blender

Detailed description

-Attached A Blend File.

There is a confirmed problem with NetRender, it occurrs in my home
render network and my job network, both in Vista and Win7,
i didn't check it in other OS.

To reproduce the problem:

- Switch to Network Render mode
- In client delete the server address and press enter
- Blender gets bloked, and the console shows a log saing in
some system "[Errno 10061]time out" and in my system " no connection could be made because the target machine actively refuses it "
Also happens if teh server is not running.

Clues:

- for some reason the server address which was 192.168.137.1 changed spontaneously to 186.18.0.50
- Firewalls are well configurated, indied other files works fine.
- I Have python 3 installed.
- The build i use is from "filiciss" builder in graphicall revision: 33664

Thanks Martin for this system, very useful and needed.

Cheers
Agustin.

System Info In the file inside this Blend file:
system-info.txt

Followup

Message

Date: 2011-01-22 01:47
Sender: Wintch Analyzer
I have a similar problem with netrender. A client process freezes when i set IP address of a master.
The solution for me was using a default port (you can forward it or something to test) or as well setting first a port on client and only then a master IP address.
i think the logic is:
default IP: 127.0.0.1 default port: 8000
User setting a different IP addres (say 192.168.137.1)>Lets try 192.168.137.1 on port 8000....timed out several times till "not responding message appears"
Hope some of these helps.

Date: 2011-01-22 02:18
Sender: Wintch Analyzer
In the .pcap file you can see SYN packets going to IP set in network render properties but before you have time to set a correct port blender stop responding. If you have a port 8000 closed on Master the only way is to set the correct port first and then the IP. Not critical but some error message and/or cancel button would be great.

Date: 2011-01-28 01:02
Sender: Martin Poirier
Should be better in revision 34537. (at most, timeout for 1s every 30s if there's a server address specified and it doesn't exist). I might change that system sometime to be less automatic and add a button to connect to server (to get its status).

Attached Files:

Name	Date	Download

NetRenderBug_compressed.blend	2011-01-16 21:53	Download
netrendertest.pcap	2011-01-22 02:18	Download

Changes:

Field	Old Value	Date	By

Status	Investigate	2011-01-28 01:02	theeth
status_id	Open	2011-01-28 01:02	theeth
close_date	None	2011-01-28 01:02	theeth
File Added	14670: netrendertest.pcap	2011-01-22 02:18	wintch
assigned_to	none	2011-01-17 15:25	ton
Category	Rendering	2011-01-17 15:25	ton
Status	New	2011-01-17 15:25	ton
File Added	14573: NetRenderBug_compressed.blend	2011-01-16 21:53	agus3d