Solve the problem of "Cannot retrieve repository metadata (repomd.xml)\\"

Although the WDCP panel has been upgraded to version 3.0+, Snail found that many netizens are still using version 2.5. This may be because some programs require lower versions of PHP and MYSQL. However, due to the official lack of operation and maintenance services for new and old versions, sometimes system update sources and erroneous documents need to be solved by ourselves.

Even though WDCP panel vulnerabilities have appeared many times, portability is still more important in the eyes of entry-level Linux VPS server users. This is no longer the case. Snails are also asked by netizens to help them install and solve some problems with WDCP. For example, this time they encountered such an error during the installation of version 2.5, as well as the accompanying solutions.

First, the error message that appears

Starting httpd: httpd: Syntax error on line 54 of /www/wdlinux/httpd-2.2.22/conf/httpd.conf: Cannot load /www/wdlinux/httpd-2.2.22/modules/libphp5.so into server: libmhash.so.2: cannot open shared object file: No such file or directory

This is a problem that occurred after Snail installed the official WDCP2.5 installation package. Then I read the previous and later document prompts and saw such an error.

Second, simultaneous errors

http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 – \\”The requested URL returned error: 404 Not Found\ \"Trying other mirror.Error: Cannot retrieve repository metadata (repomd.xml) for repository: rpmforge. Please verify its path and try again

According to the personal judgment of Snail (laozuo.org), it should be caused by the inability to obtain the rpmforge source. There are several reasons here to facilitate simple operation. I tried to modify the DNS and modify the sources available in mainland China.

Third, change the VPS host DNS and Yum source

When I checked the documentation, I saw that some users had similar problems, and the simple way was to modify the DNS and Alibaba Cloud source to solve the problem. Even snails would follow suit and solve the problem. To replace the source, you can also refer to "Replacing Alibaba Cloud yum source with CentOS to solve the problem of being unable to update".

yum clean allyum makecache

After updating the source, I executed the repair command, but the problem was still not solved.

It seems that this method still doesn’t work, so let’s continue looking for a solution. I found that I may encounter the same problem every time, but even using the same method may not necessarily solve the problem. For example, I solved this problem last night, but it seems to have failed today.

Fourth, modify rpmforge source

In fact, it is not difficult to find that when modifying DNS or modifying the source, we still cannot obtain the problem of "apt.sw.be\\" source file. Then I tried to open it and found that it could not be opened. This file, it is estimated that this address is invalid. We just go straight to find the file address and modify it.

vi /etc/yum.repos.d/rpmforge.repo

Here we see that this address was originally hidden here, and the problem should most likely be solved. Since I'm using CentOS6 64bit, I looked for a replacement.

http://mirrorlist.repoforge.org/el6/mirrors-rpmforge

Save after replacement, and then update the cache. I started by replacing the address after baseurl, and there seemed to be an error. Then I also replaced the address after mirrorlist, and no error was found when I executed update again.

Fifth, summary of problem solving

After replacing mirrors-rpmforge, there is no problem when we install the WDCP2.5 version.

Recommended site search: free domain name, asp website space, Hong Kong free virtual host icp registration website, ip online proxy, free international domain name, high defense server, vps virtual host, domain name check, Ministry of Industry and Information Technology website registration