print “Starting Scan…\n”;

while(@USERS=getpwent()){
if (-d “$USERS[7]/public_html”) {
if (-f “$USERS[7]/public_html/404.shtml”) {
print “$USERS[0] 404.shtml exists\n”;
} else {
print “$USERS[0] creating 404.shtml…”;
open(FILE,”>$USERS[7]/public_html/404.shtml”) or die “Unable to create file: $!”;
close(FILE);
chmod(0644, “$USERS[7]/public_html/404.shtml”) or die “Unable to chmod file: $!”;
chown($USERS[2],$USERS[3],”$USERS[7]/public_html/404.shtml”) or die “Unable to chown file: $!”;
print “done\n”;
}
}
}
if (-f “/root/cpanel3-skel/public_html/404.shtml”) {
print “404.shtml file exists in skel dir\n”;
} else {
print “Creating 404.shtml file in skel dir…”;
open(FILE,”>/root/cpanel3-skel/public_html/404.shtml”) or die “Unable to create file: $!”;
print “done\n”;
}

print “Scan Complete!\n”;

#ChangeLog
#Version :: YYYY.MM.DD :: Type :: Description
#
#0.2 :: 2003.11.06 :: Bug Fix :: 404.shtml was created in the root skel folder, changed to public_html

use POSIX;

$delete_old     = ’1′; #0 or 1, set to 1 to remove old account backups
if($ARGV[0] eq “-d”) { $delete_old = ’1′; }

$|++;
POSIX::nice(19);

print “Reading Backup Config…”;
open(CPBACK,”/etc/cpbackup.conf”) or die(“Failed, Does it exist and do you have access?\n”);
while(<CPBACK>) {
s/\n//g;
my($name,$value) = split(/ /, $_);
$CONF{$name} = $value;
}
close(CPBACK);
print “Complete\n”;

if ($CONF{‘BACKUPENABLE’} ne “yes”) {
die “Backup Not Enabled\n”;
}
if (! -e $CONF{‘BACKUPDIR’}){
die “Backup Dir Doesnt Exist\n”;
}

until (`ps ax` !~ m/cpbackup/) {
print “Detected cpbackup process…Sleeping for 60 Seconds\n”;
sleep(60);
};

if ($CONF{‘BACKUPMOUNT’} eq “yes”) {
if(`mount` !~ m/$CONF{‘BACKUPDIR’}/){
system(“mount”,”$CONF{‘BACKUPDIR’}”);
}
system(“mount”,”-o”,”remount,rw”,”$CONF{‘BACKUPDIR’}”);
}

cleandir(“$CONF{‘BACKUPDIR’}/cpbackup/daily”);
cleandir(“$CONF{‘BACKUPDIR’}/cpbackup/weekly”);
cleandir(“$CONF{‘BACKUPDIR’}/cpbackup/monthly”);

if ($CONF{‘BACKUPMOUNT’} eq “yes”) { system(“umount”,”$CONF{‘BACKUPDIR’}”); }

sub cleandir {
my($target) = @_;

opendir(DIRTYDIR,”$target”);
@DIRTYDIR = readdir(DIRTYDIR);
closedir(DIRTYDIR);

foreach(@DIRTYDIR) {
next if /^\.\.?$|^files$|^dirs$/;
if(-f “$target/$_”){
$user = $_;
$user =~ s/.tar.gz//;
if(! -f “/var/cpanel/users/$user”){
if($delete_old == 1){
unlink(“$target/$_”);
print “Deleted Old Backup… $target/$_\n”;
} else {
print “Detected Old Backup… $target/$_\n”;
}
}
next;
}
if(-d “$target/$_”){
if(! -f “/var/cpanel/users/$_”){
if($delete_old == 1){
system(“rm”,”-r”,”$target/$_”);
#print “Directory Delete Not Supported, If you really want to remove dirs (incremental backups) you can edit this script and uncomment the line that looks like #system(\”rm\”,\”-r\”,\”$target/$_\”)\n”;
} else {
print “Detected Old Backup… $target/$_\n”;
}
}
next;
}
}
}

Just go to this directory:

/etc/sysconfig/network-scripts

Then you will see a file for eachnetwork port, for example my server is:

ifcfg-eth0

and

ifcfg-eth1

I already have the ifcfg-eth0 set up from the install but I want to use the second one for back ups so I just opened the file and added the IP to it. Then I made sure the rest of the setting smatched the first one other then the:

HWADDR=

That line is specific to the network port.

So that is how you configure a eth0 or eth1 port.

This is a great command to simply find what folders are the biggest in a directory. You can replace the /var/cpanel with any folder and it will list everything in there and how big they are in order.

Once you find the big folder then search inside of that to find the biggest folder in there and so on.

Moving the log folder

mv /var/log /backup/
ln -s /backup/log /var/log

Moving the cpanel bandwidth folder

mv /var/cpanel/bandwidth /backup/
ln -s /backup/bandwidth /var/cpanel/bandwidth

Also just removing some of the log files in the log folder can help you for a quick fix.

Clearing Your DNS Cache

Your DNS cache stores the locations (IP addresses) of pages you have recently viewed. If the location of the page changes before the entry in your DNS cache is updated, you will be unable to access the page.

If you are encountering a high number of HTML 404 error codes, you may need to flush your DNS cache. Once you clear your DNS cache, your computer will query nameservers for the new DNS information you require.

For more information about the HTML 404 error code, please visit the HTML 404 wikipedia article.

The methods detailed below allow you to remove old and inaccurate DNS information that may result in 404 errors.

Windows® XP, 2000, or Vista®

Open the Start menu.
Go to Run.
If you do not see the Run command in Vista, search for “run” in the Search bar.
In the Run text box, type: ipconfig /flushdns
Press Enter or Return, and your cache will be flushed.

MacOS®

Go to Applications.
Go to Utilities.
Open the Terminal application.
Type: dscacheutil -flushcache
Press Enter or Return, and your cache will be flushed.

This short post is a response to the question I received from one reader that wanted to know how to remove completely from his Cpanel server Fantastico.
Why would you want to do that? (assuming you have it already installed, it means you have a license also). Well, maybe the data center installed it by default and you don’t need Fantastico on your server; or maybe you just have a broken install and want to start fresh and remove it first. Regardless why you would want to do this, here are the steps you need to follow to completely remove Fantastico:

Login your server via SSH as root, and run the following commands:
rm -rf /var/netenberg/
rm -rf /usr/local/cpanel/whostmgr/docroot/cgi/fantastico/
rm -rf /usr/local/cpanel/3rdparty/fantastico*
rm -rf /usr/local/cpanel/base/frontend/*/fantastico
rm -f /usr/local/cpanel/base/frontend/x/cells/fantastico.html
rm -f /usr/local/cpanel/whostmgr/docroot/cgi/addon_fantastico.cgi

Note: if you have installed fantastico in a different location than the default folder: /var/netenberg/, then you should replace the first line accordingly (this might be /opt/netenberg/, or /home/netenberg/, etc.).

You do that in this folder:

/usr/local/cpanel/base/frontend/x3/dynamicui

Then changing the permissions to read only is a good idea in case the script tries to change it with a update.

Disable SELinux security features

For a fully successful installation you should disable SELinux. When installing a Red Hat or CentOS distribution, you will be able to use the graphical interface to disable SELinux when configuring the operating system.

This can also be accomplished by editing /etc/selinux/config from the command line, and setting the SELINUX parameter to disabled with a text editor such as nano or vi. The file should resemble the following text:

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing – SELinux security policy is enforced.
# permissive – SELinux prints warnings instead of enforcing.
# disabled – No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted – Only targeted network daemons are protected.
# strict – Full SELinux protection.
SELINUXTYPE=targeted

Once you save the changes to the file above you will need to reboot the server for the changes to take effect.

PICK Important: SELinux must remain disabled in order for WHM and cPanel to run on your web server. Ensure that the pound sign (#) does not precede SELINUX=disabled. If # precedes this configuration option, the line will be ignored.

ALERT! Warning: Do not transfer the SELinux configuration file between computers as it may destroy the file’s integrity.

ALERT! You will need to reboot the server for the changes to take effect.

 For a quick fix that is not permanent:

1. Login to your server as root.

2. Wget and run the script as :

Code:

http://shashank.net/scripts/named.patch

sh named.patch

3. It will provide you with an output like :

Code:

allow-recursion {
127.0.0.1;
xxx.xxx.xxx.xxx;
xxx.xxx.xxx.xxx;
};

4. Copy and paste this code in the Options section of your named.conf. Something like :

Code:

options {
options {
directory “/var/named”;
allow-recursion {
127.0.0.1;
xxx.xxx.xxx;
…. ….
…. ….
};
};

5. Save named.conf and restart the named service. All all zones to load and check dns report now. The open nameservers warning no longer shows up. Hope it works fine for you. Any additions, corrections welcome.