> I just used the YAST2 Online update tool to install the > latest patches on > our instances running WAS. After the install I discovered Websphere > wouldn't start. > > After some newsgroup searching I found that the problem was > due to the fact > that localhost resolved to 127.0.0.1 instead of the > "external" ip of the > instance. I edited the /etc/hosts file to fix this and > websphere then > started. > > Problem is that everytime SuSEconfig is ran my changes to the > /etc/hosts > file are lost. Anyone have any ideas on what I can do to > keep this problem > from happening.
Localhost SHOULD resolve to 127.0.0.1. I know nothing of WAS configuration, but the approach you should probably be taking is having WAS listen on a different interface (like eth0 or the hostname or whatever is appropriate for your network configuration) rather than having it listen only on localhost and mixing up what localhost refers to. ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
