CentOS

Hi,

I'm trying to install from ispCP (active fork of VHCS).

I'm following this:
http://isp-control.net/documentation/start/installation/centos

I have added all the repo's they state, but get errors when trying to install from the EPEL repo.

When I:
[root@web05 ~]# yum install clamav clamd amavisd-new

I get this error message from all mirrors on the list.
[code](12/13): clamav-0.97-12.el5.i386.rpm | 0 B 00:16 ...
http://ftp.heanet.ie/pub/fedora/epel/5/x86_64/clamav-0.97-12.el5.i386.rpm: [Errno 4] Socket Error: (104, 'Connection reset by peer') Trying other mirror.[/code]

This is the repo file for EPEL.
[code]
[root@web05 ~]# cat /etc/yum.repos.d/epel.repo
[epel]
name=Extra Packages for Enterprise Linux 5 - $basearch
#baseurl=http://download.fedoraproject.org/pub/epel/5/$basearch
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL

[epel-debuginfo]
name=Extra Packages for Enterprise Linux 5 - $basearch - Debug
#baseurl=http://download.fedoraproject.org/pub/epel/5/$basearch/debug
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-debug-5&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL
gpgcheck=1

[epel-source]
name=Extra Packages for Enterprise Linux 5 - $basearch - Source
#baseurl=http://download.fedoraproject.org/pub/epel/5/SRPMS
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-source-5&arch=$basearch
failovermethod=priority
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL
gpgcheck=1
[/code]

I have googled alot, and searched this forum thin, with no luck.

A normal yum install works fine, it only seems to be EPEL repository.

Any hints or help would be greatly appreciated.

/Christian

Welcome to the CentOS fora. Reading [url=https://www.centos.org/modules/newbb/viewforum.php?forum=47]FAQ & Readme First[/url] is recommended for new users.

The first thing to try for yum problems is "yum clean all".

It is possible that there is a corrupted file on the mirror. The [url=http://wiki.centos.org/PackageManagement/Yum/FastestMirror]PackageManagement/Yum/FastestMirror[/url] Wiki page shows how to exclude a problematic mirror.

Edit: After looking in more detail at those instructions I would have to question the wisdom of disabling SELinux, or opening a lot of ports with no discussion of the purpose nor security implications. Some of the information seems out of date, such as the claim that [url=http://wiki.centos.org/Repositories/RPMForge]RPMforge repo[/url] will replace a lot of the system (Dag now has an [rpmforge-extras] repo, disabled by default, that should isolate packages that would replace core packages). They are replacing a [b]lot[/b] of core packages elsewhere in the procedure.

Please read about [url=http://www.centos.org/modules/newbb/viewtopic.php?topic_id=14408&forum=47]Installing Software[/url] and [url=http://wiki.centos.org/AdditionalResources/Repositories]Repositories[/url], and note the warnings and advice about installing and configuring the [url=http://wiki.centos.org/PackageManagement/Yum/Priorities]yum priorities plugin[/url]. Non-core repos should have a higher numeric value, which is a lower priority. Lower is "better" as in golf scores.

You may also want to consult the CentOS Wiki [url=http://wiki.centos.org/HowTos#head-0facb50d5796bee0bd394636c32ffa9a997a6ab5]Email articles[/url] and articles on hardening the OS:
http://wiki.centos.org/HowTos/Network/SecuringSSH
http://wiki.centos.org/HowTos/OS_Protection
http://wiki.centos.org/HowTos/Security
http://wiki.centos.org/HowTos/SELinux
http://wiki.centos.org/TipsAndTricks/SelinuxBooleans

Hi pschaff,

Sorry for the lack of reply, I have been knee deep in learning CentOS. (It quite different from FreeBSD) ;o)

Thank you for the words of warning.

Please close this thread.

I hope your learning endeavors are going well.

We normally do not close threads unless there is abuse. It is good form to let us know if you consider the topic to be solved or resolved so it can be marked appropriately. Just reply with [{RE}SOLVED] in the subject.

Posting your solution or resolution will be appreciated by future forum searchers.