ok great, thanks for assisting
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254864#msg-254864
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thursday 06 November 2014 19:17:18 tunist wrote:
> ok, so i opened the log using glogg and have pasted a relevant sequence into
> pastebin here:
> http://pastebin.com/wTQs6ALb
>
> any tips welcome, thanks
>
The problem was fixed:
http://hg.nginx.org/nginx/rev/abb466a57a22
Thank you for the r
On Friday 07 November 2014 08:07:51 tunist wrote:
> i was having a lot of trouble with 302 errors initially and then later on
> was having slow TLS performance.. i had difficulty finding the right
> combination of buffer settings to get the site to run reliably and quickly.
> if i recall correctly
i was having a lot of trouble with 302 errors initially and then later on
was having slow TLS performance.. i had difficulty finding the right
combination of buffer settings to get the site to run reliably and quickly.
if i recall correctly, that was a field that i changed while i was in the
proce
On Thursday 06 November 2014 19:17:18 tunist wrote:
> ok, so i opened the log using glogg and have pasted a relevant sequence into
> pastebin here:
> http://pastebin.com/wTQs6ALb
>
> any tips welcome, thanks
>
[..]
Ok, thanks, I see the problem.
Why have you changed the "large_client_header_buf
enabling debug on the site in question generated vast amounts of log data
and i think either some type of limit was reached or a bug caused the
logging to fail. i was unable to open the logviewer for the site's error log
after the first few minutes and eventually the interface crashed while
attempt
ok, so i opened the log using glogg and have pasted a relevant sequence into
pastebin here:
http://pastebin.com/wTQs6ALb
any tips welcome, thanks
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254651#msg-254651
___
nginx mailing list
oh, so the log file is 3.5GB in size and even though the server has enough
RAM to handle it, the log viewer crashes and gedit gets stuck too.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254648#msg-254648
___
nginx mailing list
nginx
"There's no way to find out what caused the error only by looking to
standard
error message. You should provide the debug log at least."
- ok, thanks - i will post what i can find once the next error occurs. i
upgraded to 1.7.7 and there have been 2 of these errors since then, though
debug was not
On Sunday 02 November 2014 09:03:47 tunist wrote:
> thanks, looks like the same error message is buried in that change / code,
> yes - though i am no closer to discerning the original cause of the error
> being triggered, since i am not familiar with the nginx sourecode at this
> point.
> any tips
ok, i have upgraded.. will see how that goes.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254527#msg-254527
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Then upgrade to 1.7.7
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254526#msg-254526
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
thanks, looks like the same error message is buried in that change / code,
yes - though i am no closer to discerning the original cause of the error
being triggered, since i am not familiar with the nginx sourecode at this
point.
any tips are welcomed!
Posted at Nginx Forum:
http://forum.nginx.o
Maybe this one: http://forum.nginx.org/read.php?29,250118
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254524#msg-254524
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
i am seeing many error log messages relating to SPDY on an HTTPS only
website here. this appears to also be triggering (or at least related to)
database timing problems, which is causing dbase failures.
the error log contains mostly these:
"inflate() failed: -5 while processing SPDY"
anyone know
15 matches
Mail list logo
