Applies To:

Show Versions Show Versions

Manual Chapter: Troubleshooting
Manual Chapter
Table of Contents   |   << Previous Chapter

When troubleshooting issues with the WebAccelerator system, you can look in the log files for these services, to see if error conditions exist. Use these log files for troubleshooting purposes only. For daily WebAccelerator system monitoring, use SNMP. See Chapter 5, Monitoring the WebAccelerator System for more information.
The tomcat service hosts the Configuration utility user interface, from which you configure the WebAccelerator system.
The tomcat log files are located in:
The intelligence interface (waui) service publishes acceleration policies (and changes to acceleration policies) to the WebAccelerator system.
The pvac service manages HTTP and HTTPS traffic in accordance to the associated acceleration policy.
The pvac log files are located in:
tar czvpf /var/tmp/wa.config-data.tgz /config/wa/var/lib/mysql/WA/PERFMONITOR_DATA.* /var/log/wa
Port definitions
A process was unable to obtain the port defined for it in the pvsystem.conf file. This most likely means that a process that was using that port did not shut down properly. You can use the netstat(8) command to see what process is currently using the port.
Upstream processes
A process was unable to connect to its upstream (parent) process. Some possible reasons for not being able to connect to an upstream process are:
Upstream process is not running
Check the system processes (see Checking the WebAccelerator system processes) and restart them as required.
Upstream process is not using the expected port
Check the port assignments for the upstream and downstream systems processes (see Monitoring the communications system with SNMP), and correct them in the pvsystem.conf file as required.
Network misconfiguration
Verify that the host names identified in the pvsystem.conf file are configured in DNS, and that they resolve to the correct IP addresses, and then ping the systems over the network.
Firewall misconfiguration
Verify that the firewall is open for both incoming and outgoing TCP/IP traffic for all relevant hosts and ports.
SSL certificates
The communications system uses certificate-based encrypted traffic (SSL version 3). If the certificates are corrupt or expired, or not yet valid in certain pathological cases, then communications cannot be established. If you suspect there is an issue with the SSL certificate, check the validity of the certificate on the upstream and downstream systems, using the openssl command: openssl verify/usr/local/wa/config/ssl/pvssl.pem
If there is an issue, the last line of output does not display OK. Note that Error 18 (self-signed certificate) is reported for all default WebAccelerator system installations. This is considered an acceptable error if the openssl command reports OK.
Time is not synchronized
The WebAccelerator system uses NTP to keep all system clocks synchronized. The communications system is sensitive to time synchronization issues and the clocks must be within 1000 seconds of each other for NTP to be able to correct the differential. This limit can be exceeded if there is a hardware clock failure on a host. Check the time hosts in your installation. If they are not synchronized, verify that NTP is running on each host and check for NTP errors in the /var/log/wa/messages file. For information, see Defining an NTP server.
When sending a response to a client, the WebAccelerator system inserts an informational X-PvInfo response header, as described in Understanding object type classification. This X-PvInfo response header includes codes that you can use to assess the effectiveness of your acceleration policy rules.
You can view X-PvInfo response headers by:
For additional information, including definitions of each X-PvInfo response header code, see the Policy Management Guide for the BIG-IP® WebAccelerator System.
Hot Cache
Used to store objects that do not require special assembly.
Smart Cache
Used to store objects that require special assembly processing, such as objects for which variation rules apply.
Typically, you use invalidation rules to remove specific content stored in the Smart Cache. However, there may be occasions, such as when troubleshooting cache issues, when you want to remove all of the content that the WebAccelerator system has stored in both the Smart Cache and the Hot Cache. You can clear cache either for specific applications or type of content, or for all content stored in the WebAccelerator cache.
Important: Clearing the cache on the WebAccelerator system temporarily increases traffic to the origin web servers until the WebAccelerator system repopulates the cache.
On the Main tab of the navigation pane, expand WebAccelerator, and click Invalidate Content.
The Invalidate Content Types screen opens.
Check the box next to Normalized to clear all content on which the WebAccelerator has performed URL normalization. For more information about normalized content, see Understanding URL normalization.
Check the box next to Unmapped to clear all content for unmapped hosts. Note that this application is available only if you have enabled unmapped host processing. For more information, see Processing unmapped requests.
Click the Invalidate button.
This command restarts the pvac service, which may temporarily halt the flow of HTTP traffic, and the WebAccelerator system displays the following messages:
Note: For information about configuring invalidation rules, see the Policy Management Guide for the BIG-IP® WebAccelerator System.
Table of Contents   |   << Previous Chapter

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)