It’s hard to install each option needed for a versatile video streaming script. Luckily the talented guys at ffmpeginstaller.com make an easy to use script to get FFMPEG and all of the extra tools installed.

First grab the auto installer file, you will need to right click the download button and choose to “copy link address” to get the latest version link. For example the current url now is:

http://mirror.ffmpeginstaller.com/old/scripts/ffmpeg8/ffmpeginstaller.8.0.tar.gz

So first run:

wget http://mirror.ffmpeginstaller.com/old/scripts/ffmpeg8/ffmpeginstaller.8.0.tar.gz

Then untar it:

tar -xvzf ffmpeginstaller.8.0.tar.gz

Then go into the folder:

cd ffmpeginstaller.8.0

Now run it!

./install.sh

It will ask you if you want to install everything, just choose yes.

It will install of these:

• ffmpeg
• Mplayer
• A52decoder
• Amrnb and AmrwbAll
• codecsfacc and faad2Rubyfdk-aacvo-aacencvo-amrwbenc
• flvtool2
• Git
• Mplayer
• Lame
• Libogg
• Libvorbis
• Libtheora
• Libspeex
• Libflac
• Libao
• Libwmf
• opencoreamr
• vorbistools
• X264
• MP4Box
• Xvidcore
• Yasm
• LibOggz
• Yamdi

The 

Error In Processing 451 Temporary Local

Problem is easy to fix just add the domain in the /etc/localdomains file.

It just means the domain is missing there.

You will need root access or to have your hosting company do this for you.

If your CPanel based server shows a website instead of the default Apache page you need to do three things.

Run these commands:

scripts/updateuserdomains

scripts/rebuildhttpdconf


Then reboot Apache in the WHM or by command:

service httpd restart

Cleaning up and making space on /usr

1. Restart the httpd service. This might free a little space some times.

2. Check for Apache logs like error_log, access_log , suexec_log in /usr/local/apache/logs . These can either be cleared off or if you need the logs then you can take a zipped copy and keep it aside.

3. Same can be done for the files in cPanel logs (/usr/local/cpanel/logs) as well .

4. Domlogs – Get into the /usr/local/apache/domlogs/ directory. Run the following command :-

# ls -al -SR | head -10 —> It will list 10 files in the decreasing order according to their size

If the domlog file is too large for a domain then it is possible that awstats is not running . Check whether cpanellogd is running on the server using pstree . If not, restart it .
Else, it is possible that awstats for only that particular domain is not updating. Get into the directory /usr/local/cpanel/base and check if any file as ‘awstats.domainname.com.conf’ exists. If yes , delete that file.

Now, run /scripts/runweblogs for that user. It will update the awstats and automatically clear the domlogs file thereafter. Do not delete the domlogs file itself.

5. Remove old and unwanted backups of ‘apache’ that might have been taken long ago. Also, check for any other duplicate folders that can be removed safely.

6. Remove core files, if any . Normally, some core files (like core.1234) might be present in /usr/local/cpanel/whostmgr/docroot . Check for these and remove them.

7. Restart your server, the quota might be off for that partition and reboot will correct it. Keep in mind if there is a hard drive error this can leave the server offline while the system or admin tuns a FSDK.

Cleaning up and making space on /var

Cpanel and Linux leaves a lot of log files in /var
After several years these can add up, especially in the cpanel/bandwidth folder. So a couple quick folder moves and symlinks can clean things up. This is assuming you have a /backup partition and some room in it.

1. Moving the log folder

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

2. Moving the cpanel bandwidth folder

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

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

4. You can use this command to find any other large folders:

du -ax –max-depth 1 /var | sort -n | tail

5. In some cases you just need to clean your mail queue

/usr/sbin/exiqgrep -i | xargs /usr/sbin/exim -Mrm

Other server cleaning tips:

1. Delete cPanel File Manager temp files

When users upload files in File Manager within cPanel, File Manager creates a temp file that may or may not get removed upon upload. You can remove these files using this command:

rm -fv /home/*/tmp/Cpanel_*
2.  Remove cPanel update archives

Cpanel and EasyApache updates tend to leave behind files that you probably don’t need. The following can be deleted or moved to a backup server to free up a little bit of space:

/usr/local/apache.backup*

/home/cpeasyapache (actual name may vary depending on cpanel version)

3.  Clean up Yum files

Yum updates leave package cache files on the server. You can clean up all unneeded yum files by running:

yum clean all

4. Remove pure-ftp partials

When your users upload files to the server via FTP when your server runs pureFTP as an FTP daemon, the FTP server creates temporary files starting with .pureftpd-upload* that get renamed the the actual filename when the upload completes. If the upload doesn’t complete, these files are left on the server. You can find and delete these by running:

locate .pureftpd-upload | xargs rm -fv

If you need to import or export a large mysql file, you can forget about phpmyadmin. I was stuck with a 2 gig file and needed a solution. The easiest and only way I could find was to upload the file through root with winSCP and run these command.

To export:
mysqldump --opt -Q -u username_username -p username_db > /home/dwhs_wrdprss1.sql

To import:
mysql -u username_username -p username_db < /home/dwhs_wrdprss1.sql

Firs you need to find the phpmyadmin php.ini file. Use this command to find all php.ini files:

find /usr -name php.ini

Then find the path to the php.ini file that is listed in the “phpmyadmin” folder.

Mine was

/usr/local/cpanel/3rdparty/etc/phpmyadmin

Next find these two section and change the limit how you want:

upload_max_filesize = 150M
AND
post_max_size = 150M

I wouldn’t go above 200

Than restart cpanel from the command line:

service cpanel restart

When you add your Vlan each port will need to be set to one of these:

no
tagged
untagged
forbid

Here is the definitions for each network switch Vlan setting:

Tagged:

Allows the port to join multiple VLANs.

Untagged:

Allows VLAN connection to a device that is configured for an untagged VLAN instead of a tagged VLAN. A port can be an untagged member of only one port-based VLAN.
A port can also be an untagged member of only
one protocol-based VLAN for any given protocol type.
For example, if the switch is configured with the default VLAN plus three protocol-based
VLANs that include IPX, then port 1 can be an untagged member of the default VLAN and one of the protocol-based VLANS.

No:

Appears when the switch is not GVRP-enabled; prevents the port from – or – joining that VLAN.

Auto:

Appears when GVRP is enabled on the switch; allows the port to
dynamically join any advertised VLAN that has the same VID

Forbid:

Prevents the port from joining the VLAN, even if GVRP is enabled on the switch.

If a customer happens to delete their emails you can still retrieve them from the cpanel backup system. This will take root access to move the files from the backup folder tot he customers account.

You can extract a backup archive and copy over the emails to an account’s existing mail directory. If restoring a backup archive, you will find emails located at:

/home/cpmove-username/homedir/mail/domain.com/email-account/

You can also find emails from the default account within:

/home/cpmove-username/homedir/mail/

The following thread is intended for manual migrations to cPanel, but it includes details about the maildir structure that will be useful to you:

Manual Migrations to cPanel

You can modify the following option in “WHM Home » Server Configuration » Tweak Settings” under the “Stats and Logs” tab:

“The interval, in days, to retain Exim stats in the database”

Reducing this value will decrease the amount of data that is stored in the Eximstats database.  If you decide to drop the eximstats tables completely, you can generate a new instance of the tables via:

/usr/local/cpanel/bin/updateeximstats

This simple command will list the inodes used for any group on the server:
repquota -a | head -n5 ; repquota -a | grep username
Just replace where it says “username” with the group or username you want to check.