-
Notifications
You must be signed in to change notification settings - Fork 81
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
Does anyone suffers from server restarts when larger amount of logs is pushed into Console? #124
Comments
Hi, Yes, I've experienced with this same problem too, or something like that. I have a load process that calls external API and runs for a long period, and eventually logs warns with Hangfire.Console (v1.4.2). After like a hour of operation (~40 - 50 lines in console), the worker restart in another thread, and aparently the old thread was running out of dashboard control, cause I began to detect duplicate API requests to the resources, forcing me to restart job. When I disabled the logs to console, justing commenting all lines that calls WriteLine() on injected PerformContext instance, this problem just disappeared. @krzysiek-b you found some solution to your problem? Thanks. |
Hi @lucasorth I found the same thing. To many logs caused restarts. My solution was to limit the logs in the console but keep them all elsewhere. |
I'm experiencing the same, I had to disable the console for now... |
I noticed a new version of this library came out, maybe @pieceofsummer can have a look at this issue? |
I didn't found the root cause yet, but apparently we are wrong about the log size or number of lines in console. |
Hi,
recently I found that pushing larger amount of logs (>1MB) into console within 30-40 sec forces Hangfire server to restart. Did anyone observed similar issue?
IIS memory limits are disabled
The text was updated successfully, but these errors were encountered: