Closed bbates100 closed 8 years ago
Hi,
Socket logging uses the lua-resty-socket-logger library to ship out log data. By default, the TCP connections used are kept in a keepalive pool with infinite timeout; if I had to make a blind guess, it sounds like the receiving end is closing the connection without letting the sender know? Sounds like you may want to open up an issue with the upstream library though. A few things of note:
lib/resty/waf/log.lua
for how we implement lua-resty-logger-socket, it's pretty simple.Like I said, probably best to open a bug with the upstream lib maintainers, with as many details as possible. I'll leave this issue open for a while for reference.
You were right. Thanks for the tip. It has something to do with the receiving end not responding accordingly. Closing this ticket.
Great, glad to hear there was a solution for you.
Mind sharing any details? It might make future searches for similar issues more useful.
Hi,
Been trying to send logs to my remote server via this option waf:set_option("event_log_target", "socket") . However, sometimes I get this error message of: SSL_Write() failed (SSL:) (32: Broken pipe), context: ngx.timer, client: xxx.xxx.xxx.xxx, server: 0.0.0.0:443
Any advice, in where should I start looking? Thanks