CentOS v5.0 with the CURRENT version 11.2-CURRENT_11480

[MuNLoK]

Hi,

I want to install a new server, and I need to know if I can install CentOS 5.0 to use it with the CURRENT version 11.2-CURRENT_11480. (I don't know if the website requeriment is updated with the release of the v11).

Can the installer script (http://layer1.cpanel.net/latest) install directly the CURRENT v11 version?

Thanks.

[cpanelnick]

Hi,

I want to install a new server, and I need to know if I can install CentOS 5.0 to use it with the CURRENT version 11.2-CURRENT_11480. (I don't know if the website requeriment is updated with the release of the v11).

Can the installer script (http://layer1.cpanel.net/latest) install directly the CURRENT v11 version?

Thanks.

The installer installs release by default

you can


echo "CPANEL=current" >> /etc/cpupdate.conf

before installing to force CURRENT.

[MuNLoK]

fantastic! And the CentOS v5.0 will work correctly with that version no?

Thank you!

[cpanelnick]

fantastic! And the CentOS v5.0 will work correctly with that version no?

Thank you!

Unofficially ... yes. YMMV

[MuNLoK]

Thank you!

[cpanelkenneth]

courier will fail to install. Until we get the RPMs built, you need to do this:

1. chown cpanel:cpanel /usr/local/cpanel/rpm-build/tmp
2. /scripts/courierup --force --source

You should have a working courier after that.

[mr2jzgte]

courier will fail to install. Until we get the RPMs built, you need to do this:

1. chown cpanel:cpanel /usr/local/cpanel/rpm-build/tmp
2. /scripts/courierup --force --source

You should have a working courier after that.

Most times, that will fail as well..

We modified /etc/redhat-release to say version 4, and the default install worked fine.. Alternatively, you can fine the location of the rpms, download them manually and rpm -Uvh then run /scripts/upcp and it worked fine

[chirpy]

courier will fail to install. Until we get the RPMs built, you need to do this:

1. chown cpanel:cpanel /usr/local/cpanel/rpm-build/tmp
2. /scripts/courierup --force --source

You should have a working courier after that.

That solution has worked fine for me too on CentOSv5 (had to work it out myself )

[cpanelkenneth]

Most times, that will fail as well..

We modified /etc/redhat-release to say version 4, and the default install worked fine.. Alternatively, you can fine the location of the rpms, download them manually and rpm -Uvh then run /scripts/upcp and it worked fine

If it fails, that means something else (possibly other permisisons) is wrong. One example is an edge case in the RELEASE branch where attempting to download the RPMs that aren't there triggers an alarm that causes the entire process to die 60 seconds into the courierup process. This is a bug in the RELEASE version of HttpUtils that we haven't tracked down yet, as it only afflicts distros where we don't provide RPMs, and it doesn't always happen even in those circumstances.

Running /scripts/courierup --force --verbose --source will give one a good indication of what is preventing the install from happening. The same holds true for any *up scrip that downloads RPMs.

Mixing RPMs from different distro versions is neither recommended nor supported.

[mr2jzgte]

If it fails, that means something else (possibly other permisisons) is wrong. One example is an edge case in the RELEASE branch where attempting to download the RPMs that aren't there triggers an alarm that causes the entire process to die 60 seconds into the courierup process. This is a bug in the RELEASE version of HttpUtils that we haven't tracked down yet, as it only afflicts distros where we don't provide RPMs, and it doesn't always happen even in those circumstances.

Running /scripts/courierup --force --verbose --source will give one a good indication of what is preventing the install from happening. The same holds true for any *up scrip that downloads RPMs.

Mixing RPMs from different distro versions is neither recommended nor supported.

Supported pfft If it works, it works. At the time of install, there were no packages available for rhel5 so we had to make do with what we had.

[chirpy]

Which is fine for your purposes, but it's still not a good idea to recommend it to others for the reason cpanelkenneth gave.

[vladi2n]

Well on CentOS5 after I run:

1. chown cpanel:cpanel /usr/local/cpanel/rpm-build/tmp
2. /scripts/courierup --force --source

I'v got:

(root)>/scripts/courierup --force --source
courier-imap Setup Script Version 1.0
Fetching version information from http://updates.cpanel.net/courierinstall/version (CURRENT)....Fetching http://updates.cpanel.net/courierinstall/version (0)....@xxx.xxx.xxx.xxx......connected......receiving...100%......Done
Done
This is the courier-authlib 0.57 installer release number 6cp
Using newyum support..
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Parsing package install arguments
Nothing to do
Resetting courier-authlib to cPanel Defaults and Installing the Latest Version
usermod: invalid numeric argument 'compiler'
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Parsing package install arguments
Nothing to do
Building RPM....Done
Rpm failed to build! Please recall courierup with --source --verbose to find out why at /scripts/courierup line 462.

[vladi2n]

This is + --verbose

Building RPM...error: cannot open /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm: Permission denied
Done
Rpm failed to build! Please recall courierup with --source --verbose to find out why at /scripts/courierup line 462.


The file is owned by cpanel.:

(root)>ls -la /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm
-rw-r--r-- 1 cpanel cpanel 2009871 May 4 00:01 /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm

(root)>stat /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm
File: `/usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm'
Size: 2009871 Blocks: 3944 IO Block: 4096 regular file
Device: fd00h/64768d Inode: 99158173 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 504/ cpanel) Gid: (32003/ cpanel)
Access: 2007-05-05 00:16:50.000000000 -0400
Modify: 2007-05-04 00:01:33.000000000 -0400
Change: 2007-05-04 16:23:13.000000000 -0400

[mitgib]

This is + --verbose

Building RPM...error: cannot open /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm: Permission denied
Done
Rpm failed to build! Please recall courierup with --source --verbose to find out why at /scripts/courierup line 462.


The file is owned by cpanel.:

(root)>ls -la /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm
-rw-r--r-- 1 cpanel cpanel 2009871 May 4 00:01 /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm

(root)>stat /usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm
File: `/usr/local/cpanel/rpm-build/SRPMS/courier-authlib-0.57-6cp.src.rpm'
Size: 2009871 Blocks: 3944 IO Block: 4096 regular file
Device: fd00h/64768d Inode: 99158173 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 504/ cpanel) Gid: (32003/ cpanel)
Access: 2007-05-05 00:16:50.000000000 -0400
Modify: 2007-05-04 00:01:33.000000000 -0400
Change: 2007-05-04 16:23:13.000000000 -0400

chown -R cpanel:cpanel /usr/local/cpanel/rpm-build

Fixed it for me

[vladi2n]

Well now this error:

Executing(%build): /bin/sh -e /usr/local/cpanel/rpm-build/tmp/rpm-tmp.20303
+ umask 022
+ cd /usr/local/cpanel/rpm-build/BUILD
+ cd courier-authlib-0.57
+ /usr/bin/make '%{_smp_mflags}'
make: *** No rule to make target `%{_smp_mflags}'. Stop.
error: Bad exit status from /usr/local/cpanel/rpm-build/tmp/rpm-tmp.20303 (%build)


RPM build errors:
Bad exit status from /usr/local/cpanel/rpm-build/tmp/rpm-tmp.20303 (%build)
Done
Rpm failed to build! Please recall courierup with --source --verbose to find out why at /scripts/courierup line 462.