-
Notifications
You must be signed in to change notification settings - Fork 74
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
Core dump when I use this module #29
Comments
We switched off of this in favor of jdomain for this same reason. It would core dump and then ips would go stale as DNS resolution was no longer being updated. |
By |
Yes, that is the one. |
i think i have solve this problem. |
When I try to use this module, it core dump.(nginx version 1.13.11)
hope to receive a reply.
Configure as follows:
http {
resolver 127.0.0.1:53;
upstream tcp_test {
server appa.service.consul:3307 resolve;
}
server {
listen 8888;
#proxy_pass tcp_test;
location / {
proxy_pass http://tcp_test;
}
}
}
Error log as follows:
2018/04/19 17:06:23 [debug] 6880#0: epoll add event: fd:6 op:1 ev:00002001
2018/04/19 17:06:23 [debug] 6880#0: upstream-dynamic-servers: Initial DNS refresh of 'appa.service.consul' in 64ms
2018/04/19 17:06:23 [debug] 6880#0: event timer add: 40429384: 64:3948716
2018/04/19 17:06:23 [notice] 20172#0: signal 17 (SIGCHLD) received from 6880
2018/04/19 17:06:23 [alert] 20172#0: worker process 6880 exited on signal 11 (core dumped)
The text was updated successfully, but these errors were encountered: