Cannot update software: "Error determining the latest version" [FIXED]
Hi, I hope you can help me. One of my kiwis currently fails to update as it cannot "determine the latest version". Here are the specs.
The setup:
---
Debian 8.5
BeagleBoard.org Debian Image 2016-05-13
Linux kiwisdr 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l GNU/Linux
-bash: lsb_release: command not found
---
Under the Update tab, after clicking on the "Check now" button:
Installed version: v1.515, built Apr 30 2022 18:01:27
Error determining the latest version -- check log
The log says,
--- LOG ---
Wed Jun 22 13:09:12 00:00:00.425 L KiwiSDR v1.515 --------------------------------------------------------------------
Wed Jun 22 13:09:12 00:00:00.430 L compiled: Apr 30 2022 17:54:01 on kiwisdr
Wed Jun 22 13:09:12 00:00:00.433 L -debian 8
Wed Jun 22 13:09:12 00:00:00.435 L /etc/debian_version 8.5
...
Wed Jun 22 16:59:50 03:50:38.714 ........ L UPDATE: force update check by admin
Wed Jun 22 16:59:50 03:50:38.717 ........ L UPDATE: checking for updates
Wed Jun 22 16:59:56 03:50:43.847 ........ UPDATE: fetch origin status=0x00008000
Wed Jun 22 16:59:56 03:50:43.985 ........ L UPDATE: Makefile fetch error, no Internet access? status=0x00008000 WIFEXITED=1 WEXITSTATUS=128
Wed Jun 22 16:59:56 03:50:43.988 ........ task update_task:P3:T003((1000.000 msec) TaskSleep) exited by returning
--- LOG ---
The internet access is OK as it can be accessed and used normally.
I appreciate any help to get this fixed. My other kiwi still works fine with updates.
73 Jari
Comments
What is the output of the "route" command?
It should look something like
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.100.1 0.0.0.0 UG 0 0 0 eth0
192.168.6.0 0.0.0.0 255.255.255.0 U 0 0 0 usb1
192.168.7.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.100.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
If the default is missing the address of your router, add it back in manually with (in this case)
"route add default gw 192.168.100.1 eth0"
Thanks for the reply! The route command returns,
root@kiwisdr:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default elisa.home 0.0.0.0 UG 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.7.0 * 255.255.255.252 U 0 0 0 usb0
The default gw is 192.168.1.1, and the command
route add default gw 192.168.1.1 eth0
will return "SIOCADDRT: File exists".
OK the default gateway is there so can you do two ping tests, one to your gateway as it shows in the route table and one to the software repository
TNX! I think the Internet connection is good as I can listen to this kiwi through the Internet. These pings return the following,
root@kiwisdr:~# ping -c 3 elisa.home
PING elisa.home (192.168.1.1) 56(84) bytes of data.
64 bytes from elisa.home (192.168.1.1): icmp_seq=1 ttl=64 time=6.60 ms
64 bytes from elisa.home (192.168.1.1): icmp_seq=2 ttl=64 time=8.06 ms
64 bytes from elisa.home (192.168.1.1): icmp_seq=3 ttl=64 time=6.59 ms
--- elisa.home ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 6.592/7.087/8.069/0.694 ms
root@kiwisdr:~# ping -c 3 github.com
PING github.com (140.82.121.3) 56(84) bytes of data.
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=1 ttl=52 time=51.6 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=2 ttl=52 time=45.6 ms
64 bytes from lb-140-82-121-3-fra.github.com (140.82.121.3): icmp_seq=3 ttl=52 time=44.5 ms
--- github.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 44.557/47.259/51.608/3.105 ms
OK see the thread - Post https://forum.kiwisdr.com/index.php?p=/discussion/comment/13248/#Comment_13248
As it says "Stop if there are any errors with those commands and let us know what they are. We're looking for git or filesystem problems here."
Thanks, that was a very good pointer! Updating the system...
OK good, there have been a couple of route or ISP network issues recently so that has to be tested/working before doing the actions in that post.
Next time I might just link to that post, as long as the user is OK with entering the commands exactly, and reporting errors, it should cover it.
I followed the instructions in the thread you shared. I received similar error messages as result from the 'gpu' command. So, I followed the sequence of commands that fetched the most recent version and compiled it. That process took quite a while but finally everything was fine!
Thanks again for the valuable pointer! 😃