jks

As of today (December 6) there are roughly 50 public Kiwis running v1.6xx and 120 running v1.7xx. I encourage everyone to update to v1.8xx as soon as possible. So far I've had to fix about 45 Kiwis manually.

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.

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.

v1.800 removes the /root/Beagle_SDR_GPS git clone subdirectory which had grown to anywhere between 500 and 1600 MB and replaces it with a new clone called KiwiSDR (current size 55 MB).

And also a new directory /root/KiwiSDR.files updated from kiwisdr.com (i.e. not part of the Github clone) containing large static files (current size 88 MB).

As a result the new KiwiSDR clone should grow much more slowly over time as it will mostly contain only source code changes and not historical copies of these huge binary files. So things now look roughly like this and there is now plenty of free filesystem space:

That's right. It didn't happen before with Debian 8.

You can't by default connect as root anymore due to enhanced security in Debian 9 and beyond. Get a root shell by logging in as Debian and doing a sudo su. Use the Kiwi serial number as password in both cases if the Kiwi board was attached while you re-flashed using the Kiwi Debian 11.9 image (the Kiwi software changes the default debian and root account passwords to the serial number it finds in the EEPROM of the Kiwi board).

If you want to subsequently connect as root for maintenance reasons (backing up files etc) setup an SSH key in /root/.ssh. You'll have to research how to do that. I'm not going to talk you through that process. There are other options also.

It appears that, in Firefox only, if you try and open www.short-wave.info instead of http://www.short-wave.info (note explicit http:// prefix) Firefox goes into a redirect loop. But Safari and Chrome worked fine for me in that case.

Guess I need to change the Kiwi code to force http://

Your journal file is 353MB. Do a "m clean_logs".

Of the two VPS's the latest one supports https connections. And certain services have been migrated to it. That's why the forum supports https for example. I've been moving things there, but some services are difficult to move for various reasons. So they fall down the priority list because of that. I'll get there eventually. Eventually I'll have to (e.g. the day browsers finally drop non-SSL websites).

Thanks guys, but my VPS service is not the priority at the moment. I have to get this disastrous git situation under control before every Kiwi on the planet becomes bricked.