Issue 19339 - Install to NFS partition fails
Summary: Install to NFS partition fails
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: Other Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@installation
URL:
Keywords: oooqa
: 17517 18844 20817 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-09-09 17:27 UTC by Unknown
Modified: 2008-05-17 23:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
excerpts from setup.log (23.94 KB, text/plain)
2003-09-10 13:30 UTC, Olaf Felka 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-09-09 17:27:01 UTC 
When doing an install to folder that is on a NFS mount, the 'component registration' part of the 
installation fails. Warning popup message is given for every .so component but the installation 
still claims to be succesful. System setup and local installation fails after this, claiming missing 
components. 
 
The installation works OK to a local partition. 1.1pre2 gave the same problem. 
 
System is a fresh SuSE 8.2 with all updates installed. Under Red Hat 7.3 this used to work for 
1.1pre2.
Comment 1 Olaf Felka 2003-09-10 12:00:57 UTC 
I've tried with Suse 8.2 on a mounted nfs drive: no problem OOo setup
runs without errors, Office starts fine. As you have written, it has
been ok with RH 7.3 and doesn't work with Suse 8.2. Iwould assume that
this is related to your Suse.
Comment 2 Olaf Felka 2003-09-10 13:11:27 UTC 
I've been shooting to quick.
Comment 3 Olaf Felka 2003-09-10 13:29:27 UTC 
Fact is that I can't reproduce with Suse 8.0 but I can reproduce with
Suse 8.2. 
OF -> MHU: I've tried to reproduce on /tausch/of.
DBO told that you might have some information for this special case. I
think it depends on the nfs drive.
Comment 4 Olaf Felka 2003-09-10 13:30:45 UTC 
Created attachment 9166 [details]
excerpts from setup.log
Comment 5 Olaf Felka 2003-09-22 14:29:02 UTC 
*** Issue 17517 has been marked as a duplicate of this issue. ***
Comment 6 Olaf Felka 2003-09-22 14:44:18 UTC 
*** Issue 18844 has been marked as a duplicate of this issue. ***
Comment 7 matthias.huetsch 2003-09-22 15:58:58 UTC 
As demonstrated on the SuSE 8.2 machine where of@openoffice.org could
reproduce this, the issue is due to a misconfiguration:

The 'lockd' process (RPC Lock Daemon) needs to run in order to be able
to lock files via NFS. The default SuSE 8.2 NFS client configuration
is 'broken' in that it does not start this daemon.

Once it is activated, either manually via '/etc/init.d/nfslock start',
or at system boot time via the runlevel editor, all is well.

Therefore I'm marking this issue as 'resolved worksforme' and reassign
it back to the submitter. Please verify that the above procedure also
works for you, and if it does please close this issue.

An issue can always be reopened.
Comment 8 matthias.huetsch 2003-09-22 15:59:54 UTC 
resolving as 'works for me'...
Comment 9 Olaf Felka 2003-10-07 10:20:34 UTC 
*** Issue 20817 has been marked as a duplicate of this issue. ***
Comment 10 joerg.skottke 2003-10-17 11:33:50 UTC 
*** Issue 21314 has been marked as a duplicate of this issue. ***
Comment 11 joerg.skottke 2003-10-17 11:36:49 UTC 
Tried following config:

<server>
[root@ja-3100 etc]# less exports
/home/autojsk (rw,all_squash)
/opt (rw,all_squash)


and
<client>
ja-3100:/opt on /opt type nfs (rw,addr=10.16.64.67)
ja-3100:/home/autojsk on /export/home/autojsk type nfs
(rw,addr=10.16.64.67)

and could find no problems.
Comment 12 ace_dent 2008-05-17 21:36:45 UTC 
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 13 ace_dent 2008-05-17 23:39:59 UTC 
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew