We have been getting number of attack reports from clients with Wordpress installs and further investigating we found a global attacks on wordpress.
Right now there is a very severe and global attack on all Wordpress sites on the Internet and almost all hosting providers are affected. The attack is a brute-force attack which is global and highly distributed, This attack is well organized and again very, very distributed; we have seen high number of spoofed IP addresses involved in this attack. As the IP’s are spoofed, blocking the IP’s does not help much.
If you need any asisstance in blocking this attacks please submit a 1x Hour of Support plan and we will help you right after!
Don’t hesitate to contact us if you have any questions or need further assistance.
How can I force fsck on next boot
You can force an automatic full check by changing the check interval using tune2fs (-c and/or -i).
-c max-mount-counts
Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel.
-i interval-between-checks[d|m|w]
Adjust the maximal time between two filesystem checks. No postfix or d result in days, m in months, and w in weeks. A value of zero will disable the time-dependent checking.
It is strongly recommended that either -c (mount-count-dependent) or -i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem.
The above command would tell the init scripts to run fsck on hda2 at every boot.
# tune2fs -i 1d /dev/hda2
The above command would tell the init scripts to run fsck on hda2 after 1 day.
If you only want to run fsck on the next boot, please execute the following as the root user.
This will only run the file system check on the next reboot. By touching the file “forcefsck” in the / directory, it will force the system to perform a full file system check.
The file “forcefsck” will be deleted automatically after fsck is finished.
How to force php files to use CLI
To force php files to use CLI (on the assumption your default php version uses suPHP) create an .htaccess file in your public_html directory, with the following:
<FilesMatch “\.php$”>
AddHandler application/x-httpd-php .php
</FilesMatch>
As of version 4.3.0, PHP supports a new SAPI type (Server Application Programming Interface) named CLI which means Command Line Interface. As the name implies, this SAPI type main focus is on developing shell (or desktop as well) applications with PHP. There are quite a few differences between the CLI SAPI and other SAPIs which are explained in this chapter. It’s worth mentioning that CLI and CGI are different SAPI’s although they do share many of the same behaviors.
The list of command line options provided by the PHP binary can be queried anytime by running PHP with the -h switch
More: http://in2.php.net/manual/en/features.commandline.php
Force fsck on next boot on Red Hat Enterprise Linux
If you only want to run fsck on the next boot, execute the following as the root user:
The file “forcefsck” will be deleted automatically after fsck is finished.
This will only run the file system check on the next reboot. By touching the file “forcefsck” in the / directory, it will force the system to perform a full file system check.
You can force an automatic full check by changing the check interval using tune2fs (-c and/or -i). For example:
The below command would tell the init scripts to run fsck on hda2 at every boot.
*tune2fs - adjust tunable filesystem parameters on ext2/ext3 filesystems
Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel.
Set the number of times the filesystem has been mounted. If set to a greater value than the max-mount-counts parameter set by the -c option, e2fsck(8) will check the filesystem at the next reboot.
-i interval-between-checks[d|m|w]
Adjust the maximal time between two filesystem checks. No post fix or d result in days, m in months, and w in weeks. A value of zero will disable the time-dependent checking.
It is strongly recommended that either -c (mount-count-dependent) or -i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem.
