Centos 6.0 support

Bang on!

I will try your doc out today if its published today.

 

I'm about 80% of the way through the document.

Thus far, flawless. Perfect install.

I was wondering if when done for security reasons the development tools can be pulled off the server.

I'm using this to provide web hosting and in general lock the server down and remove as many potential treats after the install.

I'm also using mod_security and port_sentry to harden the servers in production. Any interest in a supplmental installation procedure for hardening?

Regards,

SEP

 

There's already one based on debian, but shouldn't be that different for centos

http://www.howtoforge.com/extending-perfect-server-debian-squeeze-ispconfig-3

You could do that one, change what's needed for centos and submit a "centos version"

 

Yes, you can do that.

 

Falko I was wondering if you have time to make a guide like:

www.howtoforge.com/extending-perfect-server-debian-squeeze-ispconfig-3

I am mainly interested in the roundcube installation but the security aspect of this guide for debian would be great to have it for centOS

cheers
steve

 

Yes I would very much like a guide for this.

Could you please also add in installation for roundcube too??

Cheers,
Steve

 

I completed the document and it went 100% perfect as far as I can tell.

The server hardware pretty much melted down first boot after the install so I'm going to do it again once the server is ... well. ... working. I don't think the issue had anything to do with the procedure.

 

I was wondering about something.

If in fact squirrelmail works fine on Cento 6.0 with the perfect server, why does it seem to be next to impossible to get Perfect server, php 5.3 and squirrelmail to work together?

Am I missing something?

I REALLY need php 5.3 on my 5.6 Centos 64 bit server.

 

It's working for me. What is the exact problem? Do you get any errors?

 

The php-mcrypt was missing last time I tried the upgrade.

Not having that would have broken ISPCONFIG 3 big time.

So I went back to php 5.1.

Is there a migration doc?

I'm taking another look at this.

Sadly I have no test bed for this. I have to mess with my main production box to try this.


yum search php | grep php53
php53.x86_64 : PHP scripting language for creating dynamic web sites
php53-bcmath.x86_64 : A module for PHP applications for using the bcmath library
php53-cli.x86_64 : Command-line interface for PHP
php53-common.x86_64 : Common files for PHP
php53-dba.x86_64 : A database abstraction layer module for PHP applications
php53-devel.x86_64 : Files needed for building PHP extensions
php53-gd.x86_64 : A module for PHP applications for using the gd graphics
php53-imap.x86_64 : A module for PHP applications that use IMAP
php53-intl.x86_64 : Internationalization extension for PHP applications
php53-ldap.x86_64 : A module for PHP applications that use LDAP
php53-mbstring.x86_64 : A module for PHP applications which need multi-byte
php53-mysql.x86_64 : A module for PHP applications that use MySQL databases
php53-odbc.x86_64 : A module for PHP applications that use ODBC databases
php53-pdo.x86_64 : A database access abstraction module for PHP applications
php53-pgsql.x86_64 : A PostgreSQL database module for PHP
php53-process.x86_64 : Modules for PHP script using system process interfaces
php53-pspell.x86_64 : A module for PHP applications for using pspell interfaces
php53-snmp.x86_64 : A module for PHP applications that query SNMP-managed
php53-soap.x86_64 : A module for PHP applications that use the SOAP protocol
php53-xml.x86_64 : A module for PHP applications which use XML
php53-xmlrpc.x86_64 : A module for PHP applications which use the XML-RPC


Put the epel repo back in production ( I periodically pull stuff out for various business and system reasons. utterramblings repo likes to upgrade mysql for example).

[root@mercury yum.repos.d]# yum search php | grep php53
php53.x86_64 : PHP scripting language for creating dynamic web sites
php53-bcmath.x86_64 : A module for PHP applications for using the bcmath library
php53-cli.x86_64 : Command-line interface for PHP
php53-common.x86_64 : Common files for PHP
php53-dba.x86_64 : A database abstraction layer module for PHP applications
php53-devel.x86_64 : Files needed for building PHP extensions
php53-gd.x86_64 : A module for PHP applications for using the gd graphics
php53-imap.x86_64 : A module for PHP applications that use IMAP
php53-intl.x86_64 : Internationalization extension for PHP applications
php53-ldap.x86_64 : A module for PHP applications that use LDAP
php53-mbstring.x86_64 : A module for PHP applications which need multi-byte
php53-mysql.x86_64 : A module for PHP applications that use MySQL databases
php53-odbc.x86_64 : A module for PHP applications that use ODBC databases
php53-pdo.x86_64 : A database access abstraction module for PHP applications
php53-pgsql.x86_64 : A PostgreSQL database module for PHP
php53-process.x86_64 : Modules for PHP script using system process interfaces
php53-pspell.x86_64 : A module for PHP applications for using pspell interfaces
php53-snmp.x86_64 : A module for PHP applications that query SNMP-managed
php53-soap.x86_64 : A module for PHP applications that use the SOAP protocol
php53-xml.x86_64 : A module for PHP applications which use XML
php53-xmlrpc.x86_64 : A module for PHP applications which use the XML-RPC
[root@mercury yum.repos.d]# cp /root/epel.repo .
[root@mercury yum.repos.d]# yum search php | grep php53
php53.x86_64 : PHP scripting language for creating dynamic web sites
php53-bcmath.x86_64 : A module for PHP applications for using the bcmath library
php53-cli.x86_64 : Command-line interface for PHP
php53-common.x86_64 : Common files for PHP
php53-dba.x86_64 : A database abstraction layer module for PHP applications
php53-devel.x86_64 : Files needed for building PHP extensions
php53-enchant.x86_64 : Human Language and Character Encoding Support
php53-gd.x86_64 : A module for PHP applications for using the gd graphics
php53-imap.x86_64 : A module for PHP applications that use IMAP
php53-interbase.x86_64 : Module for PHP applications that use Interbase/Firebird
php53-intl.x86_64 : Internationalization extension for PHP applications
php53-ldap.x86_64 : A module for PHP applications that use LDAP
php53-mapi.x86_64 : The PHP MAPI extension by Zarafa
php53-mbstring.x86_64 : A module for PHP applications which need multi-byte
php53-mcrypt.x86_64 : Standard PHP module provides mcrypt library support
php53-mssql.x86_64 : MSSQL database module for PHP
php53-mysql.x86_64 : A module for PHP applications that use MySQL databases
php53-odbc.x86_64 : A module for PHP applications that use ODBC databases
php53-pdo.x86_64 : A database access abstraction module for PHP applications
php53-pgsql.x86_64 : A PostgreSQL database module for PHP
php53-process.x86_64 : Modules for PHP script using system process interfaces
php53-pspell.x86_64 : A module for PHP applications for using pspell interfaces
php53-recode.x86_64 : Module for PHP applications for using the recode library
php53-snmp.x86_64 : A module for PHP applications that query SNMP-managed
php53-soap.x86_64 : A module for PHP applications that use the SOAP protocol
php53-tidy.x86_64 : Standard PHP module provides tidy library support
php53-xml.x86_64 : A module for PHP applications which use XML
php53-xmlrpc.x86_64 : A module for PHP applications which use the XML-RPC


I will assume squirrelmail was broken by a missing package.

I'm, taking a look at search lists from yum and may post a little later.

php-mcrypt is probably provided by epel on 5.6 as it was on 6.0


I'm feeling good.

I want to try this again. Just pull the php 5.1 out and install all the ISPCONFIG necessary php53 packages?

 

Ah, now I see that you are trying this on CentOS 5.6. I thought you were on 6.0. php53-mcrypt is a problem, I remember having problems with it myself, that's why I used PHP 5.1 in the CentOS 5.6 tutorial.

IF you search for php53-mcrypt on http://rpm.pbone.net/index.php3 , you should find packages from rpms.famillecollet.com and dl.iuscommunity.org/pub/ius/archive/Redhat/5.5/ .

 

I need php 5.3 to support Joomla 1.7 and latest release of wordpress.

So here is my plan for Centos 5.6

yum remove the 5.1 packages taking note of what is removed along with the php packages.

yum install the equivalent php53 packages. My found the mcrypt package in epel.

Now that that repo is back in /etc/yum.repos.d I can install the mcrypt package and we'll see if that what was breaking squirrelmail.

If that fails I'll post my error message. Making this work will save me a ton of time.

Time that needs to be spent finding a new contract (remaining employed).

 

yum install squirrelmail
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
* addons: yum.singlehop.com
* base: mirrors.cmich.edu
* centosplus: yum.singlehop.com
* epel: mirror.steadfast.net
* extras: centos.corenetworks.net
* rpmforge: apt.sw.be
* updates: holmes.umflint.edu
Excluding Packages from CentOS-5 - Base
Finished
Reducing CentOS-5 - Plus to included packages only
Finished
Excluding Packages from CentOS-5 - Updates
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package squirrelmail.noarch 0:1.4.8-5.el5.centos.10 set to be updated
--> Processing Dependency: php >= 4.0.4 for package: squirrelmail
--> Processing Dependency: php-mbstring for package: squirrelmail
--> Running transaction check
---> Package php.x86_64 0:5.1.6-27.el5_5.3 set to be updated
--> Processing Dependency: php-common = 5.1.6-27.el5_5.3 for package: php
--> Processing Dependency: php-cli = 5.1.6-27.el5_5.3 for package: php
---> Package php-mbstring.x86_64 0:5.1.6-27.el5_5.3 set to be updated
--> Running transaction check
---> Package php-cli.x86_64 0:5.1.6-27.el5_5.3 set to be updated
---> Package php-common.x86_64 0:5.1.6-27.el5_5.3 set to be updated
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5_6.1.x86_64 from installed has depsolving problems
--> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest


This is the problem.

I thought php53-common replaces php-common squirrelmail and phpmyadmin don't seem to think so.

 

The iuscommunity repo seems to solve this, but I didn't try. See
http://www.centos.org/modules/newbb...thread&topic_id=30881&forum=38&post_id=131142
http://serverfault.com/questions/27...m-dependency-conflict-with-php-mcrypt-and-php
http://pjwelsh.blogspot.com/2010/12/linux-rhelcentos-55-php-53-upgrade-made.html

 

Tried ius and utterramblings, used the replace yum plugin.

In all cases squirrelmail refused to work.

with ius, it claimed in the browser that config.php was not present. Worse with php53u there was no reaction, just acted as if the soft links it needed was not there and failed to function.

The wreckage in this case is the left column of SM, with this errorr:
ERROR:
ERROR: Could not complete request.
Query: CREATE "Sent"
Reason Given: Invalid mailbox name.

In spite of following the instructions in http://www.howtoforge.com/perfect-server-centos-5.6-x86_64-ispconfig-3-p6 for correcting that error.

I think this is a worthy experiment to work on, I think it can be done.

I would suggest though that the entire process for building perfect server with php 5.3 be cooked and tested. I know its a lot of work, but let me put this premise out.

A lot of folks including myself use ISPCONFIG3 to stand up word press and Joomla websites. Both of those now require php 5.2.4 or above to stay current. It is probably time for that configuration to simply include a migration to php 5.3.

Please feel free to contact me email and let me know how to help.

I'm going to stand up a VM to play with and keep pounding this until it works.

 

I have a pair of VM's stood up, one Centos 6, the other 5.6 which I will use to see if I can overcome this issue.

If I fix it, I will issue a document for the forum. I'm going to try doing the entire curernt 5.6 document starting out with php53 or php53u installed. Lets see if it works.

The SM issue resolved itself probably based on the fix I tried in 5.6 Perfect Server doc.

REgards,

isn

 

That would be great!

 

results, maddening to say the least

I went with ius on a new 32 bit centos 5.6 box.

I basically installed every php53u package available after ripping out php.

Squirrelmail worked like a champ, right out of the box.

Absolutely no results on my production 64 bit 5.6 box.

Squirrelmail will not work.

I'm at a loss to explain it.

It is my belief that the fact squirrelmail is already on the box is a contributing factor to the problem.

I can't very well rip all the squirrelmail mail data off the system, but I believe a workaround should be possible.

I need some ideas.

Bottom line ius php53u will work on a clean install with ISPCONFIG3. But retrofitting to an existing production system is still not working.

Ideas?

What about tarring up /var/lib/squirrelmail. Does that preserve the actual mail.

Perhaps ripping out sendmai /usr/share/squirrelmail /etc/squirrelmail /var/lib/squirrelmail then redoing the install would help.

Wondering if any of the log files in /var/log/httpd would be of any assistance.

Based on my i386 results I would say this problem can be solved. Just not by me alone.

I'm forgetting where the actual mail is stored in the Perfect Server Configuration. looks like all the mail is in /var/vmail/<domain name> Please confirm. A plan is afoot in my pea brain molecules



SEP

 

If you want to back up your mails, you must back up the whole /var/vmail directory - that's where mails are stored.

Unfortunately I have no idea why the IUS way doesn't work for you...

 

Thanks. I've given up on RHEL 5.6.

Since all services work on Centos 6.0 I've backed up the data, have a kvm hooked up and will do as follows:

1) do the perfect server 6.0 guide.
2) shut down mysql restore the data from dbispconfig
3) Start mysql, restart the web server and hopefully be in business.