depending on how active your logging is, you could watch the logs and say
that if you don't receive any logs for 1 min (or whatever time is
approprate), somthing is wrong.
you could also generate known UDP logs to yourself and alert if they don't
show up.
David Lang
On Mon, 23 May 2011, Christian Lete wrote:
Hi,
I have a small question, I would need to setup an rsyslog
receiver/forwarder, listening on udp port, since some clients, only
support this option. I would need this service to be highly
available(I don't want to have two machines and having duplicated
information), but since this udp, I can't be for sure if the service
is running fine. What I thought is to indirectly check it, by having
another port listening on tcp and checking the tcp service, if the
service is not running on tcp I would assume the whole system is down
and would failover to the other instance of the cluster, that's the
only way I could think of, do you currently have another way?
thank you very much,
Regards,
Christian
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
