Axon apt update failure

General
1

I’m having trouble updating the package manager (apt) in the axon though the internet is connected.

Refer below the error:

admin@vicharak:~$ sudo apt update

Ign:1 http://apt.vicharak.in stable InRelease
Hit:2 Index of linux/ubuntu/ focal InRelease
Ign:3 http://apt.vicharak.in stable-axon InRelease
Ign:4 Index of linux/debian/ jammy InRelease
Err:5 Index of linux/debian/ jammy Release
404 Not Found [IP: 18.155.68.38 443]
Ign:1 http://apt.vicharak.in stable InRelease
Ign:3 http://apt.vicharak.in stable-axon InRelease
Ign:1 http://apt.vicharak.in stable InRelease
Ign:3 http://apt.vicharak.in stable-axon InRelease
Err:1 http://apt.vicharak.in stable InRelease
Connection failed [IP: 161.97.92.202 80]
Err:3 http://apt.vicharak.in stable-axon InRelease
Connection failed [IP: 161.97.92.202 80]
Ign:6 https://archive.ubuntu.com/ubuntu jammy InRelease
Ign:7 https://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:8 https://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:9 https://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:6 https://archive.ubuntu.com/ubuntu jammy InRelease
Ign:7 https://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:8 https://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:9 https://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:6 https://archive.ubuntu.com/ubuntu jammy InRelease
Ign:7 https://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:8 https://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:9 https://security.ubuntu.com/ubuntu jammy-security InRelease
Err:6 https://archive.ubuntu.com/ubuntu jammy InRelease
Could not connect to archive.ubuntu.com:443 (185.125.190.82). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:443 (185.125.190.83). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:443 (185.125.190.81). - connect (111: Connection refused) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:443 (91.189.91.81), connection timed out Could not connect to archive.ubuntu.com:443 (91.189.91.83), connection timed out
Err:7 https://archive.ubuntu.com/ubuntu jammy-updates InRelease
Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::101). - connect (101: Network is unreachable)
Err:8 https://archive.ubuntu.com/ubuntu jammy-backports InRelease
Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:443 (2620:2d:4002:1::101). - connect (101: Network is unreachable)
Err:9 https://security.ubuntu.com/ubuntu jammy-security InRelease
Cannot initiate the connection to security.ubuntu.com:443 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:443 (185.125.190.83). - connect (111: Connection refused) Cannot initiate the connection to security.ubuntu.com:443 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:443 (185.125.190.82). - connect (111: Connection refused) Cannot initiate the connection to security.ubuntu.com:443 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:443 (185.125.190.81). - connect (111: Connection refused) Cannot initiate the connection to security.ubuntu.com:443 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to security.ubuntu.com:443 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Could not connect to security.ubuntu.com:443 (91.189.91.81), connection timed out Could not connect to security.ubuntu.com:443 (91.189.91.83), connection timed out
Reading package lists… Done
W: https://download.docker.com/linux/ubuntu/dists/focal/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: The repository ‘Index of linux/debian/ jammy Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

2

@Sanoop The current date and time are not set properly. Could you please check the date and time using the following command?

$ date

If the date and time are incorrect, please set them using the ntpdate command to synchronize with an NTP server:

$ sudo ntpdate pool.ntp.org

After setting the correct date and time, please proceed to update :

$ sudo apt update

3

Date is proper

image

4

@Sanoop Is the board connected to Wi-Fi or Ethernet? If it’s on Wi-Fi, please use a Wi-Fi antenna for better performance. It seems to be a network issue, as it works fine on our end.

Also, the DNS server may not be responding. Try adding nameserver 8.8.8.8 to /etc/resolv.conf to use Google’s DNS.

$ echo "nameserver 8.8.8.8" >> /etc/resolve.conf

5

It is connected to Wired network on etho and I can ping the address 8.8.8.8

image

6

Give us some time, i will look into it.

7

this SBC is completely unusable, even apt upgrade does not work as there is not enough space

(Reading database ... 236854 files and directories currently installed.) Preparing to unpack .../linux-image-5.10.160-axon_20241104-axon_arm64.deb ... Unpacking linux-image-5.10.160-axon (20241104-axon) over (20241009-axon) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-5.10.160-axon _20241104-axon_arm64.deb (--unpack): cannot copy extracted data for './boot/System.map-5.10.160-axon' to '/boot/Syst em.map-5.10.160-axon.dpkg-new': failed to write (No space left on device) No apport report written because the error message indicates a disk full error dp kg-deb: error: paste subprocess was killed by signal (Broken pipe) P: Checking for EXTLINUX directory... found. P: Writing config for Image-5.10.160-axon... P: Checking for EXTLINUX directory... found. P: Writing config for Image-5.10.160-axon... Errors were encountered while processing: /var/cache/apt/archives/linux-image-5.10.160-axon_20241104-axon_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

8

Thanks @Sanoop for sending this, we will look out for this, by the new update this won’t be a problem. Then you can do apt upgrade as usual.

9

I am facing the same issue. How can I upgrade ?

10

If there is no space left in boot partition you can always remove older kernels and try to install new one.

You can do that by,

sudo apt remove linux-image-5.10.* linux-headers-5.10.*
sudo apt install linux-image-<version>-<board_name> linux-headers-<version>-<board_name>

We recommend to use vicharak linux images for better seamless performance.

11

As the board only has one kernel removing old kernel wouldn’t cause any problem?