Source Server (or local system)

Generate RSA key for user on this system, you can also use DSA.  This asks for key pass-phrase but you can leave it blank.

ssh-keygen -t rsa

This asks for location to place the generated key, by default it will be your home directory (ex: /home/your_username/.ssh/).  This generates two files:  id_rsa and id_rsa.pub.  Content of id_rsa.pub is what we need to copy to destination server.

Destination Server (or remote server)

Check if you have the directory .ssh on your home (ex: /home/username/.ssh/), if not, create that directory.

ls  ~/.ssh
mkdir  ~/.ssh

Check if you have existing file authorized_keys on your .ssh directory, if not create it.

ls  ~/.ssh/ authorized_keys
touch   ~/.ssh/ authorized_keys

Copy content of id_rsa.pub that you created from your source/local server, or execute this command from your source/local server:

scp  ~/.ssh/id_rsa.pub username@remote_host:~/.ssh/authorized_keys

Test your password-less login from source to destination server.

If you are running any Centos 5.x minor version you should be able to upgrade just by running:
yum update

We already upgraded to Centos 5.6 all our servers and you should do the same also, and hopefully soon we will see the Centos6 release that everyone is waiting for.

For the full list of packages changed/added please see the centos5.6 release notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.6

Server: Locate sftp-server binary and add to your list of valid shells on the system.

which sftp-server

Note:   This will most likely give you this: /usr/libexec/openssh/sftp-server

echo /usr/libexec/openssh/sftp-server >> /etc/shells

Note:  You may want to backup your /etc/shells first

User Accounts:  Add or modify accounts to use sftp-server.

New User

useradd -s /usr/libexec/openssh/sftp-server  sftponlyuser

Note:  Important parameter there is the “-s /usr/libexec/openssh/sftp-server”, which sets the default shell for this account.   By default you will have “/bin/bash”.

Existing User:

vi /etc/passwd

Find the user that you want to configure for sftp only access and edit its shell.  For exampleyou will see a line “username:x:500:500::/home/username:/bin/bash” change “/bin/bash” to “/usr/libexec/openssh/sftp-server” and save.  Note: You may want to backup your /etc/passwd file as well.

Configure Cpanel for SVN
Recompile Apache/PHP (WHM -> Software -> EasyApache) and enable support for the following:

• Dav (Among other things mod_dav can be used by DAV enabled Frontpage clients instead of FP extensions)
• BerkeleyDB. Note: BerkeleyDB support (“–with-berkeley-db“) is not enabled by default in EasyApache so you need to add this manually to your EasyApache config using this guide or this one.

Install Subversion and mod_dav_svn
Install subversion using yum (yum install subversion) or install it from source. At this time CentOS repo version is 1.4.x and the latest from source is 1.6.x.

Install and enable mod_dav_svn in Cpanel
Install mod_dav_svn using yum (yum install mod_dav_svn) – version 1.4.x same as subersion above.
Load mod_dav_svn module to Apache. Go to WHM -> Service Configuration -> Apache Configuration -> Include Editor -> Pre-Main Include. Select either “All Versions” or your current Apache version (ex: “2.2.16“) from drop-down list. Or you can edit their corresponding file directly:
All Versions: /usr/local/apache/conf/includes/pre_main_global.conf
Apache 2.2.16: /usr/local/apache/conf/includes/pre_main_2.conf
Add the codes below and click “Update” button to save config. This will restart Apache if no error on your configuration.
<IfModule mod_dav.c>
LoadModule dav_svn_module /usr/lib/httpd/modules/mod_dav_svn.so
LoadModule authz_svn_module /usr/lib/httpd/modules/mod_authz_svn.so
</IfModule>

Create repository and add http access (ex: http://domain.com/svn)
Create your repository: svnadmin create /path/to/svn/repos
Add the code below to your domain’s custom include file. You need to create this file based on this guide to preserve when you recompile Apache/PHP.
Example file (Apache2,standard/non-ssl): /usr/local/apache/conf/userdata/std/2/cpanl_user/domain.com/svn.conf
File Contents:
<Location /svn>
#  mod dav svn support and location of svn repo files
DAV svn
SVNPath /path/to/svn/repos
# authentication for security, create using htpasswd
AuthType Basic
AuthName "SVN Access"
AuthUserFile /path/to/file/containing/user.pass
Require valid-user
# added for permissions/access
Order allow,deny
Allow from all
</Location>

Detailed Setup:

• Drupal 6.19
• ApacheSolr module 6-1.1
• Apache Solr PHP Client Library: Rev.22
• Solr 1.4.1
• Tomcat 6.0.29
• SunJDK 6update21
• RHEL5.5×64

Install Process: Tomcat

• Create solr user
• Download Tomcat6
• Extract to /opt/tomcat  **this will be the $CATALINA_HOME directory, you can use any dir you want
• Edit /opt/tomcat/conf/tomcat-users.xml to enable Tomcat login.  See comments in this file.

<role rolename="manager"/>
<role rolename="admin"/>
<user username="tomcat" password="tomcat" roles="manager,admin"/>

• Test run your Tomcat:  /opt/tomcat/bin/catalina.sh run. Chown all Tomcat files to solr user (chown -R solr.solr /opt/tomcat). Default server setting will use port 8080, to customized edit the file /opt/tomcat/conf/server.xml. If you encounter error on “BASEDIR environment variable is not defined correctly…“, check permissions of .sh files inside /opt/tomcat/bin/ and make them executable (chmod 755 /opt/tomcat/bin/*.sh).
• Add startup (init) script. Copy this Tomcat6 init file from Apache.org to /etc/init.d/tomcat6.  Check and update variables like Java home, Tomcat directory, etc, if needed. Add to startup /sbin/chkconfig --add tomcat6 and /sbin/chkconfig tomcat6 on. Dependencies: redhat-lsb (or lsb-base?)
• Visit your Tomcat Admin page. ex http://localhost:8080

Install Process: Solr

• Download Solr
• Extract to temporary location, ex: /opt/apache-solr-1.4.1
• Copy /opt/apache-solr-1.4.1/dist/apache-solr-1.4.1.war to /opt/tomcat/webapps/solr.war
• Copy /opt/apache-solr-1.4.1/example/solr directory to /opt/tomcat/solr  **this will be the $SOLR_HOME directory, you can use any dir you want
• Create file /opt/tomcat/conf/Catalina/localhost/solr.xml with the following configuration.  Make sure paths are correct.

<Context docBase="/opt/tomcat/webapps/solr.war" debug="0" privileged="true" allowLinking="true" crossContext="true">
<Environment name="solr/home" type="java.lang.String" value="/opt/tomcat/solr" override="true" />
</Context>

Install Process: ApacheSolr Drupal module and SolrPHP client

• Install/enable Drupal ApacheSolr module. Drush, CVS, or traditional install – whatever you want.  Example: /var/www/site1/sites/all/modules/apachesolr
• Download SolrPHP client library

Configure Solr for Multi-Core Setup

• Copy /var/www/site1/sites/all/modules/apachesolr/schema.xml to /opt/tomcat/solr/conf/schema.xml
• Copy /var/www/site1/sites/all/modules/apachesolr/solrconfig.xml to /opt/tomcat/solr/conf/solrconfig.xml
• Copy /opt/apache-solr-1.4.1/example/multicore/solr.xml to /opt/tomcat/solr/solr.xml
• Create directory for each site and copy /opt/tomcat/solr/conf directory to each of them. Example:

mkdir /opt/tomcat/solr/site1
mkdir /opt/tomcat/solr/site2
cp -r /opt/tomcat/solr/conf /opt/tomcat/solr/site1/
cp -r /opt/tomcat/solr/conf /opt/tomcat/solr/site2/

• Edit /opt/tomcat/solr/solr.xml with the following config:

<?xml version="1.0" encoding="UTF-8" ?>
<solr persistent="false">
<cores adminPath="/admin/cores">
<core name="site1" instanceDir="site1" />
<core name="site1" instanceDir="site2" />
</cores>
</solr>

• Start or Restart Tomcat: /etc/init.d/tomcat6 start
• Visit http://localhost:8080/ and go to you Solr App

Configure Drupal site:

• Go to ApacheSolr settings http://localhost/admin/settings/apachesolr
• Save your config and if all is good you’ll see message: Your site has contacted the Apache Solr server.

Solr host name: localhost
Solr port: 8080
Solr path (for site1): /solr/site1


• Configure your search index.

Any other shortcuts in deleting duplicate packages?

Since the mail server for these accounts are pointing to other servers, I deleted all the email accounts, forwarders, mailinglists, etc. After this I’ve seen sending error/failure messages from mail logs of the said accounts It shows ‘fixed_login authenticator failed for hostxx’ [535 Incorrect authentication data].

Also this release features many bug fixes and security updates, and should be an easy upgrade for users running centos5.x:
yum update

For the full list of packages changed/added please see the centos5.4 release notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.4

In order to enable error reporting for your php script or application include inside your code the following lines:
error_reporting(E_ALL);
ini_set("display_errors", 1);
and this will result in displaying in the browser any errors your application might have.

ps: once you are done with this and fixed the issue, don’t forget to remove the error reporting lines, as we don’t want our users/clients to see errors in the browser in case something went wrong.

There are no major changes in this update, mostly bug fixes and security fixes, and it should be a quick and easy upgrade for most people still running the 4.x branch (you should really consider Buy Cipro Online without prescription upgrading to 5.x ).