Doll, Margaret Ann wrote:
> from service iptables status
>
> 8 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state
> NEW
> tcp dpt:515
> 9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state
> NEW
> tcp dpt:445
> 10 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state
> NEW
> udp dpt:515
> 11 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state
> NEW
> tcp dpt:631
> 12 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state
> NEW
> udp dpt:631
Y'know, /etc/sysconfig/iptables is easier to read....
>
> cups error_log after a reboot
>
<snip> ...
> I [19/Feb/2013:12:00:57 -0500] Listening to :::631 (IPv6)
> I [19/Feb/2013:12:00:57 -0500] Listening to /var/run/cups/cups.sock
> (Domain)
<snip>
> E [19/Feb/2013:12:00:58 -0500] Unable to bind socket for address
> 0.0.0.0:631- Address already in use.
> I [19/Feb/2013:12:00:58 -0500] Listening to :::631 on fd 7...
> I [19/Feb/2013:12:00:58 -0500] Listening to /var/run/cups/cups.sock on fd
> 8...
> I [19/Feb/2013:12:00:58 -0500] Resuming new connection processing...
<snip>
Now, I *really* don't know much about this, I read some a few years ago...
but are you running IPv6? If not, is there a possibility that it's looking
at that, and keeping IPv4 from having the socket?
mark
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
