om_http unexpected data from server causes nxlog service to crash

#1 bourazaniss 7 years ago

I have the usual error "Unexpected data from server ..." using om_http to send Windows event logs through Nginx to Redis.

The problem is that when randomly this error happens ( once every 5 days) the service unexpectently stops !

From the source code I can understand that NXLog receives a response which cannot map to a correnponding request.

It has a response with an appropriate length but the corresponding request is null! Possibly is a bad logic implementation, or even a network problem that could cause request/response mismatch.I really don't know.

But I also really can't understand why NxLog preferres to die instead of just return from the function in case this happens and not execute the code following the condition that drives the service to crash at the end.

Stelios

Permalink

#2 adm Nxlog ✓ 7 years ago

#1 bourazaniss

I have the usual error "Unexpected data from server ..." using om_http to send Windows event logs through Nginx to Redis. The problem is that when randomly this error happens ( once every 5 days) the service unexpectently stops ! From the source code I can understand that NXLog receives a response which cannot map to a correnponding request. It has a response with an appropriate length but the corresponding request is null! Possibly is a bad logic implementation, or even a network problem that could cause request/response mismatch.I really don't know. But I also really can't understand why NxLog preferres to die instead of just return from the function in case this happens and not execute the code following the condition that drives the service to crash at the end. Stelios

It's possible that this has been fixed in the EE already. I suggest testing the NXLog EE trial.

Once this is confirmed the fix will be merged into the CE and will be availble in the next release.