You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And it gets stuck here, until I press Ctrl+C.
Then it suddenly connects (and indeed I see it in journalctl on the server):
^CExiting upon user request!
[192.168.1.218] Connected
Then again nothing happens, until I Ctrl+C again and it terminates.
Firstly, not sure why it says Loading SSH config: None when I gave it path to the config, but more importanly why does it get stuck?
Any way to debug this further?
File "/home/roman/dev/homelab/venv/lib/python3.12/site-packages/pyinfra_cli/main.py", line 222, in cli
_main(*args, **kwargs)
File "/home/roman/dev/homelab/venv/lib/python3.12/site-packages/pyinfra_cli/main.py", line 348, in _main
connect_all(state)
File "/home/roman/dev/homelab/venv/lib/python3.12/site-packages/pyinfra/api/connect.py", line 27, in connect_all
with progress_spinner(greenlet_to_host.values()) as progress:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/contextlib.py", line 144, in __exit__
next(self.gen)
File "/home/roman/dev/homelab/venv/lib/python3.12/site-packages/pyinfra/progress.py", line 146, in progress_spinner
spinner_thread.join()
File "/usr/lib/python3.12/threading.py", line 1149, in join
self._wait_for_tstate_lock()
File "/usr/lib/python3.12/threading.py", line 1169, in _wait_for_tstate_lock
if lock.acquire(block, timeout):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/roman/dev/homelab/venv/lib/python3.12/site-packages/gevent/thread.py", line 276, in acquire
acquired = BoundedSemaphore.acquire(self, blocking, timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "src/gevent/_semaphore.py", line 184, in gevent._gevent_c_semaphore.Semaphore.acquire
File "src/gevent/_semaphore.py", line 263, in gevent._gevent_c_semaphore.Semaphore.acquire
File "src/gevent/_semaphore.py", line 253, in gevent._gevent_c_semaphore.Semaphore.acquire
File "src/gevent/_abstract_linkable.py", line 521, in gevent._gevent_c_abstract_linkable.AbstractLinkable._wait
File "src/gevent/_abstract_linkable.py", line 487, in gevent._gevent_c_abstract_linkable.AbstractLinkable._wait_core
File "src/gevent/_abstract_linkable.py", line 490, in gevent._gevent_c_abstract_linkable.AbstractLinkable._wait_core
File "src/gevent/_abstract_linkable.py", line 442, in gevent._gevent_c_abstract_linkable.AbstractLinkable._AbstractLinkable__wait_to_be_notified
File "src/gevent/_abstract_linkable.py", line 451, in gevent._gevent_c_abstract_linkable.AbstractLinkable._switch_to_hub
File "src/gevent/_greenlet_primitives.py", line 61, in gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop.switch
File "src/gevent/_greenlet_primitives.py", line 65, in gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop.switch
File "src/gevent/_gevent_c_greenlet_primitives.pxd", line 35, in gevent._gevent_c_greenlet_primitives._greenlet_switch
gevent.exceptions.LoopExit: This operation would block forever
Hub: <Hub '' at 0x7f69e6171580 epoll default pending=0 ref=0 fileno=3 resolver=<gevent.resolver.thread.Resolver at 0x7f69e80567b0 pool=<ThreadPool at 0x7f69e5f509e0 tasks=0 size=0 maxsize=10 hub=<Hub at 0x7f69e6171580 thread_ident=0x7f69e9850b80>>> threadpool=<ThreadPool at 0x7f69e5f509e0 tasks=0 size=0 maxsize=10 hub=<Hub at 0x7f69e6171580 thread_ident=0x7f69e9850b80>> thread_ident=0x7f69e9850b80>
Handles:
[]
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm having trouble getting an example from the docs work.
The command I'm running is as follows:
And it gets stuck here, until I press Ctrl+C.
Then it suddenly connects (and indeed I see it in journalctl on the server):
Then again nothing happens, until I Ctrl+C again and it terminates.
Firstly, not sure why it says
Loading SSH config: None
when I gave it path to the config, but more importanly why does it get stuck?Any way to debug this further?
My inventory is
Meta
Debug log
The text was updated successfully, but these errors were encountered: