Skip to main content

can't update

dxb04
Hello , I was trying to make few updates to my server .. I tried to make " system update ", but there was an error 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

Comments

47 comments

Date Votes
  • ffeingol
    It "looks" like either a firewall or DNS related issue. From the output it's hard to tell the repo that is failing. From the server can you ping mirrors.xtom.de (just one of the mirrors listed).
    0
  • dxb04
    It "looks" like either a firewall or DNS related issue. From the output it's hard to tell the repo that is failing. From the server can you ping mirrors.xtom.de (just one of the mirrors listed).

    Do you mean : PING mirrors.xtom.de (62.133.35.14) 56(84) bytes of data. 64 bytes from 62.133.35.14.static.xtom.de (62.133.35.14): icmp_seq=1 ttl=55 time=24.7 ms 64 bytes from 62.133.35.14.static.xtom.de (62.133.35.14): icmp_seq=2 ttl=55 time=24.7 ms 64 bytes from 62.133.35.14.static.xtom.de (62.133.35.14): icmp_seq=3 ttl=55 time=24.7 ms 64 bytes from 62.133.35.14.static.xtom.de (62.133.35.14): icmp_seq=4 ttl=55 time=24.6 ms
    0
  • dxb04
    Still i didn't find the way to solve the problem .. Any idea ?!
    0
  • cPRex Jurassic Moderator
    I would recommend trying the classic command combo first to see if that fixes things: yum clean all yum makecache yum update
    Let us know what happens with that.
    0
  • dxb04
    I would recommend trying the classic command combo first to see if that fixes things: yum clean all yum makecache yum update
    Let us know what happens with that.

    Thank you for your reply .. Actually i had tried those commands before .. and tried now again, and the result are the same : [root@server ~]# 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 [root@server ~]# yum makecache Loaded plugins: fastestmirror, universal-hooks Determining fastest mirrors epel/x86_64/metalink | 29 kB 00:00:00 * EA4: 185.157.208.252 * cpanel-addons-production-feed: 185.157.208.252 * cpanel-plugins: 185.157.208.252 * base: de.mirrors.clouvider.net * epel: www.nic.funet.fi * extras: de.mirrors.clouvider.net * updates: mirror.23m.com 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 [root@server ~]# yum update Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile epel/x86_64/metalink | 29 kB 00:00:00 * EA4: 185.157.208.252 * cpanel-addons-production-feed: 185.157.208.252 * cpanel-plugins: 185.157.208.252 * base: de.mirrors.clouvider.net * epel: www.nic.funet.fi * extras: de.mirrors.clouvider.net * updates: mirror.23m.com 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
    0
  • cPRex Jurassic Moderator
    Can you try this command on your server and see if it downloads that text file? wget http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml
    0
  • dxb04
    Can you try this command on your server and see if it downloads that text file? wget http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml

    This is the result [root@server ~]# wget http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml --2023-03-07 00:06:40-- http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml Resolving repo.mysql.com (repo.mysql.com)... 168.119.126.94 Connecting to repo.mysql.com (repo.mysql.com)|168.119.126.94|:80... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://dachbrothers.de/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml [following] --2023-03-07 00:06:40-- https://dachbrothers.de/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml Resolving dachbrothers.de (dachbrothers.de)... 168.119.126.94 Connecting to dachbrothers.de (dachbrothers.de)|168.119.126.94|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2023-03-07 00:06:41 ERROR 404: Not Found.
    0
  • cPRex Jurassic Moderator
    That seems odd - I wonder if your hosting provider has a local repository that is having issues, as I have no idea where that domain name would be coming from as part of that command. Can you reach out to your hosting provider about this issue?
    0
  • dxb04
    That seems odd - I wonder if your hosting provider has a local repository that is having issues, as I have no idea where that domain name would be coming from as part of that command. Can you reach out to your hosting provider about this issue?

    I will try to write to them , But .. Can you please tell me what should i write to them exactly ? so i can deliver the right information to them .. Then i'll update this thread with there reply
    0
  • cPRex Jurassic Moderator
    The output from that wget along with telling them you can't run "yum update" should be all they need to know.
    0
  • dxb04
    The output from that wget along with telling them you can't run "yum update" should be all they need to know.

    Okay .. I am going to mail them now Thank you so much
    0
  • dxb04
    The output from that wget along with telling them you can't run "yum update" should be all they need to know.

    The host provider requested to check /etc/resolv.conf and add the right nameservers I had checked and edited the file .. the nameservers was missing, Adding nameservers in this way : ns.domain.com IP ns2.domain.com IP Is it correct and enough ? or i need to add extra things in this file ?
    0
  • quietFinn
    Adding nameservers in this way : ns.domain.com IP ns2.domain.com IP Is it correct and enough ? or i need to add extra things in this file ?

    No it's not correct, it must be: nameserver 1stIP nameserver 2ndIP nameserver in both lines is the configuration option.
    0
  • dxb04
    No it's not correct, it must be: nameserver 1stIP nameserver 2ndIP nameserver in both lines is the configuration option.

    So i have just to keep nameserver as it is and just add the ip ?! what if i have only 1 ip .. ? Should it be : nameserver ip1 ?!
    0
  • quietFinn
    You can have only one nameserver in resolv.conf, at least one, max. three.
    0
  • dxb04
    You can have only one nameserver in resolv.conf, at least one, max. three.

    After i add the nameserver , should i restart sshd ?
    0
  • quietFinn
    You don't need to restart anything.
    0
  • dxb04
    I retried to run those commands : yum clean all yum makecache yum update I got this result : [root@server ~]# 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 [root@server ~]# yum makecache Loaded plugins: fastestmirror, universal-hooks Determining fastest mirrors Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" One of the configured repositories failed (Unknown), 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= ... 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 or subscription-manager repos --disable= 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=.skip_if_unavailable=true Cannot find a valid baseurl for repo: EA4/7/x86_64 [root@server ~]# yum update Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile Could not retrieve mirrorlist http://httpupdate.cpanel.net/ea4-c7-x86_64-mirrorlist error was 14: curl#6 - "Could not resolve host: httpupdate.cpanel.net; Name or service not known" One of the configured repositories failed (Unknown), 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= ... 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 or subscription-manager repos --disable= 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=.skip_if_unavailable=true Cannot find a valid baseurl for repo: EA4/7/x86_64
    0
  • ffeingol
    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.
    0
  • 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 : [root@server ~]# 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 [root@server ~]# 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 [root@server ~]# 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 ..
    0
  • ffeingol
    As a total guess, are there any entries in /etc /hosts for repo.mysql.com?
    0
  • 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
    0
  • 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.
    0
  • 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 :-D i run all of the commands yum clean all yum makecache yum update
    0
  • cPRex Jurassic Moderator
    Excellent idea, @ffeingol !!!!
    0
  • 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 :-D
    0
  • 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 ?!
    0
  • cPRex Jurassic Moderator
    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.
    0
  • 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 ?
    0
  • cPRex Jurassic Moderator
    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.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post