Sun Microsystems Portal Server 6 2005Q1, Planning Manual

Page: 161 / 192

Troubleshooting Portal Server
Appendix D Troubleshooting Your Portal Deployment 161
➤
To Extract the Display Profile
1.
Login as administrator.
2.
Use the
dpadmin
command to extract the display profile. For example:
./dpadmin list -u "uid=amAdmin,ou=People,o=sesta.com,o=isp" -w
password
-d "o=sesta.com,o=isp" > /tmp/displayxml
This example puts the contents of the display profile into the
/tmp/displayxml
file.
➤
To Reload the Display Profile
1.
Login as administrator.
2.
Use the
dpadmin
command to reload the display profile. For example:
./dpadmin modify -u "uid=amAdmin,ou=People,o=sesta.com,o=isp" -w
password
-d "o=sesta.com,o=isp" /tmp/updated_displayxml
This example reloads the contents of the display profile from the
/tmp/updated_displayxml
file.
High CPU Utilization for Portal Server Instance
When using the Cisco Content Services Switch, you might see a very high CPU
utilization on the Portal Server instance with Sun Java System Web Server error file
showing the following message every five seconds.
The cause of this error is a “sticky bit” setting within the Cisco Content Services
Switch that is causing these errors. These load balancers periodically ping the
servers (every five seconds) to verify that the servers are alive. After turning off the
“sticky bit” setting, which disables the ping to the server every 5 seconds, the
errors will no longer show up in the Web Server product.
[20/Jan/2003:16:53:36] failure ( 5926): Error accepting connection -5928, oserr=130
(Connect aborted)