After today's Nightly update, I have been unable to connect to my INDI server. I tried to reinstall, but it says it's allready installed.

astro@nanopct4:~$ sudo -H pip3 install indiweb
Requirement already satisfied: indiweb in /usr/local/lib/python3.8/dist-packages (0.1.7)
Requirement already satisfied: psutil in /usr/local/lib/python3.8/dist-packages (from indiweb) (5.7.3)
Requirement already satisfied: bottle in /usr/local/lib/python3.8/dist-packages (from indiweb) (0.12.18)
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from indiweb) (2.22.0)

So then I asked for an INDIWeb system check - and got this.

astro@nanopct4:~$ sudo systemctl status indiwebmanager.service
● indiwebmanager.service - INDI Web Manager
Loaded: loaded (/etc/systemd/system/indiwebmanager.service; enabled; vendo>
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-10>
Process: 5310 ExecStart=/usr/local/bin/indi-web -v (code=exited, status=1/F>
Main PID: 5310 (code=exited, status=1/FAILURE)
lines 1-5/5 (END)...skipping...
● indiwebmanager.service - INDI Web Manager
Loaded: loaded (/etc/systemd/system/indiwebmanager.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-10 20:04:00 MST; 4s ago
Process: 5310 ExecStart=/usr/local/bin/indi-web -v (code=exited, status=1/FAILURE)
Main PID: 5310 (code=exited, status=1/FAILURE)


What's going on?

Can you stop the service
sudo systemctl stop indiwebmanager.service

Then run indi-web from the command line t see what happens
indi-web -v

Thanks Kengs, here's what I got back:

astro@nanopct4:~$ sudo systemctl stop indiwebmanager.service
[sudo] password for astro:
astro@nanopct4:~$ indi-web -v
2021-02-10 21:49:03,741 - DEBUG: command line arguments: {'indi_port': 7624, 'port': 8624, 'host': '0.0.0.0', 'fifo': '/tmp/indiFIFO', 'conf': '/home/astro/.indi', 'xmldir': '/usr/share/indi/', 'verbose': True, 'logfile': None, 'server': 'standalone'}
2021-02-10 21:49:03,749 - INFO: pkill -9 indiserver
2021-02-10 21:49:03,921 - WARNING: terminating indiserver failed code 1
2021-02-10 21:49:03,921 - INFO: pkill -2 indihub-agent
2021-02-10 21:49:04,087 - WARNING: terminating indihub-agent failed code 1
2021-02-10 21:49:04,090 - INFO: using Bottle as standalone server
2021-02-10 21:49:04,152 - INFO: Deleting fifo /tmp/indiFIFO
2021-02-10 21:49:04,169 - INFO: indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO > /tmp/indiserver.log 2>&1 &
2021-02-10 21:49:04,177 - INFO: echo "start indi_astrometry" > /tmp/indiFIFO
2021-02-10 21:49:04,185 - INFO: echo "start indi_asi_ccd" > /tmp/indiFIFO
2021-02-10 21:49:04,198 - INFO: echo "start indi_nexdome" > /tmp/indiFIFO
2021-02-10 21:49:04,208 - INFO: echo "start indi_asi_wheel" > /tmp/indiFIFO
2021-02-10 21:49:04,215 - INFO: echo "start indi_sestosenso2_focus" > /tmp/indiFIFO
2021-02-10 21:49:04,223 - INFO: echo "start indi_sx_ccd" > /tmp/indiFIFO
2021-02-10 21:49:04,231 - INFO: echo "start indi_ioptronv3_telescope" > /tmp/indiFIFO
Traceback (most recent call last):
File "/usr/local/bin/indi-web", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.8/dist-packages/indiweb/main.py", line 389, in main
start_profile(profile)
File "/usr/local/lib/python3.8/dist-packages/indiweb/main.py", line 108, in start_profile
indi_server.start(info, all_drivers)
File "/usr/local/lib/python3.8/dist-packages/indiweb/indi_server.py", line 70, in start
self.start_driver(driver)
File "/usr/local/lib/python3.8/dist-packages/indiweb/indi_server.py", line 37, in start_driver
cmd = 'start %s' % driver.binary
AttributeError: 'NoneType' object has no attribute 'binary'
astro@nanopct4:~$

Trying to restart it gets the same error:

<strong>astro@nanopct4:~$ indi-web -v

2021-02-10 22:06:46,587 - DEBUG: command line arguments: {'indi_port': 7624, 'port': 8624, 'host': '0.0.0.0', 'fifo': '/tmp/indiFIFO', 'conf': '/home/astro/.indi', 'xmldir': '/usr/share/indi/', 'verbose': True, 'logfile': None, 'server': 'standalone'}
2021-02-10 22:06:46,595 - INFO: pkill -9 indiserver
2021-02-10 22:06:46,775 - WARNING: terminating indiserver failed code 1
2021-02-10 22:06:46,775 - INFO: pkill -2 indihub-agent
2021-02-10 22:06:46,955 - WARNING: terminating indihub-agent failed code 1
2021-02-10 22:06:46,958 - INFO: using Bottle as standalone server
2021-02-10 22:06:47,025 - INFO: Deleting fifo /tmp/indiFIFO
2021-02-10 22:06:47,042 - INFO: indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO > /tmp/indiserver.log 2>&1 &
2021-02-10 22:06:47,050 - INFO: echo "start indi_astrometry" > /tmp/indiFIFO
2021-02-10 22:06:47,058 - INFO: echo "start indi_asi_ccd" > /tmp/indiFIFO
2021-02-10 22:06:47,071 - INFO: echo "start indi_nexdome" > /tmp/indiFIFO
2021-02-10 22:06:47,080 - INFO: echo "start indi_asi_wheel" > /tmp/indiFIFO
2021-02-10 22:06:47,094 - INFO: echo "start indi_sestosenso2_focus" > /tmp/indiFIFO
2021-02-10 22:06:47,103 - INFO: echo "start indi_sx_ccd" > /tmp/indiFIFO
2021-02-10 22:06:47,113 - INFO: echo "start indi_ioptronv3_telescope" > /tmp/indiFIFO
Traceback (most recent call last):
File "/usr/local/bin/indi-web", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.8/dist-packages/indiweb/main.py", line 389, in main
start_profile(profile)
File "/usr/local/lib/python3.8/dist-packages/indiweb/main.py", line 108, in start_profile
indi_server.start(info, all_drivers)
File "/usr/local/lib/python3.8/dist-packages/indiweb/indi_server.py", line 70, in start
self.start_driver(driver)
File "/usr/local/lib/python3.8/dist-packages/indiweb/indi_server.py", line 37, in start_driver
cmd = 'start %s' % driver.binary
AttributeError: 'NoneType' object has no attribute 'binary'
astro@nanopct4:~$

Does your profile have another driver after indi_ioptronv3_telescope ?
It seems to be failing on the next entry in the profile after that
Could be a corrupt profile database

Cloudwatcher. That's the driver that is missing.
I created a new profile with just my mount and camera and it still fails.
How do I delete the profile database? I'm not sure how to do that.

The profile database is ~/.indi/profiles.db
If you rename it, indi-web creates a new one

That did it!!
I moved to the desktop and restarted KStars and I am back in business!

Thanks Kengs!

Problem solved!

This is one of the big reasons I love Kstars, all the knowledgeable people here who take the time to help others out!
@Peter, I like keeping up with the nightlies to try out new features but have lost imaging sessions because of my eagerness. Now I keep abreast of the nightlies on an SD card and if there is a problem I also keep the latest stable version on the nvme on the NanoPC-T4. Just pull out the SD card and boot to the nvme and I'm back in business.

I agree, except when a nightly version is the only one that works. I recently had a problem that was fixed in a nightly, but hasn’t yet made it to a stable release update. But often an update on one issue breaks something else that was working fine before.