Troubleshooting Site Selector

Use the information that is provided to help you solve problems that can occur in with Site Selector.

Click a link in the table to go to a full description and possible solution for the problem that you are experiencing.
Table 1. Site Selector Troubleshooting table
Symptom Possible cause Got to...
Site Selector not running correctly Conflicting port number  
Site Selector does not round-robin incoming requests from Solaris client Solaris systems run a "name service cache daemon"  
The sscontrol or lbadmin command fails with ‘Server not responding' or ‘unable to access RMI server' message Commands fail due to socksified stack. Or commands fail due to not starting ssserver.  
ssserver fails to start on Windows platform Windows systems do not require the host name to be in the DNS.  
Machine with duplicate routes not load balancing correctly — name resolution appears to fail Site Selector machine with multiple adapters attached to the same subnet  
Unexpected GUI behavior when using Windows platform paired with Matrox AGP video card Problem occurs when using Matrox AGP video cards while running the Load Balancer GUI  
GUI hangs (or unexpected behavior) when trying to load a large configuration file. Java™ does not have access to enough memory to handle such a large change to the GUI  
Disconnect from host when using remote Web administration through Netscape Disconnect from host will occur when resize the browser window  
On Windows platform, corrupted Latin-1 national characters appear in command prompt Change font properties of command prompt window  
On HP-UX platform, the following message occurs: java.lang.OutOfMemoryError unable to create new native thread Some HP-UX installations by default allow 64 threads per process. This is insufficient.  
On Windows platform, advisors and reach targets mark all servers down Task offloading is not disabled or may need to enable icmp.  
On Solaris systems, Load Balancer processes end when you exit the terminal session window from which they started Use the nohup command to prevent the processes that you started from receiving a hangup signal when you exit the terminal session.  


Terms and conditions for information centers | Feedback

Last updated: January 30, 2013 03:00 PM EST
File name: ttrb_ss.html