Whenever you go to install applications and services on registered RHEL servers, it’s always nice to use the RPMs because up2date will keep everything current for you. Managing upgrades gets a whole lot easier when you can bring your system up to current with one simple command. Because of this, I decided that I would try to use as many RPMs as I could when I set up our latest Horde / IMP installation.
Unfortunately, RedHat does not supply RPMs for the Horde applications, but luckily CentOS does. You should be able to download them from here. Get the latest version, which at the time of this writing was horde-3.1.3-1 and imp-h3-4.1.3-1.
Don’t install them yet though because Horde and IMP have always had a lot of dependancies which must be installed and enabled first. Installing the following RPMs should take care of them.
- mysql-4.1.20-1.RHEL4.1.i386.rpm
- mysqlclient10-3.23.58-4.RHEL4.1.i386.rpm
- mysqlclient10-devel-3.23.58-4.RHEL4.1.i386.rpm
- mysql-devel-4.1.20-1.RHEL4.1.i386.rpm
- mysql-server-4.1.20-1.RHEL4.1.i386.rpm
- perl-DBD-MySQL-2.9004-3.1.i386.rpm
- php-4.3.9-3.15.i386.rpm
- php-devel-4.3.9-3.15.i386.rpm
- php-domxml-4.3.9-3.15.i386.rpm
- php-imap-4.3.9-3.15.i386.rpm
- php-ldap-4.3.9-3.15.i386.rpm
- php-mysql-4.3.9-3.15.i386.rpm
- php-pear-4.3.9-3.15.i386.rpm
Assuming you will want up2date to handle upgrades of these packages, it is very important that you either use “up2date” to install them, or download them from correct channel at the RedHat website. You could also simply get them from the CD distribution that you used to install the system itself.
Once PEAR is installed, you will have to upgrade it, and install the PEAR::Log module.
[root@server]# pear upgrade -a PEAR-1.3.6
[root@server]# pear upgrade PEAR
Ok, now let’s make sure the web server is configured to start when the system comes up:
[root@server /]# /sbin/chkconfig –list httpd
You should see this:
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
But if you see 5:off, simply run:
[root@server /]# /sbin/chkconfig httpd on
Now we enable and start up our new MySQL database server:
[root@server /]# /sbin/chkconfig mysqld on
[root@server /]# /sbin/service mysqld start
And we’re ready to install Horde and IMP. Install the following RPM’s, which will put everything in /usr/share/horde and creates a file called horde.conf in /etc/httpd/conf.d/
- horde-3.1.3-1.c4.noarch.rpm
- imp-h3-4.1.3-1.c4.noarch.rpm
This will install the HORDE and IMP packages in /usr/share, and /usr/share/horde respectively.
Finally, we start or restart apache:
[root@server /]# /sbin/service httpd start
Grab a browser and go to the following URL to proceed with the Horde and IMP configuration.
http://server.example.com/horde/
I don’t know if you take requests, but I’ve always been curious about making tarballs into RPMs. Your second paragraph got me on that idea.
Rolling a tarball to an rpm is generally pretty easy, but I learned from the old howto at rpm.org and following along. I don’t think it’s a subject for a 500wd blogpost.
gah. Lemme qualify that. I think that the seemingly simple subject of Tarball->RPM is deceptively simple, at least to say. It’s such a broad and persnickity subject, I think that tackling it here would be brave — or foolhardy! If you want examples of really simple to messed-up RPMs, though, drop me a note/jabber. bishopolis-at-gmail.
when i enter up2date command. after filling the information i get error
aaaaaaaaaaa Fatal Error aaaaaaaaaaaaaaaaaaaaaaaaaaaa
problem registering system:
Error Class Code: 70
Error Class info:
All available subscriptions for the requested channel have been exhausted.
Please contact a Red Hat Network Sales associate.
Explanation:
An error has occurred while processing your request. If this problem
persists please enter a bug report at
bugzilla.redhat.com.
If you choose to submit the bug report,
please be sure to include
details of what you were trynig to do when this error occurred and details on how to reproduce this problem.
aaaaaa
a ok a
aaaaaa