Everything related to Maxwell network rendering systems.
User avatar
By zparrish
#385237
At one point, I was able to get all of the servers connected to the manager and then launch the Monitor, but now I just get an "Unable to connect message" when launching the monitor. I checked in Firebug and it definitely isn't getting a response at all from the server.

When I launch the manager, this is what I get:
Code: Select all
C:\Program Files\Next Limit\Maxwell 3\tp_network>tp_network.exe -manager -M 192.168.2.32
2015-02-04T19:54:49Z    INFO Replacing tree by 192.168.2.32
2015-02-04T19:54:49Z   DEBUG param weblog
2015-02-04T19:54:49Z   DEBUG param jobman
2015-02-04T19:54:49Z   DEBUG param tree
2015-02-04T19:54:49Z   DEBUG param web
2015-02-04T19:54:49Z   DEBUG param params
2015-02-04T19:54:50Z   DEBUG param buffertofile
2015-02-04T19:54:50Z    INFO Starting web Namespace(address_webserver=None, dontpublish=False, gui=True, jobfile=None, jobman='192.168.2.32', listen='192.168.2.32', loghub='192.168
.2.32', manager='192.168.2.32', mode='manager', nopreview=False, params=None, popen=False, port_jobman_listen='45445', port_jobman_publish='45446', port_log_push='45447', port_log_
web='45449', port_params_listen='45451', port_tree='45450', port_webserver='45448', request=False, shared='Y:/Maxwell Shared', tempdir='c:\\users\\zparri~1.c-s\\appdata\\local\\tem
p', threads=False, tree='192.168.2.32', verbosity='7')
2015-02-04T19:54:50Z    INFO Connected to jobman at 192.168.2.32:45445
2015-02-04T19:54:50Z    INFO Starting params Namespace(address_webserver=None, dontpublish=False, gui=True, jobfile=None, jobman='192.168.2.32', listen='192.168.2.32', loghub='192.
168.2.32', manager='192.168.2.32', mode='manager', nopreview=False, params=None, popen=False, port_jobman_listen='45445', port_jobman_publish='45446', port_log_push='45447', port_l
og_web='45449', port_params_listen='45451', port_tree='45450', port_webserver='45448', request=False, shared='Y:/Maxwell Shared', tempdir='c:\\users\\zparri~1.c-s\\appdata\\local\\
temp', threads=False, tree='192.168.2.32', verbosity='7')
22015-02-04T19:54:50Z    INFO 015-02-04T19:54:50Z    INFO CSonnected to params at 192.168.2.32:45451tarting jobman Namespace(address_webserver=None, dontpublish=False, gui=True, jo
bfile=None, jobman='192.168.2.32', listen='192.168.2.32', loghub='192.168.2.32', manager='192.168.2.32', mode='manager', nopreview=False, params=None, popen=False, port_jobman_list
en='45445', port_jobman_publish='45446', port_log_push='45447', port_log_web='45449', port_params_listen='45451', port_tree='45450', port_webserver='45448', request=False, shared='
Y:/Maxwell Shared', tempdir='c:\\users\\zparri~1.c-s\\appdata\\local\\temp', threads=False, tree='192.168.2.32', verbosity='7')

2015-02-04T19:54:50Z    INFO ~Parameters: listen_address 192.168.2.32
2015-02-04T19:54:50Z   DEBUG Listener()
2015-02-04T19:54:50Z    INFO Listening on tcp://192.168.2.32:45451
2015-02-04T19:54:50Z  NOTICE Starting Maxwell Render Job Manager 0.7.6
2015-02-04T19:54:50Z    INFO loop
Process Process-2:3:
Traceback (most recent call last):
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\multiprocessing.process", line 258, in _bootstrap
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\multiprocessing.process", line 114, in run
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\mxcjobman.mxcrun", line 213, in launch_mode
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\mxcjobman.jobman", line 250, in __init__
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\mxcjobman.jobman", line 1484, in load_state
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\google.protobuf.message", line 186, in ParseFromString
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\google.protobuf.internal.python_message", line 841, in MergeFromString
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\google.protobuf.internal.python_message", line 874, in InternalParse
  File "C:\cygwin64\home\vm6\mxcloud\build\mxcrun\out00-PYZ.pyz\google.protobuf.internal.decoder", line 652, in DecodeField
DecodeError: Truncated message.
2015-02-04T19:54:50Z  NOTICE websocket_port 45448
2015-02-04T19:54:50Z    INFO Replacing __TREE_ADDRESS__ 192.168.2.32
2015-02-04T19:54:50Z    INFO Replacing __VERSION__ 0.7.6
2015-02-04T19:54:50Z    INFO Replacing __WAN_ADDRESS__ 10.113.202.107
2015-02-04T19:54:50Z    INFO Starting tree Namespace(address_webserver=None, dontpublish=False, gui=True, jobfile=None, jobman='192.168.2.32', listen='192.168.2.32', loghub='192.16
8.2.32', manager='192.168.2.32', mode='manager', nopreview=False, params=None, popen=False, port_jobman_listen='45445', port_jobman_publish='45446', port_log_push='45447', port_log
_web='45449', port_params_listen='45451', port_tree='45450', port_webserver='45448', request=False, shared='Y:/Maxwell Shared', tempdir='c:\\users\\zparri~1.c-s\\appdata\\local\\te
mp', threads=False, tree='192.168.2.32', verbosity='7')
2015-02-04T19:54:50Z    INFO Starting buffertofile Namespace(address_webserver=None, dontpublish=False, gui=True, jobfile=None, jobman='192.168.2.32', listen='192.168.2.32', loghub
='192.168.2.32', manager='192.168.2.32', mode='manager', nopreview=False, params=None, popen=False, port_jobman_listen='45445', port_jobman_publish='45446', port_log_push='45447',
port_log_web='45449', port_params_listen='45451', port_tree='45450', port_webserver='45448', request=False, shared='Y:/Maxwell Shared', tempdir='c:\\users\\zparri~1.c-s\\appdata\\l
ocal\\temp', threads=False, tree='192.168.2.32', verbosity='7')
2015-02-04T19:54:50Z    INFO Exporting file system at Y:/Maxwell Shared for Dynatree.
2015-02-04T19:54:50Z    INFO 2r015-02-04T19:54:50Z    INFO ootPath Y:/Maxwell Shared/
Serving HTTP on0.0.0.0port45450...
2015-02-04T19:54:50Z   DEBUG Connected to jobman at 192.168.2.32
2015-02-04T19:54:50Z   DEBUG Listener()
2015-02-04T19:54:50Z    INFO Listening to tcp://192.168.2.32:45446
2015-02-04T19:54:50Z  NOTICE webserver_port 45448
2015-02-04T19:54:50Z   DEBUG Web()
2015-02-04T19:54:50Z   DEBUG send_blocking(): -> trid: 1234 query_type: REQUESTINFO
2015-02-04T19:54:51Z   DEBUG send_blocking: waiting
2015-02-04T19:54:52Z    INFO Subprocess jobman exited. Shutting down.
2015-02-04T19:54:52Z   DEBUG send_blocking: waiting
2015-02-04T19:54:53Z   DEBUG send_blocking: waiting
2015-02-04T19:54:54Z   DEBUG Connected to jobman at 192.168.2.32:45445
2015-02-04T19:54:54Z    INFO SENDING:
trid: 1234 query_type: STOPJOBMANAGER
2015-02-04T19:54:54Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:55Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:56Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:57Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:58Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:59Z    INFO All processes finished.
In trying to figure out various parts of the command line syntax, I'm wondering if I inadvertantly changed a setting in a config file somewhere. The last few lines of the command shell seam a bit odd:
Code: Select all
trid: 1234 query_type: STOPJOBMANAGER
2015-02-04T19:54:54Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:55Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:56Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:57Z    INFO Process jobman still alive. Killing it ...
2015-02-04T19:54:58Z    INFO Process jobman still alive. Killing it ...
Is there a way I can "clear the cache" of any settings stored by the technology preview? I even tried reinstalling Maxwell 3.1.0 but that didn't resolve it either.

Thanks!
User avatar
By pablo
#385277
zparrish wrote: Is there a way I can "clear the cache" of any settings stored by the technology preview? I even tried reinstalling Maxwell 3.1.0 but that didn't resolve it either.
Thanks!
Yes, settings from earlier versions can not necesarily be loaded in later versions. The files with settings and jobmanager status are in different places depending on the operating system:

- On HOMEDIR/AppData/Next Limit/tp_network/ on Windows
- On HOMEDIR/Library/ApplicatioN Support/tp_network on OSX
- On HOMEDIR/.local/share/tp_network on Linux

The three files there tp_manager.ini, tp_node.ini, tp_manager.bin are the settings for manager and node and the file where the manager stores it's state between restarts. Just delete all of them in this cases. You will be asked again to fill the parameters on launch, and the job queue will appear empty, just as if you had removed all finished renders.

Thank you for your insight,
By kami
#385482
I do also have problems connecting to the monitor.
The manager is running fine and he has connection to the nodes.
When I start the monitor it lanches a browser window with my ip: http://192.168.49.70:4480/
but that only shows "Unable to connect" in Firefox.

What would be the solution for that? I did not change any ports, nor did I have a previous version of the Maxwell Beta installed on this computer.
I'm running Windows Server 2012.
Is it a firewall issue? I also cannot connect from any other computer. What settings would I have to put in?
By kami
#385484
Hmm, I just found out that it works, if I change the URL manually to 192.168.49.70:45448
I have no idea why, but on all computers when I try to start the monitor I get to the URL 192.168.49.70:4480
User avatar
By zparrish
#385485
I can confirm Kami's experience.

After installing Maxwell 3.1.0.1 and using pablo's advice on clearing out settings, I'm able to re-establish a connection from the monitor to the manager and see the current node(s) status and activity. I do appear to be restricted though to running the monitor and the manager on the same physical machine. Here's my tp_network and IP layout for reference:

My Workstation, Manager, and Monitor:
192.168.2.32
127.0.0.1 (defaulted IP for monitor: standard loopback)

Nodes:
192.168.2.39
192.168.2.40
192.168.2.41
192.168.2.42
192.168.2.43

When I launch the monitor on my workstation (the same amchine that's running the manager), it automatically connects using the loopback IP (127.0.0.1). If I launch the monitor on one of the nodes, it correctly points to the manager IP address (192.168.2.32) but appears to use the wrong port (4480). The port established by the manager for "websocket_port" and "webserver_port" is (45448) per the command prompt / debug output of the manager. If I manually change the URL on one of the non-manager, remote machines from:

http://192.168.2.32:4480/

TO

http://192.168.2.32:45448/

It appears to work correctly. I get the correct HTML header and JS calls back to the browser and it displays the status of the render network. I haven't tested additional functionality beyond that yet and will post the results of that in another topic with specific details.

Thanks!
Sketchup 2024 Released

I would like to add my voice to this annual reques[…]