update problem [Debian filesystem was full. Huge log files, reason unknown]
Hello, Kiwi friends,
I'm having the problem that I can't do an update.
When checking for a new update I get the following error message: "Error determining the latest version -- check log"
The log file then contains the following:
Mon Jul 29 14:58:24 00:22:09.319 .... UPDATE: force update check by admin
Mon Jul 29 14:58:24 00:22:09.323 .... UPDATE: checking for updates
Mon Jul 29 14:58:25 00:22:10.350 .... UPDATE: curl Makefile error, no Internet access? status=0x00001700 WIFEXITED=1 WEXITSTATUS=23
Mon Jul 29 14:58:25 00:22:10.354 .... task update_task:P3:T03((1000.000 msec) TaskSleep) exited by returning
The Kiwi has an internet connection, port sharing is set correctly and NAT also works.
I can't get any further, can anyone help me?
I'm having the problem that I can't do an update.
When checking for a new update I get the following error message: "Error determining the latest version -- check log"
The log file then contains the following:
Mon Jul 29 14:58:24 00:22:09.319 .... UPDATE: force update check by admin
Mon Jul 29 14:58:24 00:22:09.323 .... UPDATE: checking for updates
Mon Jul 29 14:58:25 00:22:10.350 .... UPDATE: curl Makefile error, no Internet access? status=0x00001700 WIFEXITED=1 WEXITSTATUS=23
Mon Jul 29 14:58:25 00:22:10.354 .... task update_task:P3:T03((1000.000 msec) TaskSleep) exited by returning
The Kiwi has an internet connection, port sharing is set correctly and NAT also works.
I can't get any further, can anyone help me?
Comments
If you SSH to the Kiwi and "traceroute public.kiwisdr.com"
does it correctly get an IP address and then show the route to it?
Stu
What version are you currently running and has it updated OK before?
Traceroute shows me as first entry my ip of the router
and also the IP of public.kiwisdr.com (142.104.83.74)
Use ssh/PuTTY to login to the Beagle. "df ." command will tell you if your filesystem is full. "cd /var/log" then "du". End of printout from du will be the largest files. I did a "rm syslog daemon.log" because they were huge. But that isn't enough. You have to "reboot" afterwards or else the space will not be freed.