Shulou(Shulou.com)06/01 Report--

Console launch server Times for server server-1 and computer machin

For the server AdminServer, the node manager associated with the computer Machine-0 is not accessible.

All selected servers are currently in an incompatible state with this operation, are not associated with the running node manager, or are not authorized to perform the requested operation. No action will be performed

Almost all of the mistakes have been encountered. After searching the Internet for a long time, it was finally solved, basically as follows:

The node manager associated with the computer machine-2 cannot be accessed for the server server-1.

All selected servers are currently in an incompatible state with this operation, are not associated with the running node manager, or are not authorized to perform the requested operation. No action is performed.

Reason: nodemanager did not start up

1. For managedServer and adminServer on the same server:

1. You can view the node manager port of the machine in the console, such as 5556.

2. Use the netstat-nap | grep 5556 command to check whether the process with port 5556 exists to know whether nodemanager has been started, but it certainly does not exist.

3. If you use the ps-ef | grep java command to view the process, you can see the NodeManager process.

4. Use kill-9 NodeManager process number

5. Vi / etc/hosts to check whether the ip address is configured correctly

6. Vi / etc/sysconfig/network to check whether the machine name is configured correctly

7. Vi $WL_HOME/common/nodemanager/nodemanager.properties to see if the following configuration is correct. The port 5556 here is the same as the port mentioned above. If the port is incorrect, it may be because the port was modified in the console after the previous nodemanager, and the original port is saved in the nodemanager.properties file, so when nodemanager is started again, the port started is not the modified port but the original port.

ListenPort=5556

SecureListener=false

StartScriptEnabled=true

2. If AdminServer is on server An and ManagedServer is on server B:

It is also possible that nodemanager cannot be started at this time because server B cannot communicate with server A, and an socket related error will be reported at this time. At this time

1. Modify the $WL_HOME/common/nodemanager/nodemanager.properties file on server B:

SecureListener=false

StartScriptEnabled=true

2. Execute the wlst.sh script under the $WL_HOME/common/bin/ directory on B

. / wlst.sh is fine

3. After executing 2, you will go to wls:/offline >, and enter connect () here.

4. At this point, you will be asked to enter the user name, password and url of AdminServer as follows

Please enter your username [weblogic]: weblogic

Please enter your password [weblogic]:

Please enter your server URL [t3://localhost:7001]: t3://adminServerIP:port

The above three items refer to the user name, password, IP address and port when logging in to the console on server A

5. If step 4 is executed successfully, the

Successfully connected to AdminServer' AdminServer' that belongs to domain' my_domain'.

Will jump to wls:/my_domain/serverConfig >

My_damain refers to domain on server A

If step 4 is unsuccessful, you will return to step 3 and re-enter connect ()

You can also enter dumpStack () to view specific errors at this time.

6. After step 5 is executed successfully, execute it in turn under wls:/my_domain/serverConfig >.

NmEnroll ('/ home/weblogic/Oracle/Middleware/wlserver_10.3/common/nodemanager')

NmEnroll ('/ home/weblogic/Oracle/Middleware/user_projects/domains/server_b_domain')

The weblogic directory here refers to the weblogic directory on server B. modify the statement according to your own directory.

7. After the registration is successful, press ctrl+c to return to the weblogic directory, and then to the $WL_HOME/servers/bin directory

Nohup. / startNodeManager.sh & start nodemanager

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.