This account is currently locked out because a brute force attempt  was detected. Please wait 10 minutes and try again. Attempting to login again will only increase this delay. If you frequently experience this problem, we recommend having your username changed to something less generic.

Run the following as root in SSH.

mysql cphulkd
mysql> delete from brutes;
mysql> delete from logins;

vzlist -a
Shows list of all the VPS’s hosted on the Node.

vzctl start VEID
To start the VPS

vzctl stop VEID
To stop (Shut Down) the VPS

vzctl status VEID
To view the status of the particular VPS

vzctl stop VEID –fast
To stop the VPS quickly and forcefully

vzctl enter VEID
To enter in a particular VPS

vzctl set VEID –hostname vps.domain.com –save
To set the Hostname of a VPS

vzctl set VEID –ipadd 1.2.3.4 –save
To add a new IP to the hosting VPS

vzctl set VEID –ipdel 1.2.3.4 –save
To delete the IP from VPS

vzctl set VEID –userpasswd root:new_password –save
To reset root password of a VPS

vzctl set VEID –nameserver 1.2.3.4 –save
To add the nameserver IP’s to the VPS

vzctl exec VEID command
To run any command on a VPS from Node

vzyum VEID install package_name
To install any package/Software on a VPS from Node

**VEID refers to the ID of the Particular VPS**

The session.save_path setting in your php configuration file (php.ini) is not set or is set to a folder which did not exist. You might need to set the save_path setting in php.ini or verify that the folder sets in save_path exist.

It’s a pretty simple fix in the servers php.ini. First thing you need to do is locate your servers copy of the php.ini by running the following command via SSH.

root@lolwut [~]# php -i | grep php.ini
Configuration File (php.ini) Path => /usr/local/lib
Loaded Configuration File => /usr/local/lib/php.ini
root@lolwut [~]#

Once you’ve found the php.ini, use your favorite editor and locate the following line.

root@lolwut [~]# grep ‘session.save_path’ /usr/local/lib/php.ini
; session.save_path = “N;/path”
;session.save_path = /tmp
; (see session.save_path above), then garbage collection does *not*
root@lolwut [~]#

In this case, simply remove “;” which will uncomment the line. If you are missing the “/tmp” part of the line, you will need to add it. Make these changes and save the file, then restart apache and you’re good to go.

One of the most common issues when installing fantastico is a buggy wget install on the server, so a working wget version will need to be installed. Another common issue is cPanels internal php may break, but we will discuss the fix to that later on. To install the working version of wget run the following commands:

rpm -qa wget ;
wget ftp://ftp.funet.fi/pub/mirrors/ftp.redhat.com/pub/fedora/linux/core/5/i386/os/Fedora/RPMS/wget-1.10.2-3.2.1.i386.rpm
chattr -ia /usr/bin/wget
rpm -e wget ;
rpm -ivh –force wget-1.10.2-3.2.1.i386.rpm ;
rpm -qa wget ;

First thing is downloading the Fantastico files to the server.

/scripts/upcp
cd /usr/local/cpanel/whostmgr/docroot/cgi
wget -N http://www.netenberg.com/files/free/fantastico_whm_admin.tgz
tar -xzpf fantastico_whm_admin.tgz
rm -rf fantastico_whm_admin.tgz

Once the files have been downloaded, log into WHM with your root account and select “Fantastico De Luxe WHM Admin” under the plugin section on the left side of WHM at the bottom.

You will then go the Fantastico main page, where you will select “Click here” under ‘Version Information’ in the middle. Now select the stable version from the drop down menu.

Now follow the remaining steps using the default information, as all of it should be correct, though you may want to double check. Be sure to select “enable” next to suexec if it is installed on the server and also check the VPS section if you have installed this on a VPS.

If you receive cpanel_phpengine errors when logged into Fantastico as end user, run the following command via SSH.

/scripts/makecpphp

You may also run into an ioncube error when trying to log into Fantastico, which can be fixed by logging into WHM as root -> Tweak Settings -> Loader to use for internal cPanel PHP -> IonCube -> Save

If you have any issues with your install, feel free to comment this post.

2009-07-20 21:58:07 Failed to get write lock for /var/spool/exim/db/ratelimit.lockfile: timed out
2008-07-20 21:58:07 H=[xx.xx.xx.xx] temporarily rejected connection in “connect” ACL: ratelimit database not available

To fix such an error , the exim cache database on the server side needs to be clear off to stop this message.

Run the folllowing command on root :

root@lolwut [~]# rm -fv /var/spool/exim/db/*

Output :

removed `/var/spool/exim/db/ratelimit’
removed `/var/spool/exim/db/ratelimit.lockfile’
removed `/var/spool/exim/db/retry’
removed `/var/spool/exim/db/retry.lockfile’
removed `/var/spool/exim/db/wait-dk_remote_smtp’
removed `/var/spool/exim/db/wait-dk_remote_smtp.lockfile’
removed `/var/spool/exim/db/wait-remote_smtp’
removed `/var/spool/exim/db/wait-remote_smtp.lockfile’

Then run the following command on root:

root@lolwut [~]# service exim restart

If this doesn’t work , then run /scripts/upcp –force on the server and then check exim_mainlog for the changes.

How to create a compressed tar.gz file from a folder or file in Linux?

In order to create a compressed tar.gz archive from a folder/file we need to run the following tar command:

tar -czf new-tar-file-name.tar.gz file-or-folder-to-archive

Here is the command explanation:

• tar – the tar command.
• c – create new archive.
• z – compress the archive using gzip.
• f – use archive file.
• new-tar-file-name.tar.gz – the name of the tar.gz to create.
• file-or-folder-to-archive – the name of the folder we want to archive.

How to create a compressed tar.gz file from multiple files and folders in Linux?

In order to create a compressed tar.gz file from multiple files or/and folders we need to run the same tar command we used when we archived a single file/folder and to append the rest of the files/folders’ names to it.

tar -czf new-tar-file-name.tar.gz file1 file2 folder1 folder2

How to extract a compressed tar.gz file in Linux?

tar -xzf tar-file-name.tar.gz

Here is the command explanation:

• tar – the tar command.
• x – extract the archive.
• z – uncompress the archive using gzip.
• f – use archive file.
• tar-file-name.tar.gz – the name of the tar.gz to create.

The tar command will extract all the files/folders in the archive to the current directory.

How to extract a compressed tar.bz2 file in Linux?

Extracting tar.bz2 (bzip2 file) is very similar to the way you extract tar.gz file. Instead of using the -z flag you need to use the -j flag for the bzip2 format

tar -xjf tar-file-name.tar.gz

Here is the command explanation:

• tar – the tar command.
• x – extract the archive.
• j - filter the archive through bzip2
• f – use archive file.
• tar-file-name.tar.gz – the name of the tar.gz to create.

The tar command will extract all the files/folders in the archive to the current directory.

login as: root
root@server’s password:
Server refused to allocate pty
stdin: is not a tty

After a quick google search I came across the fix.

[root@node /]# vzlist -a
VEID      NPROC STATUS  IP_ADDR         HOSTNAME
1337         78 running 69.10.59.80     grumpy.thelinuxnoob.com
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV ptyp
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV tty
[root@node /]# vzctl exec 1337 /sbin/MAKEDEV pty

The issue should now be resolved and you can SSH into the VPS.

wget http://layer1.cpanel.net/perl588installer.tar.gz
tar -xvzf perl588installer.tar.gz
cd perl588installer
./install

cp -Rpf /var/lib/mysql /var/lib/mysql.BAK
Login to WHM –> Tweak Settings –> MySQL -> 5.0  and Save settings
/scripts/mysqlup –force
/scripts/perlinstaller –force Bundle::DBD::mysql
/scripts/realperlinstaller –force DBD::mysql
Recompile PHP

You’re done

This will force a hacker to have to guess 2 seperate passwords to gain root access.
(you do have 2 seperate passwords for admin and root right?)
What happens is you’ll first need to login as your admin user in SSH, then switch to the super user with the su command to get root.

We also will be forcing the use of SSH protocol 2, which is a newer, more secure SSH protocol
Just a couple more ways to help your server stay safe from the bad guys. If you’re using cPanel make sure you add your admin user to the ‘wheel‘ group so that you will be able to ‘su -‘ to root, otherwise you may lock yourself out of root.

1. SSH into your server as ‘admin‘ and gain root access by su

2. Copy and paste this line to edit the file for SSH logins
pico -w /etc/ssh/sshd_config

3. Find the line
Protocol 2, 1

4. Uncomment it and change it to look like
Protocol 2

5. Next, find the line
PermitRootLogin yes

6. Uncomment it and make it look like PermitRootLogin no

7. Save the file Ctrl+X then Y then enter

8. Now you can restart SSH
/etc/rc.d/init.d/sshd restart

Now, no one will be able to login to root with out first loggin in as admin and ’su -’ to root, and you will be forcing the use of a more secure protocol. Just make sure you remember both passwords!