> This looks like debug logs are trying to be sent to stdout - which is > failing because stdout is closed (as it should be for a daemonized > application). Something somewhere has flipped debugging information > on, and yet still forked the process off of the terminal. Configuring > the app this way should be impossible - if its something in > configuration... if not, its just a bug where debug is being properly > activated after a fork.
Good catch! I was so preoccupied with the known issue of action error not being properly acted on by the transaction processor, I did not notice the actual data. A full debug log should help to find out what is going on. Thanks! Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
