LBTO INDI Troubleshooting
Restart a Driver
The indiserver processes will restart drivers they control if it goes down. So, to bounce a driver, just
to find it and then
[web@web1 tmp]$ ps -ef | grep indi
web 2518 1 10 21:43 ? 00:03:33 /web/statserv/cgi-bin/indi.fcgi +age=2 +reconnects=100 +log=/web/server/logs/indi.fcgi.log +host=localhost:7624
root 4032 1 0 21:48 ? 00:00:00 /usr/bin/su - web /web/modules/INDI/bin/runindi
web 4034 4032 0 21:48 ? 00:00:00 -bash /web/modules/INDI/bin/runindi
web 4059 4034 2 21:48 ? 00:00:49 /web/modules/INDI/bin/indiserver -l /web/modules/INDI/logs/IS ./indialh LBTO@192.168.3.17:7630 OVMS@192.168.53.60
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
web 4070 4059 1 21:48 ? 00:00:30 ./indialh
You can see from this ps command that the indiserver here is using one local driver (
) and several on other machines (
If you kill process ID 4070, the indiserver here will restart it.
The drivers running on LBTO, OVMS
, AO machines can be bounced on those machines, if necessary.
Stop a Server running on the web cluster in Tucson:
To kill off the indi server running from the cluster (as root from the machine running "web.tucson"):
- Type: "pcs resource disable web.tucson-indi", and then "pcs status" should show that it is disabled.
- Find the INDI processes and kill them individually -- "systemctl stop indi" does not seem to kill everything.
Start a stopped Server running on the web cluster in Tucson:
- Type: "pcs resource enable web.tucson-indi", and then "pcs status" should show that it is enabled and started (after a bit).
Restart a Server
To restart an
web.tucson.lbto.org, you can kill it and the
indi.service will restart it (using the
LBTO properties are written from an INDI thread in DDS, there's no INDI server there to restart
Note: If you modify the
script, you have to reload it in the
Otherwise, it just manages the process with the same version of the file
it has loaded.
sudo systemctl daemon-reload
Not sure if the service has to be stopped and restarted. When I did this today,
because we did not have the flao_xx_wfsbcu drivers in the script, I had the
service stopped when I did the daemon-reload.
sudo systemctl stop indi.service
sudo systemctl daemon-reload
kill 2175 to kill the indiserver running
sudo systemctl start indi.service
[web@web1 IS]$ sudo systemctl status indi
indi.service - Cluster Controlled indi
Loaded: loaded (/etc/systemd/system/indi.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2017-07-21 17:45:46 UTC; 2 days ago
Main PID: 21624 (su)
21624 /usr/bin/su - web /web/modules/INDI/bin/runindi
Jul 21 17:45:46 web1.tucson.lbto.org systemd: Started Cluster Controlled indi.
Jul 21 17:45:46 web1.tucson.lbto.org systemd: Starting Cluster Controlled indi...
Jul 21 17:45:46 web1.tucson.lbto.org su: (to web) root on none