Connect ok but I get a lot of econnrefused and ehostunreach
Posted: Mon Feb 28, 2011 5:05 pm
Hi,
my server works ok since days, but looking at the logs I have lots of repeated lines with these errors:
The connection is anyway initiated within seconds from these so the configs are perfectly aligned, I only would like not to see all these logs there because they grow fast and I don't find a sense in these. I'm using no verb option so there isn't a chance I can get the log less verbose and avoid these lines, is there? Do you think there's a problem somewhere? Advices to obtain the wanted result (no such lines even if the "no-problem" persists)?
As always, thanks.
my server works ok since days, but looking at the logs I have lots of repeated lines with these errors:
This is a Windows pc connecting to the server. It happens on connections or on disconnections. I thought it could be the firewall but also another device with no firewall that is 100% reachable as far as I know creates these logs.Sat Feb 26 18:02:49 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:02:53 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:02:57 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:02 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:06 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:10 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:15 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:19 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:23 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:27 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:33 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:37 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:41 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:45 2011 read UDPv4 [EHOSTUNREACH|EHOSTUNREACH|EHOSTUNREACH]: No route to host (code=148)
Sat Feb 26 18:03:48 2011 read UDPv4 [ECONNREFUSED|ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:48 2011 ip:port write UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:48 2011 read UDPv4 [ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:50 2011 ip:port write UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:50 2011 read UDPv4 [ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:53 2011 ip:port write UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:53 2011 read UDPv4 [ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:55 2011 ip:port write UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:55 2011 read UDPv4 [ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:57 2011 ip:port write UDPv4 [ECONNREFUSED|ECONNREFUSED]: Connection refused (code=146)
Sat Feb 26 18:03:57 2011 read UDPv4 [ECONNREFUSED]: Connection refused (code=146)
The connection is anyway initiated within seconds from these so the configs are perfectly aligned, I only would like not to see all these logs there because they grow fast and I don't find a sense in these. I'm using no verb option so there isn't a chance I can get the log less verbose and avoid these lines, is there? Do you think there's a problem somewhere? Advices to obtain the wanted result (no such lines even if the "no-problem" persists)?
As always, thanks.