Re: [Condor-users] Problem with DLLs

["MD Tyka, Biochemistry" <M.Tyka@xxxxxxxxxxxxx>]

Hi,

thanks for all the replies, at least some new things to try :)

just for the record: we managed to get one of the apps (python.exe, 
requiring python24.dll) to work: on some machines msvcr71.dll was needed
on top of the python dll - unfortunately the error message doesn't go
to stderr.

> using a  batch wrapper around their exe. Some crazy users also had some
> success  using Cygwin this way to!
Ah - this is exactly what we're trying to do. we have a ported app that
compiles very well under cygwin. our condor pool does not have cygwin 
installed but we found that supplying cygwin1.dll solves that problem for
about half of our condor pool. The other half crashes the app with the 
symptoms mentioned in the prev. posts. This is what i find so hard to 
understand - the condor installations appear identical across the pool as 
far as we can tell. I will try to look at the env variables to see if 
there's any difference...

cheers,

 Mike



--On 26 April 2006 15:02 +0100 Patrick Townsend 
<patrick.townsend@xxxxxxxxxxxxx> wrote:

> We've had problems with some off-the-shelf apps requiring a fuller user
> profile than Win32 Condor provides - try getting a Condor job to return
> env  variables (set > set.txt) to see an example of the reduced
> environment. We  never solved this one and now discourage our users from
> trying it :-( For  more notes on this matter search this lists archives
> for posts from my  colleague 'SG Wilkinson' - there are six in March and
> April 2005.
>
> We do have compiled Matlab working fine in this manner though. Matlab
> DLLs  are accessed from a RO network share Condor jobs can connect to
> using a  batch wrapper around their exe. Some crazy users also had some
> success  using Cygwin this way to!
>
> 	regards
> 		Patrick.
>
> --On 26 April 2006 14:34 +0100 "Dr Ian C. Smith"
> <i.c.smith@xxxxxxxxxxxxxxx> wrote:
>
> > --On 26 April 2006 12:42 +0100 "Dr Ian C. Smith"
> > <i.c.smith@xxxxxxxxxxxxxxx> wrote:
> >
> >
> > > Incidently I'm seeing exactly this problem when I try to run SRB clients
> > > using Condor. Empty stdout and stderr and the same logfile message as
> > > you. When I run the same .exe's under my own account (which is
> > > non-priviledged) it's fine. Bizarre !
> >
> > I meant that when I run them *interactively* they work. When I change the
> > VM1_USER attribute to run the condor job under my account (with a
> > previously stored cred) they fail as well.
> >
> > -ian.
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > https://lists.cs.wisc.edu/mailman/listinfo/condor-users
>
>
>
>
> -------------------------------------
> Patrick Townsend  -  Computer Support
> Electrical  &  Electronic Engineering
> MVB room 4.27   University of Bristol
> www.bris.ac.uk     Tel: 0117 954 5288
> email: patrick.townsend@xxxxxxxxxxxxx
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users



--------------------------------------------------------------
Michael Tyka, Computational Protein Folding
C.62, Department of Biochemistry,
University of Bristol
http://www.bch.bris.ac.uk/staff/pfdg/mike.htm