Cluster troubleshooting

 

+

Search Tips   |   Advanced Search

 

Very similar to debugging portal as a stand-alone server. Must determine if it is a portal problem. Must determine node of failure and inspect portal logs, as usual. If undetermined, start from the top

• Eliminate the variables
• Isolate the problem

Note that dmgr is only involved during configuration and administration processes. Not used at all for runtime requests. All requests go straight to the nodes themselves.

1. For problems in initial installation and configuration process, check:
   • <portal_server_root>/log/wpsinstalllog.txt
   • <portal_server_root>/log/configTrace.log

2. Check the HTTP Server plugin log to verify there are no problems with the plugin and request routing

3. Stop Portal cluster members to isolate the problem to a specific cluster member, or modify plugin to direct traffic to one member
   • Does it happen on all cluster members, or just one?

4. Check the cluster member SystemOut.log & SystemErr.log
   • Now includes both WAS & Portal messages

   • Default location of logs for secondary nodes is...

     <profile_root>/logs/<server_name>

5. Use DMgr Admin Console to validate configuration

6. For portlet deployment and synchronization errors, also check nodeagent logs and Deployment Manager logs

   • Default location for nodeagent logs is...

     <profile_root>/logs/nodeagent

   • Default location for DMgr logs is...

     <profile_root>/logs/dmgr

 

Parent topic:

Set up a cluster

 

Previous topic

Install and federate secondary nodes

 

Next topic

Enable LDAP security after cluster creation

 

---