This article has been archived and is no longer maintained by F5. World Tech IT will continue to host this resource.
Topic
This article applies to WebAccelerator version 9.x/10.x. For information about other versions, refer to the following articles:
When the BIG-IP system is licensed with BIG-IP WebAccelerator™, it runs an additional set of processes on top of the standard set of BIG-IP processes. The following table lists the core BIG-IP WebAccelerator processes, and indicates the impact to the BIG-IP WebAccelerator operation if the process is not running:
| Overview of BIG-IP WebAccelerator Daemons (9.x – 10.x) | |||
|---|---|---|---|
| Daemon | Description | Impact if not running | Relevant log files |
| pvac | The pvac process performs all of the web acceleration according to the policy specified in the application configuration. The pvac process processes client requests from TMM, communicates with the origin web servers, caches objects in the Smart Cache, and performs content assembly functions such as IBR™ and MultiConnect. | The system will not process traffic. | /var/log/wa/pvac.log |
| comm_srv |
The comm_srv process is the configuration management communications server The functions of the comm_srv process are:
The pvac process connects to the comm_srv process on TCP port 12001 to receive the WebAccelerator configurations. Additionally, for BIG-IP WebAccelerators in a symmetric deployment, all pvac processes communicates with the comm_srv process on the central BIG-IP WebAccelerator for cluster and application configuration changes. |
No configuration is available to the pvac process. As a result, the system will not process traffic. | /var/log/wa/comm_srv.log |
| hds_prune | The hds_prune process monitors the available disk space on the cache partition of the hard drive. The hds_prune process is set to prune the disk cache when the partition is 80 percent full. For more information about the hds_prune process, refer to K9079: Overview of the BIG-IP WebAccelerator hds_prune process | System performance will be affected when disk cache is full. | /var/log/wa/hds_prune.log |
| waicd | The BIG-IP WebAccelerator iControl® daemon (waicd) uses iControl messages to communicate between BIG-IP WebAccelerators in a symmetric deployment for syncing up invalidations. The waicd process listens on TCP port 12012. | Invalidations between BIG-IP WebAccelerators in a symmetric deployment are not in sync. | None |
| mysqld | The MySQL database stores the following WebAccelerator information:
|
No configuration is available to the pvac process. As a result, the system will not process traffic. No performance report can be generated. | /var/lib/mysql/mysqld.err |
| tomcat | The BIG-IP WebAccelerator system uses a separate tomcat context, different from the main BIG-IP system. This tomcat context handles the BIG-IP WebAccelerator Configuration utility, which includes the following:
|
The Configuration utility does not function. |
9.4.x to 10.0.x: 10.1.0 or later: |
Starting and stopping BIG-IP WebAccelerator processes
You can use the command line to manage the BIG-IP WebAccelerator processes on the BIG-IP system. To stop, start, or restart all BIG-IP WebAccelerator processes, use the following syntax with the bigstart command:
bigstart action process
In this error message, note the following:
- < action > refers to the action for bigstart, such as stop, start or restart
- < process > is the name of the BIG-IP WebAccelerator process
Note: For information about using the bigstart utility, refer to the bigstart man page or K4080: Adding and removing services included in the bigstart process.
