[gentoo-user] OpenOffice 2.0 + NFS = hang

[gentoo-user] OpenOffice 2.0 + NFS = hang

[Konstantin V. Gavrilenko]

Hi list,

I have emerge OpenOffice 2.0 recently and noticed a strange problem,
that whenever I try to access the file located on the nfs, the OO2
hangs. The rest of the applications are working fine with nfs, and such
problem never happened with OpenOffice 1.x
The problem happens on two gentoo boxes and one box running debian.

the shares are exported on NFS server as following
#/etc/exports
/mnt/Docs
192.168.69.0/24(rw,sync,all_squash,anonuid=2000,anongid=2000)


the clients mount nfs shares as following
#/etc/fstab
nfserver:/mnt/Docs                  /mnt/Docs       nfs
defaults,hard,intr,rsize=8192,wsize=8192 0 0


thanks in advance for any help.

yours,
kos

-- 
Respectfully,
Konstantin V. Gavrilenko

Arhont Ltd - Information Security

web:    http://www.arhont.com
	http://www.wi-foo.com
e-mail: k.gavrilenko@arhont.com

tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141

PGP: Key ID - 0xE81824F4
PGP: Server - keyserver.pgp.com
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Bruno Lustosa]

[-- Attachment #1: Type: text/plain, Size: 811 bytes --]

On 10/25/05, Konstantin V. Gavrilenko <mlists@arhont.com> wrote:
>
> I have emerge OpenOffice 2.0 recently and noticed a strange problem,
> that whenever I try to access the file located on the nfs, the OO2
> hangs. The rest of the applications are working fine with nfs, and such
> problem never happened with OpenOffice 1.x
>

I experienced the same problem while trying to migrate a network share from
samba to nfs.
Everything else worked fine with nfs. I could even open the OO files in
file-roller, for example, with no errors at all.
Thus, I was forced to go back and stick to samba.
Do you get loads of 'NFS server not responding' messages in your log files
as well?

--
Bruno Lustosa, aka Lofofora | Email: bruno@lustosa.net
Network Administrator/Web Programmer | ICQ: 1406477
Rio de Janeiro - Brazil |

[-- Attachment #2: Type: text/html, Size: 1289 bytes --]

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[John Jolet]

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]


On Oct 26, 2005, at 2:08 PM, Bruno Lustosa wrote:

> On 10/25/05, Konstantin V. Gavrilenko <mlists@arhont.com> wrote:
> I have emerge OpenOffice 2.0 recently and noticed a strange problem,
> that whenever I try to access the file located on the nfs, the OO2
> hangs. The rest of the applications are working fine with nfs, and  
> such
> problem never happened with OpenOffice 1.x
>
> I experienced the same problem while trying to migrate a network  
> share from samba to nfs.
> Everything else worked fine with nfs. I could even open the OO  
> files in file-roller, for example, with no errors at all.
> Thus, I was forced to go back and stick to samba.
> Do you get loads of 'NFS server not responding' messages in your  
> log files as well?
>
in my experience samba works better for that sort of thing anyway.   
If a server serving an nfs share goes down, all the computers with  
that share mounted will go nuts, spending 100% cpu trying to get the  
share back.  Samba seems to fail more gracefully under those conditions.
> -- 
> Bruno Lustosa, aka Lofofora          | Email: bruno@lustosa.net
> Network Administrator/Web Programmer | ICQ: 1406477
> Rio de Janeiro - Brazil              |


[-- Attachment #2: Type: text/html, Size: 1759 bytes --]

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Bruno Lustosa]

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

On 10/26/05, John Jolet <john@jolet.net> wrote:
>
> in my experience samba works better for that sort of thing anyway. If a
> server serving an nfs share goes down, all the computers with that share
> mounted will go nuts, spending 100% cpu trying to get the share back. Samba
> seems to fail more gracefully under those conditions.
>

Weird thing is, the server hasn't come down. It was still up. However, I
don't know why the client was reporting those messages. Perhaps it was
failing intermitently, and OO has an issue with this and other apps don't,
because the second after OO failed to open the file, I was able to open it
in file-roller without a problem.
Isn't nfs supposed to be THE network filesystem for unix machines? Using
samba between unix machines when there's no real need seems a bit
controversial for me :)

--
Bruno Lustosa, aka Lofofora | Email: bruno@lustosa.net
Network Administrator/Web Developper | ICQ: 1406477
Rio de Janeiro - Brazil |

[-- Attachment #2: Type: text/html, Size: 1478 bytes --]

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Konstantin V. Gavrilenko]

Solved the problem.

Apparently you need to disable file locking by commenting out the
following lines:

# file locking now enabled by default
#SAL_ENABLE_FILE_LOCKING=1
#export SAL_ENABLE_FILE_LOCKING

in /usr/lib/openoffice/program/soffice

as simple as it gets.


yours,
kos




-- 
Respectfully,
Konstantin V. Gavrilenko

Arhont Ltd - Information Security

web:    http://www.arhont.com
	http://www.wi-foo.com
e-mail: k.gavrilenko@arhont.com

tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141

PGP: Key ID - 0xE81824F4
PGP: Server - keyserver.pgp.com


Konstantin V. Gavrilenko wrote:
> Hi list,
> 
> I have emerge OpenOffice 2.0 recently and noticed a strange problem,
> that whenever I try to access the file located on the nfs, the OO2
> hangs. The rest of the applications are working fine with nfs, and such
> problem never happened with OpenOffice 1.x
> The problem happens on two gentoo boxes and one box running debian.
> 
> the shares are exported on NFS server as following
> #/etc/exports
> /mnt/Docs
> 192.168.69.0/24(rw,sync,all_squash,anonuid=2000,anongid=2000)
> 
> 
> the clients mount nfs shares as following
> #/etc/fstab
> nfserver:/mnt/Docs                  /mnt/Docs       nfs
> defaults,hard,intr,rsize=8192,wsize=8192 0 0
> 
> 
> thanks in advance for any help.
> 
> yours,
> kos
> 


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Bruno Lustosa]

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

On 10/27/05, Konstantin V. Gavrilenko <mlists@arhont.com> wrote:
>
> Solved the problem.
>
> Apparently you need to disable file locking by commenting out the
> following lines:
>
> # file locking now enabled by default
> #SAL_ENABLE_FILE_LOCKING=1
> #export SAL_ENABLE_FILE_LOCKING
>
> in /usr/lib/openoffice/program/soffice
>

I think I solved it even better. I noticed that when trying to open an OO
file in nfs, I'd get these errors on syslog:

Oct 27 11:01:27 ti03 lockd: cannot monitor 192.168.7.1 <http://192.168.7.1>
Oct 27 11:01:27 ti03 lockd: failed to monitor 192.168.7.1<http://192.168.7.1>

Sure enough, rpcinfo -p (on the client) gave me this:

ti03 ~ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
391002 2 tcp 689 sgi_fam
100021 1 udp 36350 nlockmgr
100021 3 udp 36350 nlockmgr
100021 4 udp 36350 nlockmgr
100021 1 tcp 32792 nlockmgr
100021 3 tcp 32792 nlockmgr
100021 4 tcp 32792 nlockmgr

It seems rpc.statd isn't running, because status monitor doesn't show on the
list.
Just starting /etc/init.d/nfs solved the problem. Now OO opens nfs files
without a problem, and rpcinfo -p shows some other services started:

ti03 ~ # rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
391002 2 tcp 689 sgi_fam
100021 1 udp 36350 nlockmgr
100021 3 udp 36350 nlockmgr
100021 4 udp 36350 nlockmgr
100021 1 tcp 32792 nlockmgr
100021 3 tcp 32792 nlockmgr
100021 4 tcp 32792 nlockmgr
100024 1 udp 36351 status
100024 1 tcp 32793 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100005 1 udp 727 mountd
100005 1 tcp 730 mountd
100005 2 udp 727 mountd
100005 2 tcp 730 mountd
100005 3 udp 727 mountd
100005 3 tcp 730 mountd


--
Bruno Lustosa, aka Lofofora | Email: bruno@lustosa.net
Network Administrator/Web Developper | ICQ: 1406477
Rio de Janeiro - Brazil |

[-- Attachment #2: Type: text/html, Size: 4621 bytes --]

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Konstantin V. Gavrilenko]

tried it,

but it did not solve the issue on my box.

I guess, i'll stick to the commenting out the file_locking


yours,
kos

-- 
Respectfully,
Konstantin V. Gavrilenko

Arhont Ltd - Information Security

web:    http://www.arhont.com
	http://www.wi-foo.com
e-mail: k.gavrilenko@arhont.com

tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141

PGP: Key ID - 0xE81824F4
PGP: Server - keyserver.pgp.com


Bruno Lustosa wrote:
> On 10/27/05, *Konstantin V. Gavrilenko* <mlists@arhont.com
> <mailto:mlists@arhont.com>> wrote:
> 
>     Solved the problem.
> 
>     Apparently you need to disable file locking by commenting out the
>     following lines:
> 
>     # file locking now enabled by default
>     #SAL_ENABLE_FILE_LOCKING=1
>     #export SAL_ENABLE_FILE_LOCKING
> 
>     in /usr/lib/openoffice/program/soffice
> 
> 
> I think I solved it even better. I noticed that when trying to open an
> OO file in nfs, I'd get these errors on syslog:
> 
> Oct 27 11:01:27 ti03 lockd: cannot monitor 192.168.7.1 <http://192.168.7.1>
> Oct 27 11:01:27 ti03 lockd: failed to monitor 192.168.7.1
> <http://192.168.7.1>
> 
> Sure enough, rpcinfo -p (on the client) gave me this:
> 
> ti03 ~ # rpcinfo -p
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     391002    2   tcp    689  sgi_fam
>     100021    1   udp  36350  nlockmgr
>     100021    3   udp  36350  nlockmgr
>     100021    4   udp  36350  nlockmgr
>     100021    1   tcp  32792  nlockmgr
>     100021    3   tcp  32792  nlockmgr
>     100021    4   tcp  32792  nlockmgr
> 
> It seems rpc.statd isn't running, because status monitor doesn't show on
> the list.
> Just starting /etc/init.d/nfs solved the problem. Now OO opens nfs files
> without a problem, and rpcinfo -p shows some other services started:
> 
> ti03 ~ # rpcinfo -p
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     391002    2   tcp    689  sgi_fam
>     100021    1   udp  36350  nlockmgr
>     100021    3   udp  36350  nlockmgr
>     100021    4   udp  36350  nlockmgr
>     100021    1   tcp  32792  nlockmgr
>     100021    3   tcp  32792  nlockmgr
>     100021    4   tcp  32792  nlockmgr
>     100024    1   udp  36351  status
>     100024    1   tcp  32793  status
>     100003    2   udp   2049  nfs
>     100003    3   udp   2049  nfs
>     100003    2   tcp   2049  nfs
>     100003    3   tcp   2049  nfs
>     100005    1   udp    727  mountd
>     100005    1   tcp    730  mountd
>     100005    2   udp    727  mountd
>     100005    2   tcp    730  mountd
>     100005    3   udp    727  mountd
>     100005    3   tcp    730  mountd
> 
> 
> -- 
> Bruno Lustosa, aka Lofofora          | Email: bruno@lustosa.net
> <mailto:bruno@lustosa.net>
> Network Administrator/Web Developper | ICQ: 1406477
> Rio de Janeiro - Brazil              |


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Billy Holmes]

Konstantin V. Gavrilenko wrote:
> Apparently you need to disable file locking by commenting out the
> following lines:

either that or run lockd...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Billy Holmes]

Bruno Lustosa wrote:
> It seems rpc.statd isn't running, because status monitor doesn't show on 
> the list.

ah.. that's right. lockd needs statd. silly nfs.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Konstantin V. Gavrilenko]

As discussed in this thread
http://www.openoffice.org/issues/show_bug.cgi?id=54586

QTE
++++++
1  On certain Linux machines, file locking is known to fail due to the
NFS lock demon not running.
2  On certain other Linux machines, it appears that file locking fails
due to some other, not yet analyzed reason.
+++++
UNQTE

I guess my machines fall into the second category.


yours,
kos

Billy Holmes wrote:
> Konstantin V. Gavrilenko wrote:
> 
>> Apparently you need to disable file locking by commenting out the
>> following lines:
> 
> 
> either that or run lockd...

-- 
Respectfully,
Konstantin V. Gavrilenko


Arhont Ltd - Information Security

web:    http://www.arhont.com
	http://www.wi-foo.com
e-mail: k.gavrilenko@arhont.com

tel: +44 (0) 870 44 31337
fax: +44 (0) 117 969 0141

PGP: Key ID - 0xE81824F4
PGP: Server - keyserver.pgp.com
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] OpenOffice 2.0 + NFS = hang

[Bryan Whitehead]

Make sure all nfs services are running on client and server.

OR

you have iptables running and you are blocking random nfs service ports. 
Check both client and server.

run rpcinfo -p on each machine to see what ports need to be open. It might 
be better to just allow anything to go between server->client and 
client->server.

On Thu, 27 Oct 2005, Konstantin V. Gavrilenko wrote:

> As discussed in this thread
> http://www.openoffice.org/issues/show_bug.cgi?id=54586
>
> QTE
> ++++++
> 1  On certain Linux machines, file locking is known to fail due to the
> NFS lock demon not running.
> 2  On certain other Linux machines, it appears that file locking fails
> due to some other, not yet analyzed reason.
> +++++
> UNQTE
>
> I guess my machines fall into the second category.
>
>
> yours,
> kos
>
> Billy Holmes wrote:
>> Konstantin V. Gavrilenko wrote:
>>
>>> Apparently you need to disable file locking by commenting out the
>>> following lines:
>>
>>
>> either that or run lockd...
>
>

-- 
Bryan Whitehead
Email:driver@megahappy.net
-- 
gentoo-user@gentoo.org mailing list