openSUSE admin

pjessen wrote:

If this was specifically an issue with mirrorcache-eu.opensuse.org, it seems to have been resolved in the mean time.

The error message “Failed to connect to mirrorcache-eu.opensuse.org port 443 after 5 ms: No route to host” (from 2022-08-29 18:06) was an interesting example, wasn't it?
https://forums.opensuse.org/showthread.php/574427-Checking-routing-difficulties-for-download-opensuse-org?p=3153620#post3153620

From which information did you get the impression that a questionable software behaviour was adjusted?

Feel free to re-open, of course.

Are you going to perform this action for the following messages?

Sonne:~ # zypper dup
…
Retrieving package wine-debugsource-7.16-1483.2.x86_64                                                                              (16/84),   3.2 MiB ( 29.2 MiB unpacked)
Retrieving: wine-debugsource-7.16-1483.2.x86_64.rpm ................................................................................................................[error]
Download (curl) error for 'https://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Tumbleweed/x86_64/wine-debugsource-7.16-1483.2.x86_64.rpm':
Error code: Connection failed
Error message: Failed to connect to download.opensuse.org port 443 after 9 ms: No route to host

Abort, retry, ignore? [a/r/i/...? shows all options] (a): r
Retrieving: wine-debugsource-7.16-1483.2.x86_64.rpm .................................................................................................................[done]
…
Retrieving package giac-debugsource-1.7.0.43-11.57.x86_64                                                                           (18/84), 834.5 KiB (  5.7 MiB unpacked)
Retrieving: giac-debugsource-1.7.0.43-11.57.x86_64.rpm .............................................................................................................[error]
Download (curl) error for 'https://download.opensuse.org/repositories/science/openSUSE_Tumbleweed/x86_64/giac-debugsource-1.7.0.43-11.57.x86_64.rpm':
Error code: Connection failed
Error message: Failed to connect to download.opensuse.org port 443 after 5 ms: No route to host

Abort, retry, ignore? [a/r/i/...? shows all options] (a): r
Retrieving: giac-debugsource-1.7.0.43-11.57.x86_64.rpm ................................................................................................[done (176.0 KiB/s)]
…

Will further considerations become relevant for the affected network system configurations?

pjessen wrote:

The error message “Failed to connect to mirrorcache-eu.opensuse.org port 443 after 5 ms: No route to host” (from 2022-08-29 18:06) was an interesting example, wasn't it?

Yes, it was :-)

Thanks for your positive feedback.

From which information did you get the impression that a questionable software behaviour was adjusted?

I had no problem accessing https://mirrorcache-eu.opensuse.org with a browser or with wget.

This test can eventually be fine.

Unfortunately, I occasionally belong also to the group of users who are affected by undesirable software (and hardware) behaviour.

Download (curl) error for 'https://download.opensuse.org/repositories/science/openSUSE_Tumbleweed/x86_64/giac-debugsource-1.7.0.43-11.57.x86_64.rpm':
Error code: Connection failed
Error message: Failed to connect to download.opensuse.org port 443 after 5 ms: No route to host

I can't try it with zypper,

Would you dare to “provoke” the message “No route to host” more often also with this tool (or cURL)?

but it works with wget:

Are observed error statistics evolving?

Will further considerations become relevant for the affected network system configurations?

I have no idea what that means,

Can the failing components be precisely identified here?

but when zypper fails (as above),

The information “Abort, retry, ignore? [a/r/i/...? shows all options] (a): r … [done]” indicated that downloads were successfully performed for two software packages after a corresponding retry action.

could you try if it works with curl or wget?

This is possible (in principle) later again.

pjessen wrote:

I have no idea what that means, but when zypper fails (as above), could you try if it works with curl or wget?

Test command examples for further software development considerations:

Sonne:~ # zypper dist-upgrade
Retrieving repository 'Datenbanken' metadata .......................................................................................................................[error]
Repository 'Datenbanken' is invalid.
[Datenbanken|https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed] Valid metadata not found at specified URL
History:
 - Download (curl) error for 'https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/repodata/repomd.xml':
   Error code: Connection failed
   Error message: Failed to connect to download.opensuse.org port 443 after 7 ms: No route to host
 - Can't provide /repodata/repomd.xml

Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Datenbanken' because of the above error.
Problem retrieving files from 'HTTP-Dienste'.
Download (curl) error for 'https://download.opensuse.org/repositories/server:/http/openSUSE_Tumbleweed/repodata/repomd.xml':
Error code: Connection failed
Error message: Failed to connect to download.opensuse.org port 443 after 5 ms: No route to host

Please see the above error message for a hint.
Warning: Skipping repository 'HTTP-Dienste' because of the above error.
Problem retrieving files from 'Mozilla'.
Download (curl) error for 'https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/repodata/repomd.xml':
Error code: Connection failed
Error message: Failed to connect to download.opensuse.org port 443 after 5 ms: No route to host

Please see the above error message for a hint.
Warning: Skipping repository 'Mozilla' because of the above error.
…

Markus_Elfring@Sonne:~> curl -I https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/repodata/repomd.xml
HTTP/2 200 
last-modified: Wed, 31 Aug 2022 23:49:33 GMT
etag: "6b2-5e792260daabd"
accept-ranges: bytes
content-length: 1714
cache-control: must-revalidate
expires: Thu, 01 Sep 2022 16:42:35 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
content-security-policy: default-src 'none'; img-src 'self' https://static.opensuse.org; style-src 'self' https://static.opensuse.org; script-src 'self' https://static.opensuse.org 'unsafe-inline'
content-type: text/xml
date: Thu, 01 Sep 2022 16:42:35 GMT
server: Apache

Markus_Elfring@Sonne:~> curl -I https://download.opensuse.org/repositories/server:/http/openSUSE_Tumbleweed/repodata/repomd.xml
HTTP/2 200 
last-modified: Tue, 30 Aug 2022 13:11:13 GMT
etag: "6ac-5e7751d6243a0"
accept-ranges: bytes
content-length: 1708
cache-control: must-revalidate
expires: Thu, 01 Sep 2022 16:43:35 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
content-security-policy: default-src 'none'; img-src 'self' https://static.opensuse.org; style-src 'self' https://static.opensuse.org; script-src 'self' https://static.opensuse.org 'unsafe-inline'
content-type: text/xml
date: Thu, 01 Sep 2022 16:43:35 GMT
server: Apache

Markus_Elfring@Sonne:~> curl -I https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/repodata/repomd.xml
HTTP/2 200 
last-modified: Thu, 01 Sep 2022 09:17:36 GMT
etag: "6a7-5e79a158e4c09"
accept-ranges: bytes
content-length: 1703
cache-control: must-revalidate
expires: Thu, 01 Sep 2022 16:44:20 GMT
vary: Accept-Encoding
x-content-type-options: nosniff
content-security-policy: default-src 'none'; img-src 'self' https://static.opensuse.org; style-src 'self' https://static.opensuse.org; script-src 'self' https://static.opensuse.org 'unsafe-inline'
content-type: text/xml
date: Thu, 01 Sep 2022 16:44:20 GMT
server: Apache

Markus_Elfring@Sonne:/tmp> LANG=C wget https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/repodata/repomd.xml https://download.opensuse.org/repositories/server:/http/openSUSE_Tumbleweed/repodata/repomd.xml https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/repodata/repomd.xml
--2022-09-01 18:54:20--  https://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/repodata/repomd.xml
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1714 (1.7K) [text/xml]
Saving to: 'repomd.xml.1'

repomd.xml.1                                    100%[====================================================================================================>]   1.67K  --.-KB/s    in 0s      

2022-09-01 18:54:20 (1017 MB/s) - 'repomd.xml.1' saved [1714/1714]

--2022-09-01 18:54:21--  https://download.opensuse.org/repositories/server:/http/openSUSE_Tumbleweed/repodata/repomd.xml
Reusing existing connection to download.opensuse.org:443.
HTTP request sent, awaiting response... 200 OK
Length: 1708 (1.7K) [text/xml]
Saving to: 'repomd.xml.2'

repomd.xml.2                                    100%[====================================================================================================>]   1.67K  --.-KB/s    in 0s      

2022-09-01 18:54:21 (1.07 GB/s) - 'repomd.xml.2' saved [1708/1708]

--2022-09-01 18:54:21--  https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/repodata/repomd.xml
Reusing existing connection to download.opensuse.org:443.
HTTP request sent, awaiting response... 200 OK
Length: 1703 (1.7K) [text/xml]
Saving to: 'repomd.xml.3'

repomd.xml.3                                    100%[====================================================================================================>]   1.66K  --.-KB/s    in 0s      

2022-09-01 18:54:21 (1.07 GB/s) - 'repomd.xml.3' saved [1703/1703]

FINISHED --2022-09-01 18:54:21--
Total wall clock time: 0.3s
Downloaded: 3 files, 5.0K in 0s (1.04 GB/s)

pjessen wrote:

OTOH, I don't see any redirects to mirrorcache, which is a bit odd.

The applied data distribution technology is evolving, isn't it?

pjessen wrote:

elfring - does the problem persist?

Yes.

I have got the following notification after a login to my KDE Plasma session which happened also because of another restart of this computer after the distribution upgrade that became special yesterday.
https://news.opensuse.org/2022/09/02/tw-continues-release-streak/

“
Fehler beim Aktualisieren
Download (curl) error for 'https://download.opensuse.org/repositories/games/openSUSE_Tumbleweed/repodata/d63a59e6986e7b2b7b1c9927ad094f140a61ec2713a440ffcf880029aa016c6e-primary.xml.gz':
Error code: Connection failed
Error message: Failed to connect to mirrorcache-eu.opensuse.org port 443 after 10 ms: No route to host
”

Involved components:

• zypper 1.14.55-1.3
• curl 7.84.0-1.2

I came along messages which will trigger further development considerations.

• Issues with openSUSE Repos https://progress.opensuse.org/issues/104193#note-16
• Curl error 16 (CURLE_HTTP2) https://github.com/openSUSE/zypper/issues/399
• update curl error 16 https://forums.opensuse.org/showthread.php/564178-update-curl-error-16
• Fixing data processing because of reported error “CURLE_HTTP2_STREAM (92)” https://github.com/openSUSE/zypper/issues/457

pjessen wrote:

does the problem persist?

Which availability (or reachability) probability would the system administrators like to achieve for the known download services?

elfring wrote:

pjessen wrote:

does the problem persist?

Which availability (or reachability) probability would the system administrators like to achieve for the known download services?

For download.opensuse.org, allowing some time for maintenance, the objective is probably 99%, 24/7/365.

pjessen wrote:

For download.opensuse.org, allowing some time for maintenance, the objective is probably 99%, 24/7/365.

Does this desire for such a high service quality require a special system infrastructure?

Were any more details be published for the running system?
https://en.opensuse.org/openSUSE:Mirror_infrastructure

elfring wrote:

pjessen wrote:

For download.opensuse.org, allowing some time for maintenance, the objective is probably 99%, 24/7/365.

Does this desire for such a high service quality require a special system infrastructure?

Not really, it primarily means the relevant parts (mirrors, powersupplies, fans, disks, switches, routers etc) all need to be redundant, and otherwise just reduce the amount of change of the system.

Were any more details be published for the running system?

Not that I am aware of, it is not of much interest to the general public.

https://en.opensuse.org/openSUSE:Mirror_infrastructure

That is only about the mirror side of the setup.

pjessen wrote:

Does this desire for such a high service quality require a special system infrastructure?

Not really, it primarily means the relevant parts (…) all need to be redundant,

Can the resource management become more interesting accordingly?

and otherwise just reduce the amount of change of the system.

Can such information indicate a target conflict for involved (software) components?

Were any more details be published for the running system?

Not that I am aware of,

Will any documentation extensions become more helpful for the clarification of discussed issues?

it is not of much interest to the general public.

May any more design decisions be shared?

https://en.opensuse.org/openSUSE:Mirror_infrastructure

That is only about the mirror side of the setup.

Will additional explanations become relevant for the desired high-availability?

Are any monitoring tools applied which would automatically report missing hosts and corresponding ports?

elfring wrote:

pjessen wrote:

Does this desire for such a high service quality require a special system infrastructure?

Not really, it primarily means the relevant parts (…) all need to be redundant,

Can the resource management become more interesting accordingly?

If I could understand the question, I might be able to provide a sane answer :-)

This is really not the place for a general discussion, it is a ticketing system.

For a continued discussion, I advise you to consult the heroes or the mirrors mailing lists.

Why do I get the feeling I am taking part in a Turing test?

and otherwise just reduce the amount of change of the system.

Can such information indicate a target conflict for involved (software) components?

Yes.

Were any more details be published for the running system?

Not that I am aware of,

Will any documentation extensions become more helpful for the clarification of discussed issues?

What is a "documentation extension" ?

it is not of much interest to the general public.

May any more design decisions be shared?

No.

https://en.opensuse.org/openSUSE:Mirror_infrastructure

That is only about the mirror side of the setup.

Will additional explanations become relevant for the desired high-availability?

No.

Are any monitoring tools applied which would automatically report missing hosts and corresponding ports?

Yes.

pjessen wrote:

What is a "documentation extension" ?

I interpreted one part of your feedback in the way that a linked information source was limited.
Thus I have tried to find out if further background information can be determined for this issue.

Are any monitoring tools applied which would automatically report missing hosts and corresponding ports?

Yes.

• Would you like to share corresponding names?
• Did any of these tools provide notifications which correlate to the error messages that I presented here?
• Should any other constraints be taken better into account according to (temporary) network connection problems?

elfring wrote:

pjessen wrote:

What is a "documentation extension" ?

I interpreted one part of your feedback in the way that a linked information source was limited.
Thus I have tried to find out if further background information can be determined for this issue.

Please just answer my question.

Are any monitoring tools applied which would automatically report missing hosts and corresponding ports?

Yes.

• Would you like to share corresponding names?

No.

• Did any of these tools provide notifications which correlate to the error messages that I presented here?

No.

• Should any other constraints be taken better into account according to (temporary) network connection problems?

No.

pjessen wrote:

What is a "documentation extension" ?

I interpreted one part of your feedback in the way that a linked information source was limited.
Thus I have tried to find out if further background information can be determined for this issue.

Please just answer my question.

Limited (or incomplete) documentation can eventually be extended after another bit of information collection, can't it?

elfring wrote:

pjessen wrote:

What is a "documentation extension" ?

I interpreted one part of your feedback in the way that a linked information source was limited.
Thus I have tried to find out if further background information can be determined for this issue.

Please just answer my question.

Limited (or incomplete) documentation can eventually be extended after another bit of information collection, can't it?

Please just answer my question.

We made some changes on our side and it shouldn't redirect to mirrorcache-eu.opensuse.org anymore.

I would appreciate further explanations for related software adjustments.

Are there any issues observed still?

I guess that the attention will grow again if the next mass software update will be published.

Further possible improvements are in waiting queues for remaining open issues, aren't they?

See also:
Feedback by Michael Andres
https://github.com/openSUSE/zypper/issues/457#issuecomment-1587630590

elfring wrote:

We made some changes on our side and it shouldn't redirect to mirrorcache-eu.opensuse.org anymore.

I would appreciate further explanations for related software adjustments.

Could you elaborate what exact assistance is required?
From my understanding zypper occasionally couldn't access mirrorcache-eu.opensuse.org and download.opensuse.org from your machine with error message 'No route to host'.

Usually it is related to your network or ISP, at least I haven't seen this reported much from others.

Did you try to leave the ping command running for whole period while zypper is running?

Are there any issues observed still?

I guess that the attention will grow again if the next mass software update will be published.

There were few mass updates recent year - they might reveal some problems - but I don't think 'No route to host' is something which was mentioned.

Further possible improvements are in waiting queues for remaining open issues, aren't they?

Not sure what can be done about that in this ticket though.

See also:
Feedback by Michael Andres
https://github.com/openSUSE/zypper/issues/457#issuecomment-1587630590

That comment is related to handling of HTTP/2 only. At least error 'No route to host' is not related there.

Regards,
Andrii Nikitin

Could you elaborate what exact assistance is required?

I hope that some of the available network monitoring tools can become more helpful also for reported connection difficulties.

Did you try to leave the ping command running for whole period while zypper is running?

No.

I occasionally tried related programs for a while.

Not sure what can be done about that in this ticket though.

• Would you like to influence affected software components any more?
• Can error reporting approaches be still improved?

Feedback by Michael Andres
https://github.com/openSUSE/zypper/issues/457#issuecomment-1587630590

That comment is related to handling of HTTP/2 only. At least error 'No route to host' is not related there.

It was indicated that some components can be adjusted further.
How will network parts evolve accordingly?