SSH Authorized Keys Automatic Login

SSH can automatically authenticate connections when the client presents an authorized key. A client gives it’s public key to a server and then when it connects the server knows it’s allowed in and automatically allows the connection. The Keys are specific to users, so a key for user_a will not let user_b in.

Few Simple Steps

  1. Create Keys

    If the keys don’t exists already you must create them. Look in your ~/.ssh for files called id_rsa and If those files don’t exist say ssh-keygen -b 2048 -t rsa to create them.

  2. Place Keys on Server

    Copy to the server then append that to ~/.ssh/authorized_keys

Optionally you can use a DSA key, simply replace `rsa` with `dsa` above

SSH automatic login assistance script

The script automatically pushes your SSH private key to the server specified so you can have automatic SSH,scp and sftp authentication. If you don’t have a key the script will generate one for you, also this script assumes that the user running the script has a home directory on the remote host. Should note that this script will only push the RSA encrypted key.

The Script




# say: ./ hostname

# Uploads your to the specified host, wrapped for readability

if [ ! -r ${HOME}/.ssh/ ];then

ssh-keygen -b 2048 -t rsa


# Append to the copy on the remote server

cat ~/.ssh/ | ssh ${USER}@$1 “cat – >> .ssh/authorized_keys”

if [ $? -eq 0 ]; then

echo “Success”


save the script say as and execute it ./ hostname

Virtuozzo glibc-dummy-centos-4 Error (1)

If you come across this error when trying to do a “yum update” on your Virtuozzo Virtual Dedicated Server

–> Processing Dependency: glibc-common = 2.3.4-2.25 for package: glibc-dummy-centos-4–> Finished Dependency ResolutionError: Missing Dependency: glibc-common = 2.3.4-2.25 is needed by package glibc-dummy-centos-4

You can make use of the following steps to fix the problem. First you need to remove the package that is causing the problem.

yum remove glibc-dummy-centos-4

After you have removed that package you need to reinstall gcc with all the extras. You can do that simply by running the following command.

yum install gcc & yum install gcc*

If everything installed correctly you should now be able to run a yum update and it should not error out at all.

Enable SLM on Virtuozzo

 What is SLM, “Virtuozzo Service Level Management (SLM) is a system that maintains and allows administrators to configure and control the levels of service (i.e., the set of ‘promises’) provided to VPS owners.I came across some different ways of enabling SLM on the Virtuozzo Node, by far the best was the information about how to enable it with out a Node reboot. run the following commands. Edit the following files and make said changes

/etc/sysconfig/vz and change the SLM entry to slm=yes/etc/sysconfig/vzagent/vzagent.conf Locate the SLM entry, change it to 1. 


After you modified configuration file you need to restart VZAgent, use the following command on a hardware node:

vzagent_ctl restart 


How to install Cpanel and Fantastico in a VPS

cPanel installs a little bit differently in a VPS that it does on your traditional server.

Install cPanel in CentOS / Fedora VPS:

You will need yum installed on the VPS

cat /etc/redhat-release

rpm -q yum centos-yumconf


CentOS 5 :

rpm –import
rpm -Uvh
rpm -Uvh

rpm -Uvh
rpm -Uvh
rpm -Uvh
rpm -ivh
rpm -ivh
rpm -ivh
rpm -Uvh

Fedora 6:

rpm -Uvh
rpm -Uvh
rpm -Uvh
rpm -Uvh
rpm -Uvh
rpm -Uvh

Install cPanel :

mkdir /home/cpins
cd /home/cpins
sh latest

cd /usr/local/cpanel/whostmgr/docroot
rm -Rf fantastico*
wget -N
tar xzpf fantasticoinstaller.tgz
rm -f fantasticoinstaller.tgz

In /etc/xinetd.d/pop3ds

Change ‘disable = no’ to ‘disable = yes’

restart xinetd
restart cpanel

Fatal error: Allowed memory size of 123456 bytes exhausted (tried to allocate 234567 bytes) in /path/file.php

Php is setup is to limit memory usage per process. If you require more, this limit can be increased.


If you are unsure about the php.ini path, You can find your server php.ini using command :

php -i | grep php.ini

Configuration File (php.ini) Path => /usr/local/lib

Loaded Configuration File => /usr/local/lib/php.ini

and set:

memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)

to a higher value, like 20M. Save, exit, then restart apache.

DirectAdmin Apache won’t restart: [crit] (98)Address already in use: make_sock: could not bind to port 8090


Apache won’t restart: [crit] (98)Address already in use: make_sock: could not bind to port 8090

[crit] (98)Address already in use: make_sock: could not bind to port 8090
[crit] (98)Address already in use: make_sock: could not bind to port 443
[crit] (98)Address already in use: make_sock: could not bind to port 80

If you see this error in your /var/log/httpd/error_log, it would mean that apache isn’t shutting down completely before trying to restart. This means that the new process won’t be able to bind to the given ports because they’re still being used by the old copy of apache that wasn’t completely shut down.

To solve this, use a different boot script that will wait for all apache processes to stop before starting the new one:

cd /usr/local/directadmin/customapache
rm -f httpd*
./build update

Once you have the new scripts downloaded, you need to install them:


cp httpd /etc/init.d/httpd
chmod 755 /etc/init.d/httpd
chkconfig httpd reset


cp httpd_freebsd /usr/local/etc/rc.d/httpd
chmod 755 /usr/local/etc/rc.d/httpd

Where can I change log permissions so other programs can read apaches web logs?

Click on the “Tweak Settings” link under “Server Setup”. Within the “Stats and Logs” section is a text box with the heading:

“Chmod value for raw apache log files (0640 is the default):”

Change the value to suit your needs and apply the changes by clicking on the “Save” button at the bottom of the page.

Most programs only need read permissions on the log files so setting this to 0644 should suffice.