Postscript to migrating volume groups

The server failed to start due to an error yesterday. The volume group has been mounted to the original directory / home
weblogic is mainly used on the application server. It is better to start weblogic
step1: create weblogic's starting user wls
problem1: during local cmd, ping does not know the server address, but you can connect through ssh on other servers, indicating that there is a problem with routing configuration.
My local network segment is 172.20.61. And my server is 172.20.63.
Reconfigure the routing table. Modify / etc / sysconfig / static routes
Add the following routes:

any net 172.20.11.0/24 gw 172.20.63.254
any net 172.20.29.0/24 gw 172.20.63.254
any net 172.20.50.0/24 gw 172.20.63.254
any net 172.20.51.0/24 gw 172.20.63.254
any net 172.20.60.0/24 gw 172.20.63.254
any net 172.20.61.0/24 gw 172.20.63.254
any net 180.166.105.84 netmask 255.255.255.255 gw 172.20.63.254

problem2: an error was posted when weblogic was started:

<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)
        Truncated. see log file for complete stacktrace
java.net.UnknownHostException: bogon: bogon
        at java.net.InetAddress.getLocalHost(InetAddress.java:1354)

The solution is to modify the / etc/hosts file
Configure host name
127.0.0.1 app1

problem3: after the service is started, the port is also started, but it is found that it cannot be accessed. After troubleshooting, it is a firewall problem:
Turn off firewall:

service iptables stop

At this point, the server is back to normal.

Tags: Java Weblogic network firewall

Posted on Mon, 02 Dec 2019 10:17:42 -0800 by pocobueno1388