It seems that lately QHY are giving issues. Searched the forum but didn't find anything matching my issue.
I tried to update, upgrade, dist-upgrade and reinstall indi-qhy but nothing seems to work. This is the dump of:
indiserver -vvv indi_qhy_ccd
2018-04-18T22:18:29: Driver indi_qhy_ccd: pid=2615 rfd=0 wfd=6 efd=7
2018-04-18T22:18:29: Driver indi_qhy_ccd: sending msg copy 1 nq 1:
2018-04-18T22:18:29: Driver indi_qhy_ccd: indi_qhy_ccd: error while loading shared libraries: libqhyccd.so.1: cannot map zero-fill pages
2018-04-18T22:18:29: Driver indi_qhy_ccd: stderr EOF
2018-04-18T22:18:29: Driver indi_qhy_ccd: Terminated after #10 restarts.
2018-04-18T22:18:29: good bye
Even a full reinstall of indi / ekos doesn't work.
Found in the forum that 2 months ago qhy changed the name of their library from libqhy to libqhyccd but this was fixed immediately after by Jasem.
I'm running Ubuntu 16.04 mate on a rpi3.
Too bad this happens when the weather is nice after months of clouds and snow....
Have you installed libqhy or indi-qhy yourself before? You have something on your system that interferes with this. Is this on RPI3 or x86-64 system?
EDIT: Ok I know why. For some reason, the QHY SDK is reserving TOO much memory (~780 MB) but its actual use is very little, but this is leading to errors in memory use. This is not a problem on StellarMate due to memory compression but on a regular RPI3 it would be a problem. I'll try to find out why it is reserving so much memory.
I have attempted this solution and the problem wasn't resolved for my QHY5-M. It is showing the "Exposure Timeout" error since the update released 08/04/2018.
I have a QHY5-L-ii-c that seems to work without any failures but I would rather not guide using the colour cam. Any suggestions?
Your issue seems not related to the one discussed here. Whenever I have a timeout error I power off/on the camera and restart indi. Usually it is sufficient to fix the issue.
Yesterday a new release was available, have you tried to update?
If this won't fix it I suggest you post here your log file.