Weblogic 10 doesn't start through admin console

Question

Hi,
While starting a managed server on WebLogic 10.3 through the admin console I get the below error. However when starting the same managed server with a script I can successfully start it up.
<Sep 30, 2010 10:31:52 AM EEST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://10.123.456.78:7001.>
<Sep 30, 2010 10:31:52 AM EEST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Sep 30, 2010 10:31:52 AM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Sep 30, 2010 10:31:55 AM EEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
     at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:40)
     at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:35)
     at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:105)
     at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:60)
     at weblogic.server.channels.ChannelService.start(ChannelService.java:197)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.net.UnknownHostException: myServer: myServer
     at java.net.InetAddress.getLocalHost(InetAddress.java:1353)
     at weblogic.server.channels.AddressUtils$AddressMaker.getLocalHost(AddressUtils.java:38)
     at weblogic.server.channels.AddressUtils$AddressMaker.<clinit>(AddressUtils.java:35)
     at weblogic.server.channels.AddressUtils.getIPAny(AddressUtils.java:105)
     at weblogic.protocol.configuration.ChannelHelper.checkConsistency(ChannelHelper.java:60)
     at weblogic.server.channels.ChannelService.start(ChannelService.java:197)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The environment had been up and running for many months, have done many successfull restarts occasionally. But after an ungraceful shutdown (database connection was down and managed server wouldn't shutdown through admin console) of the managed server & admin server, the startup through admin console stopped working. No configurations had been modified and we have two other systems working with similar configurations.
The log is stating that "<The admin server could not be reached at http://10.123.456.78:7001.>" but it actually is listening at that IP and port and I can connect to it with other means. I'm able to ping the hostname, IP, localhost etc... and network connection shouldn't be an issue even though the log states so.
Does anyone have any ideas what is broken? Thanks for any help in advance!

Answer 1

Hi,
With script I meant the startManagedWebLogic.cmd script (on Windows). The managed server is running on the same machine as the admin server.
The hosts file has also been checked, it has the same content as two other environments which are working fine. But anyway we tried adding the IP & hostname there, but it didn't fix the issue. Nothing is wrong with the DNS either.
I'm also able to ping the address:port, with the command you gave I get the following result:
Sending 1 ping of 100 bytes.
RTT = ~0 milliseconds, or ~0 milliseconds/packet
When I'm trying to restart the managed server through admin console (on my laptop), I can see on the server side that there is a connection to the IP:port of admin server from my laptop's IP:
C:\>netstat -an | grep 7001
TCP 10.123.456.78:7001 0.0.0.0:0 LISTENING
TCP 10.123.456.78:7001 10.164.51.33:3965 ESTABLISHED
I again want to say that no changes have been done to any configurations in the environment. It was working fine before the "ungraceful" shutdown, where the connection to DB (that the managed server uses) was down and neither the managed or admin server would shutdown through admin console, but were shutdown by closing the cmd prompt window(used to start admin server) and java.exe task from taskmgr (managed server).