<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem  Starting apache httpd using sudo in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/problem-starting-apache-httpd-using-sudo/m-p/6437830#M54571</link>
    <description>&lt;P&gt;I have a very strange issue.&amp;nbsp; I can't start the (IBM IHS) apache/httpd on one RHEL 6.2 machine (VM running on HP hardware) IF I use sudo.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, I know you can't&amp;nbsp;bind to ports &amp;lt; 1024 without root privs. So I configured sudo like I always do so allow users to run "[path]/bin/apachectl" via sudo.&amp;nbsp; This works&amp;nbsp;fine on two other&amp;nbsp;supposedly identical machines, but here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, out of curiousity, I changed it&amp;nbsp;to listen on port 8080.&amp;nbsp;&amp;nbsp; Now, this is truly&amp;nbsp;odd:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ /ihs/ihs8-80/bin/apachectl start&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21095&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21096 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21097 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21098 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21129 21059&amp;nbsp; 0 14:20 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ /ihs/ihs8-80/bin/apachectl stop&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21139 21059&amp;nbsp; 0 14:21 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ sudo /ihs/ihs8-80/bin/apachectl start&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21171 21059&amp;nbsp; 0 14:21 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why would this NOT work with sudo but work fine without it?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have doubled checked my sudo setup, it is identical to the other machines where this works (on either port).&amp;nbsp; I even reinstalled the sudo rpm.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help.&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Apr 2014 19:16:52 GMT</pubDate>
    <dc:creator>Craig Johnson_1</dc:creator>
    <dc:date>2014-04-04T19:16:52Z</dc:date>
    <item>
      <title>Problem  Starting apache httpd using sudo</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problem-starting-apache-httpd-using-sudo/m-p/6437830#M54571</link>
      <description>&lt;P&gt;I have a very strange issue.&amp;nbsp; I can't start the (IBM IHS) apache/httpd on one RHEL 6.2 machine (VM running on HP hardware) IF I use sudo.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now, I know you can't&amp;nbsp;bind to ports &amp;lt; 1024 without root privs. So I configured sudo like I always do so allow users to run "[path]/bin/apachectl" via sudo.&amp;nbsp; This works&amp;nbsp;fine on two other&amp;nbsp;supposedly identical machines, but here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, out of curiousity, I changed it&amp;nbsp;to listen on port 8080.&amp;nbsp;&amp;nbsp; Now, this is truly&amp;nbsp;odd:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ /ihs/ihs8-80/bin/apachectl start&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21095&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21096 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21097 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21098 21095&amp;nbsp; 0 14:20 ?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 /ihs/ihs8-80/bin/httpd -d /ihs/ihs8-80 -k start&lt;/P&gt;&lt;P&gt;ajohnsce 21129 21059&amp;nbsp; 0 14:20 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ /ihs/ihs8-80/bin/apachectl stop&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21139 21059&amp;nbsp; 0 14:21 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ sudo /ihs/ihs8-80/bin/apachectl start&lt;/P&gt;&lt;P&gt;[ajohnsce@a300s706 ~]$ ps -ef | grep http&lt;/P&gt;&lt;P&gt;ajohnsce 21171 21059&amp;nbsp; 0 14:21 pts/0&amp;nbsp;&amp;nbsp;&amp;nbsp; 00:00:00 grep http&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why would this NOT work with sudo but work fine without it?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have doubled checked my sudo setup, it is identical to the other machines where this works (on either port).&amp;nbsp; I even reinstalled the sudo rpm.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help.&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2014 19:16:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problem-starting-apache-httpd-using-sudo/m-p/6437830#M54571</guid>
      <dc:creator>Craig Johnson_1</dc:creator>
      <dc:date>2014-04-04T19:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem  Starting apache httpd using sudo</title>
      <link>https://community.hpe.com/t5/operating-system-linux/problem-starting-apache-httpd-using-sudo/m-p/6439402#M54573</link>
      <description>&lt;P&gt;my first thought would be, possibly&amp;nbsp;selinux rearing it ugly head.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 13:28:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/problem-starting-apache-httpd-using-sudo/m-p/6439402#M54573</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2014-04-07T13:28:26Z</dc:date>
    </item>
  </channel>
</rss>

