Skip to content
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

Timeout when accessing the admin panel because of big logfile #704

Closed
flobeier opened this issue Aug 2, 2016 · 3 comments
Closed

Timeout when accessing the admin panel because of big logfile #704

flobeier opened this issue Aug 2, 2016 · 3 comments

Comments

@flobeier
Copy link

flobeier commented Aug 2, 2016

Steps to reproduce

  1. Create a large logfile (mine was >1MB)
  2. Try to access admin panel

Because the logfile is so big I run into a timeout using nginx and php5-fpm. I think this should be handled differently because in my case #680 still fills the logfile even when the loglevel is set to 4. I can use a cronjob to clear the logfile for the time being but that doesn't help others who might run into the same problem some day.

@nickvergessen
Copy link
Member

Well just make use of the log rotation feature?
https://github.com/nextcloud/server/blob/master/config/config.sample.php#L637-L644

@icewind1991
Copy link
Member

I've had no issues working with multi GB logfiles in the past

@flobeier
Copy link
Author

flobeier commented Aug 3, 2016

@nickvergessen I somehow forgot about that, thanks for pointing me in the right direction. But I'm still wondering how @icewind1991 has no issues with huge logfiles while I run into timeouts with comparably small ones. Any suggestion where I could look for the cause? System is the one described in #680 and I'm using the nextcloud nginx config. Would setting fastcgi_request_buffering to off help? The debian nginx version unfortunately doesn't support it yet.

@icewind1991 it might be something specific to my setup. While loading the admin panel php5-fpm used up all CPU power of the container. However, I'm quite certain that it was the log files fault because after I cleared it the admin panel loaded instantly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants