×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Problem with pyindi service started on boot

  • Posts: 29
  • Thank you received: 1
Hi, I have a rather complex pyindi script that I have no problems to run manually, but when started on system boot (rc.local or systemd service), it usually fails (only occasionally/randomly it starts). Until lately, it worked (mostly) also on startup, but suddenly (after latest Astroberry updates?) it usually fails and I have to restart it manually.

It always fails with the following message:
Traceback (most recent call last):
   File "/usr/local/lib/python3.7/dist-packages/PyIndi.py", line 1081, in <lambda>
     __getattr__ = lambda self, name: _swig_getattr(self, BaseClient, name)
   File "/usr/local/lib/python3.7/dist-packages/PyIndi.py", line 80, in _swig_getattr
     raise AttributeError("'%s' object has no attribute '%s'" % (class_type.__name__, name))
AttributeError: 'BaseClient' object has no attribute 'removeDevice'

This exception is always preceded by a long list of messages of this type (just sometimes with different values or empty attributes):
Dispatch command error(-1): No device available and none was created
<defNumber name="%g" label="" format="%g" min="-32767" max="32767" step="0">
0
</defNumber>

I cannot locate any particular place or operation triggering this exception. I have tried upgrading/downgrading pyindi-client between versions 0.2.5 and 0.2.7a (0.2.7 and 0.2.7b do not compile), but without success. Could it be some problem of the libindi 1.8.9 itself?
Last edit: 2 months 5 days ago by Pavel.
2 months 5 days ago #71627

Please Log in or Create an account to join the conversation.

  • Posts: 29
  • Thank you received: 1
OK. I have done some cleaning, even tried a new installation of Astroberry... It looks like completely random crashes, both run manually and at the startup.
2 months 4 days ago #71659

Please Log in or Create an account to join the conversation.

  • Posts: 29
  • Thank you received: 1
The cause seems to be a regular call to the infamous astroplan package, even just for what I thought a simple calculation. I have updated that package too and it does not seem to improve - rather the opposite.

I thought a delay in INDI event processing would cause missed events, but why does it cause this type of python exception?
1 month 2 weeks ago #72212

Please Log in or Create an account to join the conversation.

Time to create page: 0.474 seconds