Epel yum repository is an open source centos yum repository or rpm repository for developers and system administrators to perform the installation of RPM packages via yum on their virtual private server (VPS) or dedicated server.
EPEL yum repository is redhat yum repository for CentOS and additional yum repository for the existing CentOS repository.
It provides 100 % high quality software packages for Linux distributions, including RHEL (Red Hat Enterprise Linux), CentOS and Debian, and all packages maintained by Fedora repo team.
1. Prepare EPEL repository for RHEL 7/CentOS 7 64 bit (epel centos 7/epel rhel 7) :
EPEL stand for Extra Packages for Enterprise Linux. EPEL repository is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Enterprise Linux(OEL). Remi repository is a yum repository maintained by a French dude – Remi Collet. This post describe the basic steps to prepare and install the additional CentOS packages with EPEL and Remi Repository into CentOS 6.
A directory server provides a centralized directory service for your organization. It is alternative to windows active directory. This post will describes how to install and configure 389 LDAP Directory Server with a basic Lightweight Directory Access Protocol (LDAP) directory implementation. 389 Directory Server was formerly known as the Fedora Directory Server and it is an enterprise-class open source LDAP. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project.
Steps to Install and Configure 389 LDAP Directory Server
TCP and Files system Tuning : a) Decrease the time default value for tcp_keepalive_time connection. Edit the /etc/sysctl.conf file and add the following lines to the bottom of sysctl.conf ”
[root@ldap ~]# echo "net.ipv4.tcp_keepalive_time = 300" >> /etc/sysctl.conf
b) Increase number of local system ports available by editing this parameter in the /etc/sysctl.conf file :
[root@ldap ~]# mkdir ~/bin
[root@ldap ~]# vi ~/bin/getsebool
#!/bin/sh
echo on
exit 0
[root@ldap ~]# vi ~/bin/setsebool
#!/bin/sh
exit 0
[root@ldap ~]# chmod +x ~/bin/*sebool
6. Run setup script to start configure the ldap service :
[root@ldap ~]# PATH=~/bin:$PATH setup-ds-admin.pl
==============================================================================
This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
Would you like to continue with set up? [yes]:
==============================================================================
Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 23-FEBRUARY-2012.
NOTICE : System is x86_64-unknown-linux2.6.32-431.el6.x86_64 (1 processor).
Would you like to continue? [yes]:
==============================================================================
Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
Choose a setup type [2]:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
Computer name [ldap.ehowstuff.local]:
WARNING: There are problems with the hostname.
Hostname 'ldap.ehowstuff.local' is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
- address 192.168.0.5 resolves to host centos6.5.ehowstuff.local
Please check the spelling of the hostname and/or your network configuration.
If you proceed with this hostname, you may encounter problems.
Do you want to proceed with hostname 'ldap.ehowstuff.local'? [no]: yes
==============================================================================
The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
System User [nobody]:
System Group [nobody]:
==============================================================================
Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
Do you want to register this software with an existing
configuration directory server? [no]:
==============================================================================
Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):
==============================================================================
The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
Administration Domain [ehowstuff.local]:
==============================================================================
The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
Directory server network port [389]:
==============================================================================
Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
Directory server identifier [ldap]:
==============================================================================
The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
Suffix [dc=ehowstuff, dc=local]:
==============================================================================
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
==============================================================================
The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
Administration port [9830]:
==============================================================================
The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
Are you ready to set up your servers? [yes]:
Creating directory server . . .
Warning: Hostname ldap.ehowstuff.local is valid, but none of the IP addresses
resolve back to ldap.ehowstuff.local
address 192.168.0.5 resolves to host centos6.5.ehowstuff.local
Your new DS instance 'ldap' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server reconfiguration . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output: [ OK ]
The admin server was successfully started.
Admin server was successfully reconfigured and started.
Exiting . . .
Log file is '/tmp/setupGwS8hs.log'
8. Make dirsrv and dirsrv-admin service auto start at boot :
[root@ldap ~]# chkconfig dirsrv on
[root@ldap ~]# chkconfig dirsrv-admin on
9. Configure Iptables to allow server listen on port 22, 389 and 9830 :
# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
Restart iptables to take effect the changes :
[root@ldap ~]# service iptables restart
iptables: Applying firewall rules: [ OK ]
10. Verify port listen by the server using netstat :
389 Directory Server is an enterprise-class open source Lightweight Directory Access Protocol (LDAP) server for Linux and based on Fedora Directory Server. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project. This steps has been tested on CentOS 6.4 x86_64 and may work on other version of CentOS as well.
5. To install 389 LDAP, run the configuration script :
[root@centos64 ~]# /usr/sbin/setup-ds-admin.pl
==============================================================================
This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
Would you like to continue with set up? [yes]:
==============================================================================
Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 23-FEBRUARY-2012.
NOTICE : System is x86_64-unknown-linux2.6.32-358.2.1.el6.x86_64 (2 processors).
NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes). This may cause temporary server congestion from lost
client connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
WARNING : The warning messages above should be reviewed before proceeding.
Would you like to continue? [no]: yes
==============================================================================
Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
Choose a setup type [2]:
==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
.
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
Computer name [centos64.ehowstuff.local]:
==============================================================================
The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
System User [nobody]:
System Group [nobody]:
==============================================================================
Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
Do you want to register this software with an existing
configuration directory server? [no]:
==============================================================================
Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):
==============================================================================
The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
Administration Domain [ehowstuff.local]:
==============================================================================
The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
Directory server network port [389]:
==============================================================================
Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
Directory server identifier [centos64]:
==============================================================================
The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
Suffix [dc=ehowstuff, dc=local]:
==============================================================================
Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
Directory Manager DN [cn=Directory Manager]:
Password:
Password (confirm):
==============================================================================
The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
Administration port [9830]:
==============================================================================
The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
Are you ready to set up your servers? [yes]:
Creating directory server . . .
Your new DS instance 'centos64' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Starting admin server . . .
output: Starting dirsrv-admin:
output: [ OK ]
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setupDJucbG.log'
6. Start dirsrv and dirsrv-admin service :
[root@centos64 ~]# /etc/init.d/dirsrv start
Starting dirsrv:
centos64... [ OK ]
[root@centos64 ~]# /etc/init.d/dirsrv-admin start
Starting dirsrv-admin:
[ OK ]
7. Make dirsrv and dirsrv-admin service auto start at boot :
[root@centos64 ~]# chkconfig dirsrv on
[root@centos64 ~]# chkconfig dirsrv-admin on
8. Check dirsrv and dirsrv-admin service status :
[root@centos64 ~]# /etc/init.d/dirsrv-admin status
dirsrv-admin (pid 1409) is running...
[root@centos64 ~]# /etc/init.d/dirsrv status
dirsrv centos64 (pid 1317) is running...
EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. By using EPEL repository you can install some other third party software such as nagios, or bugzilla, phpmyadmin, or any other standard open source software just using yum command. These repositories are not officially supported by CentOS, but this repository provide much more current versions of popular PHP or MySQL applications. This post describe how you can prepare EPEL Repository on CentOS 6.4 x86_64.
1. Download and import the GPG keys for EPEL software packages:
This post will covers the steps to install phpMyAdmin to operate MySQL from Web browser. phpMyAdmin is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web. It can manage a whole MySQL server (needs a super-user) as well as a single database. phpMyAdmin supports a wide range of operations with MySQL. The most frequently used operations are supported by the user interface (managing databases, tables, fields, relations, indexes, users, permissions, etc), while you still have the ability to directly execute any SQL statement.
[root@centos63 ~]# yum --enablerepo=epel install phpMyAdmin php-mysql php-mcrypt -y
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: mirror.issp.co.th
* epel: mirror.nus.edu.sg
* extras: mirror.issp.co.th
* updates: mirror.issp.co.th
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php-mcrypt.i686 0:5.3.3-1.el6 will be installed
--> Processing Dependency: php-api = 20090626 for package: php-mcrypt-5.3.3-1.el6.i686
--> Processing Dependency: libmcrypt.so.4 for package: php-mcrypt-5.3.3-1.el6.i686
---> Package php-mysql.i686 0:5.3.3-14.el6_3 will be installed
--> Processing Dependency: php-pdo for package: php-mysql-5.3.3-14.el6_3.i686
---> Package phpMyAdmin.noarch 0:3.5.1-1.el6 will be installed
--> Processing Dependency: php-mbstring >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch
--> Processing Dependency: php-gd >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch
--> Processing Dependency: php >= 5.2.0 for package: phpMyAdmin-3.5.1-1.el6.noarch
--> Processing Dependency: php-php-gettext for package: phpMyAdmin-3.5.1-1.el6.noarch
--> Running transaction check
---> Package libmcrypt.i686 0:2.5.8-9.el6 will be installed
---> Package php.i686 0:5.3.3-14.el6_3 will be installed
--> Processing Dependency: php-cli = 5.3.3-14.el6_3 for package: php-5.3.3-14.el6_3.i686
---> Package php-common.i686 0:5.3.3-14.el6_3 will be installed
---> Package php-gd.i686 0:5.3.3-14.el6_3 will be installed
--> Processing Dependency: libpng12.so.0(PNG12_0) for package: php-gd-5.3.3-14.el6_3.i686
--> Processing Dependency: libpng12.so.0 for package: php-gd-5.3.3-14.el6_3.i686
--> Processing Dependency: libjpeg.so.62 for package: php-gd-5.3.3-14.el6_3.i686
--> Processing Dependency: libfreetype.so.6 for package: php-gd-5.3.3-14.el6_3.i686
--> Processing Dependency: libXpm.so.4 for package: php-gd-5.3.3-14.el6_3.i686
--> Processing Dependency: libX11.so.6 for package: php-gd-5.3.3-14.el6_3.i686
---> Package php-mbstring.i686 0:5.3.3-14.el6_3 will be installed
---> Package php-pdo.i686 0:5.3.3-14.el6_3 will be installed
---> Package php-php-gettext.noarch 0:1.0.11-3.el6 will be installed
--> Running transaction check
---> Package freetype.i686 0:2.3.11-6.el6_2.9 will be installed
---> Package libX11.i686 0:1.3-2.el6 will be installed
--> Processing Dependency: libX11-common = 1.3-2.el6 for package: libX11-1.3-2.el6.i686
--> Processing Dependency: libxcb.so.1 for package: libX11-1.3-2.el6.i686
---> Package libXpm.i686 0:3.5.8-2.el6 will be installed
---> Package libjpeg.i686 0:6b-46.el6 will be installed
---> Package libpng.i686 2:1.2.49-1.el6_2 will be installed
---> Package php-cli.i686 0:5.3.3-14.el6_3 will be installed
--> Running transaction check
---> Package libX11-common.noarch 0:1.3-2.el6 will be installed
---> Package libxcb.i686 0:1.5-1.el6 will be installed
--> Processing Dependency: libXau.so.6 for package: libxcb-1.5-1.el6.i686
--> Running transaction check
---> Package libXau.i686 0:1.0.5-1.el6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================
Package Arch Version Repository Size
====================================================================================================
Installing:
php-mcrypt i686 5.3.3-1.el6 epel 18 k
php-mysql i686 5.3.3-14.el6_3 updates 77 k
phpMyAdmin noarch 3.5.1-1.el6 epel 4.2 M
Installing for dependencies:
freetype i686 2.3.11-6.el6_2.9 CentOS6.3-Repository 363 k
libX11 i686 1.3-2.el6 CentOS6.3-Repository 585 k
libX11-common noarch 1.3-2.el6 CentOS6.3-Repository 188 k
libXau i686 1.0.5-1.el6 CentOS6.3-Repository 22 k
libXpm i686 3.5.8-2.el6 CentOS6.3-Repository 58 k
libjpeg i686 6b-46.el6 CentOS6.3-Repository 133 k
libmcrypt i686 2.5.8-9.el6 epel 94 k
libpng i686 2:1.2.49-1.el6_2 CentOS6.3-Repository 184 k
libxcb i686 1.5-1.el6 CentOS6.3-Repository 104 k
php i686 5.3.3-14.el6_3 updates 1.1 M
php-cli i686 5.3.3-14.el6_3 updates 2.2 M
php-common i686 5.3.3-14.el6_3 updates 523 k
php-gd i686 5.3.3-14.el6_3 updates 103 k
php-mbstring i686 5.3.3-14.el6_3 updates 453 k
php-pdo i686 5.3.3-14.el6_3 updates 72 k
php-php-gettext noarch 1.0.11-3.el6 epel 21 k
Transaction Summary
====================================================================================================
Install 19 Package(s)
Total download size: 10 M
Installed size: 38 M
Downloading Packages:
Setting up and reading Presto delta metadata
updates/prestodelta | 72 kB 00:00
Processing delta metadata
Package(s) data still to download: 10 M
(1/19): libmcrypt-2.5.8-9.el6.i686.rpm | 94 kB 00:00
(2/19): php-5.3.3-14.el6_3.i686.rpm | 1.1 MB 00:09
(3/19): php-cli-5.3.3-14.el6_3.i686.rpm | 2.2 MB 00:19
(4/19): php-common-5.3.3-14.el6_3.i686.rpm | 523 kB 00:04
(5/19): php-gd-5.3.3-14.el6_3.i686.rpm | 103 kB 00:00
(6/19): php-mbstring-5.3.3-14.el6_3.i686.rpm | 453 kB 00:04
(7/19): php-mcrypt-5.3.3-1.el6.i686.rpm | 18 kB 00:00
(8/19): php-mysql-5.3.3-14.el6_3.i686.rpm | 77 kB 00:00
(9/19): php-pdo-5.3.3-14.el6_3.i686.rpm | 72 kB 00:00
(10/19): php-php-gettext-1.0.11-3.el6.noarch.rpm | 21 kB 00:00
(11/19): phpMyAdmin-3.5.1-1.el6.noarch.rpm | 4.2 MB 00:36
----------------------------------------------------------------------------------------------------
Total 135 kB/s | 10 MB 01:19
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : php-common-5.3.3-14.el6_3.i686 1/19
Installing : libX11-common-1.3-2.el6.noarch 2/19
Installing : php-mbstring-5.3.3-14.el6_3.i686 3/19
Installing : php-php-gettext-1.0.11-3.el6.noarch 4/19
Installing : php-cli-5.3.3-14.el6_3.i686 5/19
Installing : php-5.3.3-14.el6_3.i686 6/19
Installing : php-pdo-5.3.3-14.el6_3.i686 7/19
Installing : php-mysql-5.3.3-14.el6_3.i686 8/19
Installing : libmcrypt-2.5.8-9.el6.i686 9/19
Installing : php-mcrypt-5.3.3-1.el6.i686 10/19
Installing : libjpeg-6b-46.el6.i686 11/19
Installing : 2:libpng-1.2.49-1.el6_2.i686 12/19
Installing : libXau-1.0.5-1.el6.i686 13/19
Installing : libxcb-1.5-1.el6.i686 14/19
Installing : libX11-1.3-2.el6.i686 15/19
Installing : libXpm-3.5.8-2.el6.i686 16/19
Installing : freetype-2.3.11-6.el6_2.9.i686 17/19
Installing : php-gd-5.3.3-14.el6_3.i686 18/19
Installing : phpMyAdmin-3.5.1-1.el6.noarch 19/19
Verifying : freetype-2.3.11-6.el6_2.9.i686 1/19
Verifying : php-5.3.3-14.el6_3.i686 2/19
Verifying : php-cli-5.3.3-14.el6_3.i686 3/19
Verifying : libXau-1.0.5-1.el6.i686 4/19
Verifying : php-common-5.3.3-14.el6_3.i686 5/19
Verifying : php-mbstring-5.3.3-14.el6_3.i686 6/19
Verifying : libXpm-3.5.8-2.el6.i686 7/19
Verifying : 2:libpng-1.2.49-1.el6_2.i686 8/19
Verifying : libxcb-1.5-1.el6.i686 9/19
Verifying : phpMyAdmin-3.5.1-1.el6.noarch 10/19
Verifying : libX11-1.3-2.el6.i686 11/19
Verifying : php-php-gettext-1.0.11-3.el6.noarch 12/19
Verifying : php-gd-5.3.3-14.el6_3.i686 13/19
Verifying : libjpeg-6b-46.el6.i686 14/19
Verifying : libX11-common-1.3-2.el6.noarch 15/19
Verifying : php-mysql-5.3.3-14.el6_3.i686 16/19
Verifying : php-pdo-5.3.3-14.el6_3.i686 17/19
Verifying : php-mcrypt-5.3.3-1.el6.i686 18/19
Verifying : libmcrypt-2.5.8-9.el6.i686 19/19
Installed:
php-mcrypt.i686 0:5.3.3-1.el6 php-mysql.i686 0:5.3.3-14.el6_3 phpMyAdmin.noarch 0:3.5.1-1.el6
Dependency Installed:
freetype.i686 0:2.3.11-6.el6_2.9 libX11.i686 0:1.3-2.el6
libX11-common.noarch 0:1.3-2.el6 libXau.i686 0:1.0.5-1.el6
libXpm.i686 0:3.5.8-2.el6 libjpeg.i686 0:6b-46.el6
libmcrypt.i686 0:2.5.8-9.el6 libpng.i686 2:1.2.49-1.el6_2
libxcb.i686 0:1.5-1.el6 php.i686 0:5.3.3-14.el6_3
php-cli.i686 0:5.3.3-14.el6_3 php-common.i686 0:5.3.3-14.el6_3
php-gd.i686 0:5.3.3-14.el6_3 php-mbstring.i686 0:5.3.3-14.el6_3
php-pdo.i686 0:5.3.3-14.el6_3 php-php-gettext.noarch 0:1.0.11-3.el6
Complete!
2. on Line 14 or 15, add IP address you permit. In this case i have added 192.168.1.0/24 and i’m using apache 2.2 :
[root@centos63 ~]# vi /etc/httpd/conf.d/phpMyAdmin.conf
<Directory /usr/share/phpMyAdmin/>
<IfModule mod_authz_core.c>
# Apache 2.4
<RequireAny>
Require ip 127.0.0.1
Require ip ::1
</RequireAny>
</IfModule>
<IfModule !mod_authz_core.c>
# Apache 2.2
Order Deny,Allow
Deny from All
Allow from 127.0.0.1 192.168.1.0/24
Allow from ::1
</IfModule>
</Directory>
This post will covers on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 6.3. EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. To install the repository, you can follow this steps :
1. First, we download and import the GPG keys for EPEL software packages:
This post will show you the quick steps to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 6.2 server.
phpPgAdmin is a web application, written in PHP and web-based administration utility for managing PostgreSQL databases. It handles all the basic functionality as well as some advanced features such as triggers, views and functions. It can create databases, create tables, alter tables and query the data. In this post, i will show how to install phpPgAdmin for PostgreSQL Databases on linux CentOS 6.2 server. Assumed that you have already configured EPEL repository.
[root@centos62 ~]# yum install phpPgAdmin -y
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.averse.net
* epel: ftp.riken.jp
* extras: mirror.averse.net
* updates: mirror.issp.co.th
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package phpPgAdmin.noarch 0:5.0.3-1.el6 will be installed
--> Processing Dependency: php-pgsql >= 4.2 for package: phpPgAdmin-5.0.3-1.el6.noarch
--> Running transaction check
---> Package php-pgsql.i686 0:5.3.3-3.el6_2.6 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================
Package Arch Version Repository Size
====================================================================================================
Installing:
phpPgAdmin noarch 5.0.3-1.el6 epel 909 k
Installing for dependencies:
php-pgsql i686 5.3.3-3.el6_2.6 updates 67 k
Transaction Summary
====================================================================================================
Install 2 Package(s)
Total download size: 976 k
Installed size: 4.9 M
Downloading Packages:
(1/2): php-pgsql-5.3.3-3.el6_2.6.i686.rpm | 67 kB 00:00
(2/2): phpPgAdmin-5.0.3-1.el6.noarch.rpm | 909 kB 00:10
----------------------------------------------------------------------------------------------------
Total 83 kB/s | 976 kB 00:11
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : php-pgsql-5.3.3-3.el6_2.6.i686 1/2
Installing : phpPgAdmin-5.0.3-1.el6.noarch 2/2
Non-fatal POSTIN scriptlet failure in rpm package phpPgAdmin-5.0.3-1.el6.noarch
warning: %post(phpPgAdmin-5.0.3-1.el6.noarch) scriptlet failed, exit status 7
Installed:
phpPgAdmin.noarch 0:5.0.3-1.el6
Dependency Installed:
php-pgsql.i686 0:5.3.3-3.el6_2.6
Complete!
In this post, i will show you on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 6.2. EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. To install the repository, you can follow this steps :
1. First we import the GPG keys for EPEL software packages:
EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. In this post, i will show you on how to install and configure the Extra Packages for Enterprise Linux (EPEL) repository on CentOS 5.8. To install the repository, you can follow this steps :
1. First we import the GPG keys for EPEL software packages:
A directory server provides a centralized directory service for your organization. It is alternative to windows active directory. This post will describes how to install and configure 389 LDAP Directory Server with a basic Lightweight Directory Access Protocol (LDAP) directory implementation. 389 Directory Server was formerly known as the Fedora Directory Server and it is an enterprise-class open source LDAP. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project.
389 Directory Server is an enterprise-class open source Lightweight Directory Access Protocol (LDAP) server for Linux and based on Fedora Directory Server. 389 Directory server has been developed by Red Hat, as part of Red Hat’s community-supported Fedora Project. This steps has been tested on CentOS 6.4 x86_64 and may work on other version of CentOS as well.
EPEL repository is another extra repository that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL) and CentOS server. By using EPEL repository you can install some other third party software such as nagios, or bugzilla, phpmyadmin, or any other standard open source software just using yum command. These repositories are not officially supported by CentOS, but this repository provide much more current versions of popular PHP or MySQL applications. This post describe how you can prepare EPEL Repository on CentOS 6.4 x86_64.
This post will covers the steps to install phpMyAdmin to operate MySQL from Web browser. phpMyAdmin is a free software tool written in PHP intended to handle the administration of MySQL over the World Wide Web. It can manage a whole MySQL server (needs a super-user) as well as a single database. phpMyAdmin supports a wide range of operations with MySQL. The most frequently used operations are supported by the user interface (managing databases, tables, fields, relations, indexes, users, permissions, etc), while you still have the ability to directly execute any SQL statement.