> Source: [sk181891](https://support.checkpoint.com/results/sk/sk181891) # sk181891 - The 'cxld' process consumes the CPU at 70%-100% on VSX Cluster Members | Property | Value | |----------|-------| | Solution ID | sk181891 | | Date Created | 2024-01-17 | | Last Modified | 2024-06-05 | | Technical Level | General | | Products | Security Gateway | | Versions | R81.20, R81.10 (EOS), R81 (EOS) | | OS | Gaia | ## Symptoms - * The '`cxld`' processes constantly consume the CPU at 70%-100% on VSX Cluster Members. This CPU utilization is observed in outputs of various commands ('`top`', '`ps`', '`cpview`' \> CPU \> Spikes). Example from CPview: ![](https://sc1.checkpoint.com/sc/SolutionsStatics/NEW_SK_NOID1705506426905/cxlpd_cpview202401171752491.png) * This issue started after installing one of these Jumbo Hotfix Accumulators: * R81.20 Jumbo Hotfix - Take 43 * R81.10 Jumbo Hotfix - Take 113 (Resolved in Take 132) * R81 Jumbo Hotfix - Take 89 ## Cause The CXLD processes that run in the context of Virtual Systems write and read the same internal file on the VSX Cluster Member, instead of doing so with a file in the context of each corresponding Virtual System. ## Solution This problem was fixed. The fix is included in: * [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 45 * [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 132 * [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 99 \* As an immediate workaround, follow this procedure: (Even if you choose to upgrade you are still must to applied this procedure on all members) 1. Connect to the command line on each VSX Cluster Member. 2. Log in to the Expert mode. 3. Examine the state of the Virtual Systems: `cphaprob state` For example, there are two VSX Cluster Member: * VSX_M_1 - ACTIVE cluster state * VSX_M_2 - STANDBY cluster state 4. On the "`STANDBY`" VSX Cluster Member (in our example, **VSX_M_2** ), perform these steps for **each** Virtual System in the "`STANDBY`" state (write down each VS ID): 1. Go to the context of the Virtual System: `vsenv ` 2. Disable the CPU utilization monitor: `fw ctl set -f int fwha_cpu_utlization_monitor_enable 0` 3. Identify the Process ID (PID) of the '`cxld`' process for this Virtual System: `cpwd_admin list | grep -E "PID|CXLD"` Note - The "`CTX`" column shows the VS ID. > Example output: > > ``` > [Expert@VSX_M_2:0]# cpwd_admin list | grep -E "PID|CXLD" > APP CTX PID STAT #START START_TIME MON COMMAND > CXLD 0 44825 E 1 [12:41:56] 3/1/2024 N cxld -d > CXLD 6 10765 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 12 45470 E 1 [10:52:53] 8/1/2024 N cxld -d > CXLD 7 11152 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 11 11153 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 4 11154 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 5 11155 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 10 11156 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 2 11157 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 8 11164 E 1 [12:44:32] 3/1/2024 N cxld -d > CXLD 9 11405 E 1 [12:44:33] 3/1/2024 N cxld -d > CXLD 3 11407 E 1 [12:44:33] 3/1/2024 N cxld -d > [Expert@VSX_M_2:0]# > ``` > > Example PIDs: > * PID of CXLD in VS 2 = 11157 > * PID of CXLD in VS 9 = 11405 4. Terminate the '`cxld`' process for this Virtual System: `kill -9 ` 5. Monitor the '`cxld`' process for this Virtual System - wait until is starts again: `watch -d -n 5 'cpwd_admin list | grep -E "PID|CXLD" | grep -E "PID| "'` Notes: * The inner command is enclosed in single quotes. * There are 3 space characters in front of the VS ID and after the VS ID. In the \, substitute the required number. * The "`PID`" column must show a non-zero integer. * The "`STAT`" column must show "`E`". Example output for VS ID 9 after the '`cxld`' process termination: > > ``` > Every 2.0s: cpwd_admin list | grep -E "PID|CXLD" | grep -E "PID| 9 " > > APP CTX PID STAT #START START_TIME MON COMMAND > CXLD 9 0 T 1 [12:44:33] 3/1/2024 N cxld -d > ``` Example output for VS ID 9 after the '`cxld`' process starts again: > > ``` > Every 2.0s: cpwd_admin list | grep -E "PID|CXLD" | grep -E "PID| 9 " > > APP CTX PID STAT #START START_TIME MON COMMAND > CXLD 9 49470 E 2 [18:16:00] 17/1/2024 N cxld -d > ``` 6. Monitor the VSX cluster state - wait for the state of this Virtual System to change to '`STANDBY`' again: `cphaprob state` Note - In the output, refer to the bottom section "`Virtual Devices Status on each Cluster Member`". 5. Administratively change the cluster state of the "STANDBY" VSX Cluster Member to "DOWN" (in our example, **VSX_M_2**): `clusterXL_admin down` 6. On the "ACTIVE" VSX Cluster Member (in our example, **VSX_M_1** ), perform Step 4 for **each** Virtual System that you changed on the previous VSX Cluster Member (in our example, **VSX_M_2**). 7. Administratively change the cluster state of the "DOWN" VSX Cluster Member to "UP" (in our example, **VSX_M_2**): `clusterXL_admin up` 8. Examine the state of each VSX Cluster Member and each Virtual System: `cphaprob state` --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content