• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

MariaDB 10.2 Repo/Mirror unreachable

Dukemaster

Dukemaster

Regular Pleskian
TITLE:
MariaDB 10.2 Repo/Mirror unreachable​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx v17.8.11_build1708180613.11 os_Ubuntu 18.04.1 LTS #38 64bit​
PROBLEM DESCRIPTION:
Since yesterday mirror http://mirror.host.ag/mariadb/repo/10.2/ubuntu/dists/bionic/InRelease is not reachable. All other updates running like usual.
Any ideas or suggestions?

root@server:~# aptitude clean
root@server:~# aptitude update
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-updates InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-backports InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-security InRelease
Hit http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 bionic InRelease
Hit http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all InRelease
Hit http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP70_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP71_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP72_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP73_17 bionic InRelease
Err http://mirror.host.ag/mariadb/repo/10.2/ubuntu bionic InRelease
Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Failed to fetch http://mirror.host.ag/mariadb/repo/10.2/ubuntu/dists/bionic/InRelease: Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
Click to expand...
STEPS TO REPRODUCE:
# aptitude clean
# aptitude update
or
# apt-get clean
# apt-get update​
ACTUAL RESULT:
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-updates InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-backports InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-security InRelease
Hit http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 bionic InRelease
Hit http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all InRelease
Hit http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP70_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP71_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP72_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP73_17 bionic InRelease
Err http://mirror.host.ag/mariadb/repo/10.2/ubuntu bionic InRelease
Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Failed to fetch http://mirror.host.ag/mariadb/repo/10.2/ubuntu/dists/bionic/InRelease: Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.​
EXPECTED RESULT:
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Dukemaster said:
TITLE:
MariaDB 10.2 Repo/Mirror unreachable​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx v17.8.11_build1708180613.11 os_Ubuntu 18.04.1 LTS #38 64bit​
PROBLEM DESCRIPTION:
Since yesterday mirror http://mirror.host.ag/mariadb/repo/10.2/ubuntu/dists/bionic/InRelease is not reachable. All other updates running like usual.
Any ideas or suggestions?

​
STEPS TO REPRODUCE:
# aptitude clean
# aptitude update
or
# apt-get clean
# apt-get update​
ACTUAL RESULT:
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-updates InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-backports InRelease
Hit Index of /linux/distributions/ubuntu/ubuntu/ bionic-security InRelease
Hit http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 bionic InRelease
Hit http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12 all InRelease
Hit http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP70_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP71_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP72_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP73_17 bionic InRelease
Err http://mirror.host.ag/mariadb/repo/10.2/ubuntu bionic InRelease
Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Failed to fetch http://mirror.host.ag/mariadb/repo/10.2/ubuntu/dists/bionic/InRelease: Could not connect to mirror.host.ag:80 (2a07:5741:0:501::1). - connect (113: No route to host) Could not connect to mirror.host.ag:80 (5.104.175.130), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.​
EXPECTED RESULT:
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
Click to expand...

Hello @Dukemaster,
I suppose you have installed MariaDB 10.2 manually ? (because by default MariaDB 10.1 is installed from distro repositories on Ubuntu 18.04).
If yes you just have to use another mirror by updating /etc/apt/sources.list.d/mariadb.list
 
Yes I updated MariaDB manually, but already two months ago. By updating (like a charm) the new repos were implemented automatically by update procedure.
I look every day for updates and it worked successfully since last October.
So, it seems that perhaps something was changed by another update, or blocked or the most relevant reason in my opinon is that the URL was changed by host.ag itself (the provider of the mirror).

Since today morning I have another problem with pum. Got this mail today morning:
Hello Administrator, there are problems on your server server.domain.com. Please fix it manually.

Reason: 2019-02-02 06:25:34 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-02-02 06:26:06 ERROR:
2019-02-02 06:26:06 ERROR: Exited with returncode 1.
Click to expand...
**** Last night I updated Ubuntu operation system ****
I know it's another thread and question, but do you know how to fix the last one?

In 5 days I want to make the Ubuntu release upgrade 18.04.2
 
Last edited:
Dukemaster said:
Yes I updated MariaDB manually, but already two months ago. By updating (like a charm) the new repos were implemented automatically by update procedure.
I look every day for updates and it worked successfully since last October.
So, it seems that perhaps something was changed by another update, or blocked or the most relevant reason in my opinon is that the URL was changed by host.ag itself (the provider of the mirror).

Since today morning I have another problem with pum. Got this mail today morning:

**** Last night I updated Ubuntu operation system ****
I know it's another thread and question, but do you know how to fix the last one?

In 5 days I will make the Ubuntu release upgrade to 18.04.2
Click to expand...

There are always some MariaDB mirrors down or sometimes definitly closed. You can try to choose a mirror from a big/trusted hosting provider to avoid this issue.

The error message your have received is due to mariadb upgrade failure :
[HUB] Plesk Update Manager (PUM) fails: pum is called with arguments
 
Thank you very much @virtubox.
Problem is,my server is hosted by a big provider (Ionos, former 1and1). They maintain the mirrors pretty competent. I've never had such a problem in 13 years now. Perhaps I asked too early for help. Tomorrow I'll phone the support of Ionos. It's also possible in the night, but I'm tired now and want to go to bed.
Thanks for the link, too, but I already got it and the provided help is the normal way. Only 1and1 can help now to change the mirror.
Good to know the problem of MariaDB, I use it only few months for the first time in my life. Before only raw MySQL. So MariaDB is a new chapter.
Lots of greets
 
Last edited:
Today time was over, didn't want to wait longer for provider or someone else to change the mirror. Therefor I watched the MariaDB support site and choose the Hosteurope mirror. Also searched for the old existing one - mirror.host.ag - which is located in Sofia, Bulgaria, nice capital city of Bulgaria.
Wonder why they didn't installed a mirror closer to my server location. Doesn't matter.
I thought about the idea to choose the mirror from Novosibirsk, where PLESK is at home. :cool:
Here is the MariaDB mirror list, sortable by Distro, Release and Version. Pretty useful.
 
Last edited:
Dukemaster said:
Today time was over, didn't want to wait longer for provider or someone else to change the mirror. Therefor I watched the MariaDB support site and choose the Hosteurope mirror. Also searched for the old existing one - mirror.host.ag - which is located in Sofia, Bulgaria, nice capital city of Bulgaria.
Wonder why they didn't installed a mirror closer to my server location. Doesn't matter.
I thought about the idea to choose the mirror from Novosibirsk, where PLESK is at home. :cool:
Here is the MariaDB mirror list, sortable by Distro, Release and Version. Pretty useful.
Click to expand...

Hello @Dukemaster,
The easiest to add MariaDB repository is to use the repo_setup_script provided by MariaDB :
Code: 
 # replace 10.x with the release you want to install (eg . 10.1, 10.2, 10.3)
bash <(wget -qO - https://downloads.mariadb.com/MariaDB/mariadb_repo_setup) \
--mariadb-server-version=10.x \
--skip-maxscale -y
 
This is really a good advice. Perhaps I'll use it.
Usually I only upgrade when it's provided by Plesk.
 
You must log in or register to reply here.

Similar threads

brainforge
Resolved System updates have started failing.
Replies
2
Views
2K
brainforge
brainforge
I
Issue maria DB update plesk 18.0.50
Replies
10
Views
4K
Maarten
M
S
Issue Installing extensions
Replies
3
Views
1K
IgorG
IgorG
R
Resolved Please, please, could help me to fix this issue?
Replies
2
Views
2K
romulojose
R
F
Resolved update failed GPG error
Replies
2
Views
2K
fgavois
F
Back
Top