Problem connecting to Firetrust (on outbound port 4051)

Well, it's up and running, but I'm not sure if it's doing what it should.
spauldingd
Student Sheep
Posts: 10
Joined: Sat Aug 29, 2009 3:40 am

Problem connecting to Firetrust (on outbound port 4051)

Fri Feb 19, 2010 4:27 am

Yesterday I noticed the error message on the web interface. In addition, the stats show

Code: Select all

Description	Total
(Yesterday)	Total
(Today)
Processed	3583	1282
Emails(ok)	608	120
FA	121	98
RBL	1395	510
Black listed	0	0
Custom filter	0	0
FA(IP)	28	9
SPF(Lite)	0	0
Gray listed	1455	556
Gray listed(ok)	264	72
Empty Email Body	3	0
Uploaded	2296	843
The numbers shown for FA seem extremely low.
Any clues? I am running 2.7.3 {U}
User avatar
nick.bolton
The Big Cheese
Posts: 1812
Joined: Thu Aug 28, 2008 4:02 pm

Re: Problem connecting to Firetrust (on outbound port 4051)

Thu Feb 25, 2010 2:06 pm

Sorry for the late reply. We restructured our backend and the knowledgebases took a bit of a hit but should be back to normal in a week.
spauldingd
Student Sheep
Posts: 10
Joined: Sat Aug 29, 2009 3:40 am

Re: Problem connecting to Firetrust (on outbound port 4051)

Fri Mar 12, 2010 6:31 am

I'm still getting the error. And the FA stats in my monitor is still very low. Yesterday FA caught 81 SPAM, today so far they have caught 0.
cliff
Evil Firetrust Employee
Posts: 31
Joined: Tue Jul 28, 2009 3:50 pm

Re: Problem connecting to Firetrust (on outbound port 4051)

Fri Mar 12, 2010 2:17 pm

Hi there,

If you are having outgoing connection issue to port 4051, First Alert can not function properly.

Can you please ping to following address and post the response here:
ping native.first-alert.net

If you ping it a few hours apart it should respond with a different IP address occasionally - this is expected as it is a load balanced service.

The fact it's connecting occasionally, and FA is registering spam, I'm leaning towards occasional DNS failures

Also, if you can post the log I can analyze it further :)

~ C
zkaesberg
It begins with a single step
Posts: 1
Joined: Fri Mar 26, 2010 5:31 am

Re: Problem connecting to Firetrust (on outbound port 4051)

Fri Mar 26, 2010 5:38 am

I am also getting this error. When I ping native.first-alert.net it resolves the IP address to 209.213.221.162 but I always get Requested Timed Out. Please let me know what I can do. Thanks...
cliff
Evil Firetrust Employee
Posts: 31
Joined: Tue Jul 28, 2009 3:50 pm

Re: Problem connecting to Firetrust (on outbound port 4051)

Tue Mar 30, 2010 12:29 am

Hi there,

Are there any other IP's that are tming out? - or just the .162 address?

The reason I ask is becasue I have seen the same IP show up in another error report recently - it may be conicidence, or could be something behind it.

Also, what was the timestamp when the error occured? (and time zone if not GMT)
spauldingd
Student Sheep
Posts: 10
Joined: Sat Aug 29, 2009 3:40 am

Re: Problem connecting to Firetrust (on outbound port 4051)

Tue Mar 30, 2010 4:24 am

Sorry I have been very busy and unable to get back to this since my last post.

I have attempted to ping native.first-alert.net multiple times from multiple locations (home, work) and it always fails to return a ping. Tracert also dies before reaching the end.

Attached is a portion of a log file.
Attachments
log-2010-03-25.txt
(231.37 KiB) Downloaded 282 times
cliff
Evil Firetrust Employee
Posts: 31
Joined: Tue Jul 28, 2009 3:50 pm

Re: Problem connecting to Firetrust (on outbound port 4051)

Wed Mar 31, 2010 3:43 pm

Hi there,

There won't be a ping response from the first alert servers due to firewalling, but you should see a different ip address occasionally as it's a balanced service. (provided you don't have the dns cached)

There has been no issues with the networking/general connectivity of the server itself, so I'm more inclined to suspect a service issue.

If it's intermittant, it will be near impossible to draw a firm conclusion, but I will review the logs this evening and see if it can shed any light.
cliff
Evil Firetrust Employee
Posts: 31
Joined: Tue Jul 28, 2009 3:50 pm

Re: Problem connecting to Firetrust (on outbound port 4051)

Sat Apr 03, 2010 10:37 pm

Hi again,

I've reviewed the logs (apologies on the delay) and can see there's a consistant error with uploading to First alert - this means it cant check with us to verify if it's spam or not.

We are not experiencing any issues with the First alert service, and all our tests to all servers are showing green lights.

Once thing I will suggest is an upgrade to the current 2.7.4 version of the software and see if the errors still occur.
If they still appear, change the logging level to 1, and send us a complete log (from a startup to the end of the day/log rotation) - and we will see if we can find any more informationof the issue.

Return to “Post Installation”