can't update
Hello ,
I was trying to make few updates to my server ..
I tried to make " system update ", but there was an error
Also i tried to enter Multi PHP section, it shows an error popup ..
Trying to install php fpm .. it keep loading but nothing happen .. at the same time it shows : Warning: You cannot set the system default to use PHP-FPM. You do not have the PHP-FPM package for your system"s default PHP version installed. I don't know what is the exact issue and how to solve it properly .. Any one can guide me in steps please Thank you
System update process has started.
"yum" reported error code "1" when it ended: w/ yum -y
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 185.15.22.168
* cpanel-addons-production-feed: 185.15.22.168
* cpanel-plugins: 185.15.22.168
* base: mirrors.xtom.de
* epel: www.nic.funet.fi
* extras: mirrors.xtom.de
* updates: mirror.23m.com
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
Often errors like this can be resolved by running `yum makecache`
System update process has finished.
Also i tried to enter Multi PHP section, it shows an error popup ..
Error: "/usr/local/cpanel/bin/python-packman" reported error code "1" when it ended: Traceback (most recent call last): File "/usr/local/cpanel/bin/packman_get_list_json", line 15, in packman.init_yum() File "/usr/local/cpanel/bin/packman_lib/yum_impl.py", line 77, in init_yum yb.repos.populateSack() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 347, in populateSack self.doSetup() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1482, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1259, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1042, in _getFile raise e yum.Errors.NoMoreMirrorsRepoError: 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 w/ /usr/local/cpanel/bin/packman_get_list_json installed Often errors like this can be resolved by running `yum makecache` Trying to install php fpm .. it keep loading but nothing happen .. at the same time it shows : Warning: You cannot set the system default to use PHP-FPM. You do not have the PHP-FPM package for your system"s default PHP version installed. I don't know what is the exact issue and how to solve it properly .. Any one can guide me in steps please Thank you
-
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 ..0 -
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? 0 -
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 ..0 -
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 ?0 -
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? 0 -
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=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>0 -
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). 0 -
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. 0 -
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 ..0 -
How big is the /boot partition? You can get that from SSH by doing the following: cd /boot df -h . The only things that are in the /boot partition are the parts of the kernel needed to boot. If it's filling up, then the only thing you can really do is to tell yum/dnf/apt to save less kernel versions. From memory CentOS based systems will save 5 kernels. 0 -
How big is the /boot partition? You can get that from SSH by doing the following: cd /boot df -h . The only things that are in the /boot partition are the parts of the kernel needed to boot. If it's filling up, then the only thing you can really do is to tell yum/dnf/apt to save less kernel versions. From memory CentOS based systems will save 5 kernels.
Filesystem Size Used Avail Use% Mounted on /dev/md1 487M 424M 39M 92% /boot
It is almost full How can i adjust ? I found this too :The filesystem "/" mounted at "/" reached "warn" status because you currently use 87.1% of its available blocks.
Used:357.83 GB Available:56.27 GB Total:436.34 GB Is it related to files saved on the drive or it could be something else ?!0 -
The only thing you can do to free up space in /boot is to remove kernels. You can figure out how may you have by simply listing the files and counting the number of vmlinuz* files there. A 487 MB boot partition is really small. In /etc/yum.conf you can set "installonly_limit=#" (where # is a number) and that will limit you to only # kernels and any more than that will be removed when a new one is installed. You need at least 2, so you can go back to an older kernel if you have issues. You can also use "package-cleanup --oldkernels --count=#" to manually reduce the number of kernels to #. You'll want to search/read up on "limit number of kernels CentOS" or something like that to get more details etc. The root partition ("/") is where everything else is stored. The rest of the OS, all your sites/email, MySQL is stored there. Unless you have very large error_log files the only way to clean up space to to reduce the account usage. You basically have a very small system. 0 -
The only thing you can do to free up space in /boot is to remove kernels. You can figure out how may you have by simply listing the files and counting the number of vmlinuz* files there. A 487 MB boot partition is really small. In /etc/yum.conf you can set "installonly_limit=#" (where # is a number) and that will limit you to only # kernels and any more than that will be removed when a new one is installed. You need at least 2, so you can go back to an older kernel if you have issues. You can also use "package-cleanup --oldkernels --count=#" to manually reduce the number of kernels to #. You'll want to search/read up on "limit number of kernels CentOS" or something like that to get more details etc. The root partition ("/") is where everything else is stored. The rest of the OS, all your sites/email, MySQL is stored there. Unless you have very large error_log files the only way to clean up space to to reduce the account usage. You basically have a very small system.
If you mean in /Boot All files are those :total 411824 dr-xr-xr-x. 6 root root 4096 Mar 4 03:31 . drwxr-xr-x 20 root root 4096 Mar 18 00:10 .. -rw-r--r-- 1 root root 153567 Aug 25 2020 config-3.10.0-1127.19.1.el7.x86_64 -rw-r--r-- 1 root root 153596 Dec 18 2020 config-3.10.0-1160.11.1.el7.x86_64 -rw-r--r-- 1 root root 153596 Jun 10 2021 config-3.10.0-1160.31.1.el7.x86_64 -rw-r--r-- 1 root root 153595 Nov 17 2020 config-3.10.0-1160.6.1.el7.x86_64 -rw-r--r-- 1 root root 153619 Jan 25 20:45 config-3.10.0-1160.83.1.el7.x86_64 drwxr-xr-x. 3 root root 1024 Sep 18 2017 efi drwxr-xr-x. 2 root root 1024 Dec 9 2020 grub drwx------. 5 root root 1024 Feb 22 00:31 grub2 -rw-------. 1 root root 51313370 Sep 18 2017 initramfs-0-rescue-9063ac396d784f4c997ceacdd0590c25.img -rw------- 1 root root 52462335 Jun 12 2021 initramfs-3.10.0-1127.19.1.el7.x86_64.img -rw------- 1 root root 13756102 Jun 12 2021 initramfs-3.10.0-1127.19.1.el7.x86_64kdump.img -rw------- 1 root root 53847637 Nov 11 05:04 initramfs-3.10.0-1160.11.1.el7.x86_64.img -rw------- 1 root root 13757946 Jun 17 2021 initramfs-3.10.0-1160.11.1.el7.x86_64kdump.img -rw------- 1 root root 53850884 Nov 11 05:03 initramfs-3.10.0-1160.31.1.el7.x86_64.img -rw------- 1 root root 52465237 Jun 12 2021 initramfs-3.10.0-1160.6.1.el7.x86_64.img -rw------- 1 root root 54257895 Feb 22 00:31 initramfs-3.10.0-1160.83.1.el7.x86_64.img -rw------- 1 root root 13800046 Mar 4 03:31 initramfs-3.10.0-1160.83.1.el7.x86_64kdump.img drwx------ 2 root root 12288 Dec 9 2020 lost+found -rw-r--r-- 1 root root 320536 Aug 25 2020 symvers-3.10.0-1127.19.1.el7.x86_64.gz -rw-r--r-- 1 root root 320678 Dec 18 2020 symvers-3.10.0-1160.11.1.el7.x86_64.gz -rw-r--r-- 1 root root 320759 Jun 10 2021 symvers-3.10.0-1160.31.1.el7.x86_64.gz -rw-r--r-- 1 root root 320667 Nov 17 2020 symvers-3.10.0-1160.6.1.el7.x86_64.gz -rw-r--r-- 1 root root 320743 Jan 25 20:46 symvers-3.10.0-1160.83.1.el7.x86_64.gz -rw------- 1 root root 3612420 Aug 25 2020 System.map-3.10.0-1127.19.1.el7.x86_64 -rw------- 1 root root 3617106 Dec 18 2020 System.map-3.10.0-1160.11.1.el7.x86_64 -rw------- 1 root root 3620234 Jun 10 2021 System.map-3.10.0-1160.31.1.el7.x86_64 -rw------- 1 root root 3617083 Nov 17 2020 System.map-3.10.0-1160.6.1.el7.x86_64 -rw------- 1 root root 3623845 Jan 25 20:45 System.map-3.10.0-1160.83.1.el7.x86_64 -rwxr-xr-x. 1 root root 5877760 Sep 18 2017 vmlinuz-0-rescue-9063ac396d784f4c997ceacdd0590c25 -rwxr-xr-x 1 root root 6765160 Aug 25 2020 vmlinuz-3.10.0-1127.19.1.el7.x86_64 -rw-r--r-- 1 root root 172 Aug 25 2020 .vmlinuz-3.10.0-1127.19.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 6769256 Dec 18 2020 vmlinuz-3.10.0-1160.11.1.el7.x86_64 -rw-r--r-- 1 root root 172 Dec 18 2020 .vmlinuz-3.10.0-1160.11.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 6773352 Jun 10 2021 vmlinuz-3.10.0-1160.31.1.el7.x86_64 -rw-r--r-- 1 root root 172 Jun 10 2021 .vmlinuz-3.10.0-1160.31.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 6769256 Nov 17 2020 vmlinuz-3.10.0-1160.6.1.el7.x86_64 -rw-r--r-- 1 root root 171 Nov 17 2020 .vmlinuz-3.10.0-1160.6.1.el7.x86_64.hmac -rwxr-xr-x 1 root root 7051880 Jan 25 20:45 vmlinuz-3.10.0-1160.83.1.el7.x86_64 -rw-r--r-- 1 root root 172 Jan 25 20:45 .vmlinuz-3.10.0-1160.83.1.el7.x86_64.hmac
There is only 11 vmlinuz, which one should i remove ? * About "installonly_limit=#", currently it is set to 5, is it enough ?! * Also "package-cleanup --oldkernels --count=#" , should it be set to 5 in my case or it doesn't matter to the previous number of ( installonly_limit ) . * The root partition, it is almost 500 GB of size, i think it could be the Backup files which is taking more space, what command can alow me view the large files / folders ?0 -
You currently have 5 kernels installed (I don't believe the rescue kernel counts): -rwxr-xr-x. 1 root root 5877760 Sep 18 2017 vmlinuz-0-rescue-9063ac396d784f4c997ceacdd0590c25 -rwxr-xr-x 1 root root 6765160 Aug 25 2020 vmlinuz-3.10.0-1127.19.1.el7.x86_64 -rwxr-xr-x 1 root root 6769256 Dec 18 2020 vmlinuz-3.10.0-1160.11.1.el7.x86_64 -rwxr-xr-x 1 root root 6773352 Jun 10 2021 vmlinuz-3.10.0-1160.31.1.el7.x86_64 -rwxr-xr-x 1 root root 6769256 Nov 17 2020 vmlinuz-3.10.0-1160.6.1.el7.x86_64 -rwxr-xr-x 1 root root 7051880 Jan 25 20:45 vmlinuz-3.10.0-1160.83.1.el7.x86_64 You don't want to just remove files, you either need to run the package-cleanup or change the installonly_limit and then yum will clean up properly. If you are backing up to your root partition, that will eat up a lot of your space. How much depends on how you are backing up (compressed, incremental etc.) and how much you are retaining. You may want to look at off server backup storage. 0 -
You currently have 5 kernels installed (I don't believe the rescue kernel counts): -rwxr-xr-x. 1 root root 5877760 Sep 18 2017 vmlinuz-0-rescue-9063ac396d784f4c997ceacdd0590c25 -rwxr-xr-x 1 root root 6765160 Aug 25 2020 vmlinuz-3.10.0-1127.19.1.el7.x86_64 -rwxr-xr-x 1 root root 6769256 Dec 18 2020 vmlinuz-3.10.0-1160.11.1.el7.x86_64 -rwxr-xr-x 1 root root 6773352 Jun 10 2021 vmlinuz-3.10.0-1160.31.1.el7.x86_64 -rwxr-xr-x 1 root root 6769256 Nov 17 2020 vmlinuz-3.10.0-1160.6.1.el7.x86_64 -rwxr-xr-x 1 root root 7051880 Jan 25 20:45 vmlinuz-3.10.0-1160.83.1.el7.x86_64 You don't want to just remove files, you either need to run the package-cleanup or change the installonly_limit and then yum will clean up properly. If you are backing up to your root partition, that will eat up a lot of your space. How much depends on how you are backing up (compressed, incremental etc.) and how much you are retaining. You may want to look at off server backup storage.
As i mentioned, installonly_limit already set to 5, so what do you think ? The backup is on " Compressed ", it is set to daily and monthly . But my question about this, is there a way to delete old backups, lets say if it is older than a month, the system delete it automatically.0 -
Hello , There is a new thing i had noticed, the WHM didn't make any backups since march 22, all the settings are the same a set on daily backup , I had check the Backup logs and found an error at the same day, what i found is : Available disk space (13 percent) is too low. Backups will not run.0 -
That value can be adjusted in WHM >> Backup Configuration under this option: "Check the available disk space. If you enable this option and the available disk space is less than the amount that you specified, the system will not run the backup." 0
Please sign in to leave a comment.
Comments
47 comments