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

a lot of logs throws 502 in nginx #10

Open
qfox opened this issue Dec 16, 2011 · 5 comments
Open

a lot of logs throws 502 in nginx #10

qfox opened this issue Dec 16, 2011 · 5 comments

Comments

@qfox
Copy link

qfox commented Dec 16, 2011

Error in nginx log:
2011/12/16 11:02:57 [error] 13912#0: *5 upstream sent too big header while reading response header from upstream,...
Client received HTTP/1.0 502 ...

fix:

@@ -602,6 +602,12 @@
*/
protected function _writeToFile($json)
{

  •    static $setCookie;
    
  •    if (!empty($setCookie)) {
    
  •        return $setCookie;
    
  •    }
    
    • // if the log path is not setup then create it
      if (!is_dir($this->getSetting(self::LOG_PATH))) {
      mkdir($this->getSetting(self::LOG_PATH));
    and
  •     return $this->_setCookie($data);
    
  •    return $setCookie = $this->_setCookie($data);
    
@titosemi
Copy link

I've having the same issue

@qfox
Copy link
Author

qfox commented May 23, 2012

Titosemi, probably you need to upgrade chromephp on server and client. Im not sure in it but try to do it.

@qfox
Copy link
Author

qfox commented May 23, 2012

If problem still exist after upgrading - just try to patch chromephp server-side library as I described above.

@apfelbox
Copy link

apfelbox commented Jul 3, 2013

Take a look at this bug report: symfony/symfony#8413

The response headers of php-fpm are too big for nginx to handle in the default config.

@hakre
Copy link

hakre commented Sep 14, 2014

Also compare with #12, an overall option to hard-limit data-size that this logging class should process sounds useful for many things.

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

4 participants