<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mohit Sethi on Medium]]></title>
        <description><![CDATA[Stories by Mohit Sethi on Medium]]></description>
        <link>https://medium.com/@mohitsethi?source=rss-4d6dbdcf1d2d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*H58uabtbqCTSqu3I.jpeg</url>
            <title>Stories by Mohit Sethi on Medium</title>
            <link>https://medium.com/@mohitsethi?source=rss-4d6dbdcf1d2d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:03:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mohitsethi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Learn to #Chess]]></title>
            <link>https://medium.com/@mohitsethi/started-learning-chess-df79e8d4b4d?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/df79e8d4b4d</guid>
            <category><![CDATA[chess]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sun, 22 Jan 2017 04:24:36 GMT</pubDate>
            <atom:updated>2017-01-22T04:25:04.371Z</atom:updated>
            <content:encoded><![CDATA[<p>As a part of my practice to learn a new game every year, i started with Chess. I’ve started with learning from <a href="https://www.chesscademy.com/">ChessAcademy</a>. Do check them out!</p><p>Twitter: <a href="https://twitter.com/chesscademy">chessacademy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df79e8d4b4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unable to monitor filesystem using inotify??]]></title>
            <link>https://medium.com/appliedcode/unable-to-monitor-filesystem-using-inotify-eb9f02ab1447?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb9f02ab1447</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Thu, 01 Dec 2016 07:07:50 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:55.771Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, Listen (inbuilt Linux command) uses inotify by default on Linux to monitor directories for changes. It’s very common to encounter with the system limit on the number of files to be monitored.</p><p>You can get the your current inotify set limit, execute below command:</p><pre>$ cat /proc/sys/fs/inotify/max_user_watches</pre><p>When this limit is not enough to watch files inside the directory, you can increase it as per your usage using below commands for temporary set limit:</p><pre>$ sudo sysctl fs.inotify.max_user_watches=524288<br>$ sudo sysctl -p</pre><p>If you want to set the limit permanently, use:</p><pre>$ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf<br>$ sudo sysctl -p</pre><p>You may also need to keep tracks of values of max_queued_events and max_user_instances.</p><p>Quicker way to set limit to inotify watchers:</p><ul><li>If you are running Debian, RedHat, or another similar Linux distribution, run the following in a terminal:</li><li>echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf &amp;&amp; sudo sysctl -p</li><li>If you are running ArchLinux, run the following command instead</li><li>echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf &amp;&amp; sudo sysctl — system</li></ul><p>Cheers!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb9f02ab1447" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/unable-to-monitor-filesystem-using-inotify-eb9f02ab1447">Unable to monitor filesystem using inotify??</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ajenti: Web based Control panel for managing linux server]]></title>
            <link>https://medium.com/appliedcode/ajenti-web-based-control-panel-for-managing-linux-server-1ff13d3361f2?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ff13d3361f2</guid>
            <category><![CDATA[ajenti]]></category>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Mon, 10 Aug 2015 17:37:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:43.386Z</atom:updated>
            <content:encoded><![CDATA[<p>Ajenti is an open-source <strong>web based system Management control panel</strong> for managing remote system administrating tasks from the browser similiar to Webmin module. It is a much powerful and lightweighted tool, that provides fast and responsive web interface for managing small server setups and best suitable for VPS and dedicated servers.<br><br>It can install packages and run commands, and you can view basic server information such as RAM in use, free disk space, etc. All this can be accessed from a web browser.<br>Optionally, an add-on package called Ajenti V allows you to manage multiple websites from the same control panel.</p><h4>Pre-requisites for Ajenti:</h4><p>1. Registered Domain name<br>2. Setup hostname on the Server on which you are going to setup the Ajenti CP.<br>3. A non-root user with sudo privileges.</p><h4>Installing Ajenti</h4><p>On your server, as a user with sudo access, first add the repository key. This is used to validate the sources of the Ajenti packages you will be installing.</p><pre>$ wget http://repo.ajenti.org/debian/key -O- | sudo apt-key add -</pre><p>Then add the actual repository to your sources list:</p><pre>$ echo &quot;deb http://repo.ajenti.org/ng/debian main main ubuntu&quot; | sudo tee -a /etc/apt/sources.list</pre><p>Now you can update your packages and begin the install process by running:</p><pre>$ sudo apt-get update &amp;&amp; sudo apt-get install ajenti</pre><p>When it prompts you to continue, type Y and press ENTER. The install process may take a few minutes. After the process is over, start the Ajenti server:</p><pre>$ sudo service ajenti restart</pre><h4>Configuring Ajenti</h4><p>Now, you ajenti is installed, need to configure and it will by default take all the default metrics of server. Open a web browser and browse to <a href="https://panel.your_domain_name:8000/">https://panel.your_domain_name:8000/</a> or <a href="https://ip:8000/">https://IP:8000/.</a><br><br>Log in with these default credentials:<br><br>Username: root<br><br>Password: admin<br><br>You will now be inside your new Ajenti control panel.</p><h4>Plugins</h4><p>Ajenti already has a lot of functionality built in by default, but if you want even more settings and configurable items in your panel, you can check out the Plugins section. Some plugins are enabled by default, while others aren’t, usually due to unsatisfied dependancies.<br><br>You can install disabled plugins by clicking on them in the Plugins menu and pressing the button next to the dependency it requires. Otherwise, if you later install an application manually and Ajenti has a plugin for, you can restart Ajenti and the corresponding menu should appear next time you log in.</p><h4>System Management</h4><p>Under the System section in the sidebar, there’s a plethora of configurable items to choose from. You can manage hard drives with the Filesystems menu.</p><p><strong>Congratulations:</strong> Ajenti control panel is installed on the server. Now, use it to manage server.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ff13d3361f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/ajenti-web-based-control-panel-for-managing-linux-server-1ff13d3361f2">Ajenti: Web based Control panel for managing linux server</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mail Server: OFBiz with Mysql Setup]]></title>
            <link>https://medium.com/appliedcode/mail-server-ofbiz-with-mysql-setup-f5e64bade787?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5e64bade787</guid>
            <category><![CDATA[apache]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sat, 08 Aug 2015 14:45:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:59.209Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*o4ZdQx599PA2T6V0.png" /></figure><p><strong>Apache OFBiz™</strong> is an open source product for the automation of enterprise processes that includes framework components and business applications for <strong>ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset Management), POS (Point Of Sale).</strong><br><br>Apache OFBiz is licensed under the Apache License Version 2.0 and is part of The <strong>Apache Software Foundation.</strong></p><h4>Step 1: Install JAVA</h4><p>Java is the primary requirement for installing Apache OFBiz. It required minimum Java 1.6 to installed on your system. Make sure you have Java installed with proper version on your system.</p><pre># java -version</pre><p>If you do not Java installed, Use below tutorial to install java else ignore it.<br><br>For Ubuntu, Debian and LinuxMint Users — Install JAVA 7 or Install <a href="http://52.55.49.1/index.php/2015/08/07/how-to-install-java-8-jdk-8u45-on-ubuntu-linuxmint-via-ppa/">JAVA 8</a></p><h4>Step 2: Install Mysql and Setup for OFBiz</h4><p>MySQL is a powerful database management system used for organizing and retrieving data</p><p>To install MySQL, open terminal and type in these commands:</p><pre>sudo apt-get install mysql-server libapache2-mod-auth-mysql php5-mysql</pre><p>During the installation, MySQL will ask you to set a root password. If you miss the chance to set the password while the program is installing, it is very easy to set the password later from within the MySQL shell.<br><br>Once you have installed MySQL, we should activate it with this command:</p><pre>sudo mysql_install_db</pre><p><strong>Creating Databases and user access for OFBiz</strong><br><br>We will be creating <strong>databases and user access </strong>which will be used with ofbiz to store the data. Below are the commands:</p><pre>mysql&gt;create database ofbiz;  <br> mysql&gt;create database ofbizolap;  <br> mysql&gt;create database ofbiztenant;  <br> mysql&gt;use mysql;  <br> mysql&gt;select database();  <br> mysql&gt;create user ofbiz@localhost;  <br> mysql&gt;create user ofbizolap@localhost;  <br> mysql&gt;create user ofbiztenant@localhost;  <br> mysql&gt;update user set password=PASSWORD(&quot;ofbiz&quot;) where User=&#39;ofbiz&#39;;  <br> mysql&gt;update user set password=PASSWORD(&quot;ofbizolap&quot;) where User=&#39;ofbizolap&#39;;  <br> mysql&gt;update user set password=PASSWORD(&quot;ofbiztenant&quot;) where User=&#39;ofbiztenant&#39;;  <br> mysql&gt;grant all privileges on *.* to &#39;ofbiz&#39;@localhost identified by &#39;ofbiz&#39;;  <br> mysql&gt;grant all privileges on *.* to &#39;ofbizolap&#39;@localhost identified by &#39;ofbizolap&#39;;  <br> mysql&gt;grant all privileges on *.* to &#39;ofbiztenant&#39;@localhost identified by &#39;ofbiztenant&#39;;</pre><h4>Step 3: Download Apache OFBiz from SVN</h4><p>We will be using SVN download latest Apache OFBiz files. first make sure you have svn client installed on system after that checkout the latest build from the subversion repository of OFBiz.</p><pre># cd /opt/  <br> # yum install subversion  <br> # svn co http://svn.apache.org/repos/asf/ofbiz/trunk apache-ofbiz</pre><h4>Step 4: Integrating Apache OFBiz with Mysql</h4><p>Before we build Apache OFBiz, we will be integrating it with Mysql<br> 1. Firstly, will be needing the JDBC connector: mysql-connector-java-5.1.14-bin.jar — to be placed in &lt;ofbiz-dir&gt;/framework/entity/lib/jdbc<br> 2. Create a backup of apache-ofbiz/framework/entity/config/entityengine.xml<br> 3. Edit entityengine.xml as follows:<br> a. Add the following datasources below the datasource ‘localmysql’</p><pre>&lt;datasource name=&quot;localmysqlolap&quot;  <br>     helper-class=&quot;org.ofbiz.entity.datasource.GenericHelperDAO&quot;  <br>     field-type-name=&quot;mysql&quot;  <br>     check-on-start=&quot;true&quot;  <br>     add-missing-on-start=&quot;true&quot;  <br>     check-pks-on-start=&quot;false&quot;  <br>     use-foreign-keys=&quot;true&quot;  <br>     join-style=&quot;ansi-no-parenthesis&quot;  <br>     alias-view-columns=&quot;false&quot;  <br>     drop-fk-use-foreign-key-keyword=&quot;true&quot;  <br>     table-type=&quot;InnoDB&quot;  <br>     character-set=&quot;latin1&quot;  <br>     collate=&quot;latin1_general_cs&quot;&gt;  <br>   &lt;read-data reader-name=&quot;seed&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;seed-initial&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;demo&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;ext&quot;/&gt;  <br>   &lt;inline-jdbc  <br>       jdbc-driver=&quot;com.mysql.jdbc.Driver&quot;  <br>       jdbc-uri=&quot;jdbc:mysql://127.0.0.1/ofbiz?autoReconnect=true&quot;  <br>       jdbc-username=&quot;ofbizolap&quot;  <br>       jdbc-password=&quot;ofbizolap&quot;  <br>       isolation-level=&quot;ReadCommitted&quot;  <br>       pool-minsize=&quot;2&quot;  <br>       pool-maxsize=&quot;250&quot;  <br>       time-between-eviction-runs-millis=&quot;600000&quot;/&gt;  <br> &lt;/datasource&gt;  <br> &lt;datasource name=&quot;localmysqltenant&quot;  <br>     helper-class=&quot;org.ofbiz.entity.datasource.GenericHelperDAO&quot;  <br>     field-type-name=&quot;mysql&quot;  <br>     check-on-start=&quot;true&quot;  <br>     add-missing-on-start=&quot;true&quot;  <br>     check-pks-on-start=&quot;false&quot;  <br>     use-foreign-keys=&quot;true&quot;  <br>     join-style=&quot;ansi-no-parenthesis&quot;  <br>     alias-view-columns=&quot;false&quot;  <br>     drop-fk-use-foreign-key-keyword=&quot;true&quot;  <br>     table-type=&quot;InnoDB&quot;  <br>     character-set=&quot;latin1&quot;  <br>     collate=&quot;latin1_general_cs&quot;&gt;  <br>   &lt;read-data reader-name=&quot;seed&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;seed-initial&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;demo&quot;/&gt;  <br>   &lt;read-data reader-name=&quot;ext&quot;/&gt;  <br>   &lt;inline-jdbc  <br>       jdbc-driver=&quot;com.mysql.jdbc.Driver&quot;  <br>       jdbc-uri=&quot;jdbc:mysql://127.0.0.1/ofbiz?autoReconnect=true&quot;  <br>       jdbc-username=&quot;ofbiztenant&quot;  <br>       jdbc-password=&quot;ofbiztenant&quot;  <br>       isolation-level=&quot;ReadCommitted&quot;  <br>       pool-minsize=&quot;2&quot;  <br>       pool-maxsize=&quot;250&quot;  <br>       time-between-eviction-runs-millis=&quot;600000&quot;/&gt;  <br> &lt;/datasource&gt;</pre><p>b. Replace derby with mysql in default, default-no-eca and test delegators as follows:</p><pre>&lt;delegator name=&quot;default&quot; entity-model-reader=&quot;main&quot; entity-group-reader=&quot;main&quot; entity-eca-reader=&quot;main&quot; distributed-cache-clear-enabled=&quot;false&quot;&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz&quot; datasource-name=&quot;localmysql&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.olap&quot; datasource-name=&quot;localmysqlolap&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.tenant&quot; datasource-name=&quot;localmysqltenant&quot;/&gt;  <br> &lt;/delegator&gt;  <br> &lt;delegator name=&quot;default-no-eca&quot; entity-model-reader=&quot;main&quot; entity-group-reader=&quot;main&quot; entity-eca-reader=&quot;main&quot; entity-eca-enabled=&quot;false&quot; distributed-cache-clear-enabled=&quot;false&quot;&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz&quot; datasource-name=&quot;localmysql&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.olap&quot; datasource-name=&quot;localmysqlolap&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.tenant&quot; datasource-name=&quot;localmysqltenant&quot;/&gt;  <br> &lt;/delegator&gt;  <br> &lt;delegator name=&quot;test&quot; entity-model-reader=&quot;main&quot; entity-group-reader=&quot;main&quot; entity-eca-reader=&quot;main&quot;&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz&quot; datasource-name=&quot;localmysql&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.olap&quot; datasource-name=&quot;localmysqlolap&quot;/&gt;  <br>   &lt;group-map group-name=&quot;org.ofbiz.tenant&quot; datasource-name=&quot;localmysqltenant&quot;/&gt;  <br> &lt;/delegator&gt;</pre><p>Save the file.</p><h4>Step 5: Installing Apache OFBiz</h4><pre># cd /opt/apache-ofbiz/  <br> # ./ant</pre><h4>Step 6: Install Dataset, Load Demo and Seed Data</h4><p>Apache OFBiz provides dataset, demo data and seed data, this data is useful for experiment. This data is unuseful for production setup.</p><pre># ./ant load-demo  <br> # ./ant load-extseed</pre><h4>Step 7: Start Apache OFBiz Service</h4><p>After installing Apache OFBiz, Use following command to start Apache OFBiz service on system.</p><pre># ./ant start</pre><h4>Access Apache OFBiz in Browser</h4><p>Access Apache OFBiz in browser on port 8443 as below given url and login credentials.</p><pre>URL: https://svr10.tecadmin.net:8443/myportal/control/main  <br> Admin Username: admin  <br> Admin Password: ofbiz</pre><p>References:<br><br>http://ofbiz.apache.org/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*Re4JmzepciHaxKOu.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*n5euCO4pIuH5lkr3.png" /></figure><p>Congratulation’s! You have successfully install apache OFBiz with Mysql integration on your Linux system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5e64bade787" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/mail-server-ofbiz-with-mysql-setup-f5e64bade787">Mail Server: OFBiz with Mysql Setup</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Install JAVA 8 (JDK 8u45) on Ubuntu & LinuxMint Via PPA]]></title>
            <link>https://medium.com/appliedcode/how-to-install-java-8-jdk-8u45-on-ubuntu-linuxmint-via-ppa-1115d64ae325?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1115d64ae325</guid>
            <category><![CDATA[java]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Fri, 07 Aug 2015 05:54:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:43.907Z</atom:updated>
            <content:encoded><![CDATA[<p>This blog post will help you to Install Oracle JAVA 8 (JDK/JRE 8u25) on Ubuntu 14.04 LTS, 12.04 LTS and 10.04 and LinuxMint systems using PPA File.</p><h4>Installing Java 8 on Ubuntu</h4><p>Add the webupd8team Java PPA repository in your system and install Oracle Java 8 using following set of commands.</p><pre>$ sudo add-apt-repository ppa:webupd8team/java  <br> $ sudo apt-get update  <br> $ sudo apt-get install oracle-java8-installer</pre><h4>Verify Installed Java Version</h4><p>After successfully installing oracle Java using above step verify installed version using following command.</p><pre>manish@tech:~$ java -version  <br> java version &quot;1.8.0_45&quot;  <br> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)  <br> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)</pre><h4><strong>Configuring Java Environment</strong></h4><p>In Webupd8 ppa repository also providing a package to set environment variables, Install this package using following command.</p><pre>$ sudo apt-get install oracle-java8-set-default</pre><h4>Reference:-</h4><p><a href="https://launchpad.net/~webupd8team/+archive/ubuntu/java">Oracle Java (JDK) 8 / 9 Installer PPA : &quot;WebUpd8&quot; team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1115d64ae325" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/how-to-install-java-8-jdk-8u45-on-ubuntu-linuxmint-via-ppa-1115d64ae325">How to Install JAVA 8 (JDK 8u45) on Ubuntu &amp; LinuxMint Via PPA</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ELK Stack: Collection and Analysis of Centralized Logs]]></title>
            <link>https://medium.com/appliedcode/elk-stack-collection-and-analysis-of-centralized-logs-75fda80355ce?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/75fda80355ce</guid>
            <category><![CDATA[kibana]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Tue, 26 May 2015 05:31:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:39.897Z</atom:updated>
            <content:encoded><![CDATA[<p>As a DevOps, it is very difficult to identify, collect and process the logs which could of System logs, Web server logs etc.</p><p>The one of the solution of above problem could be ELK stack.</p><p>ELK stack mainly composed of 3 components:</p><ul><li><strong>Elasticsearch:</strong> Store the logs collected from different servers</li><li><strong>Logstash:</strong> Collect all types of logs at centralized location</li><li><strong>Kibana:</strong> Runs the searchs and generate visual dashboard</li></ul><p><strong>How ELK works ?</strong></p><p>Logstash is an open source tool for collecting, parsing, and storing logs for future use. Kibana is a web interface that can be used to search and view the logs that Logstash has indexed. Both of these tools are based on Elasticsearch. All these together are called <strong>ELK Stack</strong>.</p><p>Using Elasticsearch as a backend datastore, and kibana as a frontend reporting tool, logstash as pipeline for storing, querying and analyzing your logs.</p><p>ELK Stack Setup has mainly four components:</p><ul><li><strong>Logstash: </strong>Server component which collects all the incoming logs</li><li><strong>Elasticsearch:</strong> stores all the logs</li><li><strong>Kibana:</strong> Web interface for searching and analysing logs</li><li><strong>Logstash Forwarder:</strong> Installed on server from which logs need to be collected. It acts as an agent uses lumberjack networking protocol to communicate with logstash.</li></ul><p>First requirement in order to setup ELK stack is to have java installed on the system.</p><p>It is recommended to run a recent version of Java in order to ensure the greatest success in running Logstash.<br><br>It’s fine to run an open-source version such as <strong>OpenJDK:http://openjdk.java.net/</strong><br>Or you can use the official Oracle version:<strong>http://www.oracle.com/technetwork/java/index.html</strong></p><p><strong>Install Elasticsearch</strong></p><p>Run the below command to get repo from apt</p><pre>sudo wget -O - http://packages.elasticsearch.org/GPG-KEY-elasticsearch | sudo apt-key add -</pre><p>Create the Elasticsearch source list</p><pre>sudo echo &#39;deb http://packages.elasticsearch.org/elasticsearch/1.1/debian stable main&#39; | sudo tee /etc/apt/sources.list.d/elasticsearch.list</pre><p>Update your apt package database:</p><pre>sudo apt-get update</pre><p>Now, we have the source to download elasticsearch, give the below command to install it</p><pre>sudo apt-get -y install elasticsearch=1.1.1</pre><p>Once, it is installed, we need to add below line to /etc/elasticsearch/elasticsearch.yml, to disable dynamic scripts.</p><p><strong>script.disable_dynamic: true</strong></p><p>In order to restrict the outside access to Elasticsearch instance(9200) by specifing the below line in configuration file.</p><p><strong>network.host: localhost</strong></p><p>If you want to access you Elasticsearch instance from clients on a different IP address via Javascript, add the following inside <strong>elasticsearch.yml</strong></p><p><strong>http.cors.enabled: true</strong><br><strong>http.cors.allow-origin: “*”</strong></p><p>Once you are done with changes, save the file and restart the service</p><pre>sudo service elasticsearch restart</pre><p>In order to boot up the Elasticsearch</p><pre>sudo update-rc.d elasticsearch defaults 95 10</pre><p>Now your Elasticsearch is all set to store for your log from multiple servers.</p><p><strong>Testing Elasticsearch:</strong></p><p>Use the below commands to test the working of elasticsearch</p><pre>ps aux | grep elasticsearch  <br> curl -X GET &#39;http://localhost:9200&#39;  <br> curl &#39;http://localhost:9200/_search?pretty&#39;</pre><p>In Browser: <a href="http://localhost:9200/">http://localhost:9200/</a></p><p><strong>Elasticsearch Kopf Plugin</strong></p><p>The kopf plugin provides an admin GUI for Elasticsearch. It helps in debugging and managing clusters and shards. It’s really easy to install:</p><pre>sudo /usr/share/elasticsearch/bin/plugin -install lmenezes/elasticsearch-kopf</pre><p>Below is the screenshot for your understanding:</p><p><strong>Install Kibana</strong></p><p>Use the below link to download the build to install kibana</p><pre>sudo wget <a href="https://download.elasticsearch.org/kibana/kibana/kibana-3.0.1.tar.gz">https://download.elasticsearch.org/kibana/kibana/kibana-3.0.1.tar.gz</a></pre><p>Extract the build,</p><pre>sudo tar xvf kibana-3.0.1.tar.gz</pre><p>Now, we need to open the kibana configuration to specify the port for elasticsearch from 9200 to 80, so we will later setup proxy server which could be nginx or squid etc. to redirect all request from port 80 to 9200. See below line in location <strong>~/kibana/config.js</strong></p><p><strong>elasticsearch: “http://”+window.location.hostname+”:80&quot;,</strong></p><p>This is necessary as kibana will be running on 80 port.</p><p>Since, we are going to install nginx, we need to specify particular location for kibana say.</p><p><strong>/opt/kibana3/</strong></p><p>Copy all the contents to this location:</p><pre>cp -R ~/kibana/* /opt/kibana3/</pre><p>Now, we hava setup the kibana, as discussed we need to install nginx, which is pretty easy.</p><p><strong>Install Nginx</strong></p><p>Use below command to install nginx</p><pre>sudo apt-get install nginx</pre><p>Next, download the Nginx configuration from kibana’s github repositories to your home dir.</p><pre>sudo wget <a href="https://gist.githubusercontent.com/thisismitch/2205786838a6a5d61f55/raw/f91e06198a7c455925f6e3099e3ea7c186d0b263/nginx.conf">https://gist.githubusercontent.com/thisismitch/2205786838a6a5d61f55/raw/f91e06198a7c455925f6e3099e3ea7c186d0b263/nginx.conf</a></pre><p>In above configuration we need to specify the FQDN (Fully Qualified Domain Name), and Kibana’s root directory.</p><p><strong>server_name FQDN;</strong><br><strong>root /root/kibana3;</strong></p><p>Once you are done with changes move the file to nginx configuration location</p><pre>sudo cp nginx.conf /etc/nginx/sites-available/default</pre><p>In order to improve your security to access nginx, you can apache2-utils to use htpasswd to generate username and password.</p><pre>sudo apt-get install apache2-utils  <br> sudo htpasswd -c /etc/nginx/conf.d/kibana.htpasswd user</pre><p>Now, you can restart the nginx service for the changes to take effect.</p><p>Kibana is now accessible via your FQDN or the public IP address of your Logstash Server i.e. <a href="http://logstash_server_public_ip/"><strong>http://logstash_server_public_ip/</strong>.</a> If you go there in a web browser, you should see a Kibana welcome page which will allow you to view dashboards but there will be no logs to view because Logstash has not been set up yet. Let’s do that now.</p><p><strong>Install Logstash</strong></p><p>The Logstash package is available from the same repository as Elasticsearch. As public key is already setup, let’s create the source list</p><pre>sudo echo &#39;deb http://packages.elasticsearch.org/logstash/1.4/debian stable main&#39; | sudo tee /etc/apt/sources.list.d/logstash.list</pre><p>Update your apt package database</p><pre>sudo apt-get update</pre><p>Install the logstash using below command:</p><pre>sudo apt-get install logstash=1.4.2-1-2c0f5a1</pre><p><strong>Generate SSL certificates:</strong></p><p>Since we are going to use Logstash Forwarder to ship logs from our Servers to our Logstash Server, we need to create an SSL certificate and key pair. The certificate is used by the Logstash Forwarder to verify the identity of Logstash Server. Create the directories that will store the certificate and private key with the following commands:</p><pre>sudo mkdir -p /etc/pki/tls/certs  <br> sudo mkdir /etc/pki/tls/private</pre><p>If you have a DNS setup with your private networking, you should create an A record that contains the <strong>Logstash Server’s private IP address — </strong>this domain name will be used in the next command, to generate the SSL certificate. Use the below command to generate it:</p><pre>sudo cd /etc/pki/tls; sudo openssl req -subj &#39;/CN=logstash_server_fqdn/&#39; -x509 -days 3650 -batch -nodes -newkey rsa:2048 -keyout private/logstash-forwarder.key -out certs/logstash-forwarder.crt</pre><p>Since, ssl certificate is generated, we need to transfer it to server from which we are going to ships logs to logstash.</p><p><strong>Configure Logstash</strong></p><p>Now, lets configure the logstash so that kibana can get the log from it.</p><p>Logstash configuration files are in the JSON-format, and reside in <strong>/etc/logstash/conf.d</strong>. The configuration consists of three sections: inputs, filters, and outputs.</p><p>Let’s create a configuration file called 01-lumberjack-input.conf and set up our “lumberjack” input (the protocol that Logstash Forwarder uses):</p><p>Create a file at location <strong>/etc/logstash/conf.d/01-lumberjack-input.conf</strong></p><p>which contains</p><p><strong>input {</strong><br><strong> lumberjack {</strong><br><strong> port =&gt; 5000</strong><br><strong> type =&gt; “logs”</strong><br><strong> ssl_certificate =&gt; “/etc/pki/tls/certs/logstash-forwarder.crt”</strong><br><strong> ssl_key =&gt; “/etc/pki/tls/private/logstash-forwarder.key”</strong><br><strong> }</strong><br><strong> }</strong></p><p>Now let’s create a configuration file called 10-syslog.conf, where we will add a filter for syslog messages at location <strong>/etc/logstash/conf.d/10-syslog.conf</strong></p><p><strong>filter {</strong><br><strong> if [type] == “syslog” {</strong><br><strong> grok {</strong><br><strong> match =&gt; { “message” =&gt; “% {SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST:syslog_hostname} % {DATA:syslog_program}(?:[%{POSINT:syslog_pid}])?: %{GREEDYDATA:syslog_message}” }</strong><br><strong> add_field =&gt; [ “received_at”, “%{@timestamp}” ]</strong><br><strong> add_field =&gt; [ “received_from”, “%{host}” ]</strong><br><strong> }</strong><br><strong> syslog_pri { }</strong><br><strong> date {</strong><br><strong> match =&gt; [ “syslog_timestamp”, “MMM d HH:mm:ss”, “MMM dd HH:mm:ss” ]</strong><br><strong> }</strong><br><strong> }</strong><br><strong> }</strong></p><p>This filter looks for logs that are labeled as “syslog” type (by a Logstash Forwarder), and it will try to use “grok” to parse incoming syslog logs to make it structured and query-able at location <strong>/etc/logstash/conf.d/30-lumberjack-output.conf</strong></p><p><strong>output {</strong><br><strong> elasticsearch { host =&gt; localhost }</strong><br><strong> stdout { codec =&gt; rubydebug }</strong><br><strong> }</strong></p><p>This output basically configures Logstash to store the logs in Elasticsearch.</p><p>With this configuration, Logstash will also accept logs that do not match the filter, but the data will not be structured (e.g. unfiltered Nginx or Apache logs would appear as flat messages instead of categorizing messages by HTTP response codes, source IP addresses, served files, etc.).</p><p>Now Restart the logstash to make changes take effect:</p><pre>sudo service logstash restart</pre><p>Setup Logstash Forwarder Package:</p><p>Get the SSL certificate which we generated previously to server from which we get the logs</p><pre>sudo scp /etc/pki/tls/certs/logstash-forwarder.crt user@server_private_IP:/tmp</pre><p><strong>Install Logstash-forwarder Package:</strong></p><p>On Server, create the Logstash Forwarder source list:</p><pre>sudo echo &#39;deb http://packages.elasticsearch.org/logstashforwarder/debian stable main&#39; | sudo tee /etc/apt/sources.list.d/logstashforwarder.list</pre><p>It also uses the same GPG key as Elasticsearch, which can be installed with this command:</p><pre>sudo wget -O - http://packages.elasticsearch.org/GPG-KEY-elasticsearch | sudo apt-key add -</pre><p>Then install the Logstash Forwarder package:</p><pre>sudo apt-get install logstash-forwarder</pre><p>Next, you will want to install the Logstash Forwarder init script, so it starts on bootup:</p><pre>sudo cd /etc/init.d/; sudo wget https://raw.githubusercontent.com/elasticsearch/logstash-forwarder/a73e1cb7e43c6de97050912b5bb35910c0f8d0da/logstash-forwarder.init -O logstash-forwarder  <br> sudo chmod +x logstash-forwarder  <br> sudo update-rc.d logstash-forwarder defaults</pre><p>Now copy the SSL certificate into the appropriate location (/etc/pki/tls/certs):</p><pre>sudo mkdir -p /etc/pki/tls/certs  <br> sudo cp /tmp/logstash-forwarder.crt /etc/pki/tls/certs/</pre><p><strong>Configure Logstash Forwarder:</strong></p><p>We need to specify in logstash forwarder configuration details of the logstash server so that it can send the details to server.</p><p>Now add the following lines into the file, substituting in your Logstash Server’s private IP address for <strong>logstash_server_private_IP</strong> at location <strong>/etc/logstash-forwarder</strong>:</p><p><strong>{</strong><br><strong> “network”: {</strong><br><strong> “servers”: [ “logstash_server_private_IP:5000” ],</strong><br><strong> “timeout”: 15,</strong><br><strong> “ssl ca”: “/etc/pki/tls/certs/logstash-forwarder.crt”</strong><br><strong> },</strong><br><strong> “files”: [</strong><br><strong> {</strong><br><strong> “paths”: [</strong><br><strong> “/var/log/syslog”,</strong><br><strong> “/var/log/auth.log”</strong><br><strong> ],</strong><br><strong> “fields”: { “type”: “syslog” }</strong><br><strong> }</strong><br><strong> ]</strong><br><strong>}</strong></p><p>Now, restart the logstash forwarder using below command</p><pre>sudo service logstash-forwarder restart</pre><p>Now, we have setup ELK stack, we just need to check the kibana dashboard for more details.</p><p>Below are the useful screenshots which represents the data which we got from server.</p><h4>Conclusion:-</h4><p>The ELK stack is very useful in different manners as in this case you will find almost all the logs that could be application log, webserver log, system log etc. Using kibana, will have a visualize report which shows the analysis of the logs which is very helpful to extract the required information.</p><p>The ELK stack is easy to maintain on the large scale systems and and large scale infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75fda80355ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/elk-stack-collection-and-analysis-of-centralized-logs-75fda80355ce">ELK Stack: Collection and Analysis of Centralized Logs</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configure S3 bucket to enable CORS configuration]]></title>
            <link>https://medium.com/appliedcode/configure-s3-bucket-to-enable-cors-configuration-3999fbc6008e?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3999fbc6008e</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sun, 24 May 2015 16:12:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:48.958Z</atom:updated>
            <content:encoded><![CDATA[<p>In order to configure s3 to allow cross-origin sharing, we need to create CORS configuration, xml document with rules that identify the origins that will allow to access your bucket, the operation(HTTP methods) will support for each origin according to configuration mentioned in S3.<br><br>In CORS configuration, you can specify following values for the AllowedMethod element.</p><ul><li>GET</li><li>PUT</li><li>POST</li><li>DELETE</li><li>HEAD</li></ul><p>While defining we must understand the following rules:</p><ul><li>First we need to specify the AllowMethod (GET, PUT, DELETE Etc) request on the first origin . The rule also allows all headers in a preflight OPTIONS request through the <strong>Access-Control-Request-Headers</strong> header.</li><li>Same rules in applied on another origin</li><li>The third rule allows cross-origin GET requests from all origins. The ‘*’ wildcard character refers to all origins.</li></ul><p><strong>Configuring S3 bucket:</strong></p><p>Within the properties of the bucket we have to choose the option <strong>“Edit CORS configuration”</strong>:</p><p>In the window that appears, enter a configuration like this:</p><p>This will accept any <strong>GET, PUT, POST or DELETE</strong> request for any element in the bucket, as long as the origin of the request is an element stored in a subdomain of example.com.</p><p>Technically, the bucket will respond to these requests with the header <strong>“Access-Control-Allow-Origin: *.example.com”</strong> when they are performed including the header Origin.</p><p>This way you can configure the s3 to enable the CORS configuration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3999fbc6008e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/configure-s3-bucket-to-enable-cors-configuration-3999fbc6008e">Configure S3 bucket to enable CORS configuration</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CORS:- Cross Origin Resource Sharing]]></title>
            <link>https://medium.com/appliedcode/cors-cross-origin-resource-sharing-95f878957deb?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/95f878957deb</guid>
            <category><![CDATA[general]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sun, 10 May 2015 07:29:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:44.043Z</atom:updated>
            <content:encoded><![CDATA[<p>Earlier, developers having the difficulty in order to make a request to a different domain from javascript. Everyone setup proxies on their websites, which was one of the onset of a new host of open redirect problems, as a way to get around the restriction. Although developers were working around this limitation using server-side proxies as well as number of techniques.<br><br>Almost all browser now support CORS (Includes IE 8+, Firefox 3.5+, Chrome)</p><h4>Cross-Origin Resource Sharing (CORS)</h4><p>* It is W3C Working draft that defines how the browser and server must communicate when accessing sources across origin. It is specification recommended by the Web Applications Working Group within the W3C.It provides a way for script running in clients browsers to use the XMLHttpRequest API object and make direct HTTP Requests to resources on domains other than from where the script was first loaded. say Zuora REST API.<br><br>* CORS provides following features:<br> <strong>Guarantees the data integrity of the API request</strong>- Nothing chenaged on its way from your server to customer.<br> <strong>Provides authentication</strong> — ensures that the person who generated the request is who they say they are.<br>The Basic idea behind CORS is to use custome HTTP headers to allow both the browser and the server to know enough about each otherin order to determine if the request or response should suceed or fail.<br><br>For a simple request, one that uses either GET or POST with no custom headers and whose body is text/plain, the request is sent with extra header called Origin, The Origin header contains the origin (protocol, domain name, and port) of the requesting page, in order to make the request to serve.<br><br>An example Origin header looks like:</p><pre>Origin: <a href="http://www.domaina.com/">http://www.domainA.com</a></pre><p>If the server decides that the request should be allowed, it sends a Access-Control-Allow-Origin header echoing back the same origin that was sent or “*” if it’s a public resource. Say,</p><pre>Access-Control-Allow-Origin: <a href="http://www.domainb.net/">http://www.domainB.net</a></pre><p>This way we can do sharing of resources against different origin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95f878957deb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/cors-cross-origin-resource-sharing-95f878957deb">CORS:- Cross Origin Resource Sharing</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MongoDB: Installation on Ubuntu/Debian Machine]]></title>
            <link>https://medium.com/appliedcode/mongodb-installation-on-ubuntu-debian-machine-4d43f6a83c2a?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d43f6a83c2a</guid>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sun, 17 Aug 2014 09:27:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:57.018Z</atom:updated>
            <content:encoded><![CDATA[<ul><li>Before making an installation of Mongodb on ubuntu we need to add sources list to local repository.</li><li>First of all, we need to add MongoDB Public GPG Key</li></ul><p><strong>sudo apt-key adv — keyserver hkp://keyserver.ubuntu.com:80 — recv 7F0CEB10</strong></p><ul><li>Next, we need to update source list /etc/apt/source.list.d/mongodb.list file using following command</li></ul><p><strong>echo ‘deb </strong><a href="http://downloads-distro.mongodb.org/repo/ubuntu-upstart"><strong>http://downloads-distro.mongodb.org/repo/ubuntu-upstart</strong></a><strong> dist 10gen’ | sudo tee /etc/apt/sources.list.d/mongodb.list</strong></p><ul><li>Now, we need to update the repository…</li></ul><p><strong>sudo apt-get update</strong></p><ul><li>Now , we are ready to install our MongoDB installation</li></ul><p><strong>apt-get install mongodb-10gen=2.2.3</strong></p><ul><li>Now we had installed MongoDB , we need to start the service</li></ul><p><strong>service mongodb start</strong></p><ul><li>To login into mongodb prompt, we give command</li></ul><p><strong>mongo</strong></p><ul><li>If you need mongodb help, use command</li></ul><p><strong>db.help()</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d43f6a83c2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/mongodb-installation-on-ubuntu-debian-machine-4d43f6a83c2a">MongoDB: Installation on Ubuntu/Debian Machine</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jenkins: Installation on Ubuntu/Debian Machine]]></title>
            <link>https://medium.com/appliedcode/jenkins-installation-on-ubuntu-debian-machine-50f68a79911f?source=rss-4d6dbdcf1d2d------2</link>
            <guid isPermaLink="false">https://medium.com/p/50f68a79911f</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Mohit Sethi]]></dc:creator>
            <pubDate>Sun, 06 Jul 2014 14:48:00 GMT</pubDate>
            <atom:updated>2017-02-09T19:45:38.894Z</atom:updated>
            <content:encoded><![CDATA[<h4>Installing Jenkins on Ubuntu or Debian</h4><p>* If you are installing Jenkins on Debian or Ubuntu, it is convenient to install the native binary package for these platforms. So. First of all, you need to add the key to your system as below:<br> $ wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | apt-key add -<br><br> $ sudo echo &quot;deb http://pkg.jenkins-ci.org/debian binary/&quot; &gt; /etc/apt/sources.list.d/jenkins.list<br><br>* Now, we update the Debian package repository, to check whether key is set and package are easily extracted.<br> $ sudo apt-get update -y<br><br>* Once this is done, you can install Jenkins using apt-get tool:<br> $ sudo apt-get install -y jenkins<br> <br> This will install jenkins as a service, with a correclty configured script at /etc/init.d/jenkins and a corresponding system user called &quot;jenkins&quot;.<br><br>* By default, you will find the jenkins WAR file in the /usr/share/jenkins directory, and the Jenkins home directory in /var/lib/jenkins.<br><br>* Now, you can start the Jenkins service:<br> $ sudo /etc/init.d/jenkins start<br> or<br> $ sudo service jenkins start<br>* You can see the Jenkins dashboard at http://localhost:8080/<br> If you can see the dashboard that means you have correct installation on Debain/Ubuntu<br> <br>This is way to install to Jenkins on Debian/Ubuntu Machine. Other Machines (REDHAT, CentOS) will require some changes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50f68a79911f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/appliedcode/jenkins-installation-on-ubuntu-debian-machine-50f68a79911f">Jenkins: Installation on Ubuntu/Debian Machine</a> was originally published in <a href="https://medium.com/appliedcode">Appliedcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>