12:17 <isene> debug help; I have a ruby script running another (python) script in backticks (to capture the output of that other script. This works just fine when running my ruby script from the terminal - but it fails when I set cron up to run the ruby script every minute. It specifically hangs on running that python script in backticks. I've searched high and low and checked permissions, etc... But I am missing

12:17 <isene> something - some difference between running the script manually and as a cron job. Any ideas?

12:19 <isene> FYI; My ruby script is logging into various Gmail accounts, fetching mails to my local imap. The python script (oauth2.py) is used to get a fresh token for oauth login to Gmail.

12:27 <mange> How are you running the cron job?

12:31 <isene> 'crontab -e' with content; * * * * * /home/geir/bin/gmail_fetch >/dev/null 2>&1

12:32 <isene> mange: Thanks for chiming in

12:33 <konsolebox> isene: Maybe gmail_fetch requires credentials? You run as root in crontab though? AFAIK

12:34 <konsolebox> isene: It hangs maybe because it's asking for input when it can't.

12:35 <isene> there isn't any input in running that python script; The line goes like this and only gives a token as output: token = `oauth2.py --generate_oauth2_token --client_id=#{clientid} --client_secret=#{clsecret} --refresh_token=#{rehreshtk}`

12:35 <isene> I set gmail_fetch to 777 to test that permissions wasn't the issue :/

12:37 <konsolebox> Just to be clear I wasn't talking about UNIX permissions when I said "credentials" but gmail's.

12:38 <isene> konsolebox: No, the python script handles all credentials

12:39 <konsolebox> isene: No local cache stored in a user file is accessed?

12:41 <isene> konsolebox: Nope

12:41 <isene> But thanks for asking

12:42 <konsolebox> isene: Try sending stdout and stderr to a file just to see if there are error messages being produed.

12:44 <isene> I found it! Changing oauth2.py to python3 /home/geir/bin/oauth2.py did the trick :-D

12:57 <mange> I was going to suggest that cron doesn't run your shell init stuff, so you should try your script in "env -i" or similar to see what might be going wrong. I'm glad you found the issue! :)

13:11 <isene> mange: And thanks for playing ball :)