• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1448
  • Last Modified:

How to set up environment for Python in cron?

I have a Python script that runs fine standalone. When I add it to the cron on a Solaris, it fails. From the output log, the problem is it cannot find the PATH and LID_LIBRARY_PATH of the executable embedded in the Python. My question is how to set this up? Should this be done in the Python or in the cron? I have tried various ways without success. Here are two examples:

02 * * * * /home/<user>/test.py input1 > /tmp/test.log 2>&1
02 * * * * SHELL=/usr/bin/bash; export SHELL; . $HOME/.profile_user; /home/<user>/test.py input1 > /tmp/test.log 2>&1

Basically the Python runs with one input parameter. In the Python script, it calls a 3rd party executable. I see two env variable scripts I need to run - one is the .profile_user and another one is the app specific env.

Many thanks!
0
eduliu
Asked:
eduliu
  • 3
  • 2
1 Solution
 
woolmilkporcCommented:
Simplest way would be running the script from root's crontab as the "normal" user with "su -", so that the full environment of that user will be initialized.

02 * * * * su - normal_user -c "/home/<user>/test.py input1 > /tmp/test.log 2>&1"

wmp
0
 
eduliuAuthor Commented:
I just tried, but it didn't work - it didn't run. I guess it's becuase I'm not running cron as root. The account I use can create cron but under my account I assume. Any other way to insert a couple of scripts to set up the environment? Thanks!
0
 
gelonidaCommented:
if you want to call 3rd party executables, then it is enough to set the PATH variable from within python before you call your executable.


Alternatively you can create a wrapper shell script setting up the env before calling your python script.

import os
os.environ['PATH'] = 'newpath:' + os.environ['PATH']
os.environ['LD_LIBRARY_PATH'] = 'newpath:' + os.environ['LD_LIBRARY_PATH']
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
gelonidaCommented:
the wrapper script solution would be:

#!/bin/sh
export PATH="newpath:$PATH"
export LD_LIBRARY_PATH="newpath:$LD_LIBRARY_PATH"

mypythonscript "$@"


0
 
gelonidaCommented:
Third way is to set the vars directly in the crontab entry:


PATH=/usr/bin:mypath LD_LIBRARY_PATH=/usr/bin:mypath  /home/<user>/test.py input1


Please note.
no semicolons and no export statementments.

In all three cases you must be sure to add ALL required directories and all required environment variables, that are needed
for your third party executable to be run.
As I don't knowit you might have to experiment
0
 
eduliuAuthor Commented:
Thank you so much for the detailed and various options. Quite embarrassing, the cause was one variable in one of the env scripts had a value assigned wrong. Things are working now. Appreciate the help!
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now