[rsyslog-notify] Forum Thread: Re: omprog retries over a long period - (Mode 'reply')

[noreply at adiscon.com]

User: itgeek 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26625#p26625

Message: 
----------
Thanks dlang and Rainier.

Right now, my omprog app exits on any error.  My understanding is that the
intervalRetryCount and resumeInterval don't apply then (they apply to
suspend).  This is consistent with what I'm seeing in my app's log file.
I'm sending a message every 10 seconds via bash logger, and seeing my app
come up/exit because it can't connect once for each message.  The message
isn't sent and is discarded.  After 1005 messages, rsyslog seems to just
give up and stop trying to load the app when it receives a message.  I have
to restart rsyslog for it to begin trying again.

Are there any settings, I may have missed, that control how rsyslog behaves
wrt starting an omprog app?

I couldn't find info on how to communicate a delivery error that would
require a suspend.

Now that I'm able to completely isolate and reproduce the problem
consistently, I'll grab the debug logs.