FastCGI timeout (Not docker related) #1119
Comments
|
Somewhere on the internet, adding the following lines to the nginx.conf was suggested as a solution to a similar problem: I tried that, but it did not solve anything. It seems, however, to prolong the waiting for the "PHP Fatal error". |
|
@indridieinarsson Thank you for your report. FYI, we did a major change to Cypht Docker: In summary, https://hub.docker.com/u/cypht replaced https://hub.docker.com/r/sailfrog/cypht-docker Details: cypht-org/cypht-docker#31 In doing so, many things changed. For example: @jonocodes @Yannick243 @Shadow243 any ideas? |
|
@marclaporte thanks for the tip. The upgrade, at which this issue started, was when upgrading from the already new setup, compiled from master 2-3 weeks ago, and to master from a couple of days ago, so it was already working with the new docker setup. |
|
So, the timeout seems to be happening in I tried reverting to the commit before that (commit 1a62fb4), and now the issue seems to be gone (running using the exact same config as before, just pulled, re-built the docker image and started). So the primary cause is probably not in docker or nginx. |
|
@josaphatim Can you take a look? That commit is from #1107 @indridieinarsson Thank you for this investigation. It is very helpful. Thanks! |
marclaporte
changed the title
|
Well done @indridieinarsson ! So then, we need @kambereBr instead of @josaphatim to review #1051 |
|
Sorry I forgot to give my feedback yesterday. There are 3 commits that affected the file mentioned in the previous comment. I suspected only one c08cac8 as my commit didn't changed anything and Victor's commit came after @indridieinarsson addressed this issue. But I wasn't able to reproduce @indridieinarsson issue as on my side everything is working as expected. |
|
@josaphatim : I'm not really familiar with php, so not really useful for any coding. But perhaps it would be possible to add some debug-logging statements around where this is happening (log says "imap/hm-imap-base.php on line 80"), just to find out more. I have 3 different accounts, and most of my mails contain some "funny symbols", as my native language (Icelandic) has some special symbols - perhaps that's relevant, since this seems to be about multibyte strings. |
@indridieinarsson Please pop by our chat room at https://gitter.im/cypht-org/community and find @kambereBr or @josaphatim to organize a screenshare. |
|
We can't reproduce issue. Can you please try https://github.com/cypht-org/cypht/releases/tag/v2.2.0 ? |
I'll do that. And sorry for ghosting your previous reply, was on vacation and not reading messages. |
|
@marclaporte : this issue is still present on tag v2.2.0 And I still get stuff like below in the log, and the cypht web page becomes unresponsive. When I think about it, it might be relevant, that I'm running this in a docker container, behind a traefik reverse proxy... |
|
I've been poking around a bit. A bit difficult to pinpoint. Going from tag 2.2.0, I replaced hm-imap-base.php with the version from commit 1a62fb4. In that constellation, the timeout is not reproducible. |
|
digging more, this part in read_literal from hm-imap-base.php is interesting (with some additional logging statement from me).
Every now and then, On the other hand,
which is just a substring, and should be the same regards of mb or not. Anyone around wise enough to know what number it is that being drawn out as substring. Is it number of characters, or number of bytes? |
|
Thank you @indridieinarsson for your persistence on this. |
|
@indridieinarsson expects this to be solved by #1230 (comment) So closing, and we'll reopen if the issue persists. |
🐛 Bugreport
I am running cypht using docker compose. Building the docker image from source locally.
Previous version ran without the issue described here (master branch ca. month ago). After updating to the most recent master branch, the issue began.
Cypht comes up as regular, and is usable (there are some issues regarding the Everything folder not displaying all accounts, but that was unchanged between versions).
After some usage, usually just a few minutes, cypth becomes unreachable, with the browser displaying just: "504 Gateway Time-out
nginx/1.26.1". Sometimes, browser says "404 page not found".
In the docker logs, I get the following:
After the "PHP Fatal error" is displayed, cypht becomes reachable again.
Once I'm in again, I notice, that the email I was reading once it became unresponsive (mail from a gmail account) is still marked as unread in the mail listing. Otherwise, marking unread mails as read once I have opened them works as expected.
Version & Environment
git commit : 5e88e14
OS : docker image, running on x64 host which is running debian.
The text was updated successfully, but these errors were encountered: