Unable to update system

Distro Discussion & Help
1

We have a lot of Servers running Freepbx 16.0.40.11 and we are unable to update with system update for about 2 weeks… the error is : Unable to run ‘yum check-updates’, can’t check for updates

if I try to run this command via SSH…
there is the error…
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
http://sng7.com/os/7.8/os/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - “Failed to connect to 2606:4700:130:436c:6f75:6466:6c61:7265: Network is unreachable”
Trying other mirror.

Is there something wrong with the update server ?
Thank you

2

It’s odd, looks like it’s trying to connect to an ipv6 ip.
Can you ping sng7.com from the cli and see if it resolves correctly?

3

When I worked at Sangoma years ago they had no external IPv6 addresses and there was no planned compatibility. You will probably need to enable ipv4 or use a 6to4 proxy… That said I do believe they moved their infrastructure behind cloudflare and that should ™ handle this

1 Like
4

Thank you all for your responses.
here’s what the ping on the cli does…
ping sng7 .com
PING sng7 . com (172.64.80.1) 56(84) bytes of data.
and it doesn’t ping at all… ???

5

Your Ping command is wrong…
Try

$ ping sng7.com
PING sng7.com (172.67.205.241): 56 data bytes
64 bytes from 172.67.205.241: icmp_seq=0 ttl=60 time=10.820 ms
64 bytes from 172.67.205.241: icmp_seq=1 ttl=60 time=7.754 ms
^C
--- sng7.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 7.754/9.287/10.820/1.533 ms

And check dig command…

$ dig sng7.com
; <<>> DiG 9.10.6 <<>> sng7.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40282
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;sng7.com.			IN	A

;; ANSWER SECTION:
sng7.com.		188	IN	A	104.21.22.170
sng7.com.		188	IN	A	172.67.205.241

;; Query time: 5 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Fri Feb 07 12:42:08 GMT 2025
;; MSG SIZE  rcvd: 69
7

and the dig result:

image
image1058×638 20.8 KB

8

heres the ping command result:

image
image838×119 4.08 KB

9

Thanks fro sharing Tom, I think if i enable IPv6 from router will get same result as yours.
But for now selected to be disable. ( personal choose )

10

Do you have any Ping restrictions for Outbound ? what about,
ping 8.8.8.8
and
ping google.com

11

@Carl55 go ahead and open a case in https://help.sangoma.com/community/s/create-a-support-ticket

Give me the case number and I will work with you on that.

13

The ip it’s resolving it’s from Cloudflare, you can try to do the following @Carl55

nano /etc/hosts
Add this line: 172.67.205.241 sng7.com
Retry

15

I am not sure if Sangoma is using (or was) that ip for any service, I can ask to the IT guys, not sure why the system would be resolving that ip though.

That’s why I offer to work with him on a case.
He is not using a “known” dns server, it could be something in his dns resolving that ip (not sure why)

Can you try to use dig but with 8.8.8.8 ?

dig @8.8.8.8 sng7.com A

16

it work !!!
thank you !

17

So probably something is wrong on your DNS, just as a test, can you please run this command?

dig @8.8.8.8 sng7.com A

19

Yeah, so the dig screenshot he shared was using this ip as the resolver: 10.80.0.30 (probably his router, but i have no idea which dns is being used from there)

The /etc/hosts it’s just a workaround
Probably the best idea is to configure /etc/resolv.conf and remove 10.80.0.30 as their DNS and use a public dns server instead (unless they are forcing in their router to use a specific dns)

20

I never liked to edit relolve.conf or hosts,. For me this is not a fix the core DNS issue just hiding or walk around ( temporarily fix. ) Tomorrow gonna have for another issue for DNS…