question Re: How to handle failure of NiFi ExecuteProcess processor while it doesn't have a failure relationship in Archives of Support Questions (Read Only)

How to handle failure of NiFi ExecuteProcess processor while it doesn't have a failure relationship

MahmoudYusuf — Tue, 29 Aug 2017 21:20:32 GMT

I am trying to execute a job by the use of ExecuteProcess processor to run the shell command that executes this job.

But if the shell command failed, the error messages only appear in the log (at the top right of the processor) but the processor doesn't have a failure relationship. I want to handle the case of failure to do some action or send emails.

Re: How to handle failure of NiFi ExecuteProcess processor while it doesn't have a failure relationship

mburgess — Tue, 29 Aug 2017 21:27:17 GMT

You may be better served with ExecuteStreamCommand rather than ExecuteProcess for this case. You could schedule a GenerateFlowFile at the same rate your ExecuteProcess was scheduled for, and set Ignore STDIN to true in ExecuteStreamCommand. Then the outgoing flow files will have the execution.status attribute set, which you can use with RouteOnAttribute to handle failures (non-zero exit codes, e.g.)

If you must use ExecuteProcess, perhaps you could run your shell command followed by a double-bar and a command that prints something you can check for later, such as:

myCommand || echo "!ERROR!"

I haven't tried this so I don't know if that would work, but if it does it would allow you to use RouteOnContent to check for that error string to indicate failure. The same technique works without the || if you know what to look for in your failed command output.

Re: How to handle failure of NiFi ExecuteProcess processor while it doesn't have a failure relationship

MahmoudYusuf — Sun, 18 Aug 2019 00:08:24 GMT

The first solution works! Thanks @Matt Burgess

Here's the RouteOnAttribute configurations.