Fixing Log Rotation Problems
Since installing cpanel on some of our server, we noticed the logs in /usr/local/apache/logs/* growing out of control without ever being rotated. In /etc/logrotate.d the script called "httpd" is the reason why. Its totally wrong. Its looking for files located in /var/log/httpd/ and that is not where my log files are located. In fact, we dont even have files in this directory. Its completely empty.
If you’re tired of seeing your /var/log/messages log file full of dropped traffic from APF firewall then we have a solution! We’ll create a separate log file for TCP/UDP OUTPUT and drops which will leave your messages log nice and clean for easy browsing!
Common Macromedia Flash Player Install Issues
Choose the most appropriate question below to help solve your issue:
Blocking and preventing brute force attacks is one of the main things you want to do on your web server to add a layer of security. While someone might not be targeting your site or server specifically, they will have automated tools that will try to guess random usernames and passwords that are common against your system. They’re essentially forcing their way to user only authorized area’s of a system, such as FTP accounts, e-mail accounts, databases, script based administration areas and root or any shell access are most common attempts. They will try multiple login attempts, guessing usernames and passwords, trying to force their way onto your machine.
RESOLUTION: When mail should be delivered off-server for a domain, the domain should be:
1. Removed from /etc/localdomains
2. Added to /etc/remotedomains
optional: then run /scripts/mailperm
Basic things that can be done to improve security.
There are numerous ports that should be open on your cPanel server, this document will try to maintain and up to date record of all of these ports:
Setting up your own nameservers can be a nightmare.
Ã‚Â See this if you're having trouble printing code examples
by Adam Pedersen
I'm getting to know far more about servers than I ever wanted to, after hundreds of hours of Google research trying to squeeze/beat performance out of Apache. I do have 15 years programming experience in other areas, and I've reached the conclusion that the only experts in Apache/Linux are the programmers who wrote (and poorly documented) all this stuff. So I've gathered everything I could learn after countless hours of frustration and I'm writing this up in return for the immense amount of help I've received from the documentation of others.
Nate Davis - firstname.lastname@example.org
Last Edited: January 12th 2004
Everything is there , and the best part is, it is not cryptic like DJB's page!
This is a combination of posts I have used in the past and have adapted to provide an excellent DNS solutions.
The prerequisites for this are just Two Servers and in this implementation 4 IP's(2 per server) as it makes it more understandable. Also you will require a web accessible domain on each server.
Basically it will allow you to use a combination of two servers to do your DNS for you one being the primary and one the secondary. You could use this for every two sets of servers you own OR possibly adapt it so that all your servers use just the two sets.
It is my intention to eventually use this solution so that DJBDns is used instead of Bind because it is so flakey and buggy in my opinion.
DJB has a $500 reward for any exploits discovered thats how good it is!
Anyway enough chat lets get down to business....................
What we are aiming for is the following set up
NS1.JOELMOSS.COM PRIMARY NS FOR SERVER 1 ON SERVER 1
NS2.JOELMOSS.COM SECONDARY NS FOR SERVER 1 ON SERVER 2
NS3.JOELMOSS.COM PRIMARY NS FOR SERVER 2 ON SERVER 2
NS4.JOELMOSS.COM SECONDARY NS FOR SERVER 2 ON SERVER 1
good place to test your nameserver...
HOW-TO: Setting up Nameservers w/o Using Primary Server IP
There have been a number of threads with various bits and pieces of this process, but I haven't seen the entire thing in one place, so here goes. As always, modifying your server is done at your own risk and I accept no responsibility for anything that may happen.
you can disable exim's virus scanner in the following way:
in /etc/exim.conf find #!!# message_filter renamed system_filter
system_filter = /etc/antivirus.exim
change it to
#!!# message_filter renamed system_filter
#system_filter = /etc/antivirus.exim
In this tutorial you will learn how to modify the Cpanel bandwidth exceeded page. This page is shown for clients automatically when they run out of bandwidth. Bandwidth counts are reset every month.
This guide will show you the ropes in how to setup cpanel nameservers and configure them properly so you can run ns1 and ns2.yoursite.com. Once your nameservers are setup clients can then use your own private nameservers for their domains.
1. Regiser your domain
Register the domain name you would like to use, you can register a domain here if you need one.This domain will be used as your nameservers - eg ns1.yourdomain.com and ns2.yourdomain.com
2. Additional IPs
Have 2 available IP addresses for your server that aren't in use.You will need to contact you provider to obtain these IP addreses.
3.Ã‚Â Registering theÃ‚Â NameserversÃ‚Â Ã‚Â
Now login to your domain management page for the domain you registered and Ã‚Â register ns1.newdomain.com and ns2.newdomain.com as nameservers (registries normally have a special facility for doing that). The registry may also have a facility to propogate these nameservers around the foreign registries - if so, you should use this facility.
This guideÃ‚Â assumes you already have Cpanel installed......this is meant to be a breif overview of some important features - not a complete WHM guide - that should be the responsibility of DarkOrb (www.cpanel.net/>)
If you do not have Cpanel installed please read the guide from DarkOrb - http://cpanel.net/docs.htm
exclude=mod_ssl* httpd* perl mysql* php* spamassassin*