Hi Botond,
Ok I enabled the keep alive config on the http server. Even though all the
messages are received by the httpd, the nxlog client side logs lot of following
message.
INFO reconnecting in 0 seconds
ERROR disconnected
INFO connecting to x.x.x.x:8000
ERROR unhandled event! (reqevents:
Hello,
I'm investigating this issue. I'm on linux (Centos 5.9). Some times
nxlog won't stop to send logs.
But in my environment next bash snip always let nxlog instance without
sending logs:
At firewall:
for f in 1 2 3
do
echo "$(date) Rejecting ..";
/sbin/iptables -I FORWARD -p udp -s IPORIG -
Hi,
The om_http module sends an HTTP 1.1 POST request in keep-alive mode.
I recommend looking at the network traffic with wireshark/tcpdump to see
what's going on.
Regards,
Botond
On Mon, 3 Mar 2014 13:36:35 +0200
Shedis wrote:
> Yes, I'm running on windows. Can you tell what http protocol ver
Hi,
I couldn't reproduce this, at least not on Linux.
If the listening process is restarted it will resume forwarding and the
errors are only logged during the time when nothing is accepting the udp
packets.
Are you on windows? Die anyone else encounter this issue?
Regards,
Botond
On Tue, 4 Ma
Hello,
I would like to know if the next behaviour it is intentional, or if it
is configurable.
I have a nxlog server which forward logs to a logstash server. nxlog
will use GELF protocol.
If gelf slave service from logstash stop to work. nxlog will have to
be restarted to get it working again.
