Most often, this is due to the receiving end not having the port opened that you chose in your <Output> directive or the service that uses that port is not started.
I would say same as above. Something on receiving end not working out right.
Check that the remote port is listening. telnet to the address and port is a solid first step. Netstat, etc to see if the port is open on the host. tcpdump or wireshark to make sure the traffic is flowing properly.
That should be a solid place to start.
Edit: doh! just realized it was UDP. so ignore the telnet part. :)
Comments (3)
Most often, this is due to the receiving end not having the port opened that you chose in your
<Output>directive or the service that uses that port is not started.Hi, I have same problem in NXLog server 4.1.4046.
Any ideas, please?
I would say same as above. Something on receiving end not working out right.
Check that the remote port is listening.
telnetto the address and port is a solid first step.Netstat, etc to see if the port is open on the host.tcpdumporwiresharkto make sure the traffic is flowing properly.That should be a solid place to start.
Edit: doh! just realized it was UDP. so ignore the telnet part. :)