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
Scheduler dies with apply2files
#3563
Comments
Note sure if this applies to database connections as well, I currently am watching these kind of issues: scheduler_err.log:
production.log:
|
I'm currently seeing about 5 instances (no matter if SaaS or package installation) per week that are affected by this issue. |
By now it's 10+ instances. |
@MrGeneration Is this issue still present? Or has it decreased/disappeared since Zammad 5.0? |
Yes, just appeared on a current stable 5.0.2! |
Fresh sample:
|
Found this in production.log today on a 4.0:
Might help. |
The issue situation here might get better with the cache changes we did this week. We should verify this on 5.2 release. |
@MrGeneration is this still a thing with recent cache changes and Redis? |
What cache changes? Could you please expect me not to know every little code change in every detail?
Not every system has to use redis so no, ignore Redis in this scenario. |
@mantas > Is this issue handled by you? Just asking, because you're assigned... |
Infos:
Expected behavior:
Scheduler does not die on e.g. high load situations.
Actual behavior:
On specific situations ( I suspect load / I/O) the scheduler dies and does not recover.
scheduler_err.log
corresponding line within
production.log
:Steps to reproduce the behavior:
Yes I'm sure this is a bug and no feature request or a general question.
The text was updated successfully, but these errors were encountered: