[SOLVED] Can't connect to repos

Ron · 2024-02-07 23:27:45

Normally I wouldn't make a post like this, but this has been going on for the last 2 hours (usually it resolves itself in a few minutes). I'm not able to contact the repos, I've been getting the message below. Anybody else getting this?

Last edited by Ron (2024-02-10 13:32:04)

Altoid · 2024-02-07 23:43:04

Hello:

Ron wrote:

... not able to contact the repos ...
Anybody else getting this?

Not with synaptic (daedalus is not in my sources.list file) but wget got me a *.deb file a couple of minutes ago without issues:

~$ wget http://deb.devuan.org/merged/pool/DEBIAN/main/s/sudo/sudo_1.9.13p3-1+deb12u1_amd64.deb
--2024-02-07 20:35:19--  http://deb.devuan.org/merged/pool/DEBIAN/main/s/sudo/sudo_1.9.13p3-1+deb12u1_amd64.deb
Resolving deb.devuan.org (deb.devuan.org)... 131.188.12.211, 147.78.194.22, 195.85.215.180, ...
Connecting to deb.devuan.org (deb.devuan.org)|131.188.12.211|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1889484 (1.8M) [application/x-debian-package]
Saving to: 'sudo_1.9.13p3-1+deb12u1_amd64.deb'

sudo_1.9.13p3-1+deb12u1_amd64.deb     100%[=============|<-snip->|=================>]   1.80M   652KB/s    in 2.8s    

2024-02-07 20:35:23 (652 KB/s) - 'sudo_1.9.13p3-1+deb12u1_amd64.deb' saved [1889484/1889484]
~$

HTH.

Best,

A.

pcalvert · 2024-02-07 23:58:39

Yes, I have been seeing something similar with apt since yesterday on a Chimaera-based Refracta system.

# apt update
Err:1 http://deb.devuan.org/merged chimaera InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:2 http://deb.devuan.org/merged chimaera-updates InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:3 http://deb.devuan.org/merged chimaera-security InRelease
  Temporary failure resolving 'deb.devuan.org'
Err:4 http://deb.devuan.org/merged chimaera-backports InRelease
  Temporary failure resolving 'deb.devuan.org'
Reading package lists... Done    
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.devuan.org/merged/dists/chimaera/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/chimaera-updates/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/chimaera-security/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/chimaera-backports/InRelease  Temporary failure resolving 'deb.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

A couple of things I did to try to diagnose the problem:

$ wget -c --user-agent="Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0" https://deb.devuan.org/merged
--2024-02-07 13:34:14--  https://deb.devuan.org/merged
Resolving deb.devuan.org (deb.devuan.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘deb.devuan.org’

$ nslookup deb.devuan.org
Server:		::1
Address:	::1#53

Non-authoritative answer:
Name:	deb.devuan.org
Address: 103.146.168.12
Name:	deb.devuan.org
Address: 95.216.15.86
Name:	deb.devuan.org
Address: 200.236.31.1
Name:	deb.devuan.org
Address: 46.4.50.2
Name:	deb.devuan.org
Address: 130.225.254.116
Name:	deb.devuan.org
Address: 141.84.43.19
Name:	deb.devuan.org
Address: 190.64.49.124
Name:	deb.devuan.org
Address: 160.16.137.156
Name:	deb.devuan.org
Address: 185.178.192.43
Name:	deb.devuan.org
Address: 158.69.153.121
Name:	deb.devuan.org
Address: 125.228.189.120
Name:	deb.devuan.org
Address: 89.174.102.150
Name:	deb.devuan.org
Address: 94.16.114.15
Name:	deb.devuan.org
Address: 185.236.240.103
Name:	deb.devuan.org
Address: 106.178.112.231
Name:	deb.devuan.org
Address: 172.234.26.53
Name:	deb.devuan.org
Address: 185.38.15.84
Name:	deb.devuan.org
Address: 185.183.113.131
Name:	deb.devuan.org
Address: 131.188.12.211
Name:	deb.devuan.org
Address: 147.78.194.22
Name:	deb.devuan.org
Address: 195.85.215.180
;; Truncated, retrying in TCP mode.
Name:	deb.devuan.org
Address: 2a0a:e5c0:10:3::6eeb
Name:	deb.devuan.org
Address: 2a01:9e40::180
Name:	deb.devuan.org
Address: 2407:b6c0::12
Name:	deb.devuan.org
Address: 2a01:4f9:2a:fa9::2
Name:	deb.devuan.org
Address: 2801:82:80ff:8000::2
Name:	deb.devuan.org
Address: 2a01:4f8:140:1102:2b76:955d:b48f:bdf3
Name:	deb.devuan.org
Address: 2001:878:346::116
Name:	deb.devuan.org
Address: 2001:4ca0:4300::1:19
Name:	deb.devuan.org
Address: 2800:a8:c001::a
Name:	deb.devuan.org
Address: 2001:e42:102:1704:160:16:137:156
Name:	deb.devuan.org
Address: 2607:5300:61:95f:7283:11d9:f86:e691
Name:	deb.devuan.org
Address: 2001:4190:801c:1::150
Name:	deb.devuan.org
Address: 2a03:4000:28:24c::
Name:	deb.devuan.org
Address: 2a0d:eb00:8006::acab
Name:	deb.devuan.org
Address: 240b:10:f00:1b00::240
Name:	deb.devuan.org
Address: 2a02:2a38:1:400:2a42:2a42:2a42:2a42

Those results are puzzling to me.

entropyagent · 2024-02-08 00:18:31

Not sure if my issue is anything like yours, but: My issue temporarely went away when I changed my /etc/resolv.conf nameserver line. It was pointing to my router/gateway, and I changed it to point directly to 9.9.9.9

Temporary "fix" because resolv.conf is regenerated upon reboot. Should probably dig a little deeper on that.

Longer story:

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver <ip address of router/gateway>

$ sudo apt update
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Ign:1 http://deb.devuan.org/merged daedalus InRelease
Ign:2 http://deb.devuan.org/merged daedalus-security InRelease
Ign:3 http://deb.devuan.org/merged daedalus-updates InRelease
Err:1 http://deb.devuan.org/merged daedalus InRelease
Temporary failure resolving 'deb.devuan.org'
Err:2 http://deb.devuan.org/merged daedalus-security InRelease
Temporary failure resolving 'deb.devuan.org'
Err:3 http://deb.devuan.org/merged daedalus-updates InRelease
Temporary failure resolving 'deb.devuan.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.devuan.org/merged/dists/daedalus/InRelease Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/daed … /InRelease Temporary failure resolving 'deb.devuan.org'
W: Failed to fetch http://deb.devuan.org/merged/dists/daed … /InRelease Temporary failure resolving 'deb.devuan.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
chip@brain:/etc$

If I change resolv.conf:

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 9.9.9.9
$ sudo apt update
Hit:1 http://deb.devuan.org/merged daedalus InRelease
Hit:2 http://deb.devuan.org/merged daedalus-security InRelease
Hit:3 http://deb.devuan.org/merged daedalus-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

Magic? Solar flares? Poor router config? (slightly more likely) But I have the idea that pointing at the router was working for a week or 2 since the Daedalus install.

fsmithred · 2024-02-08 02:01:49

To prevent network-manager from messing with your resolv.conf after you edit the file,

chattr +i /etc/resolv.conf

To undo that (in case you want to edit the file again) change the plus to minus.

aluma · 2024-02-08 09:13:18

Just from experience.
In the aria repository there is a mtr program that clearly shows problems with the network. This is what it looks like.

I had to send a similar picture to my provider when my entire network was working except Google.
Sometimes the packets were lost in one of the provider's intermediate nodes. I don’t know what they tweaked, but the problem disappeared.

 PING google.com (172.217.19.110) 56(84) bytes of data.
^C
--- google.com ping statistics ---
100 packets transmitted, 0 received, 100% packet loss, time 101381ms
PING time.in.ua (62.149.0.30) 56(84) bytes of data.
64 bytes from ntp.time.in.ua (62.149.0.30): icmp_seq=1 ttl=58 time=10.0 ms
64 bytes from ntp.time.in.ua (62.149.0.30): icmp_seq=2 ttl=58 time=9.70 ms
64 bytes from ntp.time.in.ua (62.149.0.30): icmp_seq=3 ttl=58 time=10.2 ms
^C
--- time.in.ua ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 9.707/10.005/10.266/0.257 ms

Last edited by aluma (2024-02-08 09:49:25)

swanson · 2024-02-08 09:49:36

Or you could use the file /etc/resolv.conf.tail , to add other DNS:s, which will stay put.

greenjeans · 2024-02-08 17:35:07

Got this same problem as of two days ago. Nothing else has changed in my system, will check on that resolv.conf.

aluma · 2024-02-08 17:53:37

It's literally now

  root@devuan:/# uname -srm
Linux 6.1.0-16-amd64 x86_64
root@devuan:/# date
Thu Feb  8 07:49:54 PM EET 2024
root@devuan:/# apt-get update
Hit:2 http://deb.devuan.org/merged daedalus InRelease
Get:3 http://deb.devuan.org/merged daedalus-updates InRelease [32.5 kB]
Hit:1 http://ftp.fau.de/trinity/deb/trinity-r14.1.x daedalus InRelease
Get:4 http://deb.devuan.org/merged daedalus-security InRelease [32.5 kB]
Fetched 65.0 kB in 4s (18.2 kB/s)
Reading package lists... Done
root@devuan:/#

rolfie · 2024-02-08 18:03:06

apt update/upgrade works for me on my main Daedalus system and on the two Excalibur VMs I tested yesterday.

aluma wrote:

Linux 6.1.0-16-amd64 x86_64

This is not the latest version, thats Linux 6.1.0-17-amd64 x86_64. Havent't you got linux-image-amd64 installed?

aluma · 2024-02-08 18:24:37

This is a computer for experiments.
In the synaptic settings, stable-update is selected, Linux 6.1.0-17-amd64 x86_64 in the stable-security repository.
Do you think this has anything to do with network problems?

P.S.OpenSuse Leap 15.5 is still on kernel 5... works without problems.

rolfie · 2024-02-08 18:38:25

I just noticed that the -16 kernel wasn't up to date. No relation to network issues.

Personally I don't use Synaptic for updating, I stick with the console and apt. This I am sure to receive all updates from all repos in the sources.list. You see where issues may arise if you don't include security updates?

Last edited by rolfie (2024-02-08 18:40:17)

aluma · 2024-02-08 18:48:32

@rolfie

You see where issues may arise if you don't include security updates?

Honestly, I have not encountered any problems with kernel security in my entire life with Linux (more than 20 years)

Yesterday in the next thread I talked about the successful update to Daedalus.
This is a working machine, where I compiled the kernel for my own hardware and without the support of apparmor, tomoe (from memory, not sure of the correct name), etc..

Regards.

Ron · 2024-02-08 23:49:31

Still having this issue more than 24 hours later. Why isn't there some kind of announcement from "those in the know" about what is going on, and when it is expected to be fixed? Some who posted here have had this issue for over 2 days now. It seems to me that the right thing to do is for somebody to make some kind of an announcement, at least something like "Hey, we know there's a problem, we're looking into it."

Last edited by Ron (2024-02-09 00:01:19)

GlennW · 2024-02-09 00:13:28

Hi, check your DNS is resolving...

I get no such errors when I check for updates each morning...

I'm using these now a days...

/etc/resolv.conf

# Generated by NetworkManager
search GamesBox.GlennsPref
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.0.1 #home router... optus australia dsl modem

I get some errors/warning messages from using my domain-name but it's not fatal.

I keep a copy backed up so I can change it when it gets over-written from updates, clean installs, etcetera.

All the best.

GlennW · 2024-02-09 00:18:41

p.ps. I'm using Daedalus, but I also keep Beowulf and Chimaera in my sources list for easy access, and backports.

root@GamesBox:/root  apt update && apt upgrade -y && apt autoremove -y
Hit:1 http://deb.devuan.org/merged daedalus InRelease                                                                                                      
Get:2 http://download.opensuse.org/repositories/hardware:/razer/Debian_12  InRelease [1,519 B]                                                             
Get:3 http://deb.devuan.org/merged daedalus-security InRelease [32.5 kB]                                                     
Get:4 http://download.opensuse.org/repositories/openSUSE:/Tools/Debian_12  InRelease [1,552 B]                   
Hit:5 https://dl.winehq.org/wine-builds/debian bookworm InRelease                                                 
Hit:6 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease              
Hit:7 http://deb.devuan.org/merged daedalus-updates InRelease
Hit:8 http://deb.devuan.org/merged daedalus-backports InRelease
Hit:9 http://deb.devuan.org/merged daedalus-proposed-updates InRelease
Hit:10 http://deb.devuan.org/merged chimaera InRelease
Hit:11 http://deb.devuan.org/merged chimaera-backports InRelease
Get:12 http://deb.devuan.org/merged chimaera-security InRelease [26.2 kB]
Hit:13 http://deb.devuan.org/merged beowulf InRelease
Get:14 http://deb.devuan.org/merged beowulf-security InRelease [26.1 kB]
Hit:15 http://deb.devuan.org/merged beowulf-backports InRelease
Get:16 http://deb.devuan.org/merged chimaera-security/main amd64 Packages [267 kB]
Get:17 http://deb.devuan.org/merged chimaera-security/main i386 Packages [266 kB]                                                                          
Fetched 621 kB in 7s (86.0 kB/s)                                                                                                                           
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@GamesBox:/root

Ron · 2024-02-09 01:13:50

Is the problem with the repos or local? If local, why are others having this problem also? I looked at /etc/resolv.conf but I don't know what it means.

Last edited by Ron (2024-02-09 01:22:08)

GlennW · 2024-02-09 01:51:51

Maybe that is your problem. Its a plain text file...

Try editing the file. I believe those addresses are cisco DNS routers. <edit>it's cloudfare not cisco, my bad! </edit>

you may have to stop and start the network services to get it to use the new addresses.

Some use google dns... like 8.8.8.8 but it may not be as private as you might expect.

Last edited by GlennW (2024-02-09 21:49:46)

pcalvert · 2024-02-09 02:05:04

I have Daedalus-based Refracta on an old laptop that I use infrequently. I ran apt update on it this morning and there were no problems. I wondered if maybe the problem had been fixed. I just tried doing the same on my Chimaera-based Refracta system, and it failed the same way as before.

GlennW · 2024-02-09 06:22:05

well, same here except I haven't knowingly used the refracta install method.

I just changed the battery in my 2013 laptop running Daedalus and got similar errors.

But the /etc/resolv.conf only had the modem local gateway listed, with nameserver home.

I changed it and set the attrib as Fred said above, but will check it out again tomorrow sometime.

The-Amnesiac-Philosopher · 2024-02-09 11:15:56

This seems to happen periodically with deb.devuan.org in the sources.list

I changed mine to one of the alternatives listed on this page...

http://pkgmaster.devuan.org/mirror_list.txt

Here is my sources.list...

deb http://dev.beard.ly/devuan/merged daedalus main non-free-firmware non-free contrib 

deb http://dev.beard.ly/devuan/merged daedalus-updates main non-free-firmware non-free contrib 

deb http://dev.beard.ly/devuan/merged daedalus-security main non-free-firmware non-free contrib 

deb http://dev.beard.ly/devuan/merged daedalus-backports main non-free-firmware non-free contrib

zephyr · 2024-02-09 12:23:28

The-Amnesiac-Philosophern wrote: This seems to happen periodically with deb.devuan.org in the sources.list

I too have been getting issues last few days with deb.devuan.org, using Crowz. After exhausting a lot of effort and time, I started looking elsewhere for the problem. I noticed my Devuan Xfce install had zero problems doing a full update.

I removed connman-gtk and installed network-manager & network-manager-gnome, and it works as it should.

cheers

zephyr

pcalvert · 2024-02-09 15:48:12

After my post last night, I realized that my Chimaera-based Refracta system uses connman, whereas my Daedalus-based Refracta system uses Network Manager. As an experiment, I installed network-manager-gnome and removed connman, connman-gtk, connman-ui, and connman-vpn. Now apt update works. However, I don't recommend using this solution on Chimaera because Network Manager isn't quite working right (which is probably why the system came with connman instead).

THE SOLUTION IN THIS POST IS DEPRECATED. Please go to https://dev1galaxy.org/viewtopic.php?pid=48040#p48040 for current working solution.

This is my original solution to this problem:

# cat /etc/hosts
127.0.0.1        refracta                localhost
::1              ip6-localhost ip6-loopback
fe00::0          ip6-localnet
fe00::0          ip6-mcastprefix
fe02::1          ip6-allnodes
fe02::1          ip6-allrouters

# U.S. Devuan mirror -  mirrors.hyperreal.coffee
172.234.26.53	deb.devuan.org

# Alternate U.S. Devuan mirror -  dev.beard.ly
#198.58.118.8	deb.devuan.org

As you can see, I added two mirrors to my hosts file. I could have just used one, but I wanted to have a backup mirror listed as well to make it easy to switch in the event that my primary mirror is ever offline for some reason. I obtained the IP addresses of those mirrors using nslookup. It's not a "perfect" solution, but it works.

The Devuan mirror list can be found here:
https://pkgmaster.devuan.org/mirror_list.txt

rolfie · 2024-02-09 15:55:33

Normally deb.devuan.org should do the job alright. This is no real mirror but a round robin that should pick the next or fasted server available. If the picked out server has a problem then deb.devuan.org doesn't work.

But these issues should only be present temporarily.

In any case, I haven't seen any issue here in Germany with deb.devuan.org in the last days.

aluma · 2024-02-09 16:44:02

I don't recommend using this solution on Chimaera because Network Manager isn't quite working right

Network Manager worked fine on two of my computers with different Wi-Fi cards running Chimaera.
And before that with Debian, starting with potato.
(The choice is determined by the DE Trinity applet for Network Manager)

P.S. I looked at the latest activity on github, connman -10 years ago, Network Manager - yesterday.

Last edited by aluma (2024-02-09 16:52:01)

The officially official Devuan Forum!

#1 2024-02-07 23:27:45

[SOLVED] Can't connect to repos

#2 2024-02-07 23:43:04

Re: [SOLVED] Can't connect to repos

#3 2024-02-07 23:58:39

Re: [SOLVED] Can't connect to repos

#4 2024-02-08 00:18:31

Re: [SOLVED] Can't connect to repos

#5 2024-02-08 02:01:49

Re: [SOLVED] Can't connect to repos

#6 2024-02-08 09:13:18

Re: [SOLVED] Can't connect to repos

#7 2024-02-08 09:49:36

Re: [SOLVED] Can't connect to repos

#8 2024-02-08 17:35:07

Re: [SOLVED] Can't connect to repos

#9 2024-02-08 17:53:37

Re: [SOLVED] Can't connect to repos

#10 2024-02-08 18:03:06

Re: [SOLVED] Can't connect to repos

#11 2024-02-08 18:24:37

Re: [SOLVED] Can't connect to repos

#12 2024-02-08 18:38:25

Re: [SOLVED] Can't connect to repos

#13 2024-02-08 18:48:32

Re: [SOLVED] Can't connect to repos

#14 2024-02-08 23:49:31

Re: [SOLVED] Can't connect to repos

#15 2024-02-09 00:13:28

Re: [SOLVED] Can't connect to repos

#16 2024-02-09 00:18:41

Re: [SOLVED] Can't connect to repos

#17 2024-02-09 01:13:50

Re: [SOLVED] Can't connect to repos

#18 2024-02-09 01:51:51

Re: [SOLVED] Can't connect to repos

#19 2024-02-09 02:05:04

Re: [SOLVED] Can't connect to repos

#20 2024-02-09 06:22:05

Re: [SOLVED] Can't connect to repos

#21 2024-02-09 11:15:56

Re: [SOLVED] Can't connect to repos

#22 2024-02-09 12:23:28

Re: [SOLVED] Can't connect to repos

#23 2024-02-09 15:48:12

Re: [SOLVED] Can't connect to repos

#24 2024-02-09 15:55:33

Re: [SOLVED] Can't connect to repos

#25 2024-02-09 16:44:02

Re: [SOLVED] Can't connect to repos

Board footer