Trying to get Exim running on an F13 system, everything is configured except I need to add one additional non standard port for EXIM to listen on (TCP port 554) due to some ISP filters in the way.
Problem is when I add 554 to the list of ports for Exim it won't start up and I get the following in the log file -
2010-11-01 16:03:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (2 more tries) 2010-11-01 16:03:43 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (1 more try) 2010-11-01 16:04:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: daemon abandoned
according to "netstat -an" nothing is listening on 554. I suspect its something simple, just don't know where to make the change.
Thanks, Jeff
Trying to get Exim running on an F13 system, everything is configured except I need to add one additional non standard port for EXIM to listen on (TCP port 554) due to some ISP filters in the way.
Problem is when I add 554 to the list of ports for Exim it won't start up and I get the following in the log file -
2010-11-01 16:03:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (2 more tries) 2010-11-01 16:03:43 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (1 more try) 2010-11-01 16:04:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: daemon abandoned
according to "netstat -an" nothing is listening on 554. I suspect its something simple, just don't know where to make the change.
Thanks, Jeff
after some digging around I think I found it, the problem is SELinux, in the process of modifying the rules now.
Jeff
On 11/01/2010 09:25 PM, Jeffrey Ross wrote:
Trying to get Exim running on an F13 system, everything is configured except I need to add one additional non standard port for EXIM to listen on (TCP port 554) due to some ISP filters in the way.
Problem is when I add 554 to the list of ports for Exim it won't start up and I get the following in the log file -
2010-11-01 16:03:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (2 more tries) 2010-11-01 16:03:43 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (1 more try) 2010-11-01 16:04:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: daemon abandoned
according to "netstat -an" nothing is listening on 554. I suspect its something simple, just don't know where to make the change.
Thanks, Jeff
Sounds like Selinux is blocking the port, can you disable it temporary to see if it works:
# echo 0 > /selinux/enforce
# Retest again
# echo 1 > /selinux/enforce
HTH
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/01/2010 04:46 PM, Athmane Madjoudj wrote:
On 11/01/2010 09:25 PM, Jeffrey Ross wrote:
Trying to get Exim running on an F13 system, everything is configured except I need to add one additional non standard port for EXIM to listen on (TCP port 554) due to some ISP filters in the way.
Problem is when I add 554 to the list of ports for Exim it won't start up and I get the following in the log file -
2010-11-01 16:03:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (2 more tries) 2010-11-01 16:03:43 socket bind() to port 554 for address (any IPv4) failed: Permission denied: waiting 30s before trying again (1 more try) 2010-11-01 16:04:13 socket bind() to port 554 for address (any IPv4) failed: Permission denied: daemon abandoned
according to "netstat -an" nothing is listening on 554. I suspect its something simple, just don't know where to make the change.
Thanks, Jeff
Sounds like Selinux is blocking the port, can you disable it temporary to see if it works:
# echo 0 > /selinux/enforce
# Retest again
# echo 1 > /selinux/enforce
HTH
Something like
# semanage port -a -t smtp_port_t -p tcp 554
Will probably fix this.
-
Athmane Madjoudj -
Daniel J Walsh -
Jeffrey Ross