S. Dale Morrey
sdalemorrey at gmail.com
Tue Apr 9 10:49:44 MDT 2013
Yep! That seems to have solved it. Thanks I would have never thought of
selinux. Is there anyway to completely stop/remove it on a permanent
basis? That single program seems to be all but useless at doing anything
other than getting in the way of legit apps.
On Tue, Apr 9, 2013 at 10:37 AM, Doran L. Barton <fozz at hypermoo.com> wrote:
> On Tuesday, April 09, 2013 10:18:02 AM S. Dale Morrey wrote:
> > I've checked with netstat and nothing is bound to port 80 or 8080 or
> > so I really don't know what it's problem is.
> I have to wonder if this is an SELinux issue. Run '/usr/sbin/setenforce 0'
> try starting the httpd service again. If it works, then you need to tweak
> SELinux rules so that it can bind to that port. A quick googling tells us
> way to do this is as follows:
> semanage port -a -t http_port_t -p tcp 8081
> To see the ports allowed for Apache (the http_port_t context):
> semanage port -l | grep -w http_port_t
> Hope that helps.
> Doran L. Barton <fozz at hypermoo.com> - Linux, Perl, Web, good fun, and
> "This tastiness can not be carried even by both hands."
> -- Seen on a box of chocolate cake in Japan
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
More information about the PLUG