Re: [Sqlgrey-users] Too many "warning: connect to 127.0.0.1:2501: Connection timed out"

[Dan F. <da...@ha...>]

Dave Strickler wrote:
> had these "450 Server Config Problems" long before the mods.
>   
Well.. Ive had that error plenty of times on our own, self-coded 
policy-deamons some years ago ;). I didnt mention it because your error 
is "connection timeout", while mine is "connection refused". The latter 
indicates that the port is no longer listening (eg. the deamon crashed 
and halted), where your error seems to indicate very slow response.

> Question: Do you run the cleanup in Async or Sync mode? We have been running Async, and I have always feared this was a problem, even though we have tested Sync mode and gotten the same errors.
>   
Due to the warning in sqlgrey.conf ("BEWARE: lockups have been 
reported"), we do NOT use async. I havent even tested async.

> I also noted that you run MySQL instead of Postgres. It would be possible for us to switch, but certainly difficult to try just for testing.
>   
Hmm. Dunno.. This day and age, MySQL and Postgres should be pretty equal 
in perfomance. However i never REALLY used postgres, so i can say for sure.

> Also, we almost always get these errors at the top of the hour. The only cronjob that runs at the top of the hour is a process that rolls our log files, and gzips them for us. During the gzip process the load spikes a little, but not much, even through the gzip process may take 90% of the CPU for 30-60 seconds.
>   
Well.. You could change the cron time 30 minutes and see if it still 
coincides with the error.
I remember hunting alot of errors like this..
With postgrey i got "450 Server configuration error" if the cleanup 
didnt finish quickly enough.. So i disabled cleaup, and had it run at 5 
am from a cronjob, then restart postfix to make sure.
One of our other policy-daemons had a tendency of hanging, not every 
day, but always around 6am when it happend. Turns out logrotate ran at 
6am. And logrotate stops syslog while rotating.

We have an outstanding bug in sqlgrey (due to be fixed very soon) that 
kills sqlgrey if syslog isnt running and sqlgrey is trying to write a 
log entry. If you rotate your logs every hour, that may include 
restarting syslog. If a mail transaction is initiated in the time it 
takes to rotate your logs, sqlgrey will probably die. That would explain 
your problem, however logic dictates that it would result in "Connection 
refused", not a timeout.. But i may be wrong :)

- Dan