Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed sleep time when starting hidra via control server #31

Open
schooft opened this issue Mar 28, 2022 · 0 comments
Open

Fixed sleep time when starting hidra via control server #31

schooft opened this issue Mar 28, 2022 · 0 comments

Comments

@schooft
Copy link
Contributor

schooft commented Mar 28, 2022

After starting hidra, the control server waits a hard-coded 10s until it acquires the configuration from the new hidra instance. However, in rare cases the startup can take longer than 10s and then an incomplete configuration is acquired. For example, the request_port might not be updated yet, resulting in the following error when trying to initialize a new Transfer object:

Failed to signal_socket start (connect, REQ):
'tcp://asap3-pXX.desy.de:random' Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/hidra/utils/utils_network.py",
line 651, in start_socket
     socket.connect(endpoint)
   File "zmq/backend/cython/socket.pyx", line 583, in
zmq.backend.cython.socket.Socket.connect
   File "zmq/backend/cython/checkrc.pxd", line 25, in
zmq.backend.cython.checkrc._check_rc
zmq.error.ZMQError: Invalid argument

The 10s sleep in hidra_control/server.py already has the comment

# TODO exchange that with proper communication to statserver
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant