Socket Error 10060 |
Post Reply |
Author | |
JohnD
Guest Group |
Post Options
Thanks(0)
Posted: 12 April 2006 at 10:03am |
This error has started appearing in my spam filter log. any ideas (SPF V3 beta) Exception occurred during GetSFDBStats: Socket Error # 10060 Connection timed out. John, |
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
That should happen when we perform maintenance on our web server, or on the SFDB web applicaiton. Yesterday we had a few hours of downtime on the SFDB app while upgrading it. The only effect for SpamFilter is to skip the SFDB filter check, and should be of no concern.
SpamFilter also has "intelligence" (if we can call it like that) in that if it encounters a few consecutive failures while checking the SFDB filter, it will skip the test completely for about a minute, thus saving some time in that it does not have to wait for a timeout to reach the SFDB server. It will automatically re-poll our saerver, and when the SFDB database is back online, the test resume automatically. |
|
JohnD
Guest Group |
Post Options
Thanks(0)
|
I am still getting this error still this morning. Do I need to open up a port on my firewall for updates?
John,
|
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
John,
On the lower right corner of SpamFilter's GUI window, do you see "v. 2.7.1.532" in red as the Latest build available for download? That number is retrieved via a web request to our website. If the version is displayed, your SpamFilter server was able to communicate with our webserver. As the SFDB filter makes HTTP calls to our same webserver, that should work as well. If the version is not displayed, then yes, there may be a communication problem preventing your SpamFilter server from reaching our website. From the server's console, are you able to browse to our website at www.logsat.com? If so, do you perhaps have any proxy settings that could prevent the SpamFilter's service from reaching our website? |
|
JohnD
Guest Group |
Post Options
Thanks(0)
|
No, I have the words Feature disabled, and the machine running spam filter has no access to the internet.
John,
|
|
JohnD
Guest Group |
Post Options
Thanks(0)
|
I have enabled he check for new build option, but now I get Unable to contact server.
jJohn,
|
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
The new SFDB filter works by querying our webserver to see if an IP address is blacklisted. If your server is not able to access the internet and/or the HTTP port 80 to our www.logsat.com website is closed, the filter will not be able to contact our server and an error will be reported in the logs.
In this case, you can either allow your server to contact port 80 on www.logsat.com, or you can disable the SFDB filter by entering a "0" in the threshold value unders the "Settings - Configuration - SFDB" tab. There may be a bug in that SpamFilter will try to update some stats relative to the SFDB filter even though it has been disabled, we're looking into it right now. If so, the next build to be released within the next 12-48 hours will contain the fix. |
|
JohnD
Guest Group |
Post Options
Thanks(0)
|
Thanks, I have opend a port on the firewall for spamfilter and the error is now gone.
John,
|
|
Web123
Guest Group |
Post Options
Thanks(0)
|
I am getting: EXEPTION OCCURED DURING GETSFDBStats: http/1.1 500 INTERNAL SERVER ERROR I am on v.3.0.1.552 And I can see "v. 2.7.1.532" in the gui. It also seems that I can send IPs to SFDB but not recieve Stats? Regards, Web123
|
|
Web123
Guest Group |
Post Options
Thanks(0)
|
And here logs: 04.18.06 14:26:30:437 -- (1884) Blacklist cache - starting cleanup |
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
That error "internal server error" is actually the response of our website when it experiences problems. SpamFilter currently logs it as an exception, and we'll be changing that to something less dramatic.
Unless you have thousands of such entries per day, it's not something to worry about. We are continuosly tweaking the server-end of the SFDB filter, so sometimes that error will show up. |
|
web123
Guest Group |
Post Options
Thanks(0)
|
Only a couple every 10min, so nothing for me to worry about then!
Thanks,
Web123
|
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.231 seconds.