Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | network/multiuser installation fails when installing on NFS mounted location during registration | ||
---|---|---|---|
Product: | Installation | Reporter: | Unknown <non-migrated> |
Component: | code | Assignee: | Unknown <non-migrated> |
Status: | CLOSED DUPLICATE | QA Contact: | issues@installation <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, stx123 |
Version: | OOo 1.1 RC3 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2003-08-30 15:12:08 UTC
Look at Issue 17517. It describes the same Problem , when OO will be installed on a Client with NFS mounted devices. In my way I' installed OO on an server (/usr/local), all clients in my network mount /usr/local with NFS. Up to OO1.0.3 eyerythink works well, with OO1.1rc3 I got th e following error message on the clients. On the server everything is o.k.: The application cannot be started. The component manager is not available. Start the setup application to repair the instalation from the CR or the folder containing the installation packages. repairing fails! After a few test, I tried to install OO1.1RC3 on the NFS Client and I got the following error message: Registering the components 'The libctl645li.so' component was unable to be registered retry does nothing (keeps failing) ignore goes to next file, and that fails alse (implreg.uno.so) cancel just goes to next file (which fails) On the Server an the Clients I use Slackware Linux with Kernel 2.4.21 and glibc 2.3.1. Hi Skottie, please have a look. Could it be that the problems are caused by the glibc 2.3.1? I tried this again with RC4 and the same issue exists. I tried using the STAR_PROFILE_LOCKING_DISABLED env variable, but that didn't help either. I also tried installing to an NFS mount from another SuSE 8.2 installation. The test produced no broken links, but the registration part still failed. I think the actual installation of the files is OK, but the problem comes during the registration part. What is happening during registration? Just to get a reference i tried an installation using RH8 as nfs-server to a RH Severn client. This was absolutely trouble-free. For the exports i used the parameters (rw,all_squash). I will have to recreate the entire setup in order to reproduce the problem. Hi ewinston, could you please provide me with a copy of your automounter configuration files? Thank you. This depends on the Suse 8.2 srcipts. Start the nfs and nfslock deamons in yast2. *** This issue has been marked as a duplicate of 19339 *** Dupe |