Issue 10765 - Unrecoverable error on startup due to bad hostname
Summary: Unrecoverable error on startup due to bad hostname
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: OOo 1.1 Beta
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
: 8568 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-01-18 22:41 UTC by Unknown
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

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


Attachments
Trace file from "strace" command (1.01 MB, text/plain)
2003-01-18 22:57 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-01-18 22:41:50 UTC
On redhat 8.0, for an OpenOffice new install, on startup I get 
an "unrecoverable error" with the following message displayed to the terminal:

Get_local_host: hostname '50.h2-0-0.wash-cust.oss.uswest.net' bad

I disconnected the ethernet cable so that the hostname 
is "localhost.localdomain".  When I do this it also aborts, but instead of 
getting the message above, all that is displayed to the terminal is "Aborted" 
when the error message OK button is clicked.

I ran "strace" on this and have the output.  I'll try to attach it to the 
committed message.

Thanks,
George
Comment 1 Unknown 2003-01-18 22:57:44 UTC
Created attachment 4345 [details]
Trace file from "strace" command
Comment 2 Unknown 2003-01-18 23:00:44 UTC
A trace file formed from "strace" has been attached.  (Due to what 
appeared to be looping while the error GUI is displayed, the point of 
failure would not be at the bottom of the file.)
Comment 3 Unknown 2003-01-19 19:03:44 UTC
In the program setup.log there were the following six identical errors
listed
error: RegistryItemAction::Execute() called

Comment 4 Unknown 2003-01-19 20:26:38 UTC
Summary and additional Information:
I do not believe that the bad hostname and the RegistryItemAction 
error in the setup.log have anything to do with this problem which 
continues.  I was able to get rid of the first error by disonnecting 
the ethernet cable, and the second error did not show up in the 
setup.log file when the install script for unix, rather than setup, 
was used. The following is additional information:
1) java 1.4.1 is selected for the Java verion.
2) PC with Pentium III running RedHat 8.0 with 256 meg memory.
3) the original OpenOffice directories that came with RedHad in my 
home directory (.openoffice, .user60.rbd, .sversionrc) were backed 
up, and "/usr/lib/openoffice" was moved to my home directory so as 
not to affect the new install.  (The install that comes with RedHat 
does work well, but it doesn't have the class files for API 
development, and I wanted everyting in local one directory.)     


Comment 5 Olaf Felka 2003-01-20 09:27:48 UTC
Hi Thorsten,
you are investigating in stale mounted devices.
Comment 6 thorsten.martens 2003-01-20 10:57:29 UTC
TM->LO: I don´t really know, if this problem might be double to our
IBIS problem #106761. Please have a look. Maybe MHU is responsible for
taking care of this one. Thanks !
Comment 7 Unknown 2003-01-22 16:38:06 UTC
FYI: I got StarOffice 6.0 for linux and it installs on my RedHat 8.0
machine and works flawlessly.  (Didn't do anything any different on
the install than what I was doing for the OpenOffice install.)
Comment 8 Unknown 2003-01-23 18:52:40 UTC
Is there a possibility that intalling OpenOffice and StarOffice could
affect vpn?  After each install vpn failed and I had to re-install
RedHat 8 to get vpn to work again. 
Comment 9 lo 2003-01-28 11:56:54 UTC
I am not able to reproduce this failure here... what kind of vpn are
you reffering to?
It would be helpful if you could produce a stacktrace from the
crashing office, by either starting soffice.bin in gdb or by loading
the corefile into gdb and getting a backtrace. 
Use 'ulimit -c unlimited' in bash before starting soffice in order to
have a corefile generated on abort. Then go to your office install
directory and do 'gdb program/soffice.bin <your-core-file>'. once gdb
has started issue a 'backtrace' command....
Comment 10 lo 2003-01-30 14:59:39 UTC
QA reports that current builds from openoffice.org will not work
correctly with redhat 8.0 due to incompatibilities with glibc version
shipped with redhat. Binaries shipped with redhat seem to work
reliable but are not in any way checked by OpenOffice/StarOffice QA.
Which version are you using?
Comment 11 Unknown 2003-01-30 15:18:18 UTC
I attempted to install the most recent version of OpenOffice 1.0.1
that I downloaded from OpenOffice.org on 1/18/2003.
Comment 12 lo 2003-02-07 14:27:55 UTC
Please use rpms provided by readhat to run openoffice with redhat 8.0
since openoffice.org build don't work with redhat's version of glibc.
Comment 13 dirk.voelzke 2003-02-17 10:32:18 UTC
*** Issue 8568 has been marked as a duplicate of this issue. ***
Comment 14 lo 2003-03-10 11:52:58 UTC
this one should be closed
Comment 15 Olaf Felka 2003-03-10 12:14:03 UTC
Looks like a RH problem.
Comment 16 Olaf Felka 2003-03-10 12:14:20 UTC
.