18.1 Troubleshooting common problems 18.1.1 Client issues While administrators and users work with Content Manager OnDemand systems, they might  encounter various problems. These problems can occur in several main areas. We classify  them into the following categories: In this section, we describe several of the common problems and provide possible solutions  to them. At the end of the section, we also include a list of common server messages.  Tip for determining the cause of the problems:  For the UNIX platform, the console  message might help determine the cause of the problem. However, if you use Telnet from  your personal computer, you might miss the important console message. For AIX, you can  switch the console to your current terminal by running the  swcons 'tty'  command. To  switch it back to the console, run the  swcons  command. Users often encounter the following common problems when they run client-side applications:  Reasons : The following areas might cause this problem: Resolution : Check the following conditions: Resolution : Test the scenario with the OnDemand Windows client first. If the problem  cannot be reproduced, turn on the OnDemand Web Enablement Kit (ODWEK) trace. (See  18.2, “Information collection” on page 389). After the ODWEK application programming  interface (API) in question is identified from the trace, run a stand-alone program to test  the API. (A sample program can be requested from IBM.)  GLYPH<SM590000> Indexing and loading issues GLYPH<SM590000> Content Manager OnDemand maintenance issues GLYPH<SM590000> Monitoring the main server task arssockd GLYPH<SM590000> Installation and migration issues GLYPH<SM590000> Common server messages GLYPH<SM590000> Problem : Client connection received the error  Server failed while .... – Server is not up, or the server is up but not responding to a request – TCP/IP problems between Windows and the OnDemand host – Protocol problem – Firewall problem  – OnDemand library server is up, and it accepts requests. For example, log on to the  OnDemand host and issue an  arsdoc  query against the OnDemand system log.  – You can  ping  the OnDemand host. If not, consult your OS support.  – The port OnDemand server is listening and ready for a supported protocol. For  example, issue the  netstat -tulpn  command.  – The Linux fire wall is not on. For example, use the  systemctl status firewalld command to turn off the firewall by issuing the  systemctl disable firewalld command.  GLYPH<SM590000> Problem : Content Navigator or a custom application encounters an error with OnDemand. 378  IBM Content Manager OnDemand Guide