zentyal mirror downloads

Posted on June 25, 2015July 18, 2015 by coder

Last modified	Size	Description

favicon.ico	2013-07-21 19:48	1.1K
zentyal-4.1-development-amd64.iso	2015-03-27 10:58	584M
zentyal-4.1-development-amd64.iso.md5	2015-03-27 10:58	68

zentyal-4.0-amd64.iso	2014-10-29	666.4 MB	184	i
zentyal-4.0-amd64.iso.md5	2014-10-29	56 Bytes	5	i
zentyal-3.5-vmware-img.zip	2014-07-02	760.1 MB	9	i
zentyal-3.5-vbox-img.zip	2014-07-02	760.2 MB	15	i
zentyal-3.5-kvm-img.zip	2014-07-02	760.8 MB	5	i
zentyal-3.5-i386.iso	2014-07-01	650.2 MB	121	i
zentyal-3.5-i386.iso.md5	2014-07-01	55 Bytes	3	i
zentyal-3.5-amd64.iso	2014-07-01	668.4 MB	98	i
zentyal-3.5-amd64.iso.md5	2014-07-01	56 Bytes	3	i
zentyal-3.4-vmware-img.zip	2014-03-19	705.1 MB	1	i
zentyal-3.4-vbox-img.zip	2014-03-19	705.2 MB	3	i
zentyal-3.4-kvm-img.zip	2014-03-19	705.8 MB	1	i
zentyal-3.4-amd64.iso	2014-03-17	754.8 MB	32	i
zentyal-3.4-amd64.iso.md5	2014-03-17	56 Bytes	1	i
zentyal-3.4-i386.iso.md5	2014-03-17	55 Bytes	1	i
zentyal-3.4-i386.iso	2014-03-17	735.1 MB	19	i
zentyal-3.3-vmware-img.zip	2013-12-17	654.7 MB	1	i
zentyal-3.3-vbox-img.zip	2013-12-17	654.9 MB	2	i
zentyal-3.3-kvm-img.zip	2013-12-17	655.6 MB	1	i
zentyal-3.3-i386.iso.md5	2013-12-16	55 Bytes	1	i
zentyal-3.3-i386.iso	2013-12-16	662.9 MB	6	i
zentyal-3.3-amd64.iso.md5	2013-12-16	56 Bytes	1	i
zentyal-3.3-amd64.iso	2013-12-16	682.8 MB	16	i
zentyal-3.2-vmware-img.zip	2013-12-03	636.4 MB	2	i
zentyal-3.2-vbox-img.zip	2013-12-03	636.5 MB	1	i
zentyal-3.2-kvm-img.zip	2013-12-03	637.1 MB	1	i
zentyal-3.2-amd64.iso	2013-09-19	571.0 MB	20	i
zentyal-3.2-amd64.iso.md5	2013-09-19	56 Bytes	2	i
zentyal-3.2-i386.iso.md5	2013-09-19	55 Bytes	1	i
zentyal-3.2-i386.iso	2013-09-19	550.3 MB	16	i
zentyal-3.2-rc2-i386.iso	2013-09-13	548.0 MB	1	i
zentyal-3.2-rc2-i386.iso.md5	2013-09-13	59 Bytes	1	i
zentyal-3.2-rc2-amd64.iso	2013-09-13	568.8 MB	1	i
zentyal-3.2-rc2-amd64.iso.md5	2013-09-13	60 Bytes	1	i
zentyal-3.2-rc1-i386.iso	2013-09-03	537.2 MB	1	i
zentyal-3.2-rc1-i386.iso.md5	2013-09-03	59 Bytes	1	i
zentyal-3.2-rc1-amd64.iso	2013-09-03	559.7 MB	2	i
zentyal-3.2-rc1-amd64.iso.md5	2013-09-03	60 Bytes	1	i
zentyal-3.1-2-i386.iso	2013-08-05	681.3 MB	1	i
zentyal-3.1-2-i386.iso.md5	2013-08-05	57 Bytes	1	i
zentyal-3.1-2-amd64.iso	2013-08-05	700.9 MB	4	i
zentyal-3.1-2-amd64.iso.md5	2013-08-05	58 Bytes	1	i
zentyal-3.1-1-i386.iso	2013-06-11	673.7 MB	6	i
zentyal-3.1-1-i386.iso.md5	2013-06-11	57 Bytes	1	i
zentyal-3.1-1-amd64.iso	2013-06-11	693.0 MB	1	i
zentyal-3.1-1-amd64.iso.md5	2013-06-11	58 Bytes	1	i
zentyal-3.1-i386.iso	2013-05-08	663.5 MB	2	i
zentyal-3.1-i386.iso.md5	2013-05-08	55 Bytes	1	i
zentyal-3.1-amd64.iso	2013-05-08	682.7 MB	2	i
zentyal-3.1-amd64.iso.md5	2013-05-08	56 Bytes	1	i
zentyal-3.0-2-i386.iso	2013-03-19	663.8 MB	4	i
zentyal-3.0-2-amd64.iso	2013-03-19	692.4 MB	2	i
zentyal-3.0-2-i386.iso.md5	2013-03-19	57 Bytes	1	i
zentyal-3.0-2-amd64.iso.md5	2013-03-19	58 Bytes	2	i
zentyal-3.0-2-vmware-img.zip	2013-03-19	619.3 MB	1	i
zentyal-3.0-2-vbox-img.zip	2013-03-19	619.4 MB	1	i
zentyal-3.0-2-kvm-img.zip	2013-03-19	619.3 MB	1	i
zentyal-3.0-1-vmware-img.zip	2013-03-13	627.3 MB	1	i
zentyal-3.0-1-vbox-img.zip	2013-03-13	627.4 MB	1	i
zentyal-3.0-1-kvm-img.zip	2013-03-13	627.3 MB	1	i
zentyal-3.0-1-i386.iso	2012-12-21	658.9 MB	7	i
zentyal-3.0-1-amd64.iso	2012-12-21	672.5 MB	2	i
zentyal-3.0-1-i386.iso.md5	2012-12-21	57 Bytes	6	i
zentyal-3.0-1-amd64.iso.md5	2012-12-21	58 Bytes	1	i
zentyal-3.0-amd64.iso.md5	2012-12-19	56 Bytes	1	i
zentyal-3.0-i386.iso.md5	2012-12-19	57 Bytes	1	i
zentyal-3.0-vmware-img.zip	2012-11-05	615.9 MB	3	i
zentyal-3.0-vbox-img.zip	2012-11-05	616.0 MB	1	i
zentyal-3.0-kvm-img.zip	2012-11-05	615.9 MB	1	i
zentyal-3.0-i386.iso	2012-09-13	583.6 MB	6	i
zentyal-3.0-amd64.iso	2012-09-13	599.4 MB	4	i
zentyal-3.0-rc2-i386.iso	2012-09-07	571.3 MB	1	i
zentyal-3.0-rc2-i386.iso.md5	2012-09-07	59 Bytes	1	i
zentyal-3.0-rc2-amd64.iso	2012-09-07	586.5 MB	1	i
zentyal-3.0-rc2-amd64.iso.md5	2012-09-07	60 Bytes	1	i
zentyal-3.0-rc1-i386.iso	2012-08-23	666.1 MB	3	i
zentyal-3.0-rc1-i386.iso.md5	2012-08-23	59 Bytes	1	i
zentyal-3.0-rc1-amd64.iso	2012-08-23	693.7 MB	6	i
zentyal-3.0-rc1-amd64.iso.md5	2012-08-23	60 Bytes	1	i
zentyal-2.3-2-i386.iso	2012-07-19	644.0 MB	6	i
zentyal-2.3-2-i386.iso.md5	2012-07-19	57 Bytes	1	i
zentyal-2.3-2-amd64.iso	2012-07-19	655.4 MB	1	i
zentyal-2.3-2-amd64.iso.md5	2012-07-19	58 Bytes	2	i
zentyal-2.3-1-i386.iso	2012-06-18	633.1 MB	1	i
zentyal-2.3-1-i386.iso.md5	2012-06-18	57 Bytes	2	i
zentyal-2.3-1-amd64.iso	2012-06-18	645.2 MB	1	i
zentyal-2.3-1-amd64.iso.md5	2012-06-18	58 Bytes	2	i
zentyal-2.2-2-vmware-img.zip	2012-03-14	650.9 MB	1	i
zentyal-2.2-2-vbox-img.zip	2012-03-14	652.7 MB	5	i
zentyal-2.2-2-kvm-img.zip	2012-03-14	650.8 MB	1	i
zentyal-2.3-i386.iso	2012-03-08	599.7 MB	1	i
zentyal-2.3-amd64.iso	2012-03-08	563.1 MB	1	i
zentyal-2.3-i386.iso.md5	2012-03-08	55 Bytes	1	i
zentyal-2.3-amd64.iso.md5	2012-03-08	56 Bytes	2	i
zentyal-2.2-2-i386.iso	2012-03-02	599.3 MB	11	i
zentyal-2.2-2-amd64.iso	2012-03-02	604.9 MB	2	i
zentyal-2.2-2-i386.iso.md5	2012-03-02	57 Bytes	1	i
zentyal-2.2-2-amd64.iso.md5	2012-03-02	58 Bytes	2	i
zentyal-migration-tool-2.2.exe	2011-11-03	9.7 MB	2	i
zentyal-2.2-1-i386.iso	2011-10-04	644.6 MB	6	i
zentyal-2.2-1-i386.iso.md5	2011-10-04	57 Bytes	1	i
zentyal-2.2-1-amd64.iso	2011-10-04	625.2 MB	1	i
zentyal-2.2-1-amd64.iso.md5	2011-10-04	58 Bytes	1	i
zentyal-2.2-i386.iso.md5	2011-09-14	55 Bytes	1	i
zentyal-2.2-amd64.iso.md5	2011-09-14	56 Bytes	1	i
zentyal-2.2-amd64.iso	2011-09-13	588.6 MB	1	i
zentyal-2.2-i386.iso	2011-09-13	640.2 MB	3	i
zentyal-2.2-rc2-i386.iso.md5	2011-08-25	59 Bytes	1	i
zentyal-2.2-rc2-amd64.iso.md5	2011-08-25	60 Bytes	1	i
zentyal-2.2-rc2-amd64.iso	2011-08-25	549.7 MB	4	i
zentyal-2.2-rc2-i386.iso	2011-08-25	601.5 MB	6	i
zentyal-2.2-rc1-i386.iso.md5	2011-07-23	59 Bytes	1	i
zentyal-2.2-rc1-amd64.iso.md5	2011-07-23	60 Bytes	1	i
zentyal-2.2-rc1-i386.iso	2011-07-23	574.0 MB	5	i
zentyal-2.2-rc1-amd64.iso	2011-07-23	534.7 MB	6	i
zentyal-2.0-4-amd64.iso.md5	2011-07-03	58 Bytes	1	i
zentyal-2.0-4-i386.iso.md5	2011-07-03	57 Bytes	2	i
zentyal-2.0-4-amd64.iso	2011-07-03	561.0 MB	1	i
zentyal-2.0-4-i386.iso	2011-07-03	589.8 MB	8	i
zentyal-2.1-2-i386.iso	2011-06-30	607.4 MB	5	i
zentyal-2.1-2-i386.iso.md5	2011-06-30	57 Bytes	1	i
zentyal-2.1-2-amd64.iso	2011-06-30	567.4 MB	3	i
zentyal-2.1-2-amd64.iso.md5	2011-06-30	58 Bytes	2	i
zentyal-2.1-1-i386.iso	2011-05-12	592.4 MB	1	i
zentyal-2.1-1-i386.iso.md5	2011-05-12	57 Bytes	2	i
zentyal-2.1-1-amd64.iso.md5	2011-05-12	58 Bytes	2	i
zentyal-2.1-1-amd64.iso	2011-05-12	553.0 MB	1	i
zentyal-2.1-i386.iso.md5	2011-02-22	55 Bytes	2	i
zentyal-2.1-amd64.iso.md5	2011-02-22	56 Bytes	2	i
zentyal-2.1-i386.iso	2011-02-22	529.2 MB	1	i
zentyal-2.1-amd64.iso	2011-02-22	499.5 MB	1	i
zentyal-adsync-2.0.1.exe	2011-01-12	4.1 MB	1	i
zentyal-2.0-3-i386.iso	2010-12-27	541.9 MB	7	i
zentyal-2.0-3-i386.iso.md5	2010-12-27	57 Bytes	1	i
zentyal-2.0-3-amd64.iso	2010-12-27	495.0 MB	3	i
zentyal-2.0-3-amd64.iso.md5	2010-12-27	58 Bytes	1	i
zentyal-2.0-3-vmware-img.zip	2010-12-27	881.2 MB	1	i
zentyal-2.0-3-vbox-img.zip	2010-12-27	881.4 MB	1	i
zentyal-2.0-3-kvm-img.zip	2010-12-27	881.2 MB	1	i
zentyal-2.0-2-i386.iso	2010-12-10	516.3 MB	1	i
zentyal-2.0-2-i386.iso.md5	2010-12-10	57 Bytes	1	i
zentyal-2.0-2-amd64.iso	2010-12-10	478.4 MB	1	i
zentyal-2.0-2-amd64.iso.md5	2010-12-10	58 Bytes	1	i
zentyal-adsync-2.0.exe	2010-12-10	4.0 MB	1	i
zentyal-desktop-0.1.exe	2010-12-10	52.1 MB	1	i
zentyal-2.0-1-amd64.iso.md5	2010-09-06	58 Bytes	1	i
zentyal-2.0-1-amd64.iso	2010-09-06	471.8 MB	1	i
zentyal-2.0-1-i386.iso.md5	2010-09-06	57 Bytes	1	i
zentyal-2.0-1-i386.iso	2010-09-06	481.7 MB	1	i
zentyal-2.0-i386.iso.md5	2010-09-01	55 Bytes	2	i
zentyal-2.0-i386.iso	2010-09-01	482.4 MB	3	i
zentyal-2.0-rc2-i386.iso.md5	2010-08-27	59 Bytes	1	i
zentyal-2.0-rc2-i386.iso	2010-08-27	673.6 MB	2	i
zentyal-2.0-rc1-i386.iso.md5	2010-08-23	59 Bytes	1	i
zentyal-2.0-rc1-i386.iso	2010-08-23	653.3 MB	2	i
ebox_installer-1.5-1-i386.iso.md5	2010-08-05	64 Bytes	1	i
ebox_installer-1.5-1-i386.iso	2010-08-05	648.3 MB	5	i
ebox_installer-1.5-i386.iso.md5	2010-07-25	62 Bytes	1	i
ebox_installer-1.5-i386.iso	2010-07-25	650.3 MB	2	i
ebox-1.4-2-vmware-img.zip	2010-05-15	640.6 MB	1	i
ebox-1.4-2-vbox-img.zip	2010-05-15	641.3 MB	4	i
ebox_installer-1.4-2.iso.md5	2010-05-11	59 Bytes	2	i
ebox_installer-1.4-2.iso	2010-05-11	661.8 MB	1	i
ebox_installer-1.4-1.iso.md5	2010-03-12	59 Bytes	1	i
ebox_installer-1.4-1.iso	2010-03-12	652.7 MB	2	i
ebox-1.4-vmware-img.zip	2010-03-05	880.9 MB	1	i
ebox-1.4-vbox-img.zip	2010-03-05	881.8 MB	1	i
ebox_installer-1.4.iso.md5	2010-02-04	57 Bytes	2	i
ebox_installer-1.4.iso	2010-02-04	628.7 MB	1	i
ebox-adsync-installer-1.4.exe	2010-02-02	4.0 MB	1	i
ebox_installer-1.4-rc1.iso.md5	2010-02-01	61 Bytes	1	i
ebox_installer-1.4-rc1.iso	2010-02-01	629.2 MB	1	i
ebox_installer-1.3.15.iso.md5	2010-01-16	113 Bytes	1	i
ebox_installer-1.3.15.iso	2010-01-16	560.5 MB	1	i
ebox_installer-1.2-6.iso.md5	2009-12-29	59 Bytes	1	i
ebox_installer-1.2-6.iso	2009-12-29	667.4 MB	1	i
ebox_installer-1.3.10-2.iso.md5	2009-12-03	62 Bytes	1	i
ebox_installer-1.3.10-2.iso	2009-12-03	586.5 MB	1	i
ebox_installer-1.3.10-1.iso.md5	2009-12-01	115 Bytes	1	i
ebox_installer-1.3.10-1.iso	2009-12-01	586.5 MB	1	i
ebox_installer-1.2-5.iso.md5	2009-11-30	110 Bytes	1	i
ebox_installer-1.2-5.iso	2009-11-30	665.1 MB	1	i
ebox_installer-1.2-4.iso.md5	2009-11-26	110 Bytes	1	i
ebox_installer-1.2-4.iso	2009-11-26	639.0 MB	1	i
ebox_installer-1.3.10.iso.md5	2009-11-26	113 Bytes	1	i
ebox_installer-1.3.10.iso	2009-11-26	603.4 MB	1	i
ebox_installer-1.2-3.iso	2009-11-18	716.7 MB	1	i
ebox_installer-1.2-3.iso.md5	2009-11-18	112 Bytes	1	i
ebox_installer-1.2-2.iso.md5	2009-11-06	59 Bytes	1	i
ebox_installer-1.2-2.iso	2009-11-06	716.7 MB	1	i
ebox-adsync-installer-1.3.exe	2009-10-19	4.0 MB	1	i
ebox_installer-1.2-1.iso	2009-09-29	675.2 MB	1	i
ebox_installer-1.2-1.iso.md5	2009-09-29	59 Bytes


download	2014-10-29 14:39	102M
favicon.ico	2013-07-21 19:48	1.1K
zentyal-2.2-2-amd64.iso	2012-03-02 14:57	577M
zentyal-2.2-2-amd64.iso.md5	2012-03-02 14:57	58
zentyal-2.2-2-i386.iso	2012-03-02 14:57	572M
zentyal-2.2-2-i386.iso.md5	2012-03-02 14:57	57
zentyal-3.0-2-amd64.iso	2013-03-19 09:20	660M
zentyal-3.0-2-amd64.iso.md5	2013-03-19 09:07	58
zentyal-3.0-2-i386.iso	2013-03-19 09:21	633M
zentyal-3.0-2-i386.iso.md5	2013-03-19 09:08	57
zentyal-3.2-amd64.iso	2013-09-19 08:36	545M
zentyal-3.2-amd64.iso.md5	2013-09-19 08:36	56
zentyal-3.2-i386.iso	2013-09-19 08:03	525M
zentyal-3.2-i386.iso.md5	2013-09-19 08:04	55
zentyal-3.3-amd64.iso	2013-12-16 13:30	651M
zentyal-3.3-amd64.iso.md5	2013-12-16 13:30	56
zentyal-3.3-i386.iso	2013-12-16 13:30	632M
zentyal-3.3-i386.iso.md5	2013-12-16 13:30	55
zentyal-3.4-amd64.iso	2014-03-17 18:38	720M
zentyal-3.4-amd64.iso.md5	2014-03-17 18:38	56
zentyal-3.4-i386.iso	2014-03-17 18:57	701M
zentyal-3.4-i386.iso.md5	2014-03-17 18:57	55
zentyal-3.5-amd64.iso	2014-07-01 10:36	637M
zentyal-3.5-amd64.iso.md5	2014-07-01 11:21	56
zentyal-3.5-i386.iso	2014-07-01 10:37	620M
zentyal-3.5-i386.iso.md5	2014-07-01 11:22	55
zentyal-4.0-amd64.iso	2014-10-29 14:15	636M
zentyal-4.0-amd64.iso.md5	2014-10-29 14:40	56
zentyal-4.1-development-amd64.iso	2015-03-27 10:58	584M
zentyal-4.1-development-amd64.iso.md5	2015-03-27 10:58	68

waiting for network configuration error

Posted on June 25, 2015 by coder

I have found the cause of this is having any interfaces defined in /etc/network/interfaces ( besides lo ) defined as auto. To correct this problem, the recommended solution is to remove your interfaces from this file, and set them up with network manager. Leaving /etc/network/interfaces looking like the default:

nano /etc/init/failsafe.conf

1	nano /etc/init/failsafe.conf

Around 25 lines down in the file you will see a section:

# Plymouth errors should not stop the script because we *must* reach
# the end of this script to avoid letting the system spin forever
# waiting on it to start.
$PLYMOUTH message --text="Waiting for network configuration..." || :
sleep 40

$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :
sleep 59
$PLYMOUTH message --text="Booting system without full network configuration..." || :
To solve the problem, you can just remove the calls to sleep, by commenting the out ( or at least reduce the wait time if your network really does need to wait )

# Plymouth errors should not stop the script because we *must* reach

# the end of this script to avoid letting the system spin forever

# waiting on it to start.

$PLYMOUTH message --text="Waiting for network configuration..." || :

sleep 40

$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :

sleep 59

$PLYMOUTH message --text="Booting system without full network configuration..." || :

To solve the problem, you can just remove the calls to sleep, by commenting the out ( or at least reduce the wait time if your network really does need to wait )

# Plymouth errors should not stop the script because we *must* reach
# the end of this script to avoid letting the system spin forever
# waiting on it to start.
$PLYMOUTH message --text="Waiting for network configuration..." || :
#sleep 4

$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :
#sleep 2
$PLYMOUTH message --text="Booting system without full network configuration..." || :

# Plymouth errors should not stop the script because we *must* reach

# the end of this script to avoid letting the system spin forever

# waiting on it to start.

$PLYMOUTH message --text="Waiting for network configuration..." || :

#sleep 4

$PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :

#sleep 2

$PLYMOUTH message --text="Booting system without full network configuration..." || :

ntp client

Posted on June 25, 2015June 25, 2015 by coder

# Server is ntpd

But client is $ntpdate

we need to install ntpdate

# – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Change Server Time and Location

mv /etc/localtime /etc/localtime.back
ln -s /usr/share/zoneinfo/Europe/Berlin /etc/localtime

1 2	mv /etc/localtime /etc/localtime.back ln -s /usr/share/zoneinfo/Europe/Berlin /etc/localtime

NTP server install on linux

Posted on June 24, 2015June 25, 2015 by coder

I installed NTP server on Ubuntu Server 10.04 using:

sudo apt-get install ntp

1	sudo apt-get install ntp

The NTP daemon seems working and listening on the 123 port.

However, I was not able to get the time from another machine:

sudo ntpdate -u my_ntp_server

1	sudo ntpdate -u my_ntp_server

–

Remove previous version

sudo aptitude remove ntpdate

1	sudo aptitude remove ntpdate

tail -f /var/log/syslog

#-------------------------------------------------
ntpq -c lpeer  
# Example output. 
-europium.canoni 193.79.237.14 2 u 63 64 37 97.375 71.020 1.875
-dtype.org 69.25.96.13 2 u 2 64 77 86.956 69.178 1.804

tail -f /var/log/syslog

#-------------------------------------------------

ntpq -c lpeer

# Example output.

-europium.canoni 193.79.237.14 2 u 63 64 37 97.375 71.020 1.875

-dtype.org 69.25.96.13 2 u 2 64 77 86.956 69.178 1.804

—
If you have ntpd installed on another machine, you can use your first server in the servers list of your ntp.conf file, or can synchronize one time with the -q option, as follows:

ntpd -q [IP address of your server]

1	ntpd -q [IP address of your server]

NFS Server and Client Installation on CentOS 7

Posted on June 22, 2015July 3, 2018 by coder

The NFS server exposes the internal directory as the /export folder, which is bind-mounted on the host. The Docker host then mounts this folder using the NFS protocol to its /mnt folder. Then a so-called infrastructure container is created which binds the mount folder.

For Ubuntu :

apt-get install nfs-kernel-server mkdir /export chmod 777 /export

1	apt-get install nfs-kernel-server mkdir /export chmod 777 /export

mount --bind /opt/test/db /export

1	mount --bind /opt/test/db /export

$ mount -t nfs 127.0.0.1:/export /mnt
$ exportfs -a
$ service nfs-kernel-server restart

$ mount -t nfs 127.0.0.1:/export /mnt

$ exportfs -a

$ service nfs-kernel-server restart

NFS server on CentOS 7.

Network File System (NFS) is a popular distributed filesystem protocol that enables users to mount remote directories on their server.

hostname server1.example.com and IP as 192.168.0.100

Serverside

yum install nfs-utils

#directory that will be shared by NFS:

mkdir /var/nfsshare

#Change the permissions of the folder as follows:

chmod -R 755 /var/nfsshare
chown nfsnobody:nfsnobody /var/nfsshare

yum install nfs-utils

#directory that will be shared by NFS:

mkdir /var/nfsshare

#Change the permissions of the folder as follows:

chmod -R 755 /var/nfsshare

chown nfsnobody:nfsnobody /var/nfsshare

Now create the

mkdir  /var/nfsshare as shared folder,

systemctl enable rpcbind
systemctl enable nfs-server
systemctl enable nfs-lock
systemctl enable nfs-idmap
systemctl start rpcbind
systemctl start nfs-server
systemctl start nfs-lock
systemctl start nfs-idmap

mkdir /var/nfsshare as shared folder,

systemctl enable rpcbind

systemctl enable nfs-server

systemctl enable nfs-lock

systemctl enable nfs-idmap

systemctl start rpcbind

systemctl start nfs-server

systemctl start nfs-lock

systemctl start nfs-idmap

Now we will share the NFS directory over the network a follows:

nano /etc/exports

We will make two sharing points /home and /var/nfsshare. Edit the exports file as follows:

/var/nfsshare    192.168.0.101(rw,sync,no_root_squash,no_all_squash)
/home            192.168.0.101(rw,sync,no_root_squash,no_all_squash)

1 2	/var/nfsshare 192.168.0.101(rw,sync,no_root_squash,no_all_squash) /home 192.168.0.101(rw,sync,no_root_squash,no_all_squash)

Note 192.168.0.101 is the IP of client machine, if you wish that any other client should access it you need to add the it IP wise other wise you can add “*” instead of IP for all IP access.

Condition is that it must be pingable at both ends.

start the NFS service:

systemctl restart nfs-server

1	systemctl restart nfs-server

Again we need to add the NFS service override in CentOS 7 firewall-cmd public zone service as:

firewall-cmd --permanent --zone=public --add-service=nfs
firewall-cmd --permanent --zone=public --add-service=mountd
firewall-cmd --permanent --zone=public --add-service=rpc-bind
firewall-cmd --reload

firewall-cmd --permanent --zone=public --add-service=nfs

firewall-cmd --permanent --zone=public --add-service=mountd

firewall-cmd --permanent --zone=public --add-service=rpc-bind

firewall-cmd --reload

Now we are ready with the NFS server part.

Client Side

yum install nfs-utils

# Now create the NFS directory mount points:

mkdir -p /mnt/nfs/home
mkdir -p /mnt/nfs/var/nfsshare

# Mount the NFS shared home directory in the client machine as shown below:

mount -t nfs 192.168.0.100:/home /mnt/nfs/home/

# Multi Mount
mount -t nfs 192.168.0.100:/var/nfsshare /mnt/nfs/var/nfsshare/

df -kh

[root@client1 ~]# df -kh
Filesystem                    Size  Used Avail Use% Mounted on
192.168.0.100:/var/nfsshare   39G  980M   38G   3% /mnt/nfs/var/nfsshare
192.168.0.100:/home           19G   33M   19G   1% /mnt/nfs/home

# ! Connected 

touch /mnt/nfs/var/nfsshare/test_nfs

yum install nfs-utils

# Now create the NFS directory mount points:

mkdir -p /mnt/nfs/home

mkdir -p /mnt/nfs/var/nfsshare

# Mount the NFS shared home directory in the client machine as shown below:

mount -t nfs 192.168.0.100:/home /mnt/nfs/home/

# Multi Mount

mount -t nfs 192.168.0.100:/var/nfsshare /mnt/nfs/var/nfsshare/

df -kh

[root@client1 ~]# df -kh

Filesystem Size Used Avail Use% Mounted on

192.168.0.100:/var/nfsshare 39G 980M 38G 3% /mnt/nfs/var/nfsshare

192.168.0.100:/home 19G 33M 19G 1% /mnt/nfs/home

# ! Connected

touch /mnt/nfs/var/nfsshare/test_nfs

Permanent NFS mounting

nano /etc/fstab

1	nano /etc/fstab

Add the entries like this:

[...]
192.168.0.100:/home    /mnt/nfs/home   nfs defaults 0 0
192.168.0.100:/var/nfsshare    /mnt/nfs/var/nfsshare   nfs defaults 0 0

[...]

192.168.0.100:/home /mnt/nfs/home nfs defaults 0 0

192.168.0.100:/var/nfsshare /mnt/nfs/var/nfsshare nfs defaults 0 0

Note 192.168.0.100 is the server NFS-share IP address, it will vary in your case.

This will make the permanent mount of the NFS-share.

Anwendung	NFS
Darstellung	XDR
Sitzung	(Sun-) RPC
Transport	(UDP)	TCP
Netzwerk	IP (IPv4, IPv6)
Netzzugang	Ethernet	Token
Ring	FDDI	…
Das Network File System – abgekürzt NFS (auch Network File Service) –
 ist ein von Sun Microsystems entwickeltes Protokoll, das den 
Zugriff auf Dateien über ein Netzwerk ermöglicht. 
Dabei werden die Dateien nicht wie z. B. bei FTP übertragen,
 sondern die Benutzer können auf Dateien, die sich auf einem 
entfernten Rechner befinden, so zugreifen, als ob sie auf ihrer
 lokalen Festplatte abgespeichert wären.

Bei diesem UNIX-Netzwerkprotokoll handelt es sich um einen
 Internet-Standard (RFC 1094, RFC 1813, RFC 3530, RFC 7530),
 der auch als verteiltes Dateisystem (englisch distributed file system)
 bezeichnet wird.


# Server-Adresse: 10.0.0.1
# NFSv2, NFSv3:
# Exportiert /path/to/directory an alle IPs von 10.0.0.0 bis 10.0.255.255,
# und zwar zum Lesen/Schreiben (rw), asynchronem Zugriff (Daten werden
# nicht sofort geschrieben) und auch von Ports über 1024 aus (insecure)
#
# Erreichbar als: 10.0.0.1:/path/to/directory
#
### Linux-Systeme
/path/to/directory        10.0.0.0/16(rw,async,insecure)

### FreeBSD
/path/to/directory        -network 10.0.0.0/16
# NFSv4:
# Benötigt zur optimalen Funktion eine Freigabe mit der Option fsid=0.
# Diese wird als root-Freigabe genutzt und ist als die Freigabe / zu 
# erreichen. Die anderen Freigaben liegen unterhalb davon. Ansonsten 
# ist optional eine Authentifizierung/Verschlüsselung mit Kerberos 
# möglich.
#
### Linux-Systeme:
# Erreichbar als 10.0.0.1:/
# Wird diese Freigabe eingehängt, so sind alle darunterliegenden 
# Freigaben logischerweise zugänglich.
/path/to/nfsv4/root       10.0.0.0/16(rw,async,insecure,fsid=0)
# Erreichbar als 10.0.0.1:/export1
/path/to/nfsv4/root/export1 10.0.0.0/16(rw,async,insecure)

### FreeBSD
# Root-Punkt spezifizieren (unter Linux der mit fsid=0 markierte Punkt)
V4: /path/to/nfsv4/root    -network 10.0.0.0/16
# Freigaben angeben
/path/to/nfsv4/root/export1 -network 10.0.0.0/16
Der Client kann eine Freigabe manuell mounten oder ggf. mit einem Eintrag in der Datei fstab automatisieren.


REf: Wikipedia. direct content

Anwendung NFS

Darstellung XDR

Sitzung (Sun-) RPC

Transport (UDP) TCP

Netzwerk IP (IPv4, IPv6)

Netzzugang Ethernet Token

Ring FDDI …

Das Network File System – abgekürzt NFS (auch Network File Service) –

ist ein von Sun Microsystems entwickeltes Protokoll, das den

Zugriff auf Dateien über ein Netzwerk ermöglicht.

Dabei werden die Dateien nicht wie z. B. bei FTP übertragen,

sondern die Benutzer können auf Dateien, die sich auf einem

entfernten Rechner befinden, so zugreifen, als ob sie auf ihrer

lokalen Festplatte abgespeichert wären.

Bei diesem UNIX-Netzwerkprotokoll handelt es sich um einen

Internet-Standard (RFC 1094, RFC 1813, RFC 3530, RFC 7530),

der auch als verteiltes Dateisystem (englisch distributed file system)

bezeichnet wird.

# Server-Adresse: 10.0.0.1

# NFSv2, NFSv3:

# Exportiert /path/to/directory an alle IPs von 10.0.0.0 bis 10.0.255.255,

# und zwar zum Lesen/Schreiben (rw), asynchronem Zugriff (Daten werden

# nicht sofort geschrieben) und auch von Ports über 1024 aus (insecure)

# Erreichbar als: 10.0.0.1:/path/to/directory

### Linux-Systeme

/path/to/directory 10.0.0.0/16(rw,async,insecure)

### FreeBSD

/path/to/directory -network 10.0.0.0/16

# NFSv4:

# Benötigt zur optimalen Funktion eine Freigabe mit der Option fsid=0.

# Diese wird als root-Freigabe genutzt und ist als die Freigabe / zu

# erreichen. Die anderen Freigaben liegen unterhalb davon. Ansonsten

# ist optional eine Authentifizierung/Verschlüsselung mit Kerberos

# möglich.

### Linux-Systeme:

# Erreichbar als 10.0.0.1:/

# Wird diese Freigabe eingehängt, so sind alle darunterliegenden

# Freigaben logischerweise zugänglich.

/path/to/nfsv4/root 10.0.0.0/16(rw,async,insecure,fsid=0)

# Erreichbar als 10.0.0.1:/export1

/path/to/nfsv4/root/export1 10.0.0.0/16(rw,async,insecure)

### FreeBSD

# Root-Punkt spezifizieren (unter Linux der mit fsid=0 markierte Punkt)

V4: /path/to/nfsv4/root -network 10.0.0.0/16

# Freigaben angeben

/path/to/nfsv4/root/export1 -network 10.0.0.0/16

Der Client kann eine Freigabe manuell mounten oder ggf. mit einem Eintrag in der Datei fstab automatisieren.

REf: Wikipedia. direct content

Installing hadoop 2.4.0 on Ubuntu server

Posted on June 20, 2015July 14, 2018 by coder

First of all, THESE ARE IMPORTANT FOR INDRODUCTION

*Ubuntu server 14.04
*VM in VirtualBox with 1GB RAM
*SWAP SPACE : SELECT more than 2 GB

Up-to-date system.

kutayzorlu@coder_telekom:~$ sudo apt-get update 
kutayzorlu@coder_telekom:~$ sudo apt-get upgrade

1 2	kutayzorlu@coder_telekom:~$ sudo apt-get update kutayzorlu@coder_telekom:~$ sudo apt-get upgrade

Moreover, it is advisable not to run Hadoop services through a general-purpose user, so the next step consists in adding a group hadoop and a user hadoop-user belonging to that group

kutayzorlu@coder_telekom:~$ sudo addgroup hadoop
kutayzorlu@coder_telekom:~$ sudo adduser --ingroup hadoop hadoop-user

1 2	kutayzorlu@coder_telekom:~$ sudo addgroup hadoop kutayzorlu@coder_telekom:~$ sudo adduser --ingroup hadoop hadoop-user

Installing Java
The mentioned tutorials suggest a potentially unsafe procedure in order to install the jdk through `apt-get`,

kutayzorlu@coder_telekom:~$ wget   "http://server12.kutayzorlu.com/7u45-b18/jdk-7u45-linux-x64.tar.gz"
...
kutayzorlu@coder_telekom:~$ tar -xvzf jdk-7-linux-x64.tar.gz
kutayzorlu@coder_telekom:~$ sudo mkdir /usr/local/java
kutayzorlu@coder_telekom:~$ sudo cp -r jdk1.7.0_45 /usr/local/java
kutayzorlu@coder_telekom:~$ sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/local/java/jdk1.7.0_45/bin/javac" 1
kutayzorlu@coder_telekom:~$ sudo update-alternatives --set javac /usr/local/java/jdk1.7.0_45/bin/javac

kutayzorlu@coder_telekom:~$ wget "http://server12.kutayzorlu.com/7u45-b18/jdk-7u45-linux-x64.tar.gz"

...

kutayzorlu@coder_telekom:~$ tar -xvzf jdk-7-linux-x64.tar.gz

kutayzorlu@coder_telekom:~$ sudo mkdir /usr/local/java

kutayzorlu@coder_telekom:~$ sudo cp -r jdk1.7.0_45 /usr/local/java

kutayzorlu@coder_telekom:~$ sudo update-alternatives --install "/usr/bin/javac" "javac" "/usr/local/java/jdk1.7.0_45/bin/javac" 1

kutayzorlu@coder_telekom:~$ sudo update-alternatives --set javac /usr/local/java/jdk1.7.0_45/bin/javac

Finally, a couple of environment variables should be set up so that the java executables are in $PATH and hadoop knows where java has been installed: this is easily accomplished adding

JAVA_HOME=/usr/local/java/jdk1.7.0_45
PATH=$PATH:$HOME/bin:$JAVA_HOME/bin
export JAVA_HOME
export PATH

JAVA_HOME=/usr/local/java/jdk1.7.0_45

PATH=$PATH:$HOME/bin:$JAVA_HOME/bin

export JAVA_HOME

export PATH

at the end of /etc/profile <<< We need to edit that to set automatically JAVA PATH

kutayzorlu@coder_telekom:~$ . /etc/profile
kutayzorlu@coder_telekom:~$ javac -version
javac 1.7.0_45

kutayzorlu@coder_telekom:~$ . /etc/profile

kutayzorlu@coder_telekom:~$ javac -version

javac 1.7.0_45

Setup SSH

All communications with Hadoop are encrypted via SSH, thus the corresponding server should be installed:

kutayzorlu@coder_telekom:~$ sudo apt-get install openssh-server

1	kutayzorlu@coder_telekom:~$ sudo apt-get install openssh-server

and the hadoop-user must be associated to a key pair and subsequently granting its access to the local machine:

kutayzorlu@coder_telekom:~$ su - hadoop-user
hadoop-user@coder_telekom:~$ ssh-keygen -t rsa -P ""    
#<<<<<<<<<<<< Generating public/private rsa key pair. 
The key's randomart image is: 
hadoop-user@coder_telekom:~$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

kutayzorlu@coder_telekom:~$ su - hadoop-user

hadoop-user@coder_telekom:~$ ssh-keygen -t rsa -P ""

#<<<<<<<<<<<< Generating public/private rsa key pair.

The key's randomart image is:

hadoop-user@coder_telekom:~$ cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys

Now hadoop-user should be able to access via ssh to localhost without ( WE SET THE PASS = “null”)providing a password:

hadoop-user@coder_telekom:~$ ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
Last login: 
$

hadoop-user@coder_telekom:~$ ssh localhost

The authenticity of host 'localhost (::1)' can't be established.

Last login:

Disable IPV6

Hadoop and IPV6 do not agree on the meaning of 0.0.0.0 address,

LOOK AT : ??>>>>> /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

net.ipv6.conf.all.disable_ipv6 = 1

net.ipv6.conf.default.disable_ipv6 = 1

net.ipv6.conf.lo.disable_ipv6 = 1

REBOOT SYSTEM

CONTROL

cat /proc/sys/net/ipv6/conf/all/disable_ipv6  # should be 1,
#1 meaning that IPV6 is actually disabled.

1 2	cat /proc/sys/net/ipv6/conf/all/disable_ipv6 # should be 1, #1 meaning that IPV6 is actually disabled.

Hadoop

Download and install Hadoop

Download hadoop-2.4.0.tar.gz, unpack it and move the results in /usr/local, adding a symlink using the more friendly name hadoop and changing ownership of the directory contents to the hadoop-user user:

kutayzorlu@coder_telekom:~$ wget wget http://apache.mirrors.pair.com/hadoop/common/hadoop-2.4.0/hadoop-2.4.0.tar.gz
...
kutayzorlu@coder_telekom:~$ tar -xzvf hadoop-2.4.0.tar.gz
kutayzorlu@coder_telekom:~$ sudo mv hadoop-2.4.0 /usr/local
kutayzorlu@coder_telekom:~$ cd /usr/local
kutayzorlu@coder_telekom:/usr/local$ sudo ln -s hadoop-2.4.0 hadoop
kutayzorlu@coder_telekom:/usr/local$ sudo chown -R hadoop-user:hadoop hadoop-2.4.0

kutayzorlu@coder_telekom:~$ wget wget http://apache.mirrors.pair.com/hadoop/common/hadoop-2.4.0/hadoop-2.4.0.tar.gz

...

kutayzorlu@coder_telekom:~$ tar -xzvf hadoop-2.4.0.tar.gz

kutayzorlu@coder_telekom:~$ sudo mv hadoop-2.4.0 /usr/local

kutayzorlu@coder_telekom:~$ cd /usr/local

kutayzorlu@coder_telekom:/usr/local$ sudo ln -s hadoop-2.4.0 hadoop

kutayzorlu@coder_telekom:/usr/local$ sudo chown -R hadoop-user:hadoop hadoop-2.4.0

Setup the dedicated user environment
Switch to the `hadoop-user` user and add the following lines at the end of `~/.bashrc`:

# Set Hadoop-related environment variables
export HADOOP_PREFIX=/usr/local/hadoop
export HADOOP_HOME=/usr/local/hadoop
export HADOOP_MAPRED_HOME=${HADOOP_HOME}
export HADOOP_COMMON_HOME=${HADOOP_HOME}
export HADOOP_HDFS_HOME=${HADOOP_HOME}
export YARN_HOME=${HADOOP_HOME}
export HADOOP_CONF_DIR=${HADOOP_HOME}/etc/hadoop
# Native Path
export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native
export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"
#Java path
export JAVA_HOME='/usr/local/java/jdk1.7.0_45'
# Add Hadoop bin/ directory to PATH
export PATH=$PATH:$HADOOP_HOME/bin:$JAVA_PATH/bin:$HADOOP_HOME/sbin

# Set Hadoop-related environment variables

export HADOOP_PREFIX=/usr/local/hadoop

export HADOOP_HOME=/usr/local/hadoop

export HADOOP_MAPRED_HOME=${HADOOP_HOME}

export HADOOP_COMMON_HOME=${HADOOP_HOME}

export HADOOP_HDFS_HOME=${HADOOP_HOME}

export YARN_HOME=${HADOOP_HOME}

export HADOOP_CONF_DIR=${HADOOP_HOME}/etc/hadoop

# Native Path

export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native

export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

#Java path

export JAVA_HOME='/usr/local/java/jdk1.7.0_45'

# Add Hadoop bin/ directory to PATH

export PATH=$PATH:$HADOOP_HOME/bin:$JAVA_PATH/bin:$HADOOP_HOME/sbin

To have the new environment variables in place,

1- reload .bashrc through “source .bashrc"

2- then open /usr/local/hadoop/etc/hadoop/hadoop-env.sh ,

3- uncomment the line setting JAVA_HOME and set its value to the jdk directory:

export JAVA_HOME=/usr/local/java/jdk1.7.0_45

1	export JAVA_HOME=/usr/local/java/jdk1.7.0_45

Configure Hadoop

Before being able to actually use the hadoop file system it is necessary to modify some configuration files inside /usr/local/hadoop/etc/hadoop
All such files follow the an XML format, and the updates should concern the top-level node configuration
(likely empty after the hadoop installation). Specifically:

in yarn-site.xml :

    yarn.nodemanager.aux-services
    mapreduce_shuffle
  
  
    yarn.nodemanager.aux-services.mapreduce.shuffle.class
    org.apache.hadoop.mapred.ShuffleHandler

yarn.nodemanager.aux-services

mapreduce_shuffle

yarn.nodemanager.aux-services.mapreduce.shuffle.class

org.apache.hadoop.mapred.ShuffleHandler

look in core-site.xml:

fs.default.name hdfs://localhost:9000

1
2

fs.default.name
hdfs://localhost:9000

look in mapred-site.xml

mapreduce.framework.name yarn

1
2

mapreduce.framework.name
yarn

nano hdfs-site.xml:

    dfs.replication
    1
  
  
    dfs.namenode.name.dir
    file:/usr/local/hadoop/yarn_data/hdfs/namenode
  
  
    dfs.datanode.data.dir
    file:/usr/local/hadoop/yarn_data/hdfs/datanode

dfs.replication

dfs.namenode.name.dir

file:/usr/local/hadoop/yarn_data/hdfs/namenode

dfs.datanode.data.dir

file:/usr/local/hadoop/yarn_data/hdfs/datanode

Run these commands.

hadoop-user@coder_telekom:~$ mkdir -p /usr/local/hadoop/yarn_data/hdfs/namenode
hadoop-user@coder_telekom:~$ mkdir -p /usr/local/hadoop/yarn_data/hdfs/datanode

1 2	hadoop-user@coder_telekom:~$ mkdir -p /usr/local/hadoop/yarn_data/hdfs/namenode hadoop-user@coder_telekom:~$ mkdir -p /usr/local/hadoop/yarn_data/hdfs/datanode

Formatting the distributed file system

USER should be hadoop user

hadoop-user@coder_telekom:~$ hdfs namenode -format
...

1 2	hadoop-user@coder_telekom:~$ hdfs namenode -format ...

Find the these 2 file and run

start-dfs.sh

start-yarn.sh

hadoop-user@coder_telekom:~$ start-dfs.sh
8/08/10 13:18:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [localhost]
localhost: starting namenode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-namenode-coder_telekom.out
localhost: starting datanode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-datanode-coder_telekom.out
Starting secondary namenodes [0.0.0.0]
0.0.0.0: starting secondarynamenode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-secondarynamenode-coder_telekom.out
8/08/10 13:18:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
hadoop-user@coder_telekom:~$ start-yarn.sh
starting yarn daemons
starting resourcemanager, logging to /usr/local/hadoop/logs/yarn-hadoop-user-resourcemanager-coder_telekom.out
localhost: starting nodemanager, logging to /usr/local/hadoop-2.4.0/logs/yarn-hadoop-user-nodemanager-coder_telekom.out

....

hadoop-user@coder_telekom:~$ hdfs dfs -mkdir /user
hadoop-user@coder_telekom:~$ hdfs dfs -mkdir /user/hadoop-user

... 
hadoop-user@coder_telekom:~$ hadoop jar /usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.4.0.jar pi 10 1000 ... Job Finished in 22.136 seconds Estimated value of Pi is 3.142857....

hadoop-user@coder_telekom:~$ start-dfs.sh

8/08/10 13:18:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable

Starting namenodes on [localhost]

localhost: starting namenode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-namenode-coder_telekom.out

localhost: starting datanode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-datanode-coder_telekom.out

Starting secondary namenodes [0.0.0.0]

0.0.0.0: starting secondarynamenode, logging to /usr/local/hadoop-2.4.0/logs/hadoop-hadoop-user-secondarynamenode-coder_telekom.out

8/08/10 13:18:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable

hadoop-user@coder_telekom:~$ start-yarn.sh

starting yarn daemons

starting resourcemanager, logging to /usr/local/hadoop/logs/yarn-hadoop-user-resourcemanager-coder_telekom.out

localhost: starting nodemanager, logging to /usr/local/hadoop-2.4.0/logs/yarn-hadoop-user-nodemanager-coder_telekom.out

....

hadoop-user@coder_telekom:~$ hdfs dfs -mkdir /user

hadoop-user@coder_telekom:~$ hdfs dfs -mkdir /user/hadoop-user

...

hadoop-user@coder_telekom:~$ hadoop jar /usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.4.0.jar pi 10 1000 ... Job Finished in 22.136 seconds Estimated value of Pi is 3.142857....

... 
# For stop daemons
$ stop-dfs.sh 
$ stop-yarn.sh.

...

# For stop daemons

$ stop-dfs.sh

$ stop-yarn.sh.

Hadoop security File and directory permissions

Posted on June 20, 2015June 20, 2015 by coder

Permissions for both HDFS and local fileSystem paths

The following table lists various paths on HDFS and local filesystems (on all nodes) and recommended permissions:

Filesystem	Path	User:Group	Permissions
local	`dfs.namenode.name.dir`	hdfs:hadoop	`drwx------`
local	`dfs.datanode.data.dir`	hdfs:hadoop	`drwx------`
local	$HADOOP_LOG_DIR	hdfs:hadoop	`drwxrwxr-x`
local	$YARN_LOG_DIR	yarn:hadoop	`drwxrwxr-x`
local	`yarn.nodemanager.local-dirs`	yarn:hadoop	`drwxr-xr-x`
local	`yarn.nodemanager.log-dirs`	yarn:hadoop	`drwxr-xr-x`
local	container-executor	root:hadoop	`--Sr-s--*`
local	`conf/container-executor.cfg`	root:hadoop	`r-------*`
hdfs	/	hdfs:hadoop	`drwxr-xr-x`
hdfs	/tmp	hdfs:hadoop	`drwxrwxrwxt`
hdfs	/user	hdfs:hadoop	`drwxr-xr-x`
hdfs	`yarn.nodemanager.remote-app-log-dir`	yarn:hadoop	`drwxrwxrwxt`
hdfs	`mapreduce.jobhistory.intermediate-done-dir`	mapred:hadoop	`drwxrwxrwxt`
hdfs	`mapreduce.jobhistory.done-dir`	mapred:hadoop	`drwxr-x---`

For More please Visit that page :
http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/SecureMode.html#Proxy_user

Page 37 of 858

« 1 … 35 36 37 38 39 … 858 »

Serverside

Client Side

Permanent NFS mounting

Installing hadoop 2.4.0

Installing Java The mentioned tutorials suggest a potentially unsafe procedure in order to install the jdk through apt-get,

Setup SSH

Disable IPV6

Hadoop

Download and install Hadoop

Setup the dedicated user environment Switch to the hadoop-user user and add the following lines at the end of ~/.bashrc:

Configure Hadoop

Formatting the distributed file system

Permissions for both HDFS and local fileSystem paths

Installing Java
The mentioned tutorials suggest a potentially unsafe procedure in order to install the jdk through `apt-get`,

Setup the dedicated user environment
Switch to the `hadoop-user` user and add the following lines at the end of `~/.bashrc`: