There is very little we can do to assist them, this is very much linked to their network configuration, mostly the routing tables and DNS. The safest is to set all processing nodes, but also to add all client machines, to the distributed processing configuration, using static IP addresses configuration.
Normally only the processing nodes need to be listed in the configuration (let's say Node1 and Node2), but it may help to also list the client machines (let's Workstation1, Workstation2, ...) in this situation.
The configuration file should be copied or made readable from all nodes and client machines. That can be done by setting the environment variable DTECT_BATCH_HOSTS_FILEPATH to the full path of the configuration file, especially before launching the remote processing daemon on the processing nodes.
Support Manager![]() |
----------------------------------------------------------------------------------------------------------------------- dGB Earth Sciences | |||||||
|
--
You received this message because you are subscribed to the Google Groups "OpendTect Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opendtect.org.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/1084da96-a84e-44e7-8238-88549e76f57en%40opendtect.org.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/users/CAKpeyVM08VxF3mFnzjsYOgoaET_d6ChhsM2AgeTd7HySPam46w%40mail.gmail.com.