I have tried increasing this timeout but still get the SIGTERM (kill) signal.
How can I debug this? I have timed the script in the terminal, wit `time sh script.sh` , then modifying the timeouts to be well above this number and tried the cron job without success. Thank you *Jose Rivera* p.s. We're Hiring <https://www.internavenue.com/about/jobs/>! *Data Engineer Lead **Intern Avenue <http://www.internavenue.com/>* Watch Intern Avenue on: BBC Dragons’ Den <http://www.internavenue.com/dragons-den> e: jose.riv...@internavenue.com <janos.fe...@internavenue.com> | www.internavenue.com | Great Interns Online On 18 February 2016 at 17:57, moon soo Lee <m...@apache.org> wrote: > Hi Jose Rivera, > > If your script takes more than the timeout defined here > https://github.com/apache/incubator-zeppelin/blob/master/shell/src/main/java/org/apache/zeppelin/shell/ShellInterpreter.java#L49, > the process will be terminated. > Otherwise, it looks like something send SIGTERM (kill) signal to your > script. > > Or another case? > > Thanks, > moon > > On Wed, Feb 17, 2016 at 10:22 AM Jose Rivera-Rubio < > jose.riv...@internavenue.com> wrote: > >> Hi, >> >> I have a paragraph that runs a shell script to import data from a MySQL >> db to Parquet files using Python and Pyspark (it's legacy import code, >> that's why it's in a shell script instead of the python code directly in >> the paragraph). >> >> The issue is that if I manually run the paragraph it does the import >> correctly, no issues at all. However, if I set a cron job so it runs >> periodically it fails with this cryptic error: >> >> Paragraph received a SIGTERM. >> ExitValue: 143 >> >> Any ideas? >> >> Thanks! >> >> *Jose Rivera* >> p.s. We're Hiring <https://www.internavenue.com/about/jobs/>! >> >> *Data Engineer Lead **Intern Avenue <http://www.internavenue.com/>* >> Watch Intern Avenue on: BBC Dragons’ Den >> <http://www.internavenue.com/dragons-den> >> e: jose.riv...@internavenue.com <janos.fe...@internavenue.com> | >> www.internavenue.com | Great Interns Online >> >
