| Posted by smashrc, 12-22-2009, 12:06 PM | | I'm using WHM/Cpanel VPS account, I want to know what kind of logs I should always check to keep my site healthy.
For example, mysql log. what else?? thanks I'm new to this area.
|
| Posted by njoker555, 12-22-2009, 12:21 PM | | most logs are set up automatically - apache logs and error logs will help you determine issues with your site. cpanel log telling you if anything is wrong there. Exim log to make sure no one is using your server to send out a crapload of spam, etc.
|
| Posted by VIPoint, 12-22-2009, 03:48 PM | | Location to log files on the server
cPanel
cPanel/WHM Initial Installation Errors:
* /var/log/cpanel*install* - These log files contain verbose logs of the cPanel installation, and should be the first point of reference for any issues which might occur ‘out of the box’ with new cPanel installations
cPanel/WHM Requests and Errors:
* /usr/local/cpanel/logs/error_log - cPanel logs any error it incurs here. This should always be the first place you look when you encounter errors or strange behavior in cPanel/WHM.
* /usr/local/cpanel/logs/license_log - All license update attempts are logged here. If you run into any license errors when logging in, check here.
* /usr/local/cpanel/logs/stats_log - The stats daemon (cpanellogd) logs the output from all stats generators (Awstats, Webalizer, Analog) here.
* /usr/local/cpanel/logs/access_log - General information pertaining to cPanel requests is logged here (Client Information, Request URI)
cPanel/WHM Update Logs:
* /var/cpanel/updatelogs/update-[TIMESTAMP].log - Contains all output from each upcp. Named with the timestamp from which the upcp process was executed.
Service Status Logs:
* /var/log/chkservd.log - The service monitoring daemon (chkservd) logs all service checks here. Failed services are represented with a [-], and active are represented with [+].
Apache
General Error and Auditing Logs:
* /usr/local/apache/logs/error_log - All exceptions caught by httpd, along with standard error output from CGI applications are logged here. The first place you should look when httpd crashes, or you incur errors when accessing a website.
* /usr/local/apache/logs/suexec_log - Contains auditing information reported by suexec each time a CGI application is executed. If you receive an internal server error, with no relevant information being reported to the Apache error_log, check here for potential suexec policy violations.
Domain Access Logs:
* /usr/local/apache/domlogs/domain.com - The general access log for each domain configured with cPanel.
Exim
Message Reception and Delivery:
* /var/log/exim_mainlog ( Linux ), /var/log/exim/mainlog (FreeBSD) - Receives an entry every time a message is received or delivered
Rejections based on ACLs/Policies:
* /var/log/exim_rejectlog ( Linux ), /var/log/exim/rejectlog (FreeBSD) - Receives an entry every time a message is rejected based on either ACLs or other policies (for example, aliases configured to :fail
Unexpected or Fatal Errors:
* /var/log/exim_paniclog ( Linux ), /var/log/exim/paniclog (FreeBSD) - Receives all entries exim doesn’t know how to handle. It’s generally a really bad thing when log entries are being written here, and they should be thoroughly investigated.
IMAP/POP/SpamAssassin
General Logging and Errors:
* /var/log/maillog
* /var/log/messages
The IMAP, POP, and SpamAssassin services all log here. This includes all general logging information (login attempts, transactions, spam scoring), along with fatal errors.
FTP
Logins and General Errors:
* /var/log/messages - General information and login attempts are logged here.
FTP Transactions:
* /var/log/xferlog - Is a symbolic link in most cases to /usr/local/apache/domlogs/ftpxferlog, which contains a history of the transactions made by FTP users.
MySQL
General Information and Errors:
* /var/lib/mysql/$(hostname).err - This path could vary, but is generally located in /var/lib/mysql. Could also be located at /var/log/mysqld.log
|
| Posted by mellow-h, 12-22-2009, 06:53 PM | | Logs are going to help you in finding fatal issues. If you meant healthy as performance, then most likely you need to use some server parameter like IO wait, CPU Usage, Throughput etc. I personally find wormly.com health monitoring service is a lot handy in this case.
|
| Posted by smashrc, 12-22-2009, 11:49 PM | | Thank you very much everyone. Both logging and performance monitor are very useful for me. Thanks!!
I'm trying to intsall the viewlog script athttp://www.logview.org/content/view/5/26/
I want to know what is the line 4 mean? ./logview-install
What is ./ means?
thanks
|
| Posted by MikeDVB, 12-23-2009, 12:02 AM | | is current directory.
So if you change directory to /usr/src:
cd /usr/src
and then you run "./dosomething.sh" it would be doing the following:
/usr/src/dosomething.sh
|
| Posted by smashrc, 12-23-2009, 12:14 AM | | I see I see thank you.
I'm newbie in linux. I want to know which directory should I install the Logview script? thanks
http://www.logview.org/content/view/5/26/
|
| Posted by smashrc, 12-23-2009, 02:10 AM | | Anybody please tell me where I should install? thanks
|
| Posted by MikeDVB, 12-23-2009, 02:13 AM | | I'm not familiar with that script but really all you need to do is turn on log rotation inside of WHM and then just knowing which log to check when you face a certain issue.
|
| Posted by inspiron, 12-23-2009, 11:34 AM | | usr/local/cpanel/logs
/usr/local/apache/logs
chk those location mostly.
|
| Posted by VIPoint, 12-23-2009, 01:30 PM | | smashrc,
Download the script in /usr/local/src and then unzip it and run the .sh file. The files will be automatically copied to the required locations
|
| Posted by CrazyTech, 12-23-2009, 03:26 PM | | I can recall the excitement that came along with my first server, and honestly you don't have to strictly monitor the logs; just reading them for the heck of it won't always tell you a lot. You'll find that with a bunch of servers, this is not plausible nor even possible if the number grows large enough. I'd suggest approaching things from a monitoring perspective; setup automated resources to monitor things and then use the logs as needed to investigate issues. The goal is to automate as many tasks as possible in most instances so that you can handle the issues as they come in. With a site or application, your best served by actually using the thing and using the logs to maybe figure out a slow query or optimization issue as a couple of examples.
|
|
 Add to Favourites
 Print this Article
|
