Re: WRAPIT cannot find shared object file

Thanks you for the suggestions... It was indeed an environmental path
issue... As I needed to source my fortran environmental variables in the
shell scripts. Were running now!

On Wed, Mar 10, 2010 at 2:22 PM, David Brown <dbrown@ucar.edu> wrote:

> I may be wrong but I think that the cron facility defaults to a very
> limited set of environment variables. You may need to set LD_LIBRARY_PATH
> or other variables to enable the script to find the shared library. You
> could put an 'env' command inside your crontab file to get it to dump out
> its environment and then compare that to your own environment.
> -dave
>
>
> On Mar 10, 2010, at 12:06 PM, Micah Sklut wrote:
>
> I dont believe so Rick. The permissions are set to chmod a+rx for the
> shared object file.
>
>
> On Wed, Mar 10, 2010 at 1:42 PM, Rick Brownrigg <brownrig@ucar.edu> wrote:
>
>> Hi Micah,
>>
>> As just a quick try, is it perhaps a permissions issue for the crontab
>> "user"?
>>
>> Rick
>>
>> On Mar 10, 2010, at 11:39 AM, Micah Sklut wrote:
>>
>> Hi,
>>
>> I am encountering a problem when trying to use WRAPIT.
>>
>> When I run the ncl script from the command line, there is no issues, but
>> when I run the script through crontab, I get the following error:
>>
>> ----------- ncl output --------------------
>> Wed Mar 10 17:13:02 GMT 2010
>> Copyright (C) 1995-2007 - All Rights Reserved
>> University Corporation for Atmospheric Research
>> NCAR Command Language Version 4.3.1
>> The use of this software is governed by a License Agreement.
>> See http://www.ncl.ucar.edu/ for more details.
>> warning:An error occurred loading the external file
>> /home/barells/swellinfo/ncl/gfs_atmp.so, fi
>> le not loaded
>> libsvml.so: cannot open shared object file: No such file or directory
>> warning:error at line 5 in file write_gfs_atmp.ncl
>>
>> fatal:syntax error: line 30 in file write_gfs_atmp.ncl before or near :
>> WRITE:
>> -----^
>>
>> fatal:error in statement
>> fatal:Syntax Error in block, block not executed
>> fatal:error at line 33 in file write_gfs_atmp.ncl
>>
>> ----------- ncl output end -----------
>>
>> So, there appears to be some environmental variable paths that are off,
>> during the crontab, but I haven't figured out what is wrong. This is
>> especially confusing, since I use an absolute path to the shared object
>> file.
>>
>> Any thoughts on this?
>> Thank you,
>>
>>
>> --
>> Micah Sklut
>> _______________________________________________
>> ncl-talk mailing list
>> List instructions, subscriber options, unsubscribe:
>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>
>>
>>
>
>
> --
> Micah Sklut
> Swellinfo.com
> "The Ultimate Surf Forecasting Site"
> 302.588.6241
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
>

-- 
Micah Sklut
Swellinfo.com
"The Ultimate Surf Forecasting Site"
302.588.6241

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Wed Mar 10 16:25:20 2010