search

forwardemail / status.forwardemail.net

Status Page
https://status.forwardemail.net
MIT License
20 stars 3 forks source link

IMAP Connection Issues #1172

Closed titanism closed 1 month ago

titanism commented 1 month ago

We are investigating reports of connection issues to our IMAP/POP3 servers. As soon as we have an update we will post here.

extremeleadprogram commented 1 month ago

Still seeing issues here:

redacted

titanism commented 1 month ago

@extremeleadprogram Checking in to see if you're still having issues with POP3?

titanism commented 1 month ago

We are rewriting our locking mechanism to remove Redis and rely solely on SQLite and will update here once complete.

titanism commented 1 month ago

Completed

titanism commented 1 month ago

Re-opening as we are working on an issue with SQLite server main thread blocking issues.

extremeleadprogram commented 1 month ago

image

btonbadger commented 1 month ago

Hi,

Appreciate you're fighting fires with this one, but is there any update please? I'm desperately trying to see if the lack of emails in my forwardmail imap account is down to the sqlite issues and continuing timeouts or something more sinister?

Cheers

BtonBadger

extremeleadprogram commented 1 month ago

@btonbadger - I'm with you and if that is any indication, I think it's this issue mostly if I had to guess.

extremeleadprogram commented 1 month ago

@titanism - any updates... seems worse now than ever... ???

titanism commented 1 month ago

@btonbadger it's the same issue here, we're working on it, hope to have another update soon 🙏

titanism commented 1 month ago

We've fixed a core underlying issue and deployed the fix already to production. Is there any way you can try again? If you still have issues please let us know.

The main thread in all of our workers/processes was getting blocked by an unnecessary VACUUM call on each write to temporary databases, causing huge memory issues (especially if the user's temp database file was large and unopened in a while), which unnecessary polluted memory across the many threads/processes we use for asynchronous & non-blocking operations.

The fix (besides others we've done in the past 48+ hours shown in the commit history of our GitHub repo) is here: https://github.com/forwardemail/forwardemail.net/commit/b631e67f27d6c8ed53b7e0c593f063ae1a206b75#diff-d2d0dec8425326d3b2ae25fccaf4652d340d85088b436f54a0978762127cac5dL1164

cc @btonbadger @extremeleadprogram