[GRASS-user] GRASS on cluster

GRASS GRASS user
1

Dear all,

The following happens when trying to create a new location on GRASS running on a cluster.

1. I access to the server and when I try to create a location with lat long, GRASS never asks me about the datum and ellipsoid as it normally does in my station GRASS.

2. After creating the location it says "But the PROJECTION information files were not created! You must run g.setproj successfully before projection software will work".

3. When I press crtl-C to exit the location creation menu, it says that I exited abnormally. Howeverm this is exactly what I do successfully in my station version.

4. I never have the chance to run g.setproj because when I try to access my location, GRASS does not launch and returns an error: "Error setting region (Problem with g.region?): child process exited abnormally)"

5. A way of dealing with this is to start GRASS directly on a dummy location, like spearfish60. Then changing the location with g.proj -c. The problem is that, again, GRASS replies:

GRASS 6.3.0 > g.proj -c epsg=4326 location=LatLong
g.proj: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory

6. At this point I have no clue. Thanks for your help!
Jose Miguel

2

Hi Jose Miguel,

two alternatives:

normally, you won't be the superuser (root) of the system. Then, you should set the LD_LIBRARY_PATH variable in your user environment including the lib directory of GRASS. For example, if you use bash, just edit .bashrc in your home dir and add:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<grass_install _dir>/lib

where <grass_install_dir> is where you have installed GRASS. Then save it and do: source .bashrc

The another approach requires root privileges. Just add <grass_install _dir>/lib to the file /etc/ld.so.conf (in Mandriva; in other distributions should be something similar), save it, and run "ldconfig".

Hope this works,

Jose Miguel Martins Delgado escribió:

Dear all,

The following happens when trying to create a new location on GRASS running on a cluster.

1. I access to the server and when I try to create a location with lat long, GRASS never asks me about the datum and ellipsoid as it normally does in my station GRASS.

2. After creating the location it says "But the PROJECTION information files were not created! You must run g.setproj successfully before projection software will work".

3. When I press crtl-C to exit the location creation menu, it says that I exited abnormally. Howeverm this is exactly what I do successfully in my station version.

4. I never have the chance to run g.setproj because when I try to access my location, GRASS does not launch and returns an error: "Error setting region (Problem with g.region?): child process exited abnormally)"

5. A way of dealing with this is to start GRASS directly on a dummy location, like spearfish60. Then changing the location with g.proj -c. The problem is that, again, GRASS replies:

GRASS 6.3.0 > g.proj -c epsg=4326 location=LatLong
g.proj: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory

6. At this point I have no clue. Thanks for your help!
Jose Miguel
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

--
José A. Ruiz-Arias
Solar Radiation and Atmosphere Modelling Group
http://www.ujaen.es/investiga/tep220
Physics Department, University of Jaén
Campus Lagunillas, Building A3 066
23071 Jaén Spain
Tlf: +34 953 212 474
Fax: +34 953 212 838

3

Jose Miguel Martins Delgado wrote:

5. A way of dealing with this is to start GRASS directly on a dummy
location, like spearfish60. Then changing the location with g.proj -c.
The problem is that, again, GRASS replies:

GRASS 6.3.0 > g.proj -c epsg=4326 location=LatLong
g.proj: error while loading shared libraries: libproj.so.0: cannot open
shared object file: No such file or directory

This is probably the reason why the normal location creation process
isn't working either.

The interactive startup involves invoking various helper programs,
e.g. g.setproj to set ellipsoid, datum, etc. If the proj library
cannot be found, g.setproj won't work (nor will several other
important programs, e.g. g.region).

If the proj library isn't installed on the cluster, GRASS isn't going
to work. If it's installed, but it's the wrong version, you may need
to re-compile GRASS (or it may suffice to create a symlink with the
correct name). If the problem is just that GRASS can't find it,
setting LD_LIBRARY_PATH may help.

--
Glynn Clements <glynn@gclements.plus.com>