Necessary packages for ffmpeg and ffmpeg-php Install
First run the command uname to find the arch
Then download rpmforge-release
rpm -Uhv http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm
yum clean all
yum update
yum install ffmpeg ffmpeg-devel
yum install mplayer mencoder
yum install gcc gmake make libcpp libgcc libstdc++ gcc4 gcc4-c++ gcc4-gfortran
yum install subversion ruby ncurses-devel ruby-libs
yum install flvtool2*
Run svn checkout:
svn checkout svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg
svn checkout svn://svn.mplayerhq.hu/mplayer/trunk mplayer
cd /usr/local/src/mplayer
svn update
cd /usr/local/src
Copy codecs for mplayer:
mv /usr/local/src/essential-20061022/* /usr/local/lib/codecs/
chmod -R 755 /usr/local/lib/codecs/
If you are using secure tmp:
mkdir /usr/local/src/tmp
chmod 777 /usr/local/src/tmp
export TMPDIR=/usr/local/src/tmp
For ffmpeg-php
wget http://downloads.sourceforge.net/project/ffmpeg-php/ffmpeg-php/0.6.0/ffmpeg-php-0.6.0.tbz2?use_mirror=nchc
tar -xjf ffmpeg-0.5.2.1.tbz2
phpize
./configure
make
make install
If we get an error given below while accessing phpMyAdmin.
Cannot start session without errors, please check errors given in your PHP and/or webserver log file and configure your PHP installation properly.
There can be error in writing session files. Either the owner do not have ‘write’ permission or the owner is different.
Solution
Normally tmp directories are used to dump sessions. And phpMyAdmin has its own tmp folder. Check the permission and ownership of this folder. Change it to the following
Location : /var/cpanel/userhomes/cpanel-phpmyadmin
cd /var/cpanel/userhomes/cpanel-phpmyadmin
1)Permission of tmp must be 700
2)Ownership must be cpanel-phpmyadmin
chown cpanel-phpmyadmin: -R *
The output should look similar to as given below
ll /var/cpanel/userhomes/cpanel-phpmyadmin/
total 16
drwx–x–x 4 cpanel-phpmyadmin cpanel-phpmyadmin 4096 Mar 10 23:56 ./
drwx–x–x 5 root root 4096 Mar 10 23:53 ../
drwxr-x— 2 cpanel-phpmyadmin cpanel-phpmyadmin 4096 Mar 10 23:53 mail/
drwx—— 2 cpanel-phpmyadmin cpanel-phpmyadmin 4096 Mar 10 23:56 tmp/
Exim Message Reception and Delivery log files
Exim writes three different logs, referred to as the main log, the reject log, and the panic log.
/var/log/exim_mainlog ( Linux )
/var/log/exim/mainlog (FreeBSD)
The main log records the arrival of each message and each delivery in a single line in each case. The format is as compact as possible, in an attempt to keep down the size of log files. Two-character flag sequences make it easy to pick out these lines. A number of other events are recorded in the main log. Some of them are optional, in which case the log_selector option controls whether they are included or not. A Perl script called eximstats, which does simple analysis of main log files, is provided in the Exim distribution.
The above log files receives an entry every time a message is received or delivered.
Rejections based on ACLs/Policies: Receives an entry every time a message is rejected based on either ACLs or other policies (for example, aliases configured to :fail:)
/var/log/exim_rejectlog ( Linux )
/var/log/exim/rejectlog (FreeBSD)
The reject log records information from messages that are rejected as a result of a configuration option (that is, for policy reasons).
Finding Exim Unexpected or Fatal Errors
The below log file 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.
/var/log/exim_paniclog ( Linux )
/var/log/exim/paniclog (FreeBSD)
When certain serious errors occur, Exim writes entries to its panic log. If the error is sufficiently disastrous, Exim bombs out after-wards. Panic log entries are usually written to the main log as well, but can get lost amid the mass of other entries. The panic log should be empty under normal circumstances. It is therefore a good idea to check it (or to have a cron script check it) regularly, in order to become aware of any problems.
Reference:
General Information and Configuration for Exim Logs:
http://exim.org/exim-html-current/doc/html/spec_html/ch49.html
Auditing cPanle/WHM Apache 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
This log file 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.
How to check domain access logs
/usr/local/apache/domlogs/domain.com
The general access log for each domain configured with cPanel.
