Before you begin

You can find documentation for creating custom modules your server at WHM > EasyApache > Help > Cpanel::Easy Framework POD, or and via command line at /scripts/easyapache --perldoc.

You can download a few sample custom modules below. These modules are not likely to be included in EasyApache in the near future.

Important: If you have problems building Apache with your custom modules, and you are unable to troubleshoot the problem, run /scripts/easyapache --skip-custom-optmods to build Apache and PHP without any custom modules. (Or, access the WHM equivalent found in EasyApache’s Help section).

Custom modules

Installing a custom module

To install a custom module:

1. Download and unzip it into /var/cpanel/easy/apache/custom_opt_mods/.
2. When logged into your server as root, you can install any module listed below by running the following commands. Be sure to replace $NAME.tar.gz with the filename of the module you wish to download:

wget http://easyapache.cpanel.net/optmods/$NAME.tar.gz
tar -C /var/cpanel/easy/apache/custom_opt_mods -xzf $NAME.tar.gz


Removing a custom module

In order to remove a custom module from the server, simply delete the files you created when you issued the above commands. The module will be removed from all future builds and the EasyApache interface.

Available modules

Warning: cPanel does not provide support for custom modules, including the ones linked below. The following modules are not developed by cPanel, Inc. Use them at your own risk.

mod_auth_mysql — This module allows you to authenticate users and authorize access through a MySQL database.

• Download: custom_opt_mod-mod_auth_mysql.tar.gz
• mod_auth_mysql project page.

mod_GeoIP — This module looks up the IP address of the client web user in the GeoIP database.

• Download: custom_opt_mod-mod_geoip.tar.gz
• mod_GeoIP project page

mod_python — This module embeds the Python interpreter into Apache, for faster Python applications.

• Download: custom_opt_mod-mod_python.tar.gz
• mod_python project page

GD with JIS-mapped Japanese font support — This module provides JIS-mapped Japanese font support for the GD library under PHP5.

• Download: custom_opt_mod-php5-gd_jis_mapped_japanese_font_support.tar.gz

Turkish locale patch for PHP5 — This module improves PHP5 support for Turkish.

• Download: custom_opt_mod-php5-turkish_locale_patch.tar.gz

suPHP PAM patch — This module allows you to use limits (/etc/security*.conf) with suPHP.

• Download: custom_opt_mod-suphp_pam_patch.tar.gz
• suPHP PAM patch information

Source: http://twiki.cpanel.net/twiki/bin/view/EasyApache3/CustomMods

Incoming search terms:

• easyapache how to make custom module (1)
• install easyapache on centos (1)
• linux download mod_python tar gz (1)

You can use /proc file system or the lsof command to find all the file descriptors used by a process.

/proc File System Example

Find out process ID using the ps command, enter:
# ps aux | grep processName
# ps aux | grep mysqld
Sample outputs:

root 3632 0.0 0.0 65944 1296 ? S Jun05 0:00 /bin/sh /usr/bin/mysqld_safe –datadir=/var/lib/mysql –socket=/var/lib/mysql/mysql.sock –log-error=/var/log/mysqld.log –pid-file=/var/run/mysqld/mysqld.pid –user=mysql
mysql 3679 9.0 8.9 1393476 733756 ? Sl Jun05 3448:12 /usr/libexec/mysqld –basedir=/usr –datadir=/var/lib/mysql –user=mysql –pid-file=/var/run/mysqld/mysqld.pid –skip-external-locking –socket=/var/lib/mysql/mysql.sock
root 44723 0.0 0.0 61188 820 pts/0 S+ 17:48 0:00 grep mysqld

You can also use the pidof command as follows to find out the process id’s (pids) of the named programs:
# pidof processName
# pidof mysqld
Sample outputs:

3679

Note down the PID # 3679.

/proc/$pid/fd Directory Example

Type the following command:
# ls /proc/3679/fd
# ls -l /proc/3679/fd
Sample outputs:

total 0
lr-x—— 1 root root 64 Jul 1 13:09 0 -> /dev/null
l-wx—— 1 root root 64 Jul 1 13:09 1 -> /var/log/mysqld.log
lrwx—— 1 root root 64 Jul 1 13:09 10 -> socket:[14667]
lrwx—— 1 root root 64 Jul 1 13:09 100 -> /var/lib/mysql/blogdb/wp_term_relationships.MYI
lrwx—— 1 root root 64 Jul 1 13:09 101 -> /var/lib/mysql/blogdb/wp_postmeta.MYI
lrwx—— 1 root root 64 Jul 1 13:09 102 -> /var/lib/mysql/blogdb/wp_terms.MYI
lrwx—— 1 root root 64 Jul 1 13:09 103 -> /var/lib/mysql/orders/discussionread.MYD
lrwx—— 1 root root 64 Jul 1 13:09 104 -> /var/lib/mysql/orders/comments.MYI
lrwx—— 1 root root 64 Jul 1 13:09 105 -> /var/lib/mysql/orders/useractivation.MYI
lrwx—— 1 root root 64 Jul 1 13:09 106 -> /var/lib/mysql/orders/postparsed.MYI
lrwx—— 1 root root 64 Jul 1 13:09 107 -> /var/lib/mysql/orders/sigparsed.MYI
lrwx—— 1 root root 64 Jul 1 13:09 108 -> /var/lib/mysql/support/forum.MYI
……
…….
…
(output truncated)

lsof command Example

Type the command as follows:
# lsof -a -p {PID-HERE}
# lsof -a -p 3679
Sample outputs:

COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
mysqld 3679 mysql cwd DIR 8,2 4096 7667720 /var/lib/mysql
mysqld 3679 mysql rtd DIR 8,2 4096 2 /
mysqld 3679 mysql txt REG 8,2 7721832 15185707 /usr/libexec/mysqld
mysqld 3679 mysql mem REG 8,2 13074466 /lib64/ld-2.5.so (path inode=13074445)
mysqld 3679 mysql mem REG 8,2 13074602 /lib64/libc-2.5.so (path inode=13074454)
mysqld 3679 mysql mem REG 8,2 13074603 /lib64/libdl-2.5.so (path inode=13074461)
mysqld 3679 mysql mem REG 8,2 13074608 /lib64/libm-2.5.so (path inode=13074464)
mysqld 3679 mysql mem REG 8,2 13074612 /lib64/libpthread-2.5.so (path inode=13074491)
mysqld 3679 mysql mem REG 8,2 85928 15193367 /usr/lib64/libz.so.1.2.3
mysqld 3679 mysql mem REG 8,2 247496 13074620 /lib64/libsepol.so.1
mysqld 3679 mysql mem REG 8,2 95464 13074623 /lib64/libselinux.so.1
mysqld 3679 mysql mem REG 8,2 13074615 /lib64/librt-2.5.so (path inode=13074500)
mysqld 3679 mysql mem REG 8,2 13074618 /lib64/libnsl-2.5.so (path inode=13074469)
mysqld 3679 mysql mem REG 8,2 13074633 /lib64/libcrypt-2.5.so (path inode=13074459)
mysqld 3679 mysql mem REG 8,2 1366272 13074653 /lib64/libcrypto.so.0.9.8e
mysqld 3679 mysql mem REG 8,2 13074655 /lib64/libresolv-2.5.so (path inode=13074496)
mysqld 3679 mysql mem REG 8,2 58400 13074610 /lib64/libgcc_s-4.1.2-20080825.so.1
mysqld 3679 mysql mem REG 8,2 10000 13074666 /lib64/libcom_err.so.2.1
mysqld 3679 mysql mem REG 8,2 15193399 /usr/lib64/libk5crypto.so.3.1 (path inode=15186140)
mysqld 3679 mysql mem REG 8,2 9728 13074658 /lib64/libkeyutils-1.2.so
mysqld 3679 mysql mem REG 8,2 15193402 /usr/lib64/libgssapi_krb5.so.2.2 (path inode=15186013)
mysqld 3679 mysql mem REG 8,2 15193397 /usr/lib64/libkrb5support.so.0.1 (path inode=15186147)
mysqld 3679 mysql mem REG 8,2 15193400 /usr/lib64/libkrb5.so.3.3 (path inode=15184571)
mysqld 3679 mysql mem REG 8,2 976312 15180443 /usr/lib64/libstdc++.so.6.0.8
mysqld 3679 mysql mem REG 8,2 315032 13074667 /lib64/libssl.so.0.9.8e
mysqld 3679 mysql mem REG 8,2 13074479 /lib64/libnss_files-2.5.so (path inode=13074476)
mysqld 3679 mysql 0r CHR 1,3 4102 /dev/null
…..
..
…
mysqld 3679 mysql 234u REG 8,2 0 7700867 /var/lib/mysql/order/subscribediscussion.MYD
mysqld 3679 mysql 238u REG 8,2 2048 7700637 /var/lib/mysql/email/mailqueue.MYI
mysqld 3679 mysql 239u REG 8,2 79060 7700593 /var/lib/mysql/email/mailqueue.MYD
mysqld 3679 mysql 340u REG 8,2 17690624 7766217 /var/lib/mysql/blogdb/wp_posts.MYI

To see statistics on file descriptors used, enter:
# cat /proc/3679/net/sockstat
Sample outputs:

sockets: used 183
TCP: inuse 5 orphan 0 tw 0 alloc 9 mem 2
UDP: inuse 9 mem 1
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0

Please note that on older kernel such as those shipped with RHEL 5 or Suse 9 or Debian 4 or 5 use system wild statistics file descriptors file called /proc/net/sockstat:
# cat /proc/net/sockstat
Sample outputs:

sockets: used 455
TCP: inuse 146 orphan 0 tw 673 alloc 146 mem 9
UDP: inuse 14 mem 0
RAW: inuse 0
FRAG: inuse 0 memory 0

Incoming search terms:

• plesk lsof (1)

When deciding when and how to create an index in your MySQL database, it’s important to consider how the data is being used.

Let’s say you have a database of employees. We will create it like this:

CREATE TABLE employees (
ID INT,
name VARCHAR(60),
salary decimal(10,2),
date hired(date)
)

So you will notice that this table is pretty simplistic, and doesn’t really contain all the info you would need to actually manage employees, but its just for the sake of demonstration, and you could always add more later, or even make another table and use joins if you had really complex needs.

For now we will go over these real quick.

The ID is basically just a number (INT) which can hold a very large number. If this were real world I would probably make it unsigned, since you will never have a negative employee ID – but either way, you will never reach the number of employees it would take to get to the number that would fill up an INT.

Even unsigned int will hold values up to 2,147,483,647. So if you have 2 billion employees, you would probably not be a developer anymore  .

You might want to consider making the field an auto increment, and primary key, the auto increment depending on how data will be entered into this database.

Name is a simple varchar(60) which should cover most people’s names.

Salary is a decimal with 10 total digits, two on the right hand side of the decimal point. This would handle a salary of up to 99,999,999.99 – again, you’re not likely to hit this limit.

Date hired will be a date in this format 2010-05-06. YYYY-MM-DD.

So when considering this simple table, where would you expect to need an index?
If we assign ID as a primary key, we don’t need one there.

Indexes are best used on columns that are frequently used in where clauses, and in any kind of sorting, such as “order by”.

You should also pay attention to whether or not this information will change frequently, because it will slow down your updates and inserts. Since you wont frequently be adding employees, you don’t have to worry about the inserts.

Let’s say that you will be looking up the employees with a php web interface and the end user will be typing in the employees name to find them, since remembering the employee ID’s would be cumbersome.

It sounds like this situation would be good to use an index.

A – You won’t be updating the employee’s name very often, so you don’t have to worry about a performance hit there.

B – You WILL be using the employee in where clauses like this:

select * from employees where name ='smith';

C – You WILL be generating reports, which will probably be alphabetic, like this:

select * from employees order by name asc;

So in this simple example it’s easy to see when it would be important to use indexes.

So, you could do it like this:

create index name_index on employees (name);

You might be working on a more complex database, so it’s good to remember a few simple rules.

- Indexes slow down inserts and updates, so you want to use them carefully on columns that are FREQUENTLY updated.

- Indexes speed up where clauses and order by.

Remember to think about HOW your data is going to be used when building your tables.

There are a few other things to remember. If your table is very small, i.e., only a few employees, it’s worse to use an index than to leave it out and just let it do a table scan. Indexes really only come in handy with tables that have a lot of rows.

So, if Joe’s Pet Shop was using this database, they would probably be able to leave the index off the “name” column.

If Microsoft was using this database (hah!) they might want to throw and index in there.

Another thing to remember, that is a con in the situation of our employees database, is that if the column is a variable length, indexes (as well as most of MySQL) perform much less efficiently.

As you can see there are many things to consider with indexes, even with a very simple table as this.

I would suggest looking at the explain command in MySQL, which I will be writing about in the future.

http://www.tsmonaghan.com

Incoming search terms:

• purftp max connections directadmin (2)
• how to add index mysql plesk (1)
• mysql maxconnections directadmin (1)

mysqldump –all-databases> alldatabases.sql

How to Backing up only the Database Structure in MySQL
You can backup only the database structure by telling mysqldump not to back up the data. You can do this by using the –no-data parameter when you call mysqldump.

mysqldump –no-data –databases Customers Orders Comments > structurebackup.sql

Incoming search terms:

• mysqldump all databases plesk centos (2)

I do not issue any guarantee that this will work for you!

1 Preliminary Note

I’m using a CentOS 5.5 server with the IP address 192.168.0.100 here.

2 Installing WebDAV

If Apache is not already installed, install it as follows:

yum install httpd

Afterwards, open /etc/httpd/conf/httpd.conf and make sure that the dav and dav_fs modules are enabled in the LoadModule section (they should be enabled by default):

vi /etc/httpd/conf/httpd.conf

[...]
LoadModule dav_module modules/mod_dav.so
[...]
LoadModule dav_fs_module modules/mod_dav_fs.so
[...]

Then create the system startup links for Apache and start it:

chkconfig –levels 235 httpd on
/etc/init.d/httpd start

3 Creating A Virtual Host

I will now create a default Apache vhost in the directory /var/www/web1/web. For this purpose, I will add a default vhost at the end of /etc/httpd/conf/httpd.conf. If you already have a vhost for which you’d like to enable WebDAV, you must adjust this tutorial to your situation.

First, we create the directory /var/www/web1/web and make the Apache user and group (apache) the owner of that directory:

mkdir -p /var/www/web1/web
chown apache:apache /var/www/web1/web

Then add the new vhost at the end of /etc/httpd/conf/httpd.conf:

vi /etc/httpd/conf/httpd.conf

[...]
NameVirtualHost *:80
<VirtualHost *:80>
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www/web1/web/
        <Directory /var/www/web1/web/>
                Options Indexes MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

</VirtualHost>

Then reload Apache:

/etc/init.d/httpd reload

4 Configure The Virtual Host For WebDAV

Now we create the WebDAV password file /var/www/web1/passwd.dav with the user test (the -c switch creates the file if it does not exist):

htpasswd -c /var/www/web1/passwd.dav test

You will be asked to type in a password for the user test.

(Please don’t use the -c switch if /var/www/web1/passwd.dav is already existing because this will recreate the file from scratch, meaning you lose all users in that file!)

Now we change the permissions of the /var/www/web1/passwd.dav file so that only root and the members of the apache group can access it:

chown root:apache /var/www/web1/passwd.dav
chmod 640 /var/www/web1/passwd.dav

Now we modify our vhost at the end of /etc/httpd/conf/httpd.conf and add the following lines to it:

vi /etc/httpd/conf/httpd.conf

[...]
        Alias /webdav /var/www/web1/web

        <Location /webdav>
           DAV On
           AuthType Basic
           AuthName "webdav"
           AuthUserFile /var/www/web1/passwd.dav
           Require valid-user
       </Location>
[...]

The Alias directive makes (together with <Location>) that when you call /webdav, WebDAV is invoked, but you can still access the whole document root of the vhost. All other URLs of that vhost are still “normal” HTTP.

The final vhost should look like this:

[...]
NameVirtualHost *:80
<VirtualHost *:80>
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www/web1/web/
        <Directory /var/www/web1/web/>
                Options Indexes MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

        Alias /webdav /var/www/web1/web

        <Location /webdav>
           DAV On
           AuthType Basic
           AuthName "webdav"
           AuthUserFile /var/www/web1/passwd.dav
           Require valid-user
       </Location>

</VirtualHost>

Reload Apache afterwards:

/etc/init.d/httpd reload

5 Testing WebDAV

We will now install cadaver, a command-line WebDAV client:

yum install cadaver

To test if WebDAV works, type:

cadaver http://localhost/webdav/

You should be prompted for a user name. Type in test and then the password for the user test. If all goes well, you should be granted access which means WebDAV is working ok. Type quit to leave the WebDAV shell:

[root@server1 ~]# cadaver http://localhost/webdav/
Authentication required for webdav on server `localhost’:
Username: test
Password:
dav:/webdav/> quit
Connection to `localhost’ closed.
[root@server1 ~]#

6 Configure A Windows XP Client To Connect To The WebDAV Share

Click on My Network Places on your desktop (I have a German Windows, so the names are a bit different in the screenshots):

Select Add a Network Place from the Network Tasks menu (on the left):

The Add Network Place Wizard comes up. Click on the Next button:

Select Choose another network location, and click on Next:

Enter http://192.168.0.100:80/webdav as the location and click on Next. You must specify the port in the WebDAV URL (:80). For some strange reason this makes Windows XP accept the normal username (e.g. test) – otherwise Windows XP expects NTLM usernames (that would have the form www.example.com\test).

You will be prompted for a user name and a password. Type in the user name test and the password for the user test:

Then type in a name for the WebDAV folder:

To open the new connection, keep the Open this network place when I click Finish box checked, and click on Finish:

The WebDAV folder will then open where you can browse the contents of the /var/www/web1/web directory and its subdirectories on the server, and you will find an icon for your new WebDAV share in the My Network Places folder:

7 Configure A Linux Client (GNOME) To Connect To The WebDAV Share

If you want to connect to the WebDAV share from a GNOME desktop, go to Places > Connect to Server…:

Select WebDAV (HTTP) as the Service type, type in the Server (192.168.0.100 in this example) and then the Folder (webdav). Do not fill in a User Name yet because otherwise the connection will fail. Click on Connect afterwards:

Now you are being prompted for a user name and password. Type in test along with the password, then click on Connect:

You might get the following error…

… but at the same time the WebDAV share should appear on the desktop, which means you can ignore the error:

Double-click on the icon to open the WebDAV share:

8 Links

• WebDAV: http://www.webdav.org/
• Apache: http://httpd.apache.org/
• CentOS: http://www.centos.org/

Incoming search terms:

• directadmin webdav (6)
• kloxo webdav (3)
• oracle dav on web folder (3)
• webdav centos (3)
• webdav directadmin (3)
• webdav rhel6 (2)
• centos webdav windows 7 (2)
• plesk webdav centos (2)
• webdav file share centos (1)
• mount webdav centos (1)

I do not issue any guarantee that this will work for you!

1 Preliminary Note

In this tutorial I use the hostname server1.example.com with the IP address 192.168.0.100. These settings might differ for you, so you have to replace them where appropriate.

2 Installing MySQL 5.0

To install MySQL, we do this:

yum install mysql mysql-server

Then we create the system startup links for MySQL (so that MySQL starts automatically whenever the system boots) and start the MySQL server:

chkconfig –levels 235 mysqld on
/etc/init.d/mysqld start

Set passwords for the MySQL root account:

mysql_secure_installation

[root@server1 ~]# mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we’ll need the current
password for the root user.  If you’ve just installed MySQL, and
you haven’t set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on…

Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.

Set root password? [Y/n] <– ENTER
New password: <– yourrootsqlpassword
Re-enter new password: <– yourrootsqlpassword
Password updated successfully!
Reloading privilege tables..
… Success!

By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] <– ENTER
… Success!

Normally, root should only be allowed to connect from ’localhost’.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] <– ENTER
… Success!

By default, MySQL comes with a database named ’test’ that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] <– ENTER
- Dropping test database…
… Success!
- Removing privileges on test database…
… Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] <– ENTER
… Success!

Cleaning up…

All done!  If you’ve completed all of the above steps, your MySQL
installation should now be secure.

Thanks for using MySQL!

[root@server1 ~]#

3 Installing Apache2

Apache2 is available as a CentOS package, therefore we can install it like this:

yum install httpd

Now configure your system to start Apache at boot time…

chkconfig –levels 235 httpd on

… and start Apache:

/etc/init.d/httpd start

Now direct your browser to http://192.168.0.100, and you should see the Apache2 placeholder page:

Apache’s default document root is /var/www/html on CentOS, and the configuration file is /etc/httpd/conf/httpd.conf. Additional configurations are stored in the /etc/httpd/conf.d/ directory.

4 Installing PHP5

We can install PHP5 and the Apache PHP5 module as follows:

yum install php

We must restart Apache afterwards:

/etc/init.d/httpd restart

5 Testing PHP5 / Getting Details About Your PHP5 Installation

The document root of the default web site is /var/www/html. We will now create a small PHP file (info.php) in that directory and call it in a browser. The file will display lots of useful details about our PHP installation, such as the installed PHP version.

vi /var/www/html/info.php

<?php
phpinfo();
?>

Now we call that file in a browser (e.g. http://192.168.0.100/info.php):

As you see, PHP5 is working, and it’s working through the Apache 2.0 Handler, as shown in the Server API line. If you scroll further down, you will see all modules that are already enabled in PHP5. MySQL is not listed there which means we don’t have MySQL support in PHP5 yet.

6 Getting MySQL Support In PHP5

To get MySQL support in PHP, we can install the php-mysql package. It’s a good idea to install some other PHP5 modules as well as you might need them for your applications. You can search for available PHP5 modules like this:

yum search php

Pick the ones you need and install them like this:

yum install php-mysql php-gd php-imap php-ldap php-odbc php-pear php-xml php-xmlrpc

Now restart Apache2:

/etc/init.d/httpd restart

Now reload http://192.168.0.100/info.php in your browser and scroll down to the modules section again. You should now find lots of new modules there, including the MySQL module:

7 phpMyAdmin

phpMyAdmin is a web interface through which you can manage your MySQL databases.

First we enable the RPMforge repository on our CentOS system as phpMyAdmin is not available in the official CentOS 5.5 repositories:

On x86_64 systems:

wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm
rpm -Uhv rpmforge-release-0.5.1-1.el5.rf.x86_64.rpm

On i386 systems:

wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.i386.rpm
rpm -Uhv rpmforge-release-0.5.1-1.el5.rf.i386.rpm

phpMyAdmin can now be installed as follows:

yum install phpmyadmin

Now we configure phpMyAdmin. We change the Apache configuration so that phpMyAdmin allows connections not just from localhost (by commenting out the <Directory “/usr/share/phpmyadmin”> stanza):

vi /etc/httpd/conf.d/phpmyadmin.conf

#
#  Web application to manage MySQL
#

#<Directory "/usr/share/phpmyadmin">
#  Order Deny,Allow
#  Deny from all
#  Allow from 127.0.0.1
#</Directory>

Alias /phpmyadmin /usr/share/phpmyadmin
Alias /phpMyAdmin /usr/share/phpmyadmin
Alias /mysqladmin /usr/share/phpmyadmin

Next we change the authentication in phpMyAdmin from cookie to http:

vi /usr/share/phpmyadmin/config.inc.php

[...]
/* Authentication type */
$cfg['Servers'][$i]['auth_type'] = 'http';
[...]

Restart Apache:

/etc/init.d/httpd restart

Afterwards, you can access phpMyAdmin under http://192.168.0.100/phpmyadmin/:

8 Links

• Apache: http://httpd.apache.org/
• PHP: http://www.php.net/
• MySQL: http://www.mysql.com/
• CentOS: http://www.centos.org/
• phpMyAdmin: http://www.phpmyadmin.net/

Incoming search terms:

• phpadmin (3)
• centos5 5 htttpd conf phpmyadmin (2)
• production grade centos apache mysql php phpadmin (1)
• plesk mysql so 5 5 (1)
• php apache mysql phpmyadmin directadmin on centos (1)
• installed apache2 debian cant access 192 168 0 100 (1)
• installare server lamp phpmyadmin centos mysql 5 5 (1)
• install httpd php5 from centos cdrom (1)
• install apache2 handler on centos (1)
• instalar mod mysql apache centos (1)

#!/bin/bash
# Shell script to backup MySql database
# To backup Nysql databases file to /backup dir and later pick up by your
# script. You can skip few databases from backup too.
# ——————————————————————–
# This is a free shell script under GNU GPL version 2.0 or above
# Copyright (C) 2004, 2005 nixCraft project
# ————————————————————————-

MyUSER=“SET-MYSQL-USER-NAME” # USERNAME
MyPASS=“SET-PASSWORD” # PASSWORD
MyHOST=“localhost” # Hostname

# Linux bin paths, change this if it can‘t be autodetected via which command
MYSQL=”$(which mysql)”
MYSQLDUMP=”$(which mysqldump)”
CHOWN=”$(which chown)”
CHMOD=”$(which chmod)”
GZIP=”$(which gzip)”

# Backup Dest directory, change this if you have someother location
DEST=”/backup”

# Main directory where backup will be stored
MBD=”$DEST/mysql”

# Get hostname
HOST=”$(hostname)”

# Get data in dd-mm-yyyy format
NOW=”$(date +”%d-%m-%Y”)”

# File to store current backup file
FILE=””
# Store list of databases
DBS=””

# DO NOT BACKUP these databases
IGGY=”test”

[ ! -d $MBD ] && mkdir -p $MBD || :

# Only root can access it!
$CHOWN 0.0 -R $DEST
$CHMOD 0600 $DEST

# Get all database list first
DBS=”$($MYSQL -u $MyUSER -h $MyHOST -p$MyPASS -Bse ‘show databases‘)”

for db in $DBS
do
skipdb=-1
if [ "$IGGY" != "" ];
then
for i in $IGGY
do
[ "$db" == "$i" ] && skipdb=1 || :
done
fi

if [ "$skipdb" == "-1" ] ; then
FILE=”$MBD/$db.$HOST.$NOW.gz”
# do all inone job in pipe,
# connect to mysql using mysqldump for select mysql database
# and pipe it out to gz file in backup dir
$MYSQLDUMP -u $MyUSER -h $MyHOST -p$MyPASS $db | $GZIP -9 > $FILE
fi
done

Incoming search terms:

• linux mysqldump backup to network (2)
• CentOS website backup shell scripts (2)
• back up data host win (1)
• mysql shell (1)
• mysqldump backup centos script (1)
• php script to dump mysql plesk psa (1)
• plesk shell backup (1)
• script back up mysql on centos (1)
• script backup mysql linux gzip (1)
• script mysqldump backup plesk (1)

Sometimes, when you have got a large number of tables in your database and while taking the dump of that particular database, you would have encountered this strange error

mysqldump: Got error: 1016: Can't open file: '.\database\certain_table.frm' (errno: 24) when using LOCK TABLES

There are two solutions to avoid this error

1. Set the following value to some higher number in your mysql database

set open-files-limit=20000

2. or, While taking the mysql dump, use –lock-tables=off option.

mysqldump --lock-tables=off -u root -p db-with-lots-of-tables > db.sql

Incoming search terms:

• (errno: 24) when using lock tables (6)
• mysqldump error 1016 (2)
• mysqldump: got error: 1016: cant open file: (errno: 24) when using lock tables (2)
• mysqldump errno:24 (1)
• mysqldump error 24 (1)
• mysqldump got error 1016 can\t open file (errno 24) when using lock tables (1)
• mysqldump lock tables (1)
• mysqldump to file use limit (1)
• mysqldump: got error: 1016: can\t open file: frm\ (errno: 24) when using lock tables (1)
• phpmyadmin 1016 cant open file errno 24 (1)

Today working on a client project, a shell script which uses MySQL to dump the database, has got me into this error

mysqldump: Got error: 1045: Access denied for user

I was typically amazed getting this error because all my configurations were correct. I have created proper users to access MySQL database and correctly configured the MySQL server settings. FYI, my script was on one server and the MySQL was running on a separate dedicated box. The connection between them were TCP based.

After few minutes of head hunching, I was able to figure out the problem. So if you got into the same problem any time, follow the following guidelines to get over with it:

1. Check that whether you have created the proper MySQL user and gave them the required permission. You can check the user permission by following command.

SHOW GRANTS FOR 'user'@'localhost';

SHOW GRANTS FOR 'user'@'192.168.1.1';

If the permissions are not proper, you might think of providing it properly by

GRANT ALL ON database.* TO 'user'@'localhost' identified by 'password';

2. Check whether you are including the host properly in case of remote MySQL connections.

mysql -h host -u user -p database

3. Finally, if you have created user and didn’t restarted your MySQL server or ran following command, your MySQL user permissions will not take effect in-spite of creating them. (Ps. This was the issue I was having.)

FLUSH PRIVILEGES

After running the above command, my script was able to connect to database properly.

Incoming search terms:

• mysqldump: got error: 1045: access denied for user (6)
• mysqldump plesk error 1045 (2)
• mysqldump: Got error: 1045: Access denied for user root@localhost (using password: YES) when try (2)
• mysqldump: got error: 1045 centos (1)
• mysqldump: Got error: 1045: Access denied for user liuqinghua@localhost (using password: YES) wh (1)
• mysqldump: Got error: 1045: Access denied for user ODBC@ (1)
• mysqldump: got error: 1045: access denied for user p@ (using password: yes) when trying to connect (1)
• mysqldump: Got error: 1045: Access denied for user root@10 127 5 34 (using password: YES) when t (1)
• mysqldump: Got error: 1045: Access denied for user root@127 0 0 1 (using password: YES) when trying to connect (1)
• mysqldump: Got error: 1045: Access denied for user root@20 154 44 81 (using password: YES) when (1)

Razor, Pyzor and DCC are spamfilters that use a collaborative filtering network. To install them, run

apt-get install razor pyzor dcc-client

Now we have to tell SpamAssassin to use these three programs. Edit /etc/spamassassin/local.cf so that it looks like this:

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
###########################################################################
#
# rewrite_header Subject *****SPAM*****
# report_safe 1
# trusted_networks 212.17.35.
# lock_method flock

# dcc
use_dcc 1
dcc_path /usr/bin/dccproc
dcc_add_header 1
dcc_dccifd_path /usr/sbin/dccifd

#pyzor
use_pyzor 1
pyzor_path /usr/bin/pyzor
pyzor_add_header 1

#razor
use_razor2 1
razor_config /etc/razor/razor-agent.conf

#bayes
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1

Run

/etc/init.d/amavis restart

afterwards.

Now I want to insert some custom rulesets that can be found on the internet into SpamAssassin. I have tested those rulesets, and they make spam filtering a lot more effective. Create the file /usr/local/sbin/sa_rules_update.sh:

#!/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/71_sare_redirect_pre3.0.0.cf -O 71_sare_redirect_pre3.0.0.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_bayes_poison_nxm.cf -O 70_sare_bayes_poison_nxm.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_html.cf -O 70_sare_html.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_html4.cf -O 70_sare_html4.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_html_x30.cf -O 70_sare_html_x30.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_header0.cf -O 70_sare_header0.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_header3.cf -O 70_sare_header3.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_header_x30.cf -O 70_sare_header_x30.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_specific.cf -O 70_sare_specific.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_adult.cf -O 70_sare_adult.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/72_sare_bml_post25x.cf -O 72_sare_bml_post25x.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/99_sare_fraud_post25x.cf -O 99_sare_fraud_post25x.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_spoof.cf -O 70_sare_spoof.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_random.cf -O 70_sare_random.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_oem.cf -O 70_sare_oem.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_genlsubj0.cf -O 70_sare_genlsubj0.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_genlsubj3.cf -O 70_sare_genlsubj3.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_genlsubj_x30.cf -O 70_sare_genlsubj_x30.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_unsub.cf -O 70_sare_unsub.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/70_sare_uri.cf -O 70_sare_uri.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://mywebpages.comcast.net/mkettler/sa/antidrug.cf -O antidrug.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.timj.co.uk/linux/bogus-virus-warnings.cf -O bogus-virus-warnings.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.yackley.org/sa-rules/evilnumbers.cf -O evilnumbers.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.stearns.org/sa-blacklist/random.current.cf -O random.current.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/88_FVGT_body.cf -O 88_FVGT_body.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/88_FVGT_rawbody.cf -O 88_FVGT_rawbody.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/88_FVGT_subject.cf -O 88_FVGT_subject.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/88_FVGT_headers.cf -O 88_FVGT_headers.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/88_FVGT_uri.cf -O 88_FVGT_uri.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/99_FVGT_DomainDigits.cf -O 99_FVGT_DomainDigits.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/99_FVGT_Tripwire.cf -O 99_FVGT_Tripwire.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.rulesemporium.com/rules/99_FVGT_meta.cf -O 99_FVGT_meta.cf &> /dev/null cd /etc/spamassassin/ &> /dev/null && /usr/bin/wget http://www.nospamtoday.com/download/mime_validate.cf -O mime_validate.cf &> /dev/null /etc/init.d/amavis restart &> /dev/null exit 0

chmod 755 /usr/local/sbin/sa_rules_update.sh

Then run that script once, it will fetch those rulesets and insert them into SpamAssassin:

/usr/local/sbin/sa_rules_update.sh

We create a cron job so that those rulesets will be updated regularly. Run

crontab -e

to open the cron job editor. Create following cron job:

23 4 */2 * * /usr/local/sbin/sa_rules_update.sh &> /dev/null

This will update the rulesets every second day at 4.23h.

(Note (a little off-topic): on Debian Sarge crontab -e will automatically open the editor nano. If you are used to working with the editor vi (like me), run the following commands:

rm -f /etc/alternatives/editor
ln -s /usr/bin/vi /etc/alternatives/editor

Afterwards, run crontab -e, and vi will come up.)

9 Quota Exceedance Notifications

If you want to get notifications about all the email accounts that are over quota, then do this:

cd /usr/local/sbin/
wget http://puuhis.net/vhcs/quota.txt
mv quota.txt quota_notify
chmod 755 quota_notify

Open /usr/local/sbin/quota_notify and edit the variables at the top:

my $POSTFIX_CF = "/etc/postfix/main.cf";
my $MAILPROG = "/usr/sbin/sendmail -t";
my $WARNPERCENT = 80;
my @POSTMASTERS = ('postmaster@isp.tld');
my $CONAME = 'ISP.tld';
my $COADDR = 'postmaster@isp.tld';
my $SUADDR = 'postmaster@isp.tld';
my $MAIL_REPORT = 1;
my $MAIL_WARNING = 1;

Run

crontab -e

to create a cron job for that script:

0 0 * * * /usr/local/sbin/quota_notify &> /dev/null

Incoming search terms:

• centos cpanel postfix virtual users (2)
• quota txt postfix (2)
• smtp-auth quota spamassassin clamav (2)
• modify quota mysql postfix -dovecot (1)
• spamassassin amavis rewrite_header solved (1)
• spamassassin virtual domain mysql (1)