jks

v1.800 does not have the admin page reload problem. v1.800 fixes that problem. I want to state this so people don't get the wrong idea and start complaining to me (this happens all the time when inaccurate information is posted on the forum).

What you probably saw was the state of the sources in /root after a failed v1.8xx transition. When v1.7xx decides it needs to transition to v1.8xx a few things happen. Remember that it is running out of /usr/local/bin/kiwid and uses only the configuration files in /root/kiwi.config. So the state of the sources don't matter.

The sources in /root/Beagle_SDR_GPS are removed to make disk space in case the filesystem is full. Which is why we are in this mess to begin with. Then the new KiwiSDR repo is git cloned. Then a build of v1.8xx is attempted. If the build fails for any reason the source files will look like it is on v1.8xx. But if you cd; cd KiwiSDR; ms the log will show it still running on the v1.7xx out of /usr/local/bin/kiwid because the build never finished and installed the v1.8xx version. And if the Kiwi restarts same thing.

Okay, I see what's wrong. Will be fixed in v1.801

Today we're enabling an auto update to v1.711, and thereby on to v1.800, for Debian 8 Kiwi's with admin passwords starting with the letter "i" through "l". If this is successful the next update will be applied to all D8 systems.

What's different with v1.711 is that it preemptively attempts to repair the Debian package system to lessen the chance of the build/update failing. This is based on the experience gained repairing D8 systems by hand over the last several days.

This update will of course not affect systems already updated to v1.8xx.

The image you download to create an SD card for re-flashing a BBG/BBB-based Kiwi-1 or Kiwi-2 has been updated from Debian 11.9 to 11.11 and Kiwi software release v1.690 to v1.800.

Full instructions here: http://kiwisdr.com/info/#id-net-reflash

Yes, this problem can occur anytime in the future a Kiwi first crosses the barrier between pre- and post-v1.8xx. That's the point at which the git repo rebase occurs. So going from v1.699 to v1.8xx qualifies (even if v1.800 itself is skipped).

In your case it sounds like you have a Kiwi at a remote site with automatic updates turned off so you can more carefully control the update schedule (an entirely reasonable thing to do). It would be better if you just let me manually do the update to v1.800 now and save you any potential problems when you're next out there. Just set a temporary admin password and email it to support@kiwisdr.com and I'll be happy to do that.