Issue 21314 - OOo no more useable on NFS mounts ?
Summary: OOo no more useable on NFS mounts ?
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Joost Andrae
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-16 12:31 UTC by Unknown
Modified: 2004-01-22 16:30 UTC (History)
1 user (show)

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

Attachments
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-10-16 12:31:06 UTC 
We use OOo 1.0.x on our network for a long time, installed on an NFS partition,
with server and clients running Mandrake 9.1 (server) and 9.0 (clients).

OOo is on /usr/local/software (NFS partition)
/home is an NFS partion as well.

I tried to install OOo1.1 the same way. I succeeded with "setup -net", root can
use it, and even ordinary users ON THE SERVER.

After that, I try to launch it on a client from the NFS partition to make a
workstation install, but I have this message (with ./setup -debug) :

types.rdb and services.rdb not found or damaged
ExitCode: 30


"setup -c" on my OOo archive is OK.

This is really annoying since it's the better way to install OOo very quickly on
a big network...
Comment 1 joerg.skottke 2003-10-17 11:33:51 UTC 
Dupe to issue 19339

*** This issue has been marked as a duplicate of 19339 ***
Comment 2 Unknown 2003-10-20 15:31:32 UTC 
Sorry but lockd is already running on my client and on my server. I
tried to restart it on both sides, and tried setup again, without success.

OOo1.0.3 is on the same nfs partition and works well.
Comment 3 Olaf Felka 2003-10-27 12:21:27 UTC 
of- jsk: You gave this issue some attention. Any further ideas?
Comment 4 joerg.skottke 2003-12-11 07:54:43 UTC 
In fact i have no idea. I've never seen any trouble like this. But since there
are others reporting similar issues there must be something to it ...

Maybe Joost has an idea? He's got a lot of experience with nfs.

Reassigning to JA
Comment 5 Joost Andrae 2003-12-15 15:58:18 UTC 
JA: the exit code 30 means "install procedure not found" and is only valid
within a response file installation where there is an error within the response
file. Please check this. On the other hand a "setup -c" just checks the
integrity of the install archives but not of the "network installation itself".
I would like to propose to install the "network installation" and to check the
response file. I doubt this is an NFS problem.
Comment 6 Joost Andrae 2003-12-17 10:26:00 UTC 
JA: changed priority to P3. Working on NFS works like a charm. This must be
something different.
Comment 7 Joost Andrae 2004-01-22 16:30:29 UTC 
JA: cannot reproduce
Comment 8 Joost Andrae 2004-01-22 16:30:53 UTC 
JA: closing