SQLgrey database error/SQLgrey recovered DB

[erroneus]

I keep getting emails reporting errors and recovery every 30 minutes. I have deleted a bunch of old entries using the method provided in the SQLgrey list page at the bottom, but the errors keep reporting and have been since about the 4th of January.

I suspect something is a little off in the database file itself and that I need to perform some sort of "compact database" operation but I don't know how. Any suggestions?

[wiggidy]

I get this a tonne too. However we do get a lot of mail 30000+ accounts, so I chalked it up to busy server. In any event mail still seems to flow so ?????

If there is a small solution/workaround I would definitely be interested

PS my first post, been using ESVA last 2 weeks and we handle a lot of mail... end result.... SWEET!!! this does work very nice in an ESX environment, KUDOs to the creator(s)

[erroneus]

I'm with you in that it doesn't seem to cause any problems but I'd rather it not get such errors either.

I'm considering rebuilding my ESVA. I built one the other day for a friend and it wasn't so bad though it was rather time consuming. Rebuilding the VM with all the typical tweaks and also updating the MailScanner/ClamAV would be a good thing to do anyway.

[erroneus]

Run a search for "SQLgrey" and my username (erroneus) and you will see that I created the same or similar problem with ESVA 2.0.5.7. It seems that the periodic error report is linked to my periodic update of the recipient_access file.

I wouldn't have connected the two naturally since one is SQLgrey and the other is postmap/postfix, but they do seem to be related.

I may do some further digging into the issue, but my guess is that updating postmap/postfix will reset the connection between postfix and sqlgrey which results in the error reporting. (The connection between the two is via inet:localhost:2501. Restarting postfix is probably also upsetting sqlgrey.)

I am temporarily suspending the hourly cron job to see if those errors go away.