[GRASS-user] gislock: Permission denied

Hello,

since last week I get this error, if I want to start grass61.

as user baliola:

grass61
Cleaning up temporary files.....
ERROR: LOCATION_NAME not set
Starting GRASS ...
///.gislock: Permission denied
ERROR: /usr/local/grass-6.1.cvs/etc/lock:
baliola is currently running GRASS in selected mapset. Concurrent use not
allowed.

grass61 /data1/grassdb/spearfish57/PERMANENT
Cleaning up temporary files.....
Starting GRASS ...
ERROR: LOCATION_NAME not set
///.gislock: Permission denied
ERROR: /usr/local/grass-6.1.cvs/etc/lock:
baliola is currently running GRASS in selected mapset. Concurrent use not
allowed.

I searched the GRASS ML and found a few mails with hints but applied them
without success:

- Search for .gislock and deleted them
- remove /usr/local/grass... and reinstalled with fresh cvs
- applied chmod on grassdb

I definitely have no .gislock file on my system anymore, but nevertheless I
receive this promt.

as root I get:

grass61

login UI with locations only - no mapset are displayed - I can create a new
mapset, login and work successfully. However trying to access other mapsets
results in this error:

grass61 /data1/grassdb/spearfish57/PERMANENT
GRASS 6.1.cvs (spearfish57):/home/baliola > Error in startup script: ERROR:

MAPSET PERMANENT - permission denied
    while executing
"close $input"
    (procedure "MapCanvas::zoom_gregion" line 7)
    invoked from within
"MapCanvas::zoom_gregion $mon"
    (procedure "MapCanvas::create" line 39)
    invoked from within
"MapCanvas::create"
    (procedure "Gm::startmon" line 11)
    invoked from within
"Gm::startmon"
    (procedure "Gm::create" line 71)
    invoked from within
"Gm::create"
    (procedure "main" line 29)
    invoked from within
"main $argc $argv"
    (file "/usr/local/grass-6.1.cvs/etc/gm/gm.tcl" line 518)

sorry, if I missed any relevant mails - thanks in advance for any hint.

cheers Martin

On Tue, Jun 13, 2006 at 05:14:28PM +0200, Martin Wegmann wrote:

Hello,

since last week I get this error, if I want to start grass61.

as user baliola:

>grass61
>Cleaning up temporary files.....
>ERROR: LOCATION_NAME not set
>Starting GRASS ...
>///.gislock: Permission denied
>ERROR: /usr/local/grass-6.1.cvs/etc/lock:
>baliola is currently running GRASS in selected mapset. Concurrent use not
>allowed.

>grass61 /data1/grassdb/spearfish57/PERMANENT
>Cleaning up temporary files.....
>Starting GRASS ...
>ERROR: LOCATION_NAME not set
>///.gislock: Permission denied
>ERROR: /usr/local/grass-6.1.cvs/etc/lock:
>baliola is currently running GRASS in selected mapset. Concurrent use not
>allowed.

I searched the GRASS ML and found a few mails with hints but applied them
without success:

- Search for .gislock and deleted them
- remove /usr/local/grass... and reinstalled with fresh cvs
- applied chmod on grassdb

I definitely have no .gislock file on my system anymore, but nevertheless I
receive this promt.

I had recently the same problem and discovered that a .gislock file
is also written in LOCATION/MAPSET/.

If you look there, they may be a leftover file:

ls -la /data1/grassdb/spearfish57/PERMANENT/.gislock

Markus

On Tuesday 13 June 2006 17:43, Markus Neteler wrote:

On Tue, Jun 13, 2006 at 05:14:28PM +0200, Martin Wegmann wrote:

[...]

>
> I definitely have no .gislock file on my system anymore, but nevertheless
> I receive this promt.

I had recently the same problem and discovered that a .gislock file
is also written in LOCATION/MAPSET/.

If you look there, they may be a leftover file:

ls -la /data1/grassdb/spearfish57/PERMANENT/.gislock

/data1/grassdb/spearfish57/PERMANENT$ ls -la
total 128
drwxrwxrwx 22 baliola grass 4096 Jun 13 16:50 .
drwxrwxrwx 7 baliola grass 4096 Jun 8 14:15 ..
-rwxrwxrwx 1 baliola grass 520 Jun 13 16:50 .bash_history
-rwxrwxrwx 1 root root 663 Jun 13 16:48 .bashrc
drwxrwxrwx 4 baliola grass 4096 Apr 25 17:37 .tmp
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 COMBINE
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 Census
-rwxrwxrwx 1 baliola grass 169 Nov 5 2001 DEFAULT_WIND
-rwxrwxrwx 1 baliola grass 803 May 25 2004 HISTORY
drwxrwxrwx 4 baliola grass 4096 Mar 29 1998 Informix
-rwxrwxrwx 1 baliola grass 14 Mar 29 1998 MYNAME
-rwxrwxrwx 1 baliola grass 130 Jun 4 2003 PROJ_INFO
-rwxrwxrwx 1 baliola grass 38 Apr 24 2001 PROJ_UNITS
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 TIGER
-rwxrwxrwx 1 baliola grass 296 Feb 11 2003 TODO
-rwxrwxrwx 1 baliola grass 132 May 25 2004 VAR
-rwxrwxrwx 1 baliola grass 287 Jul 11 2005 WIND
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 bdlg
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cats
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cell
drwxrwxrwx 37 baliola grass 4096 Jul 11 2005 cell_misc
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cellhd
drwxrwxrwx 2 baliola grass 4096 Mar 3 2004 colr
drwxrwxrwx 3 baliola grass 4096 Mar 29 1998 colr2
drwxrwxrwx 2 baliola grass 4096 May 25 2004 dbf
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 dlg
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 fcell
drwxrwxrwx 2 baliola grass 4096 Nov 15 2001 g3dcell
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 hist
drwxrwxrwx 3 baliola grass 4096 Mar 29 1998 paint
drwxrwxrwx 42 baliola grass 4096 Jul 11 2005 vector
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 windows

thanks for this hint, but doing updatedb and search for '.gislock' gives no
results either - theoretically in nearly every loc/mapset must be a .gislock
because I cannot login to any loc/mapset as user.

Martin

I redid it with the new spearfish6 dataset:

grass61 /data1/grassdb/spearfish60/PERMANENT/
Cleaning up temporary files.....
ERROR: LOCATION_NAME not set
Starting GRASS ...
///.gislock: Permission denied
ERROR: /usr/local/grass-6.1.cvs/etc/lock:
baliola is currently running GRASS in selected mapset. Concurrent use not
allowed.

what astonished me is that installing fresh GRASS cvs and an untouched
location/mapset still results in that error message.

I updated my db 'updatedb' and did locate *gislock but still no entry.

Does GRASS create a hidden settings/history file somewhere which feeds the old
information to a newly installed version?

Martin

baliola@wpf063:/data1/grassdb/spearfish60/PERMANENT$ ls -la
total 116
drwxr-xr-x 21 baliola baliola 4096 Mar 15 18:22 .
drwxr-xr-x 4 baliola baliola 4096 Mar 3 2004 ..
drwxr-xr-x 2 baliola baliola 4096 Mar 29 1998 COMBINE
drwxr-xr-x 2 baliola baliola 4096 Mar 29 1998 Census
-rw-r--r-- 1 baliola baliola 287 Apr 11 2005 DEFAULT_WIND
-rw-r--r-- 1 baliola baliola 1646 Mar 15 18:22 HISTORY
drwxr-xr-x 4 baliola baliola 4096 Mar 29 1998 Informix
-rw-r--r-- 1 baliola baliola 14 Mar 29 1998 MYNAME
-rw-r--r-- 1 baliola baliola 130 Jun 4 2003 PROJ_INFO
-rw-r--r-- 1 baliola baliola 38 Apr 24 2001 PROJ_UNITS
drwxr-xr-x 2 baliola baliola 4096 Mar 29 1998 TIGER
-rw-r--r-- 1 baliola baliola 286 Jan 17 17:57 TODO
-rw-r--r-- 1 baliola baliola 66 Apr 11 2005 VAR
-rw-r--r-- 1 baliola baliola 291 Mar 15 17:56 WIND
drwxr-xr-x 2 baliola baliola 4096 Mar 29 1998 bdlg
drwxr-xr-x 2 baliola baliola 4096 Mar 2 2004 cats
drwxr-xr-x 2 baliola baliola 4096 Mar 3 2004 cell
drwxr-xr-x 37 baliola baliola 4096 Mar 2 2004 cell_misc
drwxr-xr-x 2 baliola baliola 4096 Mar 2 2004 cellhd
drwxr-xr-x 2 baliola baliola 4096 Mar 3 2004 colr
drwxr-xr-x 3 baliola baliola 4096 Mar 29 1998 colr2
drwxr-xr-x 2 baliola baliola 4096 Mar 15 18:19 dbf
drwxr-xr-x 2 baliola baliola 4096 Mar 29 1998 dlg
drwxr-xr-x 2 baliola baliola 4096 Mar 3 2004 fcell
drwxr-xr-x 2 baliola baliola 4096 Nov 15 2001 g3dcell
drwxr-xr-x 2 baliola baliola 4096 Mar 3 2004 hist
drwxr-xr-x 3 baliola baliola 4096 Mar 29 1998 paint
drwxr-xr-x 47 baliola baliola 4096 Mar 15 18:19 vector
drwxr-xr-x 2 baliola baliola 4096 Jan 17 17:54 windows

On Tuesday 13 June 2006 18:01, Martin Wegmann wrote:

On Tuesday 13 June 2006 17:43, Markus Neteler wrote:
> On Tue, Jun 13, 2006 at 05:14:28PM +0200, Martin Wegmann wrote:

[...]

> > I definitely have no .gislock file on my system anymore, but
> > nevertheless I receive this promt.
>
> I had recently the same problem and discovered that a .gislock file
> is also written in LOCATION/MAPSET/.
>
> If you look there, they may be a leftover file:
>
> ls -la /data1/grassdb/spearfish57/PERMANENT/.gislock

/data1/grassdb/spearfish57/PERMANENT$ ls -la
total 128
drwxrwxrwx 22 baliola grass 4096 Jun 13 16:50 .
drwxrwxrwx 7 baliola grass 4096 Jun 8 14:15 ..
-rwxrwxrwx 1 baliola grass 520 Jun 13 16:50 .bash_history
-rwxrwxrwx 1 root root 663 Jun 13 16:48 .bashrc
drwxrwxrwx 4 baliola grass 4096 Apr 25 17:37 .tmp
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 COMBINE
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 Census
-rwxrwxrwx 1 baliola grass 169 Nov 5 2001 DEFAULT_WIND
-rwxrwxrwx 1 baliola grass 803 May 25 2004 HISTORY
drwxrwxrwx 4 baliola grass 4096 Mar 29 1998 Informix
-rwxrwxrwx 1 baliola grass 14 Mar 29 1998 MYNAME
-rwxrwxrwx 1 baliola grass 130 Jun 4 2003 PROJ_INFO
-rwxrwxrwx 1 baliola grass 38 Apr 24 2001 PROJ_UNITS
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 TIGER
-rwxrwxrwx 1 baliola grass 296 Feb 11 2003 TODO
-rwxrwxrwx 1 baliola grass 132 May 25 2004 VAR
-rwxrwxrwx 1 baliola grass 287 Jul 11 2005 WIND
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 bdlg
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cats
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cell
drwxrwxrwx 37 baliola grass 4096 Jul 11 2005 cell_misc
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 cellhd
drwxrwxrwx 2 baliola grass 4096 Mar 3 2004 colr
drwxrwxrwx 3 baliola grass 4096 Mar 29 1998 colr2
drwxrwxrwx 2 baliola grass 4096 May 25 2004 dbf
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 dlg
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 fcell
drwxrwxrwx 2 baliola grass 4096 Nov 15 2001 g3dcell
drwxrwxrwx 2 baliola grass 4096 Jul 11 2005 hist
drwxrwxrwx 3 baliola grass 4096 Mar 29 1998 paint
drwxrwxrwx 42 baliola grass 4096 Jul 11 2005 vector
drwxrwxrwx 2 baliola grass 4096 Mar 29 1998 windows

thanks for this hint, but doing updatedb and search for '.gislock' gives no
results either - theoretically in nearly every loc/mapset must be a
.gislock because I cannot login to any loc/mapset as user.

Martin

_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser

Martin Wegmann <wegmann@biozentrum.uni-wuerzburg.de> wrote:

>grass61 /data1/grassdb/spearfish60/PERMANENT/
>Cleaning up temporary files.....
>ERROR: LOCATION_NAME not set
>Starting GRASS ...
>///.gislock: Permission denied

///

looks like missing enviro vars,

$GISDBASE/$LOCATION_NAME/$MAPSET/.gislock

if all three are unset that will condense to

///.gislock

Thus it is trying to write to
/.gislock

but you are not root, so you can't write there. (do not try as root)

Find out why "ERROR: LOCATION_NAME not set".

e.g. try moving away ~/.grassrc6

Hamish

Martin Wegmann wrote:

since last week I get this error, if I want to start grass61.

as user baliola:

>grass61
>Cleaning up temporary files.....
>ERROR: LOCATION_NAME not set

This is the root of the problem.

Try deleting the ~/.grassrc6 file first.

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

thanks, deleting ~/.grassrc6 solved the problem.

Martin

On Wednesday 14 June 2006 10:49, Glynn Clements wrote:

Martin Wegmann wrote:
> since last week I get this error, if I want to start grass61.
>
> as user baliola:
> >grass61
> >Cleaning up temporary files.....
> >ERROR: LOCATION_NAME not set

This is the root of the problem.

Try deleting the ~/.grassrc6 file first.