<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SLES Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://www.vavai.net/tag/sles/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/sles/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Tue, 08 Dec 2015 20:20:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Zimbra : No space left on device &#038; Inode Usage</title>
		<link>https://www.vavai.net/zimbra-no-space-left-on-device-inode-usage/</link>
					<comments>https://www.vavai.net/zimbra-no-space-left-on-device-inode-usage/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Tue, 08 Dec 2015 20:20:34 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1967</guid>

					<description><![CDATA[<p>Yesterday, I got a phone call from my customer regarding their Zimbra Mail Server. I&#8217;ve helped them setting up and configuring Zimbra, 2-3 years ago. Their Zimbra mail server not working properly since yesterday morning. Dig on log details show me error message : &#8220;Zimbra No space left on device&#8221;, but it should be wrong,...</p>
<p>The post <a href="https://www.vavai.net/zimbra-no-space-left-on-device-inode-usage/">Zimbra : No space left on device &#038; Inode Usage</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Yesterday, I got a phone call from my customer regarding their Zimbra Mail Server. I&#8217;ve helped them setting up and configuring Zimbra, 2-3 years ago. Their Zimbra mail server not working properly since yesterday morning. Dig on log details show me error message : <em>&#8220;Zimbra No space left on device&#8221;</em>, but it should be wrong, because they have plenty free space both on system and data disk. I&#8217;m remembering that I&#8217;ve  experience  similar error on one of my hosting server when compromised account broadcast too many small files and fill in all Inode allocation.<br />
<a href="http://54.254.121.108/wp-content/uploads/2015/12/vavai-df-h.png"><img fetchpriority="high" decoding="async" class="alignnone size-full wp-image-1970" src="http://54.254.121.108/wp-content/uploads/2015/12/vavai-df-h.png" alt="vavai-df-h" width="729" height="205" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2015/12/vavai-df-h.png 729w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2015/12/vavai-df-h-300x84.png 300w" sizes="(max-width: 729px) 100vw, 729px" /></a><br />
<span id="more-1967"></span>The first command that I did was stopping Zimbra services. Deeper investigation <strong>with df -ih</strong> prove me that the problem came from similar cause. All Inode file system has been full and no free Inode available. Checking <strong>/tmp</strong> folder seems to make the server hang for a while, until then displaying too many files. Looking at the result, there were about 1 million files on /tmp/tmpXXX, eating all Inode stock.<br />
<a href="http://54.254.121.108/wp-content/uploads/2015/12/vavai-df-i.png"><img decoding="async" class="alignnone size-full wp-image-1971" src="http://54.254.121.108/wp-content/uploads/2015/12/vavai-df-i.png" alt="vavai-df-i" width="873" height="210" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2015/12/vavai-df-i.png 873w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2015/12/vavai-df-i-300x72.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2015/12/vavai-df-i-768x185.png 768w" sizes="(max-width: 873px) 100vw, 873px" /></a><br />
I was lucky to find out that /tmp has too many files on it, but you can also using following command to looking for suspected folder :<br />
[code lang=&#8221;bash&#8221;]sudo find . -xdev -type f | cut -d &#8220;/&#8221; -f 2 | sort | uniq -c | sort -n<br />
[/code]<br />
or<br />
[code lang=&#8221;bash&#8221;]for i in /*; do echo $i; find $i |wc -l; done[/code]<br />
or for specific folder :<br />
[code lang=&#8221;bash&#8221;]for i in /tmp/*; do echo $i; find $i |wc -l; done[/code]<br />
I&#8217;m trying to remove all /tmp file starting with tmp-XXX on file name but server responded that removal command was not successful  because there were too many files on the search criteria (I forgot an error details <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> ). I ended up manually delete the file with : <strong>rm /tmp/tmp1*</strong>, <strong>rm /tm/tmp2*</strong> and so on, increment with number and then alphabet on it&#8217;s file name.<br />
After a while, I&#8217;m too tired to delete temporary file manually. In short calculate, I must execute 10 (for number from 1-10)+26 (for lowercase alphabet)+26 (for uppercase alphabet), totally 62 times execution. Not a smart ways to do stupid works <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /><br />
Searching for a bash script, I got this nice and simpler script :<br />
[code lang=&#8221;bash&#8221;]<br />
for alphabet in {A..Z}<br />
do<br />
echo $alphabet<br />
rm /tmp/tmp_$alphabet*<br />
done<br />
[/code]<br />
The script could be nicer if could also include number and lowercase alphabet on top of script but never mind, I was quite satisfied to run above script as much as 3 times only by changing the parameter.<br />
In less than 5 minutes, all temporary files was deleted successfully and server have pretty much Inode available now. I can now starting Zimbra services and monitor log for any possible cause. The following log entry on <strong>/var/log/zimbra.log</strong> caught my attention :<br />
<em>>Dec<span class="Apple-converted-space">  7 13:14:36 mail postfix/proxymap[19610]: warning: ldap:/opt/zimbra/conf/ldap-slm.cf is unavailable. open /opt/zimbra/conf/ldap-slm.cf: Permission denied</em><br />
Checking on my other running Zimbra instance give me following permission :<br />
[code lang=&#8221;bash&#8221;]# ls -ltrh  /opt/zimbra/conf/ldap-slm.cf[/code]<br />
<em>>-rw-r&#8212;&#8211; 1 zimbra postfix 603 Dec<span class="Apple-converted-space">  3 02:20 /opt/zimbra/conf/ldap-slm.cf</em><br />
I&#8217;m stopping Zimbra services again, then execute fix the permission :<br />
[code lang=&#8221;bash&#8221;]/opt/zimbra/libexec/zmfixperms &#8211;extended &#8211;verbose[/code]<br />
and then looking at file permission again before restarting the services. However, my eyes stumble upon with other error logs :<br />
<em>>Dec<span class="Apple-converted-space">  7 06:27:41 mail postfix/postdrop[4233]: warning: mail_queue_enter: create file maildrop/952460.4233: Permission denied</em><br />
<em>>Dec<span class="Apple-converted-space">  7 06:27:42 mail postfix/postdrop[6057]: warning: mail_queue_enter: create file maildrop/43485.6057: Permission denied</em><br />
<em>>Dec<span class="Apple-converted-space">  7 06:27:42 mail postfix/postdrop[6084]: warning: mail_queue_enter: create file maildrop/127795.6084: Permission denied</em><br />
<em>>Dec<span class="Apple-converted-space">  7 06:27:51 mail postfix/postdrop[19190]: warning: mail_queue_enter: create file maildrop/739237.19190: Permission denied</em><br />
It&#8217;s seems some postdrop services are still exist and running and was not affected by stopping Zimbra services. I&#8217;m trying to stop Zimbra services again and then kill all Zimbra and postdrop process with root permission :<br />
[code lang=&#8221;bash&#8221;]<br />
killall zimbra<br />
killall postdrop<br />
ps aux | grep zimbra<br />
ps aux | grep postdrop<br />
[/code]<br />
and then restarting Zimbra services. Finally, Zimbra working properly now and no error entries on Zimbra logs. Mission accomplised <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>The post <a href="https://www.vavai.net/zimbra-no-space-left-on-device-inode-usage/">Zimbra : No space left on device &#038; Inode Usage</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-no-space-left-on-device-inode-usage/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>VMware Tips : vCenter Server Appliance (vCSA) Installation &#038; Configuration</title>
		<link>https://www.vavai.net/vmware-tips-vcenter-server-appliance-vcsa-installation-configuration/</link>
					<comments>https://www.vavai.net/vmware-tips-vcenter-server-appliance-vcsa-installation-configuration/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Mon, 17 Feb 2014 09:18:50 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE]]></category>
		<category><![CDATA[vCenter]]></category>
		<category><![CDATA[vCenter Server Appliance]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1743</guid>

					<description><![CDATA[<p>What is VMware vCenter Server Appliance? Prior to vSphere 5.0, we can only run vCenter on Windows Server, either on physical or virtual machine (VM ). Since vSphere 5.1, VMware provide an option to run vCenter in the form of VM appliance. vCenter Server Appliance ( vCSA ) is a package system based on SUSE...</p>
<p>The post <a href="https://www.vavai.net/vmware-tips-vcenter-server-appliance-vcsa-installation-configuration/">VMware Tips : vCenter Server Appliance (vCSA) Installation &#038; Configuration</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h3>What is VMware vCenter Server Appliance?</h3>
<p>Prior to vSphere 5.0, we can only run vCenter on Windows Server, either on physical or virtual machine (VM ). Since vSphere 5.1, VMware provide an option to run vCenter in the form of VM appliance.<br />
vCenter Server Appliance ( vCSA ) is a package system based on SUSE Linux Enterprise Server 11 64 bit. In early versions of vCSA, it includes IBM DB2 database that sufficient to manage maximum 5 vSphere host or up to 50 VM. In vCSA 5.5, VMware replace IBM DB2 databases with vPostgres and increase capability so that each vCSA can handle up to 300 hosts and 3000 VM.<br />
Just like Windows -based vCenter Server, vCSA can also be managed using web access or via vSphere client, although VMware improving web based applications so that most of the new features can only be managed through vCenter Web Access client.<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter.jpg"><img decoding="async" class="alignnone size-full wp-image-1803" alt="vavai-excellent-vmware-vcenter" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter.jpg" width="411" height="371" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter.jpg 411w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-300x271.jpg 300w" sizes="(max-width: 411px) 100vw, 411px" /></a></p>
<h3><span id="more-1743"></span>The advantages of using vCenter appliance</h3>
<ol>
<li><strong>Deployment Simplification</strong>, the system configuration mostly done by using web, installing the Windows-based vSphere client is not mandatory. Web client interface can be accessed either via Windows or Linux or Mac</li>
<li><span style="line-height: 1.5em;"><strong>Lower license costs</strong>, because we do not need to buy a Windows license for vCenter Server and Windows client (XP, Vista, 7 , 8 ) for vSphere client as if using Windows based vSphere client</span></li>
<li><span style="line-height: 1.5em;"><strong>Universal Access</strong>. We can manage vSphere environment by using browser</span></li>
<li><span style="line-height: 1.5em;"><strong>Future models</strong>. Some applications such as VMware vSphere Data Protection can only be accessed using vCenter Webclient</span></li>
</ol>
<h3>Disadvantages of Using the vCenter Appliance</h3>
<ol>
<li><strong>vCenter Linked Mode</strong>. Link mode option for vCenter integration not available on vCSA</li>
<li><span style="line-height: 1.5em;"> <strong>Microsoft SQL Server Database</strong>. vCSA doesn&#8217;t  support  Microsoft SQL Server database</span></li>
<li><span style="line-height: 1.5em;"><strong>IPv6</strong>. vCSA access using IPv6 currently not supported</span></li>
</ol>
<h3>Appliance Deployment</h3>
<p>vCenter appliance can be downloaded via http://vmware.com/download in the form of an .ova and .ovf file as well. Prior to deployment, prepare the following matters :</p>
<ul>
<li>Resources capability to deploy VM with minimum 8 GB of memory, at least a dual core processor with a minimum capacity of 125 GB disk (use thick provisioning mechanism) . vCenter Appliance can run as a VM on VMware vSphere or VMware Workstation</li>
<li><span style="line-height: 1.5em;">vCenter Server Appliance (OVF+VMDK or OVA version), can be downloaded from VMWare website</span></li>
<li><span style="line-height: 1.5em;">Proper DNS settings to identify for vCenter and host naming resolution</span></li>
</ul>
<p>To deploy vCenter Appliance, please do the following :</p>
<ol>
<li>Open the vCenter Client and connect to the destination host</li>
<li><span style="line-height: 1.5em;">Select the menu File | Deploy OVF Template<br />
</span><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1805" alt="vavai-excellent-vmware-vcenter-appliance-deployment" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment.jpg" width="486" height="295" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment.jpg 486w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment-300x182.jpg 300w" sizes="auto, (max-width: 486px) 100vw, 486px" /></a></li>
<li><span style="line-height: 1.5em;">Select the .OVA or OVF file</span></li>
<li><span style="line-height: 1.5em;">Follow the deployment wizard instruction<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment-wizard.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1806" alt="vavai-excellent-vmware-vcenter-appliance-deployment-wizard" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment-wizard.jpg" width="716" height="456" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment-wizard.jpg 716w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-appliance-deployment-wizard-300x191.jpg 300w" sizes="auto, (max-width: 716px) 100vw, 716px" /></a></span></li>
<li><span style="line-height: 1.5em;">After finishing deployment wizard,  start vCenter for initial setup. Please be patient <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /><br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-cli.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1807" alt="vavai-excellent-vmware-vcenter-cli" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-cli.jpg" width="728" height="377" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-cli.jpg 728w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-excellent-vmware-vcenter-cli-300x155.jpg 300w" sizes="auto, (max-width: 728px) 100vw, 728px" /><br />
</a></span><span style="line-height: 1.5em;">Note : These are possibly incorrect network settings for initial setup due to availability/unavailability of DHCP server. to reset or modify network settings, navigate to console with the user name : <strong>root</strong> and password : <strong>vmware</strong> then run the command :</p>
<pre>/opt/vmware/share/vami/vami_config_net</pre>
<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup1.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1808" alt="vavai-vcenter-setup1" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup1.png" width="605" height="403" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup1.png 605w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup1-300x200.png 300w" sizes="auto, (max-width: 605px) 100vw, 605px" /></a><br />
Change the network configuration according to the correct configuration </span></li>
<li><span style="line-height: 1.5em;">After completing the installation and configuration of the network, please access the web menu on https://IP-Address-vCenter:5480, for example <strong>https://192.168.1.24:5480</strong> or <strong>https://vcenter-lab.excellent.co.id</strong>. Log in using the default user : <strong>root</strong> and the default password : <strong>vmware<br />
</strong></span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup2.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1809" alt="vavai-vcenter-setup2" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup2.png" width="948" height="351" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup2.png 948w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup2-300x111.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup2-768x284.png 768w" sizes="auto, (max-width: 948px) 100vw, 948px" /></a></span></li>
<li><span style="line-height: 1.5em;">On the first step , click &#8220;Accept License Agreement&#8221;. vCenter will checking the configuration and restart the service. Wait for a moment until the system goes into the next wizard<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup3.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1810" alt="vavai-vcenter-setup3" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup3.png" width="839" height="640" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup3.png 839w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup3-300x229.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup3-768x586.png 768w" sizes="auto, (max-width: 839px) 100vw, 839px" /></a><br />
</span></li>
<li><span style="line-height: 1.5em;">The next part is vCenter configuration settings. Here we can upgrade the settings from previousversion, import configuration files from the backup configuration as well as from other vCenter or perform custom configurations. For initial setup, leave the settings as is and select the<strong> Configure option with Default Settings</strong> button<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup4.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1811" alt="vavai-vcenter-setup4" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup4.png" width="662" height="460" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup4.png 662w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup4-300x208.png 300w" sizes="auto, (max-width: 662px) 100vw, 662px" /></a></span></li>
<li><span style="line-height: 1.5em;">Click <strong>Start</strong> to starting  vCenter system configuration. The process will take between 5-10 minutes. If there is a failure at this stage, re-check the VM specification or VM configuration. Based on my experience, the configuration process may fail if vCenter has only 4 or 6 GB of memory<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup5.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1812" alt="vavai-vcenter-setup5" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup5.png" width="665" height="464" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup5.png 665w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup5-300x209.png 300w" sizes="auto, (max-width: 665px) 100vw, 665px" /><br />
</a></span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup6.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1813" alt="vavai-vcenter-setup6" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup6.png" width="664" height="461" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup6.png 664w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup6-300x208.png 300w" sizes="auto, (max-width: 664px) 100vw, 664px" /></a></span></li>
<li><span style="line-height: 1.5em;">Once the configuration process is complete , click the<strong> Close</strong> button. vCenter will automatically displaying the dashboard panel as shown on the following screenshot<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup7.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1814" alt="vavai-vcenter-setup7" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup7.png" width="839" height="642" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup7.png 839w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup7-300x230.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup7-768x588.png 768w" sizes="auto, (max-width: 839px) 100vw, 839px" /></a></span></li>
<li><span style="line-height: 1.5em;">To manage VM or host using vCenter, we can use vCenter web client by opening address https://IP-vCenter or http://hostname-vCenter, for example https://192.168.1.24 or https://vcenter- lab.excellent.co.id on browser and then select the <strong>Log in to vSphere web Client</strong> menu on top right corner<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup8.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1815" alt="vavai-vcenter-setup8" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup8.png" width="726" height="566" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup8.png 726w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup8-300x234.png 300w" sizes="auto, (max-width: 726px) 100vw, 726px" /></a></span></li>
<li><span style="line-height: 1.5em;">Log in using the the default <strong>root</strong> user and default password : <strong>vmware</strong><br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup9.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1816" alt="vavai-vcenter-setup9" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup9.png" width="719" height="208" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup9.png 719w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup9-300x87.png 300w" sizes="auto, (max-width: 719px) 100vw, 719px" /></a></span></li>
<li><span style="line-height: 1.5em;">Below are vCenter web client with default settings<br />
</span><span style="line-height: 1.5em;"><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup10.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1817" alt="vavai-vcenter-setup10" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup10.png" width="1362" height="696" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup10.png 1362w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup10-300x153.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup10-1024x523.png 1024w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup10-768x392.png 768w" sizes="auto, (max-width: 1362px) 100vw, 1362px" /></a></span></li>
<li><span style="line-height: 1.5em;">vCenter can also be accessed using the Windows based vSphere client<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup11.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1818" alt="vavai-vcenter-setup11" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vcenter-setup11.png" width="942" height="599" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup11.png 942w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup11-300x191.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-vcenter-setup11-768x488.png 768w" sizes="auto, (max-width: 942px) 100vw, 942px" /></a></span><span style="line-height: 1.5em;"><br />
</span></li>
</ol>
<p>After installing and configuring vCenter system, we can manage vSphere environment and applying some rule or advanced features such as vSphere HA, DRS, vMotion, FT, etc.</p>
<p>The post <a href="https://www.vavai.net/vmware-tips-vcenter-server-appliance-vcsa-installation-configuration/">VMware Tips : vCenter Server Appliance (vCSA) Installation &#038; Configuration</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/vmware-tips-vcenter-server-appliance-vcsa-installation-configuration/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Zimbra Collaboration Suite Urgent Patch Releases (Exploit-DB)</title>
		<link>https://www.vavai.net/zimbra-collaboration-urgent-patch-releases-exploit-db/</link>
					<comments>https://www.vavai.net/zimbra-collaboration-urgent-patch-releases-exploit-db/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sat, 15 Feb 2014 20:52:04 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1746</guid>

					<description><![CDATA[<p>Last week, Zimbra issued patch releases for Zimbra Collaboration 8.x and 7.x, resolving two critical security vulnerabilities. It&#8217;s strongly recommend that any customer running the following versions of Zimbra Collaboration apply the patches: 8.0.5, 8.0.4, 8.0.3 7.2.5, 7.2.4, 7.2.3, 7.2.2 These issues are being tracked in Zimbra Bugzilla systems as the following: Bug # 80338...</p>
<p>The post <a href="https://www.vavai.net/zimbra-collaboration-urgent-patch-releases-exploit-db/">Zimbra Collaboration Suite Urgent Patch Releases (Exploit-DB)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg"><img loading="lazy" decoding="async" class="alignleft size-full wp-image-1710" alt="zimbra-logo" src="http://54.254.121.108/wp-content/uploads/2014/02/zimbra-logo1.jpg" width="200" height="53" /></a>Last week, Zimbra issued patch releases for Zimbra Collaboration 8.x and 7.x, resolving two critical security vulnerabilities. It&#8217;s strongly recommend that any customer running the following versions of Zimbra Collaboration apply the patches:<br />
8.0.5, 8.0.4, 8.0.3<br />
7.2.5, 7.2.4, 7.2.3, 7.2.2<br />
These issues are being tracked in Zimbra Bugzilla systems as the following:<br />
<a href="https://bugzilla.zimbra.com/show_bug.cgi?id=80338">Bug # 80338</a><br />
<strong>Summary:</strong> Privilege Escalation via LFI<br />
<strong>Affected Versions:</strong> 7.2.2 and 8.0.2 and all previous releases<br />
<a href="https://bugzilla.zimbra.com/show_bug.cgi?id=84547">Bug # 84547</a><br />
<strong>Summary:</strong> Critical Security Vulnerability<br />
<strong>Affected Versions:</strong> 7.2.5 and 8.0.5 and all previous releases<br />
<span id="more-1746"></span>The official patch downloads and release notes can be found here: <a href="http://www.zimbra.com/downloads/ne-archives-downloads.html">Network Edition Downloads: Enterprise Messaging and Collaboration Software by Zimbra</a> or for Open Source Edition : <a href="http://www.zimbra.com/downloads/os-archives-downloads.html">Binary Archive for Open Source Editions</a><br />
Please follow the release notes for installation instructions. Each patch release is a cumulative update, including any fixes from previous patch releases for that version.<br />
More Details :</p>
<blockquote><p>Bug 80338 (Feb 2013) is a Local File Inclusion vulnerability that leads to potential Privilege Escalation:</p>
<ul>
<li>Bug 80338: Privilege Escalation via LFI</li>
<li>CVE: <a href="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7091" target="_blank" rel="nofollow noopener noreferrer">https://web.nvd.nist.gov/view/vuln/d&#8230;=CVE-2013-7091</a></li>
<li>Affected versions: 7.2.2 and 8.0.2 and all previous releases</li>
</ul>
<p>Bug 84547 is a newer Critical Security Vulnerability (Dec 2013) that has not had further details released (in order to protect other customers):</p>
<ul>
<li>Bug 84547: Critical Security Vulnerability</li>
<li>CVE: <a href="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7217" target="_blank" rel="nofollow noopener noreferrer">https://web.nvd.nist.gov/view/vuln/d&#8230;=CVE-2013-7217</a></li>
<li>Affected Versions: 7.2.5 and 8.0.5 and all previous releases (except 7.1.4, 7.2.0, 7.2.0 Patch 1, and 7.2.1, which are not susceptible to Bug 84547)</li>
</ul>
<p>There is great urgency for getting this patched on your platform, as there is an exploit for Bug 80338 in the wild, discussed here:</p>
<ul>
<li><a href="http://www.zimbra.com/forums/announcements/67236-security-guidance-reported-0day-exploit.html" target="_blank" rel="noopener noreferrer">Security Guidance for reported &#8220;0day Exploit&#8221;</a></li>
<li><a href="http://www.exploit-db.com/exploits/30085/" target="_blank" rel="nofollow noopener noreferrer">http://www.exploit-db.com/exploits/30085/</a></li>
</ul>
<p>And it has been used to install upload rogue Zimlets and bitcoin mining processes (and potentially others) on some customer systems. You can read about the clean-up steps for this here:</p>
<ul>
<li><a href="https://wiki.zimbra.com/wiki/Investigating_and_Securing_Systems" target="_blank" rel="noopener noreferrer">https://wiki.zimbra.com/wiki/Investi&#8230;curing_Systems</a></li>
</ul>
<p>As noted, there are patches and upgrades available here:</p>
<ul>
<li><a href="http://info.zimbra.com/zimbra-news-new-patch-release-new-training-courses-and-upcoming-events" target="_blank" rel="noopener noreferrer">http://info.zimbra.com/zimbra-news-n&#8230;pcoming-events</a></li>
<li><a href="http://www.zimbra.com/forums/announcements/68390-critical-security-patches-posted-8-0-x-7-2-x.html" target="_blank" rel="noopener noreferrer">Critical Security Patches posted for 8.0.X/7.2.X</a></li>
<li><a href="http://www.zimbra.com/forums/announcements/67336-critical-security-vulnerability-addressed-7-2-6-8-0-6-maintenance-releases.html" target="_blank" rel="noopener noreferrer">Critical Security Vulnerability Addressed in 7.2.6/8.0.6 Maintenance Releases</a></li>
</ul>
<p>Please let us know if further questions. Please upgrade or patch at first opportunity. Sorry for the difficulties on this.</p></blockquote>
<p>I strongly recommend to upgrading all Zimbra version 7.x.x into 7.2.6 and 8.x.x into 8.0.6 if possible. If you can not perform an update in the near future, please go with the above update releases ( only need a few steps than upgrading all services). Based on experience, upgrading Zimbra 6.0.8 in SLES 11 SP1 64 bit into 8.0.6 are worked flawlessly with only a few library update (zlib library). I&#8217;ll be post the details later on next tutorial <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>The post <a href="https://www.vavai.net/zimbra-collaboration-urgent-patch-releases-exploit-db/">Zimbra Collaboration Suite Urgent Patch Releases (Exploit-DB)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-collaboration-urgent-patch-releases-exploit-db/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>WHM/CPanel : How to Move MySQL Data Folder</title>
		<link>https://www.vavai.net/whmcpanel-how-to-move-mysql-data-folder/</link>
					<comments>https://www.vavai.net/whmcpanel-how-to-move-mysql-data-folder/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Wed, 12 Feb 2014 11:29:45 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[CPanel]]></category>
		<category><![CDATA[Moving]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<category><![CDATA[WHM]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1712</guid>

					<description><![CDATA[<p>Last week, I checked WHM (Web Hosting Management) server which used by this blog,  Excellent website and  Vavai.com due to an error messages regarding failed WHM update. After a few checking, it seems that root partition only left a bit free space and one of the largest folder  is var/lib/mysql which contain a MySQL server databases. Before the partition...</p>
<p>The post <a href="https://www.vavai.net/whmcpanel-how-to-move-mysql-data-folder/">WHM/CPanel : How to Move MySQL Data Folder</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/mysql-logo.jpg"><img loading="lazy" decoding="async" class="alignleft  wp-image-1718" style="margin: 5px;" alt="mysql-logo" src="http://54.254.121.108/wp-content/uploads/2014/02/mysql-logo.jpg" width="239" height="175" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/mysql-logo.jpg 399w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/mysql-logo-300x219.jpg 300w" sizes="auto, (max-width: 239px) 100vw, 239px" /></a>Last week, I checked WHM (Web Hosting Management) server which used by <a href="http://v2.vavai.net">this blog</a>,  <a href="http://www.excellent.co.id">Excellent </a>website and  <a href="http://www.vavai.com">Vavai.com</a> due to an error messages regarding failed WHM update. After a few checking, it seems that root partition only left a bit free space and one of the largest folder  is <b>var/lib/mysql </b>which contain a MySQL server databases. Before the partition getting lower and lower and would caused another problem, I decided to move the folder to another bigger partition.<br />
The following are the processes which I have done to prevent further problem. Please note that while doing this setting, there will be a minimal down time (1-2 minutes). In this case, I prepare different partition on /dev/sdc1 which have approximately 100 GB free space and mounted to /srv/whm) :<span id="more-1712"></span></p>
<ol>
<li>Go to WHM, choose Service Manager menu and uncheck on <strong>Monitoring MySQL </strong>option  then click save. It&#8217;s an important step to prevent MySQL services to being automatically restart by WHM service monitor</li>
<li>SSH or Putty to WHM console and run the following command :
<pre>mkdir -p /srv/backup/
chmod 777 -R /srv/backup
mysqldump --all-databases | gzip &gt; /srv/backup/alldatabases.sql.gz
rsync -av /var/lib/mysql /srv/whm/
chown -R mysql:mysql /srv/whm/mysql
/etc/init.d/mysql stop
rsync -av --delete-after /var/lib/mysql /srv/whm/
mv /var/lib/mysql /srv/backup
ln -s /srv/whm/mysql /var/lib/mysql
/etc/init.d/mysql start</pre>
</li>
<li><span style="line-height: 1.5em;">Back again to WHM, choose Service Manager and check on monitoring MySQL then save</span></li>
</ol>
<p>On the above step, I choose to take a safe precaution, so I back up the data using rsync command before moving the data.  It would take longer steps but safer than the simple steps but  has risk of data loss. If you feel confident, you can ignore the rsync command and  just go through the instruction : Shutting down MySQL service, move the data into another folder, then make the symlink, and finally re-activate the MySQL services.<br />
Actually, those instructions are should be applicable for non WHM MySQL server, for example, to move the mysql data on openSUSE / SLES server.</p>
<p>The post <a href="https://www.vavai.net/whmcpanel-how-to-move-mysql-data-folder/">WHM/CPanel : How to Move MySQL Data Folder</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/whmcpanel-how-to-move-mysql-data-folder/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>VMware vSphere Tips : VMware Tools Installation on SUSE Linux Enterprise Server 11 (SLES 11) VM</title>
		<link>https://www.vavai.net/vmware-vsphere-tips-vmware-tools-installation-on-suse-linux-enterprise-server-11-sles-11-vm/</link>
					<comments>https://www.vavai.net/vmware-vsphere-tips-vmware-tools-installation-on-suse-linux-enterprise-server-11-sles-11-vm/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Tue, 11 Feb 2014 02:48:50 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[VMware Tools]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1596</guid>

					<description><![CDATA[<p>One of the most important step, but often forgotten by the user while configuring Virtual Machine on VMware vSphere are VMware tools installation and configuration. In addition to improving VM’s performance (increase the quality on VGA, network card, etc), VMware tools also useful to provide the ability on host server to restart and shut down the VM...</p>
<p>The post <a href="https://www.vavai.net/vmware-vsphere-tips-vmware-tools-installation-on-suse-linux-enterprise-server-11-sles-11-vm/">VMware vSphere Tips : VMware Tools Installation on SUSE Linux Enterprise Server 11 (SLES 11) VM</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vmware.jpg"><img loading="lazy" decoding="async" class="alignleft size-full wp-image-1607" style="margin: 5px;" alt="vavai-vmware" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-vmware.jpg" width="232" height="228" /></a>One of the most important step, but often forgotten by the user while configuring Virtual Machine on VMware vSphere are VMware tools installation and configuration. In addition to improving VM’s performance (increase the quality on VGA, network card, etc), VMware tools also useful to provide the ability on host server to restart and shut down the VM normally.<br />
VMware Tools installation on Windows based VM generally quiet easy. Choose the <b>Install/Upgrade VMware Tools </b>menu, the auto installer will automatically run, click a few steps to install and then restart the VM guest to assure the change. On Linux based VM, the setting is different, the processes itself need a more steps to make it run properly. Those differences make some vSphere SysAdmin worries and choose to deploy VM without installing VMware tools rather than crashing the VM <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /><span id="more-1596"></span><br />
There are several ways in doing the VMware tools installation on linux, ranging from standard method which some people said it quiet difficult, until the easy one. The following are the standard VMware Tools installation steps on SUSE Linux Enterprise Server.</p>
<ol>
<li>Create a snapshot as a preventative measure to prevent unwanted things</li>
<li>Check the system version, to make sure which SLES system is being used : <b>cat/etc/SuSE-release<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-1.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1599" alt="vavai-install-vmware-tools-pada-sles-11-1" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-1.jpg" width="487" height="97" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-1.jpg 487w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-1-300x60.jpg 300w" sizes="auto, (max-width: 487px) 100vw, 487px" /></a><br />
</b></li>
</ol>
<ol start="3">
<li>Make sure OS type of VM guest. If it appears wrong, the mounted binary VMware Tools cannot be installed. (For example, it&#8217;s a  Linux VM, but set on guest mode = Windows or otherwise. Another case is SLES was installed but the OS type is set to Debian)<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-5.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1600" alt="vavai-install-vmware-tools-pada-sles-11-5" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-5.jpg" width="686" height="356" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-5.jpg 686w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-5-300x156.jpg 300w" sizes="auto, (max-width: 686px) 100vw, 686px" /></a></li>
</ol>
<ol start="4">
<li>Mount the VMware tools, choose the menu on VM :  <strong>Guest | Install/Upgrade VMware Tools</strong>. If you use vSphere Web Client, choose VM and then click  <strong>Summary tab | Install VMware Tools</strong>. If there is an error message while trying to mount the CD ROM-such as the CD ROM on guest is not available-add the CD ROM (Set the VM to off before set the CD ROM)<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-4.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1601" alt="vavai-install-vmware-tools-pada-sles-11-4" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-4.jpg" width="673" height="423" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-4.jpg 673w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-4-300x189.jpg 300w" sizes="auto, (max-width: 673px) 100vw, 673px" /></a><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-3.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1602" alt="vavai-install-vmware-tools-pada-sles-11-3" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-3.jpg" width="625" height="376" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-3.jpg 893w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-3-300x180.jpg 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-3-768x462.jpg 768w" sizes="auto, (max-width: 625px) 100vw, 625px" /></a></li>
<li>Make sure compilation package (kernel-source make gcc) is available. If it does not, install it using the following command : <strong>zypper in kernel-source make gcc</strong>.</li>
</ol>
<ol start="6">
<li>Make sure the working kernel and kernel-source have the same version. Check it out by using following command : <b>uname –r </b>and<b><b> zypper if kernel-source</b></b><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-2.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1603" alt="vavai-install-vmware-tools-pada-sles-11-2" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-2.jpg" width="558" height="528" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-2.jpg 697w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-2-300x284.jpg 300w" sizes="auto, (max-width: 558px) 100vw, 558px" /></a></li>
</ol>
<ol start="7">
<li>Mount and Install VMware Tools (adjust the binary name in the mount result folder) with the following instruction :<br />
[code language=&#8221;bash&#8221;]</p>
<pre>mount /dev/sr0 /mnt
cp /mnt/* /opt
cd /opt
tar -zxvf VMwareTools-9.0.0-782409.tar.gz</pre>
<p>[/code]<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-7.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1604" alt="vavai-install-vmware-tools-pada-sles-11-7" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-7.jpg" width="571" height="147" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-7.jpg 816w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-7-300x77.jpg 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-7-768x198.jpg 768w" sizes="auto, (max-width: 571px) 100vw, 571px" /></a></li>
</ol>
<ol start="8">
<li>Go to extracted folder (vmware-tools-distrib) and install VMware Tools with the following command : <strong>./vmware-install.pl</strong> and follow the instruction</li>
<li>After finish the installation step, we can check the status on VM summary, whether the VMware Tools already installed or not<br />
<a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-9.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1605" alt="vavai-install-vmware-tools-pada-sles-11-9" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-9.jpg" width="575" height="332" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-9.jpg 958w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-9-300x173.jpg 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-9-768x444.jpg 768w" sizes="auto, (max-width: 575px) 100vw, 575px" /><br />
</a><a href="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-10.jpg"><img loading="lazy" decoding="async" class="alignnone  wp-image-1606" alt="vavai-install-vmware-tools-pada-sles-11-10" src="http://54.254.121.108/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-10.jpg" width="662" height="288" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-10.jpg 736w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/vavai-install-vmware-tools-pada-sles-11-10-300x130.jpg 300w" sizes="auto, (max-width: 662px) 100vw, 662px" /></a></li>
</ol>
<p>For some SysAdmin, especially Windows based SysAdmin,  the above tutorial seems to be quite complicated  because I try to show all the steps as detail as I could explain to you. Besides this standard way, there is also another simpler and easier way by using VMware Operating System Specific Packages (OSPs,. I will discuss it later). Although looks like a complicated step, this standard procedure has an advantage compared to OSPs, such as:</p>
<ol>
<li>Shows that we are really Linux SysAdmin whose able to play with CLI (this part is intermezzo, you can ignore it <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /> )</li>
<li>This method is applicable on Linux openSUSE or others Linux Distro. The VMware installation in all Linux Distro or System are similar with the tutorial above, the difference is only in the installation essentials package (kernel-source, make, gcc. ex : on Ubuntu, compilation package can be install by using following command : <strong>apt-get install build-essentials</strong>)</li>
<li>Applicable if VMware Operating System Specific Packages (OSPs) is not available for guest OS</li>
<li>Applicable if OS type are a brand new Linux system, non-mainstream <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /> system, or a remastered system</li>
<li>Applicable if the installation using VMware Operating System Specific Packages (OSPs) failed</li>
</ol>
<p>The post <a href="https://www.vavai.net/vmware-vsphere-tips-vmware-tools-installation-on-suse-linux-enterprise-server-11-sles-11-vm/">VMware vSphere Tips : VMware Tools Installation on SUSE Linux Enterprise Server 11 (SLES 11) VM</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/vmware-vsphere-tips-vmware-tools-installation-on-suse-linux-enterprise-server-11-sles-11-vm/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>Torrent Download via CLI/Console</title>
		<link>https://www.vavai.net/torrent-download-via-cliconsole/</link>
					<comments>https://www.vavai.net/torrent-download-via-cliconsole/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Sun, 09 Feb 2014 09:41:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Aria2]]></category>
		<category><![CDATA[Download]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<category><![CDATA[Torrent]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1551</guid>

					<description><![CDATA[<p>When downloading large files such as Linux ISO files or backup files, I usually use the default browser download application or use wget. Unfortunately, in some case, I prefer to do download using torrent because it may faster than using wget. On Windows system, I usually use Bitorrent or uTorrent and on Linux-GUI based, Transmission is...</p>
<p>The post <a href="https://www.vavai.net/torrent-download-via-cliconsole/">Torrent Download via CLI/Console</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="http://54.254.121.108/wp-content/uploads/2014/02/logo-download.png"><img loading="lazy" decoding="async" class="alignleft  wp-image-1552" style="margin: 5px;" alt="logo-download" src="http://54.254.121.108/wp-content/uploads/2014/02/logo-download.png" width="179" height="179" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/logo-download.png 256w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2014/02/logo-download-150x150.png 150w" sizes="auto, (max-width: 179px) 100vw, 179px" /></a>When downloading large files such as Linux ISO files or backup files, I usually use the default browser download application or use wget. Unfortunately, in some case, I prefer to do download using torrent because it may faster than using wget. On Windows system, I usually use Bitorrent or uTorrent and on Linux-GUI based, Transmission is my default choice.<br />
Well, how if using openSUSE minimal or other Linux-based Console/non GUI? For this, I usually use aria2.<span id="more-1551"></span></p>
<blockquote>
<h3>Aria 2 : Parallelizing Multi-Protocol Utility for Downloading Files</h3>
<p>aria2 is a utility for downloading files. It has completely new design concept from its predecessor, Aria, and is written from scratch. aria2 has a segmented downloading engine in its core. It can download one file from multiple URLs or multiple connections from one URL. This results in very high speed downloading, much faster than ordinary browsers. This engine in was implemented in a single-thread model. The architecture is clean and easy to extend. aria2 currently supports HTTP, FTP, and BitTorrent.</p></blockquote>
<p>Actually, Aria2  is a GUI-based applications and also provide tools for CLI. One of the advantages using aria2  is it&#8217;s support for torrent file and FTP besides HTTP download by default.<br />
How to install aria2?</p>
<ol>
<li>If using GUI based desktop, go to  <a href="http://software.opensuse.org/package/aria2">http://software.opensuse.org/package/aria2</a> and install using One-Click-Install feature (can only be done via openSUSE or SLES). Do not forget to adjust the type and version of openSUSE/SLES to match the version of the running system</li>
<li>If using openSUSE 13.1 CLI, execute the following command :<br />
[code language=&#8221;bash&#8221;]<br />
zypper ar http://download.opensuse.org/repositories/openSUSE:/13.1/standard/ aria2<br />
zypper ref<br />
zypper in aria2<br />
[/code]</li>
<li>or for SLES 11 :<br />
[code language=&#8221;bash&#8221;]<br />
zypper ar http://download.opensuse.org/repositories/home:/holgerob/SLE_11 aria2<br />
zypper ref<br />
zypper in aria2<br />
[/code]</li>
<li>Once installed, aria2 can be run through the console with the command: <strong>aria2c name-of-file</strong>, ex :<br />
[code language=&#8221;bash&#8221;]<br />
aria2c http://kambing.ui.ac.id/iso/opensuse/13.1/iso/openSUSE-13.1-DVD-x86_64.iso<br />
[/code][code language=&#8221;bash&#8221;]<br />
aria2c http://kambing.ui.ac.id/iso/opensuse/13.1/iso/openSUSE-13.1-DVD-x86_64.iso.torrent<br />
[/code]</li>
</ol>
<p>Aria2 will automatically check the size of the file and start the download process. Here is an example of the process log:<br />
<em>$ aria2c http://kambing.ui.ac.id/iso/opensuse/13.1/iso/openSUSE-13.1-DVD-i586.iso.torrent</em><br />
<em>2014-02-05 12:15:28.103709 WARN – You may encounter the certificate verification error with HTTPS server. See –ca-certificate and –check-certificate option.</em><br />
<em>2014-02-05 12:15:28.426243 NOTICE – Download complete: /srv/www/htdocs/iso/openSUSE-13.1-DVD-i586.iso.torrent</em><br />
<em>2014-02-05 12:15:28.467413 NOTICE – IPv4 DHT: listening to port 6994</em><br />
<em>*** Download Progress Summary as of Wed Feb 5 12:16:28 2014 ***</em><br />
<em>================================================================================</em><br />
<em>[#2 SIZE:0B/4,236.0MiB(0%) CN:0 SEED:0 SPD:0Bs]</em><br />
<em>FILE: /srv/www/htdocs/iso/openSUSE-13.1-DVD-i586.iso/openSUSE-13.1-DVD-i586.iso</em><br />
<em>——————————————————————————–</em><br />
<em>[#2 SIZE:0B/4,236.0MiB(0%) CN:0 SEED:0 SPD:0Bs] [FileAlloc:#2 4,206.7MiB/4,236.0</em><br />
<em>2014-02-05 12:17:27.274574 NOTICE &#8211; IPv4 BitTorrent: listening to port 6905</em><br />
<em>2014-02-05 12:17:27.274708 NOTICE &#8211; IPv6 BitTorrent: listening to port 6905</em><br />
<em>*** Download Progress Summary as of Wed Feb 5 12:17:30 2014 ***</em><br />
<em>================================================================================</em><br />
<em>[#2 SIZE:0B/4,236.0MiB(0%) CN:44 SEED:0 SPD:0Bs]</em><br />
<em>FILE: /srv/www/htdocs/iso/openSUSE-13.1-DVD-i586.iso/openSUSE-13.1-DVD-i586.iso</em><br />
<em>——————————————————————————–</em><br />
<em>*** Download Progress Summary as of Wed Feb 5 12:18:30 2014 ***</em><br />
<em>================================================================================</em><br />
<em>[#2 SIZE:18.5MiB/4,236.0MiB(0%) CN:44 SEED:30 SPD:399.4KiBs ETA:3h12s]</em><br />
<em>FILE: /srv/www/htdocs/iso/openSUSE-13.1-DVD-i586.iso/openSUSE-13.1-DVD-i586.iso</em></p>
<p>The post <a href="https://www.vavai.net/torrent-download-via-cliconsole/">Torrent Download via CLI/Console</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/torrent-download-via-cliconsole/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Tips : Improving Zimbra Mail Server Security with Fail2Ban</title>
		<link>https://www.vavai.net/tips-improving-zimbra-mail-server-security-with-fail2ban/</link>
					<comments>https://www.vavai.net/tips-improving-zimbra-mail-server-security-with-fail2ban/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Fri, 21 Oct 2011 04:45:31 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Fail2Ban]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1305</guid>

					<description><![CDATA[<p>Zimbra mail server has it’s own anti spam based on SpamAssasin and anti virus addon based on ClamAV to block incoming and outgoing malicious. The default addon has a pretty good performance when configured properly, but if you want to increase the security of Zimbra mail server, fail2ban is an additional plugin to be considered. What is...</p>
<p>The post <a href="https://www.vavai.net/tips-improving-zimbra-mail-server-security-with-fail2ban/">Tips : Improving Zimbra Mail Server Security with Fail2Ban</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p style="text-align: justify;"><a href="http://54.254.121.108/wp-content/uploads/2011/10/Fail2ban_logo.png"><img loading="lazy" decoding="async" class="size-full wp-image-1359 alignleft" style="margin: 5px;" alt="Fail2ban_logo" src="http://54.254.121.108/wp-content/uploads/2011/10/Fail2ban_logo.png" width="135" height="130" /></a>Zimbra mail server has it’s own anti spam based on SpamAssasin and anti virus addon based on ClamAV to block incoming and outgoing malicious. The default addon has a pretty good performance when configured properly, but if you want to increase the security of Zimbra mail server, fail2ban is an additional plugin to be considered.</p>
<p style="text-align: justify;">What is Fail2Ban</p>
<p style="text-align: justify;"><em>Fail2ban is an intrusion prevention framework written in the Python programming language. It is able to run on POSIX systems that have an interface to a packet-control system or firewall installed locally (for example, iptables or TCP Wrapper).</em></p>
<p style="text-align: justify;"><em>Fail2ban operates by monitoring log files (e.g. /var/log/pwdfail, /var/log/auth.log, etc.) for selected entries and running scripts based on them. Most commonly this is used to block selected IP addresses that may belong to hosts that are trying to breach the system’s security. It can ban any host IP that makes too many login attempts or performs any other unwanted action within a time frame defined by the administrator.</em></p>
<p>Here is a guide to improve the security of Zimbra mail server by using Fail2Ban :</p>
<ol>
<li>Install Fail2Ban and IPtables. If you are using <a href="http://web.archive.org/web/20130530072636/http://v2.vavai.net/2011/12/installing-zimbra-mail-server-on-sles-11-sp1-64-bit-in-less-than-30-minutes-part-3/">Minimal Server Appliance</a>, both Fail2ban and IPtables has been successfully installed on the appliance. To install it manually, run the following command with root permission :
<pre>zypper ar http://download.opensuse.org/repositories/security/SLE_11/ fail2ban
zypper in fail2ban</pre>
</li>
<li>Create a new file <strong>/etc/fail2ban/filter.d/zimbra.conf</strong>. This file contains regular expression to parsing Zimbra log which will trigger the banned process if it happens several times in a specified time interval. Contents of<strong>/etc/fail2ban/filter.d/zimbra.conf</strong> :
<div id="highlighter_936138">
<pre># Fail2Ban configuration file
#
# Author:
#
# $Revision: 1 $
#
[Definition]
# Option:  failregex
# Notes.:  regex to match the password failures messages in the logfile. The
#          host must be matched by a group named "host". The tag "&lt;HOST&gt;" can
#          be used for standard IP/hostname matching and is only an alias for
#          (?:::f{4,6}:)?(?P&lt;host&gt;[\w\-.^_]+)
# Values:  TEXT
#
failregex = \[ip=&lt;HOST&gt;;\] account - authentication failed for .* \(no such account\)$
                        \[ip=&lt;HOST&gt;;\] security - cmd=Auth; .* error=authentication failed for .*, invalid password;$
                        ;oip=&lt;HOST&gt;;.* security - cmd=Auth; .* protocol=soap; error=authentication failed for .* invalid password;$
                        \[oip=&lt;HOST&gt;;.* SoapEngine - handler exception: authentication failed for .*, account not found$
                        WARN .*;ip=&lt;HOST&gt;;ua=ZimbraWebClient .* security - cmd=AdminAuth; .* error=authentication failed for .*;$
                        NOQUEUE: reject: RCPT from .*\[&lt;HOST&gt;\]: 550 5.1.1 .*: Recipient address rejected:
# .*\[ip=&lt;HOST&gt;;\] .* - authentication failed for .* \(invalid password\)
#
# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT
#
ignoreregex =</pre>
</div>
</li>
<li>Create/edit <strong>/etc/fail2ban/jail.conf</strong> with the following contents :
<div id="highlighter_585059">
<pre># Fail2Ban configuration file
#
# Author: Cyril Jaquier
#
# $Revision: 747 $
## The DEFAULT allows a global definition of the options. They can be overridden
# in each jail afterwards.
[DEFAULT]
# "ignoreip" can be an IP address, a CIDR mask or a DNS host. Fail2ban will not
# ban a host which matches an address in this list. Several addresses can be
# defined using space separator.
ignoreip = 127.0.0.1/8 202.43.115.188/32
# "bantime" is the number of seconds that a host is banned.
bantime = 600
# A host is banned if it has generated "maxretry" during the last "findtime"
# seconds.
findtime = 600
# "maxretry" is the number of failures before a host get banned.
maxretry = 3
# "backend" specifies the backend used to get files modification. Available
# options are "gamin", "polling" and "auto". This option can be overridden in
# each jail too (use "gamin" for a jail and "polling" for another).
#
# gamin: requires Gamin (a file alteration monitor) to be installed. If Gamin
# is not installed, Fail2ban will use polling.
# polling: uses a polling algorithm which does not require external libraries.
# auto: will choose Gamin if available and polling otherwise.
backend = auto
# This jail corresponds to the standard configuration in Fail2ban 0.6.
# The mail-whois action send a notification e-mail with a whois request
# in the body.
[ssh-iptables]
enabled = false
filter = sshd
action = iptables[name=SSH, port=ssh, protocol=tcp]
sendmail-whois[name=SSH, dest=zeze@vavai.com, sender=fail2ban@excellent.co.id]
logpath = /var/log/messages
maxretry = 5
# This jail forces the backend to "polling".
[sasl-iptables]
enabled = false
filter = sasl
backend = polling
action = iptables[name=sasl, port=smtp, protocol=tcp]
sendmail-whois[name=sasl, dest=support@excellent.co.id]
logpath = /var/log/zimbra.log
# Here we use TCP-Wrappers instead of Netfilter/Iptables. "ignoreregex" is
# used to avoid banning the user "myuser".
[ssh-tcpwrapper]
enabled = false
filter = sshd
action = hostsdeny
sendmail-whois[name=SSH, dest=support@excellent.co.id]
ignoreregex = for myuser from
logpath = /var/log/messages
# This jail uses ipfw, the standard firewall on FreeBSD. The "ignoreip"
# option is overridden in this jail. Moreover, the action "mail-whois" defines
# the variable "name" which contains a comma using "". The characters '' are
# valid too.
[zimbra-account]
enabled = true
filter = zimbra
action = iptables-allports[name=zimbra-account]
sendmail[name=zimbra-account, dest=support@excellent.co.id]
logpath = /opt/zimbra/log/mailbox.log
bantime = 600
maxretry = 5
[zimbra-audit]
enabled = true
filter = zimbra
action = iptables-allports[name=zimbra-audit]
sendmail[name=Zimbra-audit, dest=support@excellent.co.id]
logpath = /opt/zimbra/log/audit.log
bantime = 600
maxretry = 5
[zimbra-recipient]
enabled = true
filter = zimbra
action = iptables-allports[name=zimbra-recipient]
sendmail[name=Zimbra-recipient, dest=support@excellent.co.id]
logpath = /var/log/zimbra.log
#findtime = 604800
bantime = 172800
maxretry = 5
[postfix]
enabled = true
filter = postfix
action = iptables-multiport[name=postfix, port=smtp, protocol=tcp]
sendmail-buffered[name=Postfix, dest=support@excellent.co.id]
logpath = /var/log/zimbra.log
bantime = -1
maxretry = 5
#[sasl]
#enabled = true
#port = smtp,ssmtp,imap2,imap3,imaps,pop3,pop3s
#filter = sasl
# You might consider monitoring /var/log/warn.log instead
# if you are running postfix. See http://bugs.debian.org/507990
#logpath = /var/log/zimbra.log</pre>
</div>
<p style="text-align: justify;">jail.conf contains data log path to be check and email address for banned notification. Do not forget to fill in the parameters ignoreip to prevent Fail2Ban banned internal network</p>
</li>
<li>Edit file <strong>/etc/fail2ban/action.d/sendmail.conf</strong> and change the line :
<div id="highlighter_867532">
<pre>Fail2Ban" | /usr/sbin/sendmail -f &lt;sender&gt; &lt;dest&gt;</pre>
</div>
<p>into</p>
<div id="highlighter_315958">
<pre>Fail2Ban" | /opt/zimbra/postfix/sbin/sendmail -f &lt;sender&gt; &lt;dest&gt;</pre>
</div>
</li>
<li>Restart Fail2Ban services
<div id="highlighter_273041">
<pre>service fail2ban restart</pre>
</div>
</li>
</ol>
<p style="text-align: justify;">Fail2Ban will sent a notification email to specified email address if found intrusion that match with Fail2Ban rule. IP will be instantly banned if it has qualified many times and match with Fail2Ban rules in a predefined time interval. We can also modify jail.conf  or create another regular expression to check other logs.</p>
<p>Below are screenshot of notification email from Fail2Ban:<br />
<a href="http://web.archive.org/web/20130530072636/http://www.excellent.co.id/product-services/zimbra/implementasi-fail2ban-untuk-meningkatkan-performa-keamanan-zimbra-mail-server-2/attachment/fail2ban/" rel="attachment wp-att-2207"><img loading="lazy" decoding="async" title="fail2ban" alt="" src="http://web.archive.org/web/20130530072636im_/http://www.excellent.co.id/wp-content/uploads/2012/09/fail2ban.jpeg" width="416" height="283" /></a></p>
<p style="text-align: justify;">Fail2Ban is quite powerful and can be used to anticipate the kind of brute-force attack, both on email and other server services such as web servers, FTP servers, database servers and others.</p>
<p>The post <a href="https://www.vavai.net/tips-improving-zimbra-mail-server-security-with-fail2ban/">Tips : Improving Zimbra Mail Server Security with Fail2Ban</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/tips-improving-zimbra-mail-server-security-with-fail2ban/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>User Account Integration between Samba PDC &#038; Zimbra Mail Server on openSUSE/SLES</title>
		<link>https://www.vavai.net/user-account-integration-between-samba-pdc-zimbra-mail-server-on-opensuse-sles/</link>
					<comments>https://www.vavai.net/user-account-integration-between-samba-pdc-zimbra-mail-server-on-opensuse-sles/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Wed, 31 Mar 2010 02:33:08 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[LDAP]]></category>
		<category><![CDATA[OpenLDAP]]></category>
		<category><![CDATA[PDC]]></category>
		<category><![CDATA[Samba]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1172</guid>

					<description><![CDATA[<p>Note : This is part one of 2 article. I decided to split the tutorial to make it easier to read (and to write 🙂 ) This tutorial describes how you can configure Zimbra Mail Server &#38; Collaboration Suite and Samba to act as a primary domain controller (PDC) that uses Zimbra LDAP (Lightweight Directory...</p>
<p>The post <a href="https://www.vavai.net/user-account-integration-between-samba-pdc-zimbra-mail-server-on-opensuse-sles/">User Account Integration between Samba PDC &#038; Zimbra Mail Server on openSUSE/SLES</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><em>Note : This is part one of 2 article. I decided to split the tutorial to make it easier to read (and to write <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> )</em><br />
<a class="highslide" onclick="return vz.expand(this)" href="http://54.254.121.108/wp-content/uploads/2010/03/zimbra-opensuse1.jpeg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1195" title="zimbra-opensuse" src="http://54.254.121.108/wp-content/uploads/2010/03/zimbra-opensuse1.jpeg" alt="" width="200" height="200" /></a><br />
This tutorial describes how you can configure Zimbra Mail Server &amp; Collaboration Suite and Samba to act as a primary domain controller (PDC) that  uses Zimbra LDAP (Lightweight Directory Access Protocol) as a central password  database for authenticating users on Linux and Windows desktops. The  integration process will make it easier for administrators to manage Zimbra Mail Server and Samba PDC / Active Directory account because it  use same LDAP database. If  applied in corporate environments or institutions who have been using  Windows Server, this guide can be used to set up Linux servers to  replace the Windows Active Directory Server and Microsoft Exchange  Server.<br />
The setup described in this document is not the only possible way  to make Samba and Zimbra use the same user database for authentication.  You may also use <a href="http://v2.vavai.net/2010/03/30/zimbra-mail-server-with-external-authentication-using-samba-pdcopenldap/">Zimbra External Authentication with Samba PDC</a>. External authentication are a little bit easy to be setting up, but we must manage the mailbox profile in Zimbra and it doesn&#8217;t seamlessly integrate Zimbra into Samba PDC+OpenLDAP. It is highly recommended to get familiar with Zimbra, Samba, LDAP and  PAM, before you start the installation.<br />
This tutorial are based on Zimbra wiki article : <a title="http://wiki.zimbra.com/index.php?title=UNIX_and_Windows_Accounts_in_Zimbra_LDAP_and_Zimbra_Admin_UI_6.0" rel="nofollow" href="http://wiki.zimbra.com/index.php?title=UNIX_and_Windows_Accounts_in_Zimbra_LDAP_and_Zimbra_Admin_UI_6.0">UNIX and Windows Accounts in Zimbra LDAP and Zimbra  Admin UI 6.0</a> but has been tune up to works successfully on openSUSE/SLES environment. The original wiki using Ubuntu/RedHat environment which doesn&#8217;t automatically fit with openSUSE/SLES configuration.<br />
I&#8217;m using Zimbra Mail Server 6.0.5 64 bit with the following configuration :<br />
<strong> Domain &amp; Hostname</strong></p>
<pre>Domain   : vavai.co.id
Hostname : zcspdc.vavai.co.id</pre>
<p><strong> IP Address<br />
</strong></p>
<pre>IP Address    : 192.168.10.1
Name Server 1 : 192.168.10.1
Name Server 2 : 8.8.8.8  (Google public DNS Server)
Name Server 3 : 208.67.222.222 (OpenDNS public DNS Server)
Router        : 192.168.10.254 (ADSL Modem)</pre>
<p><strong>File /etc/hosts</strong></p>
<pre>127.0.0.1       localhost
192.168.10.1    zcspdc.vavai.co.id zcspdc</pre>
<h4>ZIMBRA INSTALLATION</h4>
<p>Please use following article to install Zimbra on SLES 11 : <a href="http://v2.vavai.net/2010/02/10/installing-zimbra-6-0-5-64-bit-on-sles-11-64-bit/">Installing Zimbra 6.0.5 64 bit on  SUSE Linux Enterprise Server (SLES) 11  64 bit</a> or use this tutorial : <a title="http://v2.vavai.net/2009/12/22/installing-zimbra-6-0-4-on-opensuse-11-1-64-bit-part-1/" rel="nofollow" href="http://v2.vavai.net/2009/12/22/installing-zimbra-6-0-4-on-opensuse-11-1-64-bit-part-1/">Installing Zimbra 6.0.4 on openSUSE 11.1 64 bit</a> for Zimbra+openSUSE version.</p>
<h4>ZIMBRA LDAP CONFIGURATION</h4>
<p>The following script will automatically configure Zimbra LDAP as below :</p>
<ul>
<li>Add Samba Schema into Zimbra LDAP</li>
<li>Add proper index into Zimbra LDAP Schema</li>
<li>Add 2 user (zmposix and zmposixroot) as Zimbra LDAP Administrative Account with  default  password : rahasia</li>
<li>Adjust Zimbra LDAP ACL to allow administrative task regarding Samba-Zimbra integration</li>
<li>Add Admin Extension Zimbra Posfix Account and Zimbra  Samba Extension</li>
</ul>
<p>Thanks to Peracchi and Lithorus on the following thread on <a href="http://www.zimbra.com/forums/administrators/33168-help-make-zimbra-samba-tutorial-ubuntu-8-04-3-server-zimbra-6-0-1-a-3.html">Zimbra Forum</a> for idea and a great script.<br />
To run the automated script, run the following commandon console/terminal :<br />
[code language=&#8217;cpp&#8217;]<br />
su<br />
cd /srv<br />
wget -c http://vavai.com/wp-content/uploads/zcs-samba.tar.gz<br />
tar -zxvf zcs-samba.tar.gz<br />
su &#8211; zimbra<br />
cd /srv/zcs-samba<br />
./zcs-samba.sh<br />
[/code]<br />
NOTE : The script will automatically use &#8216;rahasia&#8217; (Indonesian word means &#8216;secret&#8217; <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f61b.png" alt="😛" class="wp-smiley" style="height: 1em; max-height: 1em;" /> ) as default password for zmposixroot and zmposix password. Please modify script to use your own password by change the following code on /srv/zcs-samba/zcs-samba.shÂ  :<br />
[code language=&#8217;cpp&#8217;]<br />
# set password for the posix ldap accounts<br />
ZMPOSIX_LDAP_PASSWORD=`/opt/zimbra/openldap/sbin/slappasswd -s rahasia`<br />
ZMPOSIXROOT_LDAP_PASSWORD=`/opt/zimbra/openldap/sbin/slappasswd -s rahasia`<br />
echo &#8220;Domain : $DOMAIN&#8221;<br />
echo &#8220;Hostname : $HOSTNAME&#8221;<br />
echo &#8220;Zimbra LDAP Password : $ZIMBRA_LDAP_PASSWORD&#8221;<br />
echo &#8220;LDAP Prefix : $LDAP_PREFIX&#8221;<br />
echo &#8220;ZMPOSIX_LDAP_PASSWORD : rahasia&#8221;<br />
[/code]<br />
Change &#8216;rahasia&#8217; on the above line with your own password.</p>
<h4>SAMBA INSTALLATION</h4>
<ul>
<li>Open YAST | Network Service | Samba Server. YAST will automatically added Samba package if you never install it.</li>
<li>On the first  wizard, fill in the  workgroup/domain name. I&#8217;m using vavai.co.id as my domain name as shown on top of the tutorial. Click Next.</li>
<li>On  Samba Server Type, Choose Primary Domain  Controller (PDC) and then click Next</li>
<li>On  start-up, choose <strong>Service Start During Boot</strong> so  Samba will automatically be activated during boot. Don&#8217;t forget to open your Firewall port</li>
<li>Move to  LDAP Setting tab.</li>
<li>Click on <strong>Use LDAP Password Back-End </strong>option</li>
<li>Change  LDAP Server URL from default entry ldap://127.0.0.1 to be  ldap://192.168.10.1 (remember my  IP address configuration above). Use same address toÂ  IdMap Back-End</li>
<li>Change  Search Base DN to Zimbra LDAP DN, mine are  dc=vavai,dc=co,dc=id</li>
<li>Fill in Administrator DN and the password:  uid=zmposixroot,cn=appaccts,cn=zimbra). Click Test Connection to test the connection between Zimbra and Samba machine.</li>
<li>Click Advanced Setting | Expert LDAP Setting</li>
<li> Change user suffix to be ou=people</li>
<li>Change group suffix to be ou=groups</li>
<li>Change Machine suffix to be ou=machines</li>
<li>Click OK to close Expert LDAP Setting windows</li>
<li>Click  OK to close  Samba Server wizard. Fill in  password for Samba root /Administrator password.  To prevent any confused setting, I&#8217;m using same password between zmposixroot, zmposix and Samba root password <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f61b.png" alt="😛" class="wp-smiley" style="height: 1em; max-height: 1em;" /></li>
</ul>
<h4>SAMBA CONFIGURATION</h4>
<ul>
<li>Open /etc/samba/smb.conf with your preferred text editor (vi, gedit,  kate or kwrite)</li>
<li>Give it a # (comment mark) on the following line (if you do not use dhcp on your Samba configuration) :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]<br />
include = /etc/samba/dhcp.conf<br />
[/code]</p>
<ul>
<li>Save the configuration</li>
</ul>
<h4>LDAP CLIENT CONFIGURATION</h4>
<ul>
<li>Click YAST | Network Services | LDAP Client</li>
<li> Click  <strong>Use LDAP</strong> on User Authentication</li>
<li>Change Address to use Zimbra IP (192.168.10.1)</li>
<li>Fill in LDAP Base DN (dc=vavai,dc=co,dc=id)</li>
<li>Leave others as is</li>
<li>Click Advanced Configuration</li>
<li> Change <strong>Password Change Protocol</strong> to MD5</li>
<li>Leave <strong> Group Member Attribute = Member</strong> setting</li>
<li>Click on Administration Setting tab</li>
<li>Fill in uid=zmposixroot,cn=appaccts,cn=zimbra on   Administrator DN text box. LeaveÂ  <strong>Append Base DN </strong>setting unchecked</li>
<li>Leave <strong> Create Default Configuration Objects</strong> setting unchecked</li>
<li>Click OK</li>
<li>Click OK</li>
</ul>
<h4>NSS-LDAP &amp; PAM-LDAP CONFIGURATION</h4>
<ul>
<li>Open file /etc/ldap.conf with your preferred text  editor and change the following line (remove  # mark)</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]<br />
host 192.168.10.1<br />
base dc=vavai,dc=co,dc=id<br />
binddn uid=zmposix,cn=appaccts,cn=zimbra<br />
bindpw rahasia<br />
rootbinddn uid=zmposixroot,cn=appaccts,cn=zimbra<br />
port 389<br />
bind_policy soft<br />
nss_reconnect_tries 2<br />
uri ldap://192.168.10.1/<br />
ssl start_tls<br />
tls_cacertdir /opt/zimbra/conf/ca<br />
tls_checkpeer no<br />
pam_password md5<br />
nss_base_passwd         ou=people,dc=vavai,dc=co,dc=id?one<br />
nss_base_shadow         ou=people,dc=vavai,dc=co,dc=id?one<br />
nss_base_group          ou=groups,dc=vavai,dc=co,dc=id?one<br />
nss_base_hosts          ou=machines,dc=vavai,dc=co,dc=id?one<br />
[/code]</p>
<ul>
<li>Save the configuration</li>
<li>Edit /etc/nsswitch.conf and change the following line :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]<br />
passwd: compat<br />
group: compat<br />
[/code]<br />
with<br />
[code language=&#8217;cpp&#8217;]passwd: files ldap<br />
group: files ldap<br />
[/code]</p>
<ul>
<li> Edit /etc/pam.d/common-account and change the configuration as below :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]account sufficient pam_unix.so<br />
account sufficient pam_ldap.so<br />
[/code]</p>
<ul>
<li> Edit /etc/pam.d/common-auth and change the configuration as below :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]auth sufficient pam_ldap.so<br />
auth sufficient pam_unix.so<br />
[/code]</p>
<ul>
<li> Edit /etc/pam.d/common-password and change the configuration as below :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]password sufficient pam_unix.so<br />
password sufficient pam_ldap.so<br />
[/code]</p>
<ul>
<li> Edit /etc/pam.d/common-session and change the configuration as below :</li>
</ul>
<p>[code language=&#8217;cpp&#8217;]session sufficient pam_unix.so<br />
session sufficient pam_ldap.so<br />
[/code]<br />
Tutorial will be continue to part 2 of User Account Integration between Samba PDC &amp; Zimbra Mail Server on openSUSE / SLES.</p>
<p>The post <a href="https://www.vavai.net/user-account-integration-between-samba-pdc-zimbra-mail-server-on-opensuse-sles/">User Account Integration between Samba PDC &#038; Zimbra Mail Server on openSUSE/SLES</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/user-account-integration-between-samba-pdc-zimbra-mail-server-on-opensuse-sles/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 2 (Finish)</title>
		<link>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-2-finish/</link>
					<comments>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-2-finish/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Tue, 30 Mar 2010 08:52:46 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[LDAP]]></category>
		<category><![CDATA[PDC]]></category>
		<category><![CDATA[Samba]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1186</guid>

					<description><![CDATA[<p>Previous tutorial : Samba PDC+OpenLDAP on openSUSE/SLES Part 1, Setting LDAP Server SETTING LDAP CLIENT Click YAST &#124; Network Services &#124; LDAP Client Click Use LDAP pada User Authentication Fill in Address with server IP or by using 127.0.0.1 as default address MarkÂ  LDAP TLS/SSL option checked if you choose to use TLS/SSL on previous...</p>
<p>The post <a href="https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-2-finish/">How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 2 (Finish)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Previous tutorial : <a href="http://v2.vavai.net/2010/03/30/how-to-samba-pdcopenldap-on-opensusesles-part-1/">Samba PDC+OpenLDAP on openSUSE/SLES Part 1, Setting LDAP Server</a><br />
<a class="highslide" onclick="return vz.expand(this)" href="http://54.254.121.108/wp-content/uploads/2010/03/samba-pdc1.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1189" title="samba-pdc" src="http://54.254.121.108/wp-content/uploads/2010/03/samba-pdc1.jpg" alt="" width="500" height="375" /></a><br />
<strong>SETTING LDAP CLIENT</strong></p>
<ol>
<li>Click YAST | Network Services | LDAP Client</li>
<li>Click <strong>Use LDAP</strong> pada <strong>User Authentication</strong></li>
<li>Fill in Address with server IP or by using 127.0.0.1 as default address</li>
<li>MarkÂ  <strong>LDAP TLS/SSL </strong>option checked if you choose to use TLS/SSL on previous tutorial, or vice versa, leave it unchecked if you choose to not use TLS on previous tutorialÂ  <strong><br />
</strong></li>
<li>Fill in LDAP Base DN (dc=namadomain, dc=tld, ex : dc=vavai,dc=co,dc=id). You may also get the LDAP Base DN by clickingÂ  <strong>Fetch DN </strong>button</li>
<li>Leave others option as is<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap8.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1083" title="pdc-ldap8" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap8.png" alt="" width="449" height="465" /></a></li>
<li>Click <strong>Advanced Configuration</strong></li>
<li>Change <strong>Password Change Protocol</strong> to MD5</li>
<li>Leave option <strong>Group Member Attribute = Member</strong> unchanged<br />
<strong> `<br />
</strong><a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap9.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1084" title="pdc-ldap9" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap9.png" alt="" width="449" height="465" /></a><strong><br />
</strong></li>
<li>Click <strong>Administration Setting</strong></li>
<li>Fill in cn=Administrator on <strong>Administrator DN</strong>. Don&#8217;t forget to give a check on <strong>Append Base DN </strong>option</li>
<li>Mark a check on <strong>Create Default Configuration Objects </strong>option<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap10.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1085" title="pdc-ldap10" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap10.png" alt="" width="449" height="465" /></a></li>
<li>Click OK</li>
<li>Click OK</li>
</ol>
<p><strong>SETTING SAMBA SERVER PRIMARY DOMAIN CONTROLLER (PDC)</strong></p>
<ol>
<li>Open YAST | Network Services | Samba Server</li>
<li>Fill in workgroup/domain name on first wizard. I&#8217;m usingdomain <a href="http://vavai.com">vavai.co.id</a> as my  workgroup name. Click <strong>Next</strong><br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap11.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1090" title="pdc-ldap11" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap11.png" alt="" width="440" height="362" /></a></li>
<li>On  <strong>Samba Server Type</strong> option, choose <strong>Primary Domain Controller (PDC)</strong>. Click  Next</li>
<li>On  start-up tab, choose <strong>Service Start During Boot</strong> option, so  Samba will automatically started on boot. Don&#8217;t forget to click <strong>Open Port in Firewall </strong>if you use firewall on intranet zone<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap12.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1091" title="pdc-ldap12" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap12.png" alt="" width="440" height="362" /></a></li>
<li>Move to  <strong>LDAP Setting</strong> tab.</li>
<li>Click on <strong>Use LDAP Password Back-End</strong></li>
<li>Fill inÂ  Administrator DN and password setting (cn=Administrator,dc=vavai,dc=co,dc=id, adjust it with your domain name). Click  <strong>Test Connection</strong> to test LDAP server connection. If  test result is failed, recheck your configuration setting.<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap13.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1092" title="pdc-ldap13" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap13.png" alt="" width="466" height="422" /></a></li>
<li>Click  OK and then fill in  Samba root /Administrator password<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap14.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1093" title="pdc-ldap14" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap14.png" alt="" width="281" height="234" /></a></li>
</ol>
<p><strong>SETTING USER NAME &amp; PASSWORD</strong></p>
<ol>
<li>Click on <strong>YAST | Security and Users | User &amp; Group Management</strong></li>
<li>Click <strong>Expert Options | LDAP User &amp; Group Configuration</strong> option on bottom-right-corner menu</li>
<li>Fill in LDAP Admin password (see whether your bind DN configuration has setup correctly)</li>
<li>Move to  Configuration Module, and then chooseÂ  <strong>userconfiguration</strong><br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap15.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1094" title="pdc-ldap15" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap15.png" alt="" width="462" height="434" /></a></li>
<li>Change <strong>susemaxpasswordlength</strong> with your maximum password length</li>
<li>Change <strong>suseminpasswordlength</strong> with your minimum password length</li>
<li>Change  susepasswordhash from SSHA toÂ  SMD5</li>
<li>Click OK</li>
<li>Click on <strong>Set Filter </strong>option on top-right-corner menu and choose <strong>LDAP Users</strong>. This will display all LDAP user list, currently are empty because we have create any user yet</li>
<li>Click <strong>Add</strong></li>
<li>Fill in user profile and password<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap16.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1095" title="pdc-ldap16" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap16.png" alt="" width="462" height="434" /></a></li>
<li>Click OK</li>
</ol>
<p>Restart all service (or reboot your computer) to test all the service. f you wish to join Windows workstation into Samba PDC+LDAP domain, use the Samba root user name and password as Administrator user. Share folder, Profile, netlogon and custom setting could be modified within YAST | Network Services | Samba Server. Samba LDAP user could be added or modify with the above procedure using YAST | Security &amp; Users | User &amp; Group Management.</p>
<p>The post <a href="https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-2-finish/">How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 2 (Finish)</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-2-finish/feed/</wfw:commentRss>
			<slash:comments>9</slash:comments>
		
		
			</item>
		<item>
		<title>How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 1</title>
		<link>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-1/</link>
					<comments>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-1/#comments</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Tue, 30 Mar 2010 03:40:49 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[LDAP]]></category>
		<category><![CDATA[PDC]]></category>
		<category><![CDATA[Samba]]></category>
		<category><![CDATA[SLES]]></category>
		<category><![CDATA[SUSE Family]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=1179</guid>

					<description><![CDATA[<p>I have written Samba PDC+OpenLDAP tutorial on openSUSE on previous article but the tutorial are based on manual configuration and need too many steps to make it usable. Now, I want to share how to make Samba PDC+OpenLDAP on openSUSE or SLES with automatic configuration using the YAST way 🙂 . The tutorial should be...</p>
<p>The post <a href="https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-1/">How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 1</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a class="highslide" onclick="return vz.expand(this)" href="http://54.254.121.108/wp-content/uploads/2010/03/windows-linux2.jpg"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1184" title="windows-linux" src="http://54.254.121.108/wp-content/uploads/2010/03/windows-linux2.jpg" alt="" width="350" height="204" /></a><br />
I have written <a href="http://v2.vavai.net/2010/01/29/tutorial-samba-pdc-openldap-on-opensuse-11-1-%E2%80%93-part-6/">Samba PDC+OpenLDAP tutorial on openSUSE</a> on previous article but the tutorial are based on manual configuration and need too many steps to make it usable. Now, I want to share how to make Samba PDC+OpenLDAP on openSUSE or SLES with automatic configuration using the YAST way <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> . The tutorial should be easy to understand and and need a few step to make it ready for testing.<br />
<strong>INSTALLING OPENSUSE</strong><br />
Install openSUSE 11.2 with or without GUI, choose which one suitable for your purpose. I&#8217;m using a GUI example because this tutorial intended for student <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /> . a Minimal server selection (text mode) maybe a better option for production server. Please refer to <a href="http://en.opensuse.org/INSTALL_Local">openSUSE 11.2 installation guide</a> if you need an assistance regarding openSUSE installation.<br />
Lucky for Indonesian <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f600.png" alt="😀" class="wp-smiley" style="height: 1em; max-height: 1em;" /> , I&#8217;ve written a PDF tutorial with clear explanation regarding openSUSE installation for this purposeÂ  : <a href="http://vavai.com/2010/03/21/tutorial-instalasi-opensuse-11-2-versi-server-berbasis-gui-2/">Tutorial Instalasi openSUSE 11.2 Versi Server Berbasis GUI</a><br />
<strong>INSTALLING  LDAP SERVER</strong><br />
Follow these wizard to install and configure LDAP server :</p>
<ol>
<li>Open YAST | Software | Software Management<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap1.png"><img loading="lazy" decoding="async" class="size-full wp-image-1069 alignnone" title="pdc-ldap1" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap1.png" alt="" width="455" height="269" /></a></li>
<li>Choose View | Pattern</li>
<li>Scroll to  Server Function</li>
<li>Give a checked mark on <strong>File Server, DHCP and DNS Server, Directory Server (LDAP)</strong><br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap2.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1070" title="pdc-ldap2" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap2.png" alt="" width="480" height="375" /></a></li>
<li>Click <strong>Accept</strong></li>
<li>openSUSE should be automatically detect  dependency package. Click <strong>Continue </strong>to install selected package<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap3.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1071" title="pdc-ldap3" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap3.png" alt="" width="451" height="389" /></a></li>
<li>Close  YAST and then open again. I take this step to make sure YAST refresh new package installation and add to it&#8217;s menu</li>
<li>Choose YAST | Network Service | LDAP Server</li>
<li>Click <strong>Yes </strong>on <strong>Start LDAP Server. </strong>Give it a check mark on <strong>Open Port in Firewall</strong> if you use firewall. Leave others as is and then click <strong>Next</strong><br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap4.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1072" title="pdc-ldap4" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap4.png" alt="" width="468" height="388" /></a></li>
<li>Click <strong>Enable TLS </strong>and then create TLS Certificate by using <strong>Launch CA Management Module </strong>button and follow the wizard. Leave it unchecked if you wish to use LDAP without TLS connection.<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap5.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1073" title="pdc-ldap5" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap5.png" alt="" width="468" height="388" /></a></li>
<li>On  basic database setting fill in the default database setting :<br />
[code language=&#8217;cpp&#8217;]<br />
Database Type : hdb<br />
Base DN : dc=domainname, dc=tld<br />
Example :<br />
If myÂ  domain = vavai.co.id, configuration will be like this : Base DN = dc=vavai, dc=co, dc=id<br />
If my domain = vavai.com, configuration will be like this : Base DN = dc=vavai, dc=com<br />
Administrator DN : cn= Administrator. Leave  Append Base DN option checked<br />
Don&#8217;t forget to fill your  LDAP Password<br />
Also, leave a check mark onÂ  &#8220;Use this database as the default for OpenLDAP&#8221;<br />
[/code]<br />
Click  Next if all setting has been completed.<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap6.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1074" title="pdc-ldap6" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap6.png" alt="" width="468" height="388" /></a></li>
<li>Click Finish<br />
`<br />
<a class="highslide" onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap7.png"><img loading="lazy" decoding="async" class="alignnone size-full wp-image-1075" title="pdc-ldap7" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap7.png" alt="" width="468" height="388" /></a></li>
</ol>
<p><strong>ADD SAMBA SCHEMA</strong></p>
<ol>
<li>Open YAST | Network Services | LDAP Server</li>
<li>Click   <strong>Schema Files</strong> on left pane menu</li>
<li>Click Add and add <strong>Samba3.Schema</strong> so we will have following   LDAP Schema : schema, core, cosine, inetorgperson,  rfc2307bis,yast and samba3<br />
`<br />
<a onclick="return vz.expand(this)" href="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap-schema.png"><img loading="lazy" decoding="async" title="pdc-ldap-schema" src="http://vavai.com/wp-content/uploads/2010/03/pdc-ldap-schema.png" alt="" width="450" height="351" /></a></li>
<li>Click OK</li>
</ol>
<p>Next Tutorial are LDAP Client Configuration</p>
<p>The post <a href="https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-1/">How To : Samba PDC+OpenLDAP on openSUSE/SLES Part 1</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/how-to-samba-pdcopenldap-on-opensusesles-part-1/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 10/213 objects using Disk
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d3b35uem336dgh.cloudfront.net
Lazy Loading (feed)
Minified using Disk
Database Caching 2/64 queries in 0.029 seconds using Disk

Served from: www.vavai.net @ 2026-11-11 13:10:33 by W3 Total Cache
-->