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

websocket错误日志记录到syslog的问题 #556

Closed
ruitingh opened this issue Dec 19, 2014 · 6 comments
Closed

websocket错误日志记录到syslog的问题 #556

ruitingh opened this issue Dec 19, 2014 · 6 comments

Comments

@ruitingh
Copy link

升级到了tengine 2.1.0,发现
设置websocket日志"error_log" 记录到 syslog;
error_log出现很多如下错误:
[error] 839006#0: *2154531 upstream prematurely closed connection while reading response header from upstream
系统日志出现如下错误:
kernel: nginx[932167]: segfault at 0 ip 000000000044853b sp 00007ffff6102490 error 4 in nginx[400000+2c1000]
kernel: nginx[932168]: segfault at 0 ip 000000000044853b sp 00007ffff6102490 error 4 in nginx[400000+2c1000]
kernel: nginx[932172]: segfault at 0 ip 000000000044853b sp 00007ffff6102490 error 4 in nginx[400000+2c1000]
kernel: __ratelimit: 6 callbacks suppressed

查看了一下nginx官方文档,有点像 1.7.4 更新说明里的:
Bugfix: a segmentation fault might occur if logging of errors to
syslog was used; the bug had appeared in 1.7.1.

@chobits chobits closed this as completed Dec 19, 2014
@chobits chobits reopened this Dec 19, 2014
@chobits
Copy link
Member

chobits commented Dec 19, 2014

可否看一下是哪个函数segfault了:

$ gdb sbin/nginx -ex 'disassemble 0x44853b' -ex 'quit'

@cfsego
Copy link
Member

cfsego commented Dec 19, 2014

希望能贴一下写日志的配置

@cfsego
Copy link
Member

cfsego commented Dec 19, 2014

请确认你的情况是error_log写在http{}内部

@perfmjs
Copy link

perfmjs commented Dec 19, 2014

写在server {}内部可以吗?

@cfsego
Copy link
Member

cfsego commented Dec 19, 2014

如果是这样
请先用这里的patch
#557

@perfmjs
Copy link

perfmjs commented Dec 19, 2014

谢谢这么快回复,我们下周一去试一下你发的patch#557

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

5 participants