freebsd stable - Dec 2005 - nfs locking (was: Re: OOO 2.0 compiles but doesn't work properly)

On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff <roberthuff@rcn.com> wrote
about OOO 2.0 compiles but doesn't work properly:

RH> >  The home directory is coming from a nfs-server, so the user-setup
RH> >  should be identical. I already tried to delete .openoffice.org2,
RH> >  but that didn't help either. Any further hints?

RH> 	Yes - check the archives.  There was at least one other person
RH> reporting problems with OpenOffice+NFS.

Yes, I see... the problem seems so be that you have to run lockd and statd
to get ooo running on nfs. The machine where everything's working fine is
running 5.4 with statd and lockd. The machine with the problems is running
6.0 and didn't have statd and lockd activated.
However, activating them (and rebooting) didn't solve the problem here.
That's why I'm taking this over to -stable mailing list:

I've got a FreeBSD 6.0 NFS client here, which is connected to a FreeBSD
4.10-Server. Both sides are running statd and lockd, but processes
requesting locks (kdm in the first place after booting here) get stuck in
the state "lockd". The same setup works fine with a FreeBSD 5.4
client. Are
there any known problems concerning nfs and 6.0, or do I miss anything
else?


cu
  Gerrit

Hi,

Am Donnerstag, 1. Dezember 2005 16:49 schrieb Gerrit
K?hn:
> I've got a FreeBSD 6.0 NFS client here, which is connected to
> a FreeBSD 4.10-Server. Both sides are running statd and lockd,
> but processes requesting locks (kdm in the first place after
> booting here) get stuck in the state "lockd". The same setup
> works fine with a FreeBSD 5.4 client. Are there any known
> problems concerning nfs and 6.0, or do I miss anything else?
Here comes one of the dreaded "me too" posts. I'm having the same 
problem, I guess: statd and lockd enabled on server and clients, 
both 6.0-RELEASE (!). KDM starts, though, but login to KDE 
fails, Gnome cannot start completely (panel does not show any 
applets), OOo 2.0 freezes, when xkilled, rm -R .OpenOffice2 in 
the user directory fails ("Directory not empty").
I know that users at my deployment had problems emtying the Trash 
on the KDE desktop but this was right after the upgrade 5.4->6.0 
some weeks ago. No severe problems since then, until yesterday 
when none of the users was able to login anymore, Gnome broken 
as well etc.

Disabling rpc.lockd in rc.conf on the client side made the 
symptoms disappear, but i fear the real problem is still there.

Sorry that I can't give a better solution.

Andreas
-- 
Andreas Braml
Netzwerk f?r radio 98eins
PGP: http://www.braml.org/radio.asc

Please avoid sending me Microsoft Office (e.g. Word, PowerPoint)
attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051201/ac7b9afc/attachment.bin

On Thu, 01 Dec 2005 16:49:55 +0100, Gerrit K?hn  
<gerrit@pmp.uni-hannover.de> wrote:
> On Wed, 30 Nov 2005 10:29:02 -0500 Robert Huff <roberthuff@rcn.com>
wrote
> about OOO 2.0 compiles but doesn't work properly:
>
> RH> >  The home directory is coming from a nfs-server, so the
user-setup
> RH> >  should be identical. I already tried to delete
.openoffice.org2,
> RH> >  but that didn't help either. Any further hints?
>
> RH> 	Yes - check the archives.  There was at least one other person
> RH> reporting problems with OpenOffice+NFS.
>
> Yes, I see... the problem seems so be that you have to run lockd and  
> statd
> to get ooo running on nfs. The machine where everything's working fine
is
> running 5.4 with statd and lockd. The machine with the problems is  
> running
> 6.0 and didn't have statd and lockd activated.
> However, activating them (and rebooting) didn't solve the problem here.
> That's why I'm taking this over to -stable mailing list:
>
> I've got a FreeBSD 6.0 NFS client here, which is connected to a FreeBSD
> 4.10-Server. Both sides are running statd and lockd, but processes
> requesting locks (kdm in the first place after booting here) get stuck in
> the state "lockd". The same setup works fine with a FreeBSD 5.4
client.
> Are
> there any known problems concerning nfs and 6.0, or do I miss anything
> else?
Another me too: freebsd 6.0-stable client and a Linux 2.6.x debian 3.1  
server.
All processes that try to lock a file hang in stats lockd.
A workaround is using the -L option of mount_nfs.

-- 
  Ronald Klop
  Amsterdam, The Netherlands

On Fri, 2 Dec 2005 02:19, Gerrit K?hn wrote:
> Yes, I see... the problem seems so be that you have to run lockd and statd
> to get ooo running on nfs. The machine where everything's working fine
is
> running 5.4 with statd and lockd. The machine with the problems is running
> 6.0 and didn't have statd and lockd activated.
> However, activating them (and rebooting) didn't solve the problem here.
> That's why I'm taking this over to -stable mailing list:
You can get OOo to not do locking.

Edit this file..
/usr/local/openoffice.org2.0.RC3/program/soffice

and put a # in front of these 2 lines
SAL_ENABLE_FILE_LOCKING=1
export SAL_ENABLE_FILE_LOCKING


-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051202/eba1a384/attachment.bin