Yes, that did it. Thanks! Does this have broader implications? On Wed, Mar 25, 2015 at 11:29 PM, Yuvi Panda <[email protected]> wrote:
> On Thu, Mar 26, 2015 at 11:37 AM, Anthony Di Franco <[email protected]> > wrote: > > Not sure if this is a labs-specific issue or just a stumper for me on how > > the infrastructure works, but I'm having trouble after the upgrade of > > tools-login submitting jobs from it to the grid engine in a way that > worked > > pre-upgrade. > > > > I have a python script running from a virtualenv (I had to rebuild the > > virtualenv for the new python version,) which, when run from tools-login > > directly, runs fine, but when submitted via the grid engine, is unable to > > import the SSL module correctly (symptom: httplib2 does not initialize > > properly in a way that indicates SSL module did not load). > > > > I was originally running the virtualenv-installed python executable via > its > > absolute path. I switched to sourcing c-env from the script and running > the > > python so implied in hopes that might give me a better chance of the > right > > environment; no luck. > > > > I have looked at specifying PYTHONPATH and examined sys.path from within > the > > script to confirm it is the same in both cases. > > > > Does anyone have any thoughts on what might be going wrong? Could a > > system-wide SSL module that subtly doesn't work, or is absent, be > > implicated? Differences in what the module itself, if it is the same, is > > doing under the two conditions? > > Have you tried adding '-l release=trusty' to your grid submissions? I > wonder if it is virtualenv-on-precise vs virtualenv-on-trusty issues. > > > -- > Yuvi Panda T > http://yuvi.in/blog >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
