Closed Paolo97Gll closed 1 year ago
Hi, the message is just a debug message and has nothing to do with the server crash. Also we do not have indigo_focuser_esatto driver. Is this some custom driver? Most likely this is the driver that crashes. Unfortunately, The log does not give any information about what happened. So I want to ask you to do something that will give us more information:
Instal valgrind: $ sudo apt-get install valgrind
Run the indigo server as you normally would but add extra "--" option and run it through valgrind: $ valgrind indigo_server -- -vvv .... >indigo_valgrind.log 2>&1
if you are running indigo with sudo add it before valgrind: $ sudo valgrind indigo_server -- -vvv .... >indigo_valgrind.log 2>&1
Then send us indigo_valgrind.log
However, I am almost sure that you should send a report to the driver developer.
Thank you ! Rumen
On Sun, Apr 2, 2023 at 10:35 AM Paolo Galli @.***> wrote:
We can't start indigo_server 2.0-228, the server crashes with the following error:
07:24:34.391371 indigo_server: port_type(): path = /dev/tty, type = 0, res = -1 error = 'Inappropriate ioctl for device'
After the crash, the server restarts immediately and automatically.
Complete error log in trace mode:
07:26:23.130337 indigo_server: INDIGO server 2.0-228 built on 2023-03-30T11:40:31+00:00 production 07:26:23.130987 indigo_server: Server sodoma.astrogeo.va.it:7624 thread started 07:26:23.157317 indigo_server: Driver indigo_focuser_esatto 2.0.0.9 loaded 07:26:23.157420 indigo_server: B <- Attach device 'PrimaLuceLab ESATTO Focuser' 07:26:23.157452 indigo_server: 1 devices attached 07:26:25.744404 indigo_server: Can't connect to socket 192.168.40.82:7624 (No route to host) 07:26:31.888453 indigo_server: Can't connect to socket 192.168.40.82:7624 (No route to host) 07:26:33.200096 indigo_server: port_type(): path = /dev/ttyS31, type = 0, res = 0 07:26:33.200286 indigo_server: port_type(): path = /dev/ttyS30, type = 0, res = 0 07:26:33.200408 indigo_server: port_type(): path = /dev/ttyS29, type = 0, res = 0 07:26:33.200521 indigo_server: port_type(): path = /dev/ttyS28, type = 0, res = 0 07:26:33.200657 indigo_server: port_type(): path = /dev/ttyS27, type = 0, res = 0 07:26:33.200793 indigo_server: port_type(): path = /dev/ttyS26, type = 0, res = 0 07:26:33.200910 indigo_server: port_type(): path = /dev/ttyS25, type = 0, res = 0 07:26:33.201008 indigo_server: port_type(): path = /dev/ttyS24, type = 0, res = 0 07:26:33.201117 indigo_server: port_type(): path = /dev/ttyS23, type = 0, res = 0 07:26:33.201259 indigo_server: port_type(): path = /dev/ttyS22, type = 0, res = 0 07:26:33.201376 indigo_server: port_type(): path = /dev/ttyS21, type = 0, res = 0 07:26:33.201509 indigo_server: port_type(): path = /dev/ttyS20, type = 0, res = 0 07:26:33.201630 indigo_server: port_type(): path = /dev/ttyS19, type = 0, res = 0 07:26:33.201729 indigo_server: port_type(): path = /dev/ttyS18, type = 0, res = 0 07:26:33.201825 indigo_server: port_type(): path = /dev/ttyS17, type = 0, res = 0 07:26:33.201913 indigo_server: port_type(): path = /dev/ttyS16, type = 0, res = 0 07:26:33.202027 indigo_server: port_type(): path = /dev/ttyS15, type = 0, res = 0 07:26:33.202136 indigo_server: port_type(): path = /dev/ttyS14, type = 0, res = 0 07:26:33.202227 indigo_server: port_type(): path = /dev/ttyS13, type = 0, res = 0 07:26:33.202313 indigo_server: port_type(): path = /dev/ttyS12, type = 0, res = 0 07:26:33.202405 indigo_server: port_type(): path = /dev/ttyS11, type = 0, res = 0 07:26:33.202491 indigo_server: port_type(): path = /dev/ttyS10, type = 0, res = 0 07:26:33.202605 indigo_server: port_type(): path = /dev/ttyS9, type = 0, res = 0 07:26:33.202695 indigo_server: port_type(): path = /dev/ttyS8, type = 0, res = 0 07:26:33.202818 indigo_server: port_type(): path = /dev/ttyS7, type = 0, res = 0 07:26:33.202934 indigo_server: port_type(): path = /dev/ttyS6, type = 0, res = 0 07:26:33.203048 indigo_server: port_type(): path = /dev/ttyS5, type = 0, res = 0 07:26:33.203156 indigo_server: port_type(): path = /dev/ttyS4, type = 0, res = 0 07:26:33.203264 indigo_server: port_type(): path = /dev/ttyS3, type = 0, res = 0 07:26:33.203372 indigo_server: port_type(): path = /dev/ttyS2, type = 0, res = 0 07:26:33.203462 indigo_server: port_type(): path = /dev/ttyS1, type = 0, res = 0 07:26:33.204676 indigo_server: port_type(): path = /dev/tty, type = 0, res = -1 error = 'Inappropriate ioctl for device' 07:26:35.617563 indigo_server: INDIGO server 2.0-228 built on 2023-03-30T11:40:31+00:00 production 07:26:35.618190 indigo_server: Server sodoma.astrogeo.va.it:7624 thread started 07:26:35.637435 indigo_server: Driver indigo_focuser_esatto 2.0.0.9 loaded 07:26:35.637507 indigo_server: B <- Attach device 'PrimaLuceLab ESATTO Focuser' 07:26:35.637534 indigo_server: 1 devices attached
I can't say if the error is due to version 2.0-228 or an early version. I can only say that in indigo 2.0-208 the error is present but the server doesn't crash.
The server is running Ubuntu server 22.04.
— Reply to this email directly, view it on GitHub https://github.com/indigo-astronomy/indigo/issues/475, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5EZBL7MM5L5L5UIFAUL3LW7ET3HANCNFSM6AAAAAAWQEKQ4Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I had a plan to do it next week :) But I'll wait if you did already...
Hi, sorry for the late reply, I was out!
It was my fault. As @rumengb pointed out, we use custom drivers, but I totally forgot to compile them with the new indigo 2.0-228 (they were compiled with indigo 2.0-208). Now everything works!
I was fooled by the fact that indigo always crashed the same way and exactly after the tty port error message. Thank you for the help!
@Paolo97Gll, We have other users asking for this driver. Would you be willing to share it with us so that we include it in the main distribution?
Sorry for the late reply! We would love to include it in the main branch, but unfortunately, we cannot share it for two main reasons:
It is highly custom (written in C++ 2020 and communicates with the focuser via REST APIs and a reverse proxy since the focuser cannot connect to an existing WiFi).
We are under NDA with the manufacturer as we asked for the communication APIs to develop the said driver.
However, we are big fans of the project, and we can tell you the following:
We know there are INDI USB drivers for ESATTO and other Primaluce Lab products. We have tested them and can confirm that they work. So you could use them as a development base. Here the INDI driver communication protocol for the ESATTO and other PrimaLuceLab products:
We are also willing to test the drivers you develop. We have a spare ESATTO 3" and an ESATTO 3.5" LP connected to the dome equipment.
We also suggest that you contact PrimaLuceLab. When we did it, they were very helpful, and provided us with, albeit under NDA, the communication APIs for ESATTO and SESTOSENSO. Maybe, given that you are the developers of an important communication framework, they will give you the API without any special agreement.
Finally, we would like to leave you a note. At the top of the INDI files we linked us is written "USB Control Specification Document Revision 3.3 published 2020.07.08". However, we cannot find that file anywhere on internet.
Thank you for the explanation, I understand. I saw INDI drivers already and even more useful was the discussion on INDI developers forum with communication logs, so I think I have an idea how it works. I also noticed that USB Control Specification Document and I know it is not available anywhere from public sources.
I tried to connect PrimaLuceLab couple of times with no reaction from their side at all :(
We can't start indigo_server 2.0-228, the server crashes with the following error:
After the crash, the server restarts immediately and automatically.
Complete error log in trace mode:
I can't say if the error is due to version 2.0-228 or an early version. I can only say that in indigo 2.0-208 the error is present but the server doesn't crash.
The server is running Ubuntu server 22.04.