Unknown PDG scheduler type: tractorscheduler ??

   1807   4   0
User Avatar
Member
4 posts
Joined: July 2022
Offline
Option "Set as Default Scheduler" of "tractorscheduler" node was not set "tractorscheduler" , so I set the "Default Top Scheduler" in the "topgeometry" node directly to "tractorscheduler".

After setting the option, the error message "unknown pdg scheduler type:tractorscheduler" is displayed.

I added the tractor site package path to my PYTHONPATH environment.

Does anyone know about this issue?

Attachments:
bbb.png (167.2 KB)

User Avatar
Staff
600 posts
Joined: May 2014
Offline
This likely means that the Tractor Python library isn't loaded properly. You can verify that by opening a Python Shell in your Houdini session, and attempting to import one of the components of the Python module. For example, verify that import tractor.api.author succeeds.

Note that if you're using a Python 3 build of Houdini, you'll also need to use the Python 3 version of the Tractor Python API or it won't be possible for Houdini to import it.
Edited by tpetrick - Oct. 17, 2022 12:37:14
User Avatar
Member
4 posts
Joined: July 2022
Offline
tpetrick
This likely means that the Tractor Python library isn't loaded properly. You can verify that by opening a Python Shell in your Houdini session, and attempting to import one of the components of the Python module. For example, verify that import tractor.api.author succeeds.

Note that if you're using a Python 3 build of Houdini, you'll also need to use the Python 3 version of the Tractor Python API or it won't be possible for Houdini to import it.

------------------------------------------------------------

Thank you. I set the path with tractor python3 aip, now Set as Default Scheduler Option works well.

However, another problem arose.

Any idea why this error is occurring?

-----------------------------------------
/opt/hfs19.5/python/bin/python /core/tmp/houdini/test_render/31890/pdgtemp/scripts/pdgmq.py --xmlport 9012 --relayport 9013 --connectionfile /core/tmp/houdini/test_render/31890/pdgtemp/pdgmq_server.txt --start
PDG_MQ rf025 9012 9013
18:44:27: Message Queue Server Running
18:44:37: 0.0 mps, avg=0.0ms, max=0.0ms




Traceback (most recent call last):
File "/core/tmp/houdini/test_render/31890/pdgtemp/scripts/pdgmq.py", line 795, in <module>
Caught Signal 2, signalling child 19175
File "/core/tmp/houdini/test_render/31890/pdgtemp/scripts/pdgmq.py", line 784, in main
exit_code = _start_server(args.host, args.xmlport, args.relayport,
File "/core/tmp/houdini/test_render/31890/pdgtemp/scripts/pdgmq.py", line 731, in _start_server
relay_server_instance.handle_request()
File "/opt/hfs19.5/python/lib/python3.9/socketserver.py", line 294, in handle_request
ready = selector.select(timeout)
File "/opt/hfs19.5/python/lib/python3.9/selectors.py", line 416, in select
fd_event_list = self._selector.poll(timeout)
KeyboardInterrupt
Edited by m83studio - Oct. 20, 2022 20:52:16
User Avatar
Member
1 posts
Joined: Oct. 2022
Offline
try

PDGMQ_USE_IP=1
User Avatar
Member
4 posts
Joined: July 2022
Offline
This was our firewall and port issue.
After setting the port in the firewall it works well.

Thanks for your answer.
Edited by m83studio - Oct. 20, 2022 20:51:59
  • Quick Links