Apache 2.0 Running a site on another port with a second ipaddress

[sgoldman at MIT.EDU (Stephen B Goldman)]

Hello Tom,
   This is a second address on the machine -
The first in 192.168.1.35  which listens on 80

The second Virtual Host is 192.168.1.110  which should listen on 1185-


I tested 192.168.1.110 on 80 and it worked-

the goal is it to have listen on 1185

and this is where the problem is.

Thanks,
Stephen




Quoting Tom Metro <blu at vl.com>:

> Stephen B Goldman wrote:
>> Running Apache 2.0 - I received a "no listening sockets" when I try to
>> bind a second ip address (192.168.1.110) Port 1185 on my web server.
>
> It isn't clear from your description whether you are adding an IP 
> alias using a non-standard listening port, if you are just adding a 
> second listening port on the same IP, or changing the port from 80 to 
> 1185.
>
>
>> [root at tophat log]# tail messages
> [...]
>> Apr 20 10:07:20 tophat httpd: httpd shutdown failed
>> Apr 20 10:07:25 tophat httpd: (13)Permission denied: make_sock: 
>> could not bind
>> to address 192.168.1.110:1185
>> Apr 20 10:07:25 tophat httpd: no listening sockets available, shutting down
>> Apr 20 10:07:25 tophat httpd: Unable to open logs
>> Apr 20 10:07:25 tophat kernel: audit(1177078045.770:10): avc:  denied  {
>> name_bind } for  pid=6497 comm="httpd" src=1185 
>> scontext=root:system_r:httpd_t
>> tcontext=system_u:object_r:port_t tclass=tcp_socket
>> Apr 20 10:07:25 tophat httpd: httpd startup failed
>
> This wouldn't happen to be a Red Hat system running SELinux where you 
> need to adjust the rules to allow the httpd process to access the 
> otherwise non-privileged port, 1185? The kernel log entry above 
> suggests this is the problem.
>
>  -Tom
>
> -- 
> Tom Metro
> Venture Logic, Newton, MA, USA
> "Enterprise solutions through open source."
> Professional Profile: http://tmetro.venturelogic.com/
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.