can't update

[dxb04]

have you tried adding some public DNS resolves to see if the one your host gave you has issues? You can try adding Google (8.8.4.4 and 8.8.8.8) or CloudFlare (1.1.1.1 and 1.0.0.1). /etc/resolv.conf is processed top do, so you'd want to add this to the top of the list.

I tried google dns

this was the result :

[[email protected] ~]# yum clean all
Loaded plugins: fastestmirror, universal-hooks
Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins base epel extras mysql-connectors-community mysql-tools-community mysql57-community updates
Cleaning up list of fastest mirrors
[[email protected] ~]# yum makecache
Loaded plugins: fastestmirror, universal-hooks
Determining fastest mirrors
epel/x86_64/metalink | 28 kB 00:00:00
* EA4: 178.18.193.52
* cpanel-addons-production-feed: 178.18.193.52
* cpanel-plugins: 178.18.193.52
* base: de.mirrors.clouvider.net
* epel: www.nic.funet.fi
* extras: mirror.checkdomain.de
* updates: mirror.netcologne.de
EA4 | 2.9 kB 00:00:00
cpanel-addons-production-feed | 2.9 kB 00:00:00
cpanel-plugins | 2.9 kB 00:00:00
base | 3.6 kB 00:00:00
epel | 4.7 kB 00:00:00
extras | 2.9 kB 00:00:00
http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



One of the configured repositories failed (MySQL Connectors Community),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=mysql-connectors-community ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable mysql-connectors-community
or
subscription-manager repos --disable=mysql-connectors-community

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=mysql-connectors-community.skip_if_unavailable=true

failure: repodata/repomd.xml from mysql-connectors-community: [Errno 256] No more mirrors to try.
http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[[email protected] ~]# yum update
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 28 kB 00:00:00
* EA4: 178.18.193.52
* cpanel-addons-production-feed: 178.18.193.52
* cpanel-plugins: 178.18.193.52
* base: de.mirrors.clouvider.net
* epel: www.nic.funet.fi
* extras: centos.schlundtech.de
* updates: mirror.netcologne.de
EA4 | 2.9 kB 00:00:00
cpanel-addons-production-feed | 2.9 kB 00:00:00
cpanel-plugins | 2.9 kB 00:00:00
base | 3.6 kB 00:00:00
extras | 2.9 kB 00:00:00
http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



One of the configured repositories failed (MySQL Connectors Community),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=mysql-connectors-community ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable mysql-connectors-community
or
subscription-manager repos --disable=mysql-connectors-community

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=mysql-connectors-community.skip_if_unavailable=true

failure: repodata/repomd.xml from mysql-connectors-community: [Errno 256] No more mirrors to try.
http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found



And CloudFlare shows the same ..

 

[ffeingol]

As a total guess, are there any entries in /etc /hosts for repo.mysql.com?

 

[dxb04]

As a total guess, are there any entries in /etc /hosts for repo.mysql.com?

Yes , there is ..
i found 2 extra lines


168.119.126.94 repo.mysql.com yum.mariadb.org
104.21.90.187 data.easyconfig.net easyconfig.net


 

[ffeingol]

And there is your issue. The hosts file is overriding DNS for repo.mysql.com and yum.mariiadb.org. You'll have to ask your hosting provider why they are doing that, as that IP is obviously not providing a valid repo any longer. Short term you can try commenting out the first line (add a # in the 1st position of the 168.119.126.94 line) and see if that resolves the issue.

 

[dxb04]

And there is your issue. The hosts file is overriding DNS for repo.mysql.com and yum.mariiadb.org. You'll have to ask your hosting provider why they are doing that, as that IP is obviously not providing a valid repo any longer. Short term you can try commenting out the first line (add a # in the 1st position of the 168.119.126.94 line) and see if that resolves the issue.

It works now

i run all of the commands

yum clean all
yum makecache
yum update

 

[cPRex]

Excellent idea, @ffeingol !!!!

 

[dxb04]

Hello everyone ,
I would like to thank you all :
ffeingol
cPRex
ffeingol

For helping me figuring the problem which i face for months .
Now almost every thing is working fine

Thank you

 

[dxb04]

One more thing ,

At WHM : Home /DNS Functions /DNS Zone Manager

I found a record of ( my-server-ip.cprapid.com )

Is it normal to be there ?!

 

[cPRex]

Yes, that record is normal. That is the placeholder domain that gets created when cPanel is first installed on your machine so you can still access WHM with a secure certificate. It gets overridden when you setup the server's hostname.

 

[dxb04]

Yes, that record is normal. That is the placeholder domain that gets created when cPanel is first installed on your machine so you can still access WHM with a secure certificate. It gets overridden when you setup the server's hostname.

So it is ok to be there at DNZ ZONE ?

I noticed that i am receiving emails titled : The service “imap” appears to be down.

Then after few minutes i receive other email titled : The service “imap” is now operational.

* Is it a normal email notification from the server , or it has other meaning ?

 

[cPRex]

Yes, it's fine that DNS zone exists, but it would also be fine if you wanted to remove it as long as you have a proper hostname configured.

As for the IMAP issue, it depends how often you receive that notification. If it's just once, I wouldn't worry about it as it could be part of the server's update process. If it is happening more frequently, there is likely some investigation that needs to happen.

 

[dxb04]

Yes, it's fine that DNS zone exists, but it would also be fine if you wanted to remove it as long as you have a proper hostname configured.

As for the IMAP issue, it depends how often you receive that notification. If it's just once, I wouldn't worry about it as it could be part of the server's update process. If it is happening more frequently, there is likely some investigation that needs to happen.

well , sometimes i don't receive in hours , sometimes every few minutes ..

 

[cPRex]

Do you normally have a lot of email traffic on the server? If so, I'm wondering if you're hitting some IMAP limits and the system isn't able to properly monitor the service.

If you don't have a lot of email traffic on the machine, it could be there is an attack against the email services on the system. Do you have cPHulk enabled on the machine?

 

[dxb04]

Do you normally have a lot of email traffic on the server? If so, I'm wondering if you're hitting some IMAP limits and the system isn't able to properly monitor the service.

If you don't have a lot of email traffic on the machine, it could be there is an attack against the email services on the system. Do you have cPHulk enabled on the machine?

Actually no ..

cPHulk is enabled already ..

 

[dxb04]

Actually no ..

cPHulk is enabled already ..

Looks like there is lot of email notifications i am receiving .
more than 40 notifications in less than 8 hours ..
is it normal ?!

If it is an email attack , how i can stop it ?

 

[cPRex]

The first thing you'd want to do is to confirm it is actually an attack against the mailserver. Do you see a lot of failed login in the /var/log/maillog file?

 

[dxb04]

The first thing you'd want to do is to confirm it is actually an attack against the mailserver. Do you see a lot of failed login in the /var/log/maillog file?

What i can see " if i am reading the file well " , there is lot of data lines for today's date !

Looks like :


spamd[8997]: spamd: connection from localhost [127.0.0.1]:35388 to port 783, fd 5
dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<H9K4Vqj2hoV/AAAB>dovecot: lmtp(10104): Connect from local
dovecot: lmtp(10104): Connect from local
dovecot: lmtp(10104): Disconnect from local: Logged out (state=GREETING)
dovecot: imap-login: Login: user=<__cpanel__service__auth__imap__0wt0iczlmwt5lirg>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=10114, secured, session=<5cy8Vqj2xr5/AAAB>



 

[ffeingol]

I'm 99% sure that one is just the WHM process to see that IMAP is working (and it will restart it if it's not). It's from 127.0.0.1 to 127.0.0.1 (localhost).

 

[cPRex]

Correct - since that is from localhost, it is just the monitoring tool.

@dxb04 - at this point, it would be best to submit a ticket to our team so we can take a look.

 

[dxb04]

Correct - since that is from localhost, it is just the monitoring tool.

@dxb04 - at this point, it would be best to submit a ticket to our team so we can take a look.

I'm 99% sure that one is just the WHM process to see that IMAP is working (and it will restart it if it's not). It's from 127.0.0.1 to 127.0.0.1 (localhost).

Thank you for the reply ..

I prefer to learn myself , to be able to solve any issues in future

by the way , currently i didn't noticed that i am receiving any emails , i don't know if it is normal or it's being redirect to junk mail .. not sure !

Moreover ,
There is a warning email i am receiving , it is about " Disk Usage "



The filesystem “/boot” mounted at “/boot” reached “warn” status because you currently use 92.17% of its available blocks.



I think there is files need to be removed ..