Issues with high acquisition rates

  • Posts: 9
  • Thank you received: 16

Replied by Leonard Bottleman on topic Issues with high acquisition rates

An ASI software engineer replied to my post on the ZWO forum indicating that the long delay for for the exposure completion status to switch from working to success was expected.

This is a bit disappointing, but without access to the code I cannot guess what it is doing that is taking so long.
The following user(s) said Thank You: Emmanuel Bertin
6 years 7 months ago #23566

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

  • Posts: 9
  • Thank you received: 2

Replied by Emmanuel Bertin on topic Issues with high acquisition rates

I suspected that the "Failed to save file to" in "Upload: Client" mode was due to Ekos running out of file descriptors. This seems indeed to be the case. The problem vanishes when I push the maximum number of open file descriptors to 4096 per user (was 1024 by default on my system). Sounds like a close() is missing somewhere :).
Last edit: 6 years 7 months ago by Emmanuel Bertin.
6 years 7 months ago #23585

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

Replied by Jasem Mutlaq on topic Issues with high acquisition rates

Well, where is the close() missing? I know this has been reported before, but whenever a new FITS is used, the previous one is always closed first.
6 years 7 months ago #23588

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

  • Posts: 9
  • Thank you received: 16

Replied by Leonard Bottleman on topic Issues with high acquisition rates

I experimented with many short exposures while monitoring the files held open by kstars, indiserver, and indi_asi_ccd.

I saw no open file changes for indiserver or indi_asi_ccd.

For kstars after the first exposure there were 6 additional files held open: a socket, a pair of event fds, /dev/urandom, and the image file (open twice).

When I took many images the number of open files remained the same, with only the open image file changing.

However, if the number of fits viewers increases, then the number of files help open also increases -- I can only reproduce this when I trigger the rapid looping bug where the image download takes longer than the image exposure, which we know is an issue.

When you think kstars or indi is holding open too many files please get the pids for kstars, indiserver and indi_asi_ccd, and then for each please list the open files:

ls -l /proc/<pid>/fd

Where <pid> is the process pid -- you may want to redirect the output of each ls command to a file.

Then post here the results of what you've found.

Thanks!
The following user(s) said Thank You: Emmanuel Bertin
Last edit: 6 years 6 months ago by Leonard Bottleman.
6 years 6 months ago #23596

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


×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...
  • Posts: 9
  • Thank you received: 2

Replied by Emmanuel Bertin on topic Issues with high acquisition rates


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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

  • Posts: 9
  • Thank you received: 16

Replied by Leonard Bottleman on topic Issues with high acquisition rates

Thanks Emmanuel.

At first I could not recreate the socket leak even when following your instructions.

I then used strace on kstars and discovered that it (actually the QT layer) was constantly looking for phonon4qt5_backend from the qt /usr/lib install. Looking up phonon4qt5 in the system software manager I found several KDE provides packages including a back end gstreamer package. I do not use KDE (just not a fan) and so my system does not have this package installed.

I installed the package.

Afterward at the end of each image capture I got an annoying sound. Worse, when I took multiple images in the scheduler kstars leaked a socket pair per image (in addition playing the sound). It did not leak sockets with preview.

I then removed the package (phonon4qt5-backend-gstreamer) and the socket leak vanished.

If you use KDE you can test if disabling sound notifications stops the socket leak ( option to disable failure sounds ), or if you do not use KDE try removing the package I listed above and restart kstars.

Obviously a real fix is needed, but I am not familiar enough with the kstars source code to be helpful here (I am more of a low level software guy).

Leonard
The following user(s) said Thank You: Jasem Mutlaq, Emmanuel Bertin
6 years 6 months ago #23634

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

Replied by Jasem Mutlaq on topic Issues with high acquisition rates

I don't have control over other Qt/KDE software, but if they have a bug, we can help them resolve it. You can turn off the sounds from Settings --> Configure Notifications. Maybe I should turn them off for < 1 second captures?
The following user(s) said Thank You: Emmanuel Bertin
6 years 6 months ago #23635

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

  • Posts: 9
  • Thank you received: 2

Replied by Emmanuel Bertin on topic Issues with high acquisition rates


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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

Replied by Jasem Mutlaq on topic Issues with high acquisition rates

I made quite a few changes yesterday to both INDI & KStars about this issue, but need to test it more today. For KStars bugs, the best place is bugs.kde.org
For INDI bugs, here: github.com/indilib/indi/issues
The following user(s) said Thank You: Emmanuel Bertin
Last edit: 6 years 6 months ago by Jasem Mutlaq.
6 years 6 months ago #23650

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

Time to create page: 0.399 seconds