pieyedpiper
Posts: 8
Joined: Wed Mar 28, 2018 7:04 pm

Buster Update Issue

Fri Jul 12, 2019 11:01 am

Yesterday I tried to install a clean version of Raspbian based on 2019-06-20-raspbian-buster-full which was successfully written to a card. There were significant issues trying to update after the installation with error message wrt paths not found etc, totally unable to find/install any updates.

I reformatted the card and reinstalled and tried again today. After booting up there was an issue with the following report:

Error checking for updates.
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'


I rebooted and then ran sudo apt update with the following response.

[email protected]:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:4 http://raspbian.raspberrypi.org/raspbian buster/contrib armhf Packages [58.7 kB]
Fetched 13.1 MB in 26s (496 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
71 packages can be upgraded. Run 'apt list --upgradable' to see them.

After proceeding the update took the best part of 20 mins.

So the most significant issue seems to be the error message after the initial update.

As an aside, given that the latest image was used, the update seems to be pretty slow (20 mins) although I guess there were 71 packages.

pieyedpiper
Posts: 8
Joined: Wed Mar 28, 2018 7:04 pm

Re: Buster Update Issue

Fri Jul 12, 2019 11:47 am

Update. After making some more changes on the pi e.g. adding new users, now no longer able to update.

[email protected]:~ $ sudo apt update
[sudo] password for Xname:
Err:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian buster InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://raspbian.raspberrypi.org/raspbia ... /InRelease Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/d ... /InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.


Not good.

Andyroo
Posts: 3255
Joined: Sat Jun 16, 2018 12:49 am
Location: Lincs U.K.

Re: Buster Update Issue

Fri Jul 12, 2019 11:55 am

pieyedpiper wrote:
Fri Jul 12, 2019 11:47 am
...
Err:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian buster InRelease
Temporary failure resolving 'archive.raspberrypi.org'
...
That infers you do not have an internet connection.

Can you post the output of

Code: Select all

ifconfig

Code: Select all

route

Code: Select all

ping 8.8.8.8

Code: Select all

ping google.com
Need Pi spray - these things are breeding in my house...

gsahli
Posts: 4
Joined: Mon Sep 04, 2017 3:06 am

Re: Buster Update Issue

Fri Jul 12, 2019 12:56 pm

Had a similar issue. I'm using Synaptic.
Got error:
"Could not download all repository indexes"
Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'

Not an internet issue...

Code: Select all

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=23.8 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=23.5 ms

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.200.30  netmask 255.255.255.0  broadcast 192.168.200.255
        inet6 fe80::2f4d:97b8:4d86:3113  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:72:c1:1f  txqueuelen 1000  (Ethernet)
        RX packets 110606  bytes 155457151 (148.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 57116  bytes 4689637 (4.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

gsahli
Posts: 4
Joined: Mon Sep 04, 2017 3:06 am

Re: Buster Update Issue

Fri Jul 12, 2019 1:05 pm

More specifics:
was trying to install LXQT
got error:

Code: Select all

W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/libf/libfm-qt/libfm-qt6_0.14.1-8+rpi1_armhf.deb
  404  Not Found [IP: 93.93.128.193 80]

W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/pool/main/libf/libfm-qt/libfm-qt-l10n_0.14.1-8+rpi1_all.deb
  404  Not Found [IP: 93.93.128.193 80]
  
E: lximage-qt: dependency problems - leaving unconfigured
E: lxqt: 15.3846:dependency problems - leaving unconfigured
E: pcmanfm-qt: dependency problems - leaving unconfigured
E: lxqt-core: dependency problems - leaving unconfigured 

pieyedpiper
Posts: 8
Joined: Wed Mar 28, 2018 7:04 pm

Re: Buster Update Issue

Fri Jul 12, 2019 2:09 pm

Thanks for your speedy feedback., I suspect you are right. Data below (specific IP and MAC masked).

~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.yyy.zzz netmask 255.255.255.0 broadcast 192.168.yyy.255
inet6 1111::2222:3333:4444:5555 prefixlen 64 scopeid 0x20<link>
ether 11:22:33:44:55:66 txqueuelen 1000 (Ethernet)
RX packets 32029 bytes 9642737 (9.1 MiB)
RX errors 0 dropped 10 overruns 0 frame 0
TX packets 3466 bytes 281813 (275.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 300 (300.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 300 (300.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.yyy.xxx netmask 255.255.255.0 broadcast 192.168.yyy.255
inet6 aaaa::bbbb:cccc:dddd:eeee prefixlen 64 scopeid 0x20<link>
ether aa:bb:cc:dd:ee:ff txqueuelen 1000 (Ethernet)
RX packets 52177 bytes 14471200 (13.8 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 14 bytes 1599 (1.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

~ $ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.yyy.254 0.0.0.0 UG 202 0 0 eth0
default 192.168.yyy.254 0.0.0.0 UG 303 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 303 0 0 wlan0

~ $ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 235ms

~ $ ping google.com
PING google.com (216.58.204.46) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- google.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 197ms


Note that I can successfully ping both of these from the PC attached to the pi so seemingly not a network issue.,

After the initial update I had installed and enabled ufw. The default rules are deny incoming and outgoing and I have never had issues connecting for updates in the past. Just thought I would check out whether this is a factor.

sudo ufw allow out http

Oddly enough, update now seems to work.

~ $ sudo apt update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.


Here are the data for ifconfig with this ufw change.

~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.yyy.zzz netmask 255.255.255.0 broadcast 192.168.yyy.255
inet6 1111:22223333:4444:5555 prefixlen 64 scopeid 0x20<link>
ether 11:22:33:44:55:66 txqueuelen 1000 (Ethernet)
RX packets 32277 bytes 9666768 (9.2 MiB)
RX errors 0 dropped 10 overruns 0 frame 0
TX packets 3482 bytes 282750 (276.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6 bytes 300 (300.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 300 (300.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.yyy.xxx netmask 255.255.255.0 broadcast 192.168.yyy.255
inet6 aaaa::bbbb:cccc:dddd:eeee prefixlen 64 scopeid 0x20<link>
ether aa:bb:cc:dd:ee:ff txqueuelen 1000 (Ethernet)
RX packets 52638 bytes 14606479 (13.9 MiB)
RX errors 0 dropped 3 overruns 0 frame 0
TX packets 14 bytes 1599 (1.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Still cannot ping 8.8.8.8 and google.com.

So I disabled ufw and hey presto, can now ping 8.8.8.8 and google.com. :D

Reset ufw and then re-enabled. Cannot ping 8.8.8.8 and google.com. :(

So I think this suggests a UFW compatibility issue in this latest update that was downloaded.

Thoughts?

Andyroo
Posts: 3255
Joined: Sat Jun 16, 2018 12:49 am
Location: Lincs U.K.

Re: Buster Update Issue

Fri Jul 12, 2019 5:15 pm

No need to hide any part of the internal (private) addresses - the internet will not route this from site to site and it can be a pain to debug issues :lol:

The note
The default rules are deny incoming and outgoing
suggest that you have set ufw to block ALL outgoing traffic...

I have ufw (inactive) loaded on a 3B+ under Buster (IPv6 disabled) and not seeing any issues with updates / network access. At a very basic level I would:

Code: Select all

sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh
sudo ufw enable
Running the status command I get

Code: Select all

sudo ufw status verbose

Code: Select all

Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW IN    Anywhere
This still allows update / upgrade to be run.

I think

Code: Select all

sudo ufw reset
will clear all rules (I'm on a Pi via ssh so cannot play too much) BUT does not touch the defaults so you would have to issue

Code: Select all

sudo ufw default allow outgoing
to reset them.

edit:
A quick man ufw shows:
On installation, ufw is disabled with a default incoming policy of deny, a default forward policy of deny, and a default outgoing policy of allow
so its a safe default (hint Microsoft)
Need Pi spray - these things are breeding in my house...

pieyedpiper
Posts: 8
Joined: Wed Mar 28, 2018 7:04 pm

Re: Buster Update Issue

Fri Jul 12, 2019 10:08 pm

My error.

When I set up from scratch I have a standard set of instructions that I follow. For ufw these include:
sudo ufw enable
sudo ufw default deny incoming #just to confirm default set
sudo ufw default allow outgoing #just to confirm default set
sudo allo from 192.168.xxx.yyy to any port 11111 proto tcp
sudo allo from 192.168.xxx.zzz to any port 11111 proto tcp

When I reset the ufw I assumed that this would reset the defaults. I didn't realise that the defaults were unaffected.

I think my error on this install (and yesterday) must have been copying sudo ufw default deny incoming and only changing incoming to outgoing...so my default, not reset, was to block outgoing. Never done this before, have now done it twice in two days embarrassingly. :cry:

Many thanks for your time and feedback on this.

martinmarty
Posts: 27
Joined: Mon Sep 22, 2014 1:03 am

Re: Buster Update Issue

Sat Jul 13, 2019 11:56 am

This morning I was having a similar issue as the original poster while trying to bring my RPi 2 model B up-to-date. It is running Raspbian Buster Lite.

I got the same error about the repository having changed from testing to stable.

From reading other posts, I was able to resolve my problem by doing:

sudo apt-get update --allow-releaseinfo-change

after that, these worked as normal:

sudo apt-get upgrade
sudo apt-get dist-upgrade

YMMV.

gsahli
Posts: 4
Joined: Mon Sep 04, 2017 3:06 am

Re: Buster Update Issue

Sun Jul 14, 2019 3:55 am

That's a good method.
I switched to a different repository and no longer have the issue. So, I think it's a server settings issue.

User avatar
HawaiianPi
Posts: 4185
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: Buster Update Issue

Sun Jul 14, 2019 4:48 am

martinmarty wrote:
Sat Jul 13, 2019 11:56 am
sudo apt-get update --allow-releaseinfo-change
sudo apt update -y is less typing. ;)

You can do it all in one command line.

Code: Select all

sudo apt update -y && sudo apt full-upgrade -y
Of course there is a new image now that resolved the status change issue (2019-07-10), so this only applies to images prior to that.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Return to “Raspbian”