-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caddy with cache-handler crashes frequently on virtuozzo/jelastic #62
Comments
Here is a log entry of Caddy crashing with cache-handler enabled. The instance was hovering at about 50% memory usage at the time of the crash and CPU was below 5%
|
Hi |
After monitoring the instance for a couple of days and allocating 4x the memory than previously to have more headroom, I can report that memory usage continuously grows without ever dropping. I would expect memory consumption to reside on a stable level after most of the cacheable items are in cache but not a continuous increase. I assume that the crash is OOM-related even though jelastic doesn't show any evidence, but jelastic stats and charts are notoriously unhelpful. With more resources assigned, the trend is that all resources are being used, which leads me to believe that there is a memory leak. |
Hey @genox, I'm currently debugging that. |
@darkweak thank you. happy to test a new release and provide further feedback. |
@genox can you retry with |
@darkweak Thanks - I built and deployed this version, I will keep an eye on mem consumption for the next few days. |
@darkweak Caddy crashed after about 2 days uptime:
Memory was not starting to bloat yet, though. |
It tries to update headers while request is done, I'm working on a fix for that. |
Hi,
I have an issue with caddy terminating after a while when running on Virtuozzo/Jelastic. It is a bit difficult to debug this issue since logs are not easy to come by. But maybe there are known issues?
Basically, the behaviour is like this: Caddy runs just fine without the cache activated in the Caddyfile. Once cache is activated, I can hammer it with requests and it is stable, however, after a period of about 24 hours Caddy terminates and since virtuozzo doesn't offer a restart policy for its implementation of running custom docker containers, it has to be manually restarted. Unfortunately I am bound to use Jelastic here with this setup.
The Caddyfile is quite simple:
The instance has 2GB of memory assigned and doesn't report any OOM issues. Load is minimal, even when running load-tests. Caddy is caching requests to a NextJS instance that serves certain responses with s-maxage/stale-while-revalidate headers and this works fine, too.
So my first question is, have there been reports of crashes for this environment or nextJS in particular?
I will try to get my hands on a log file to post here.
The text was updated successfully, but these errors were encountered: