I feel like I'm crying "wolf!", so let's put this "bug" on ice for a
moment: my previous hang issues were a showstopper for me and I got
really busy at work. I migrated my email out of aox because I didn't
have time to debug further.

Last night I saw that a release was likely approaching and I'm the port
maintainer on FreeBSD, so I fired 3.1.3 up with a clean database and
started syncing my email with imapsync. I thought I saw the old
stall/hang I used to hit -- no CPU consumption on the aox/postgres side,
client doesn't appear to be doing anything but waiting/locked
indefinitely. Built git head -- thought I saw the same thing. Left it
running all night in that tmux session, woke up this morning and saw
mails moving.....

I'm not connecting with TLS right now, and previously I was able to
reproduce it both with and without. This heisenbug might have gone away,
but my environment is slightly different from January but I know there
hasn't been that much code change since earlier in the year...

Let me get all my mail in it and spend a few days reading it from a few
clients and see if I can trigger it again. It would usually 
happen within an hour or two of service uptime and the only fix was to
restart my client or restart the aox service. 

Funny how when I start playing with aox again I long for my email to be
back in it (it's so damn fast!).

Reply via email to