×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel

3 weeks 18 hours ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57087
Hello,

I opened a ticket with StellarMate, but figured that I would post here as well to see if anyone has had a similar experience.

I recently switched from the StellarMate stable to the beta channel to address an issue that I was having with camera shutter control behavior on 1.5.2. After upgrading to 1.5.3, the GPSD driver now crashes at start every time I start Indi and try to connect to my devices (it fixed my camera issue though). I had GPS working just fine under 1.5.2, so I know that the GPS device I am using is supported and functional.

I attempted to enable logging, but no logs are produced in the log folder when the crashing occurs. I went so far as to even do a clean install of 1.5.2 and upgrade it to 1.5.3 before configuring any equipment to rule out an incompatibility with my previous configuration files after upgrading.

Any thoughts are appreciated.

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57116
Update: I saw that there is a new Ekos Debugger tool and was able to use it to get some log info about the crash:

Debug Log:

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[New inferior 2 (process 2431)]
[Inferior 1 (process 2427) detached]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
process 2431 is executing new program: /usr/bin/indi_gpsd
[Inferior 2 (process 2431) exited with code 0177]

Application Log:

2020-07-21T23:01:13: startup: /usr/bin/indiserver -r 0 -v indi_gpsd indi_gphoto_ccd indi_celestron_sct_focus indi_eqmod_telescope
[Attaching after Thread 0xb6ffa090 (LWP 2427) fork to child process 2431]
[Detaching after fork from parent process 2427]
2020-07-21T23:01:13: Driver indi_gpsd: pid=2431 rfd=3 wfd=6 efd=7
2020-07-21T23:01:13: Driver indi_gphoto_ccd: pid=2432 rfd=4 wfd=9 efd=10
2020-07-21T23:01:13: Driver indi_celestron_sct_focus: pid=2433 rfd=5 wfd=12 efd=13
2020-07-21T23:01:13: Driver indi_eqmod_telescope: pid=2434 rfd=8 wfd=15 efd=16
2020-07-21T23:01:13: listening to port 7624 on fd 11
2020-07-21T23:01:13: Driver indi_eqmod_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on SQM.SKY_QUALITY
2020-07-21T23:01:13: Driver indi_eqmod_telescope: snooping on GPS Simulator.TIME_UTC
2020-07-21T23:01:13: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_PARK
2020-07-21T23:01:13: Driver indi_eqmod_telescope: snooping on Dome Simulator.DOME_SHUTTER
2020-07-21T23:01:13: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_sk.xml
2020-07-21T23:01:13: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_align_sk.xml
2020-07-21T23:01:13: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_simulator_sk.xml
2020-07-21T23:01:13: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_scope_limits_sk.xml
2020-07-21T23:01:13: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on EQMod Mount.EQUATORIAL_EOD_COORD
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on EQMod Mount.TELESCOPE_INFO
2020-07-21T23:01:13: Driver indi_gphoto_ccd: snooping on EQMod Mount.GEOGRAPHIC_COORD
2020-07-21T23:01:13: Driver indi_gpsd: indi_gpsd: symbol lookup error: indi_gpsd: undefined symbol: _ZN4INDI13DefaultDeviceD2Ev
2020-07-21T23:01:13: Driver indi_gpsd: stderr EOF
2020-07-21T23:01:13: Driver indi_gpsd: Terminated after #0 restarts.
Child process 2431 died
No stack.

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

2 weeks 6 days ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57125
Hello,

In terminal.

Use: sudo systemctl status gpsd

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57130
stellarmate@stellarmate:~ $ sudo systemctl status gpsd
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; disabled; vendor preset: en
Active: active (running) since Tue 2020-07-21 20:28:11 EDT; 40min ago
Process: 457 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, sta
Main PID: 472 (gpsd)
Tasks: 2 (limit: 4915)
Memory: 1.8M
CGroup: /system.slice/gpsd.service
\u2514\u2500472 /usr/sbin/gpsd -n -b /dev/gps

Jul 21 20:28:11 stellarmate systemd[1]: Starting GPS (Global Positioning System)
Jul 21 20:28:11 stellarmate systemd[1]: Started GPS (Global Positioning System)
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: device open of /dev/ttyA
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: read-only device open of
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: device open of /dev/ttyA
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: read-only device open of
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: /dev/ttyACM1: device activati
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: /dev/ttyACM1: activation fail
lines 1-18/18 (END)...skipping...
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2020-07-21 20:28:11 EDT; 40min ago
Process: 457 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 472 (gpsd)
Tasks: 2 (limit: 4915)
Memory: 1.8M
CGroup: /system.slice/gpsd.service
\u2514\u2500472 /usr/sbin/gpsd -n -b /dev/gps

Jul 21 20:28:11 stellarmate systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 21 20:28:11 stellarmate systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: device open of /dev/ttyACM1 failed: Device or resource busy - retrying read-only
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: read-only device open of /dev/ttyACM1 failed: Device or resource busy
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: device open of /dev/ttyACM1 failed: Device or resource busy - retrying read-only
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: SER: read-only device open of /dev/ttyACM1 failed: Device or resource busy
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: /dev/ttyACM1: device activation failed.
Jul 21 20:28:12 stellarmate gpsd[472]: gpsd:ERROR: /dev/ttyACM1: activation failed, freeing device

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

2 weeks 6 days ago 2 weeks 6 days ago by AradoSKYindi.
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57131
Hello,

The first issue is what new RS232 device has been added. My EQMOD requires an RS232 connection. I use rules to manage RS232 connection devices.


Use: sudo udevadm info /dev/ttyACM0

Next

Use: sudo udevadm info /dev/ttyACM1

Let’s see what is using both before setting an action plan. I think I see the problem, but I want to confirm the ports are open.

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57133
Thanks so much for the help! My USB devices are as follows:

/dev/ttyUSB0 - FTDI USB cable for EQMOD mount
/dev/ttyUSB1 - FTDI USB interface for Kmtronic USB relay for camera shutter
/dev/ttyACM0 - Mapped to /dev/focuser via StellarMate Serial Port Assistant for Celestron focus motor
/dev/ttyACM1 - Mapped to /dev/gps via StellarMate Serial Port Assistant for USB GPS dongle

Output from the commands:

stellarmate@stellarmate:~ $ sudo udevadm info /dev/ttyACM0
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM0
N: ttyACM0
L: 0
S: focuser
S: serial/by-id/usb-Celestron_Celestron_Focuser_MF_v1-if00
S: serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM0
E: DEVNAME=/dev/ttyACM0
E: MAJOR=166
E: MINOR=0
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=5221281
E: ID_BUS=usb
E: ID_VENDOR_ID=15a2
E: ID_MODEL_ID=a50f
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_PCI_INTERFACE_FROM_DATABASE=XHCI
E: ID_VENDOR_FROM_DATABASE=Freescale Semiconductor, Inc.
E: ID_MODEL_FROM_DATABASE=VL805 USB 3.0 Host Controller
E: ID_VENDOR=Celestron
E: ID_VENDOR_ENC=Celestron
E: ID_MODEL=Celestron_Focuser
E: ID_MODEL_ENC=Celestron\x20Focuser
E: ID_REVISION=0000
E: ID_SERIAL=Celestron_Celestron_Focuser_MF_v1
E: ID_SERIAL_SHORT=MF_v1
E: ID_TYPE=generic
E: ID_USB_INTERFACES=:020201:0a0000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: ID_USB_CLASS_FROM_DATABASE=Communications
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_1_1_0
E: DEVLINKS=/dev/focuser /dev/serial/by-id/usb-Celestron_Celestron_Focuser_MF_v1-if00 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: TAGS=:systemd:

stellarmate@stellarmate:~ $ sudo udevadm info /dev/ttyACM1
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
N: ttyACM1
L: 0
S: gps1
S: gps
S: serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00
S: serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/tty/ttyACM1
E: DEVNAME=/dev/ttyACM1
E: MAJOR=166
E: MINOR=1
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=5231341
E: SYSTEMD_WANTS=gpsdctl@ttyACM1.service
E: ID_BUS=usb
E: ID_VENDOR_ID=1546
E: ID_MODEL_ID=01a7
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_PCI_INTERFACE_FROM_DATABASE=XHCI
E: ID_VENDOR_FROM_DATABASE=U-Blox AG
E: ID_MODEL_FROM_DATABASE=[u-blox 7]
E: ID_VENDOR=u-blox_AG_-_www.u-blox.com
E: ID_VENDOR_ENC=u-blox\x20AG\x20-\x20www.u-blox.com
E: ID_MODEL=u-blox_7_-_GPS_GNSS_Receiver
E: ID_MODEL_ENC=u-blox\x207\x20-\x20GPS\x2fGNSS\x20Receiver
E: ID_REVISION=0100
E: ID_SERIAL=u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver
E: ID_TYPE=generic
E: ID_USB_INTERFACES=:020201:0a00ff:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: ID_USB_CLASS_FROM_DATABASE=Communications
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_3_1_0
E: DEVLINKS=/dev/gps1 /dev/gps /dev/serial/by-id/usb-u-blox_AG_-_www.u-blox.com_u-blox_7_-_GPS_GNSS_Receiver-if00 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0
E: TAGS=:systemd:

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

2 weeks 6 days ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57134
Hello,

Use: sudo systemctl enable gpsd

Next

Use: sudo systemctl start gpsd

Thank you for the output. This helps to see the status.

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57135
Nothing happened after starting gpsd, but this is the output:

stellarmate@stellarmate:~ $ sudo systemctl enable gpsd
Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gpsd
Created symlink /etc/systemd/system/multi-user.target.wants/gpsd.service \u2192 /lib/systemd/system/gpsd.service.
stellarmate@stellarmate:~ $ sudo systemctl start gpsd
stellarmate@stellarmate:~ $

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

2 weeks 6 days ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57136
Hello,

Good deal. GPSD is now operational. You
should be able to open KSTARS and EKOS.

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57137
Unfortunately, the gpsd driver still crashes as soon as I start indi and my devices connect.

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

2 weeks 6 days ago 2 weeks 6 days ago by AradoSKYindi.
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57138
Hello,

Let’s check the status of GPSD.

Use: sudo systemctl status gpsd


Crashes when loading usually means the driver is expecting it to be at one port but the port is taken. In .indi at the root of /home/stellermate/.indi has the indi_gpsd. XML file. Use geany to open the file and see which port it thinks it is supposed to see. Look for ttyACM. Currently, gpsd is at ttyACM1.

I have the same uBlox-7 device.

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

2 weeks 6 days ago
Gonzo
Fresh Boarder
Fresh Boarder
Posts: 18
More
Topic Author
GPSD Crashing After Update to StellarMate 1.5.3 via Beta Channel #57139
The indi_gpsd.xml file appears to be blank when opened in geany.

Status of gpsd:

stellarmate@stellarmate:~ $ sudo systemctl status gpsd
\u25cf gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-07-21 21:22:49 EDT; 34min ago
Main PID: 559 (gpsd)
Tasks: 2 (limit: 4915)
Memory: 1.8M
CGroup: /system.slice/gpsd.service
\u2514\u2500559 /usr/sbin/gpsd -n -b /dev/gps

Jul 21 21:22:49 stellarmate systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 21 21:22:49 stellarmate systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: SER: device open of /dev/ttyACM1 failed: Device or resource busy - retrying read-only
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: SER: read-only device open of /dev/ttyACM1 failed: Device or resource busy
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: SER: device open of /dev/ttyACM1 failed: Device or resource busy - retrying read-only
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: SER: read-only device open of /dev/ttyACM1 failed: Device or resource busy
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: /dev/ttyACM1: device activation failed.
Jul 21 21:22:49 stellarmate gpsd[559]: gpsd:ERROR: /dev/ttyACM1: activation failed, freeing device

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

Time to create page: 0.983 seconds