Service Pack for ProLiant (SPP) Version 2015.10.0 Direct download link

HP keeps disconnecting the connection when I am trying to retrieve the Full ISO Image of Service Pack for ProLiant (SPP) Version 2015.10.0.

To spare you some time, I made a direct link.

From HP: Download

From (much faster and no dropping connections): *Link removed* Unfortunately I have been contacted by HP to remove the direct link to the file, sorry guys.

Simple SSH bruteforce prevention using iptables

Since I like to learn more about scripting, I decided to write my own SSH bruteforce prevention script instead of installing a plug-and-play tool. You can run the script manually or have it run every hour or so using crontab.

As root, create a new directory for the script and files, name it for example bfCheck:

# mkdir bfCheck

In this folder, create a new file, name it for example

# cd bfCheck
# touch

Open the file using nano and copy paste the following script:

# nano -w

blockIPs=”$(cat /var/log/secure | grep “Failed password for” | grep -v “invalid” | awk {‘print $11’} | sort | uniq -c | awk -v limit=50 ‘$1 > limit{print $2}’)”

if [ -z “$blockIPs” ]
echo “No match found, skipping”

while read -r line; do
if grep -q $line <<<$currentIPs
echo “IP address already blocked, skipping. IP: $line”
/sbin/iptables -A INPUT -s $line -p tcp –dport 22 -j DROP
echo “Blocking IP address: $line”
echo `date +”%b %d %H:%M:%S”` Blocking $line >> /root/bfCheck/iptables.log
done <<< “$blockIPs”


Save and close (ctrl+x & y).

Change the file’s mode, give it +x:

# chmod +x

Run the script, you will it will start blocking IP addresses or it will show you that not match is found:

# ./

Please note the limit=50 at the very first line of the script just after #!/bin/sh. You can change it to your wishes, it means that it will only block the IP address if there was more than 50 tries to access your server with an invalid password.

Error: The monit service does not respond. Refer to Parallels technical support for help.

I have Plesk 12 installed on a machine running CentOS 6, but I am not able to start Watchdog due to the following error message:

Error: The monit service does not respond. Refer to Parallels technical support for help.

It seems that the monitrc template is using a log location which doesn’t exist and therefor failes to start.

Open the following file:

# nano -w /usr/local/psa/etc/modules/watchdog/monitrc.tpl

Find the following line:

set logfile /var/log/plesk/modules/monit.log

Change this line to and save the file:

set logfile /var/log/plesk/monit.log

Start watchdog. It should start without any errors.

hpacucli not detecting HP Smart Array Controller

In some cases hpacucli is not detecting the HP Smart Array Controller, in my case it was a HP P420 controller.

=> ctrl all show

Error: No controllers detected.


You can solve this issue by loading the sg module:

# modprobe sg

You’ll see now that the controller is detected:

=> ctrl all show

Smart Array P420 in Slot 2 (sn: XXXXXXXX)


MySQL crashing during startup

I just had a server on which I was not able to start MySQL.

The MySQL error log shows the following:

121121 18:30:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
121121 18:30:13 [Note] Plugin ‘FEDERATED’ is disabled.
121121 18:30:13  InnoDB: Initializing buffer pool, size = 8.0M
121121 18:30:13  InnoDB: Completed initialization of buffer pool
InnoDB: Log scan progressed past the checkpoint lsn 4 420487967
121121 18:30:13  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
InnoDB: Doing recovery: scanned up to log sequence number 4 420585640
InnoDB: 2 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1156938 row operations to undo
InnoDB: Trx id counter is 0 303173632
121121 18:30:14  InnoDB: Starting an apply batch of log records to the database…
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 17:30:14 UTC – mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338374 K  bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
stack_bottom = 0 thread_stack 0x40000
The manual page at contains
information that should help you find out what is causing the crash.
121121 18:30:14 mysqld_safe mysqld from pid file /var/lib/mysql/ ended

I tried to find the reason for this by enabling higher logging, but every time the error log was the same, until I discovered that the innodb_log_file_size was not big enough. I set it to 256MB and it solved the problem:


Plesk: Unable to connect to database: saved admin password is incorrect

Not able to log in to Plesk Panel. The following MySQL error is shown instead of the login screen:

ERROR: PleskFatalException
Unable to connect to database: saved admin password is incorrect.

0: common_func.php3:150
    psaerror(string ‘Unable to connect to database: saved admin password is incorrect.’)
1: auth.php3:107
ERROR: PleskFatalException
Unable to connect to database: saved admin password is incorrect.

0: common_func.php3:150
    psaerror(string ‘Unable to connect to database: saved admin password is incorrect.’)
1: auth.php3:107

This is caused because the password in file /etc/psa/.psa.shadow doesn’t match with with the admin password.

Reset the (MySQL) admin password using ch_admin_passwd. Run the following with root access:

# /usr/local/psa/admin/bin/ch_admin_passwd

Problem installing VMWare ESXi 5 on DL HP120 G7

It seems that HP DL120 G7 have difficulties with installing VMWare ESXi5 while ESXi4 is running fine.

During the installation it crashes with the following error message:

No place on disk to dump data.

This occurs because an option in the BIOS.

To fix the problem reboot your server into the BIOS and go to:

Power Management Options -> HP Power Regulator -> and set this option to: OS Control Mode

Solution for ip_conntrack: table full, dropping packet.

Today, I was working on a brand new  (apache) server, hosting a website with 3000 concurrent visitors. The load on the server was very low while the website was dropping network connections. I ran dmesg and the following message was repeating over and over:

ip_conntrack: table full, dropping packet.


It seems that ip_conntrack keeps track of what the state is of the connections and get filled up when you have a large amount of connections.

With the following command you can check the current tracked connections:

# cat /proc/sys/net/ipv4/netfilter/ip_conntrack_count


Probably the result is near to the maximum connections, which we can show with the following command:

# cat /proc/sys/net/ipv4/ip_conntrack_max


If you want to adjust this – you should do it to get rid of the ‘dropping packet message‘ – you can do this by running the following command:

# echo 131072 > /proc/sys/net/ipv4/ip_conntrack_max


If you want to make this value permanent you have to add the following line into /etc/sysctl.conf:

# net.ipv4.ip_conntrack_max=131072


Note: Adjust the value (131072) to your own wish, the higher the number, the more memory will be used.

Monitoring I/O on Linux

You can use iostat to find out disk utilization, but with iotop you can monitor the actual read/write. iotop watches the I/O usage information output by the kernel and displays it in a table of current I/O usage by processes.

iotop syntax for monitoring I/O usage

  • -o Will only show processes or threads which are actually doing I/O instead of showing all processes/threads.
  • -a Will show accumulated I/O instead of bandwith. With this syntax iotop shows the amount of I/O processes have done since iotop started.

If the -a syntax doesn’t work you have to update iotop to the latest version by installing it manually.


265 be/3 root          0.00 B     16.00 K  0.00 %  0.05 % [jbd2/sda5-8]
2567 be/4 root          0.00 B     23.73 M  0.00 %  0.00 % wget
24908 be/4 www-data      0.00 B      4.00 K  0.00 %  0.00 % apache2 -k start
1955 be/4 www-data      0.00 B     16.00 K  0.00 %  0.00 % apache2 -k start

Spamassassin: Block / blacklist an e-mail address

I am running Postfix on my Debian Linux server and using spamassassin to detect spam e-mails. However sometimes you just want to block all incoming e-mail from a domain name or e-mail address. With option ‘blacklist_from‘ in spamassassin this is very simple and useful.

Locate your spamassassin configuration file and open it with your text editor:

# find /etc -name
# nano -w /etc/spamassassin/

Now you have found your configuration file, simply add the following line to block all incoming e-mail from

blacklist_from *

Save your configuration file and restart spamassassin:

# /etc/init.d/spamassassin restart 

This is it! Simple eh??