If your Stream script crashes, try the following to resolve the issue:
- If you have access to the worker nodes, try to execute the script from the command line on the worker node. This is a sanity check that the script can be executed. Of course, one would have to provide the script's STDIN.
- Look at the Stream execution logs for possible crash causes. The logs are captured by the SQL-MapReduce logging mechanism. You can view the logs in the AMC.
- To view the row output of the script, you could specify the information to generate in the arguments clause of Stream:
OUTPUTS ('line varchar') - The "catch-all" error exit code is 1. If your Stream query execution results in an exit code of 1, one possibility is that the script is exceeding Stream's default memory limit of 4 GB. To test whether this memory limit is the cause of the error, remove the memory limit by specifying the 'unlimited" option for the MEM_LIMIT_MB argument of Stream.