The PDPD daemon unexpectedly exits on a VSX Gateway

Technical Information

• Product: VSX (Traditional)
• Version: R81.20
• Last Modified: 2024-10-06

Symptoms

• The PDPD daemon unexpectedly exits on a VSX Gateway, continuously generating a core dump file.

• When you run the pdp update all command on VS1, this error message appears:

  daemon did not respond or not running!
  

• Some AD users are not identified and matched to the Access Role on the affected VSX Gateway.

• The $FWDIR/log/pdpd.elg.x contains repeated exceptions similar to these:

  [worker_1] Warning: Messages processing blocked for 2555 milliseconds.
  check_caller_thread_safe: [WARNING] Non thread safe action: Mainloop thread id = 4034517824 while current thread id = 4047278400 (LWP 100350)
  Backtrace with 9 levels: [1] 0xf5e657e3 [/opt/CPshrd-R81.20/CTX/CTX00001/lib/libComUtils.so] (offset 0xf7e3)
  [2] T_event_desched_e [/opt/CPshrd-R81.20/CTX/CTX00001/lib/libComUtils.so] (offset 0x11800)
  [3] T_event_desched [/opt/CPshrd-R81.20/CTX/CTX00001/lib/libComUtils.so] (offset 0x11880)
  [4] _ZN25CLdapConfigurationManagerD1Ev [/opt/CPshrd-R81.20/CTX/CTX00001/lib/libcpldapcl.so] (offset 0x975d0)
  [5] _ZN25CLdapConfigurationManagerD0Ev [/opt/CPshrd-R81.20/CTX/CTX00001/lib/libcpldapcl.so] (offset 0x97660)
  [6] 0xf3b6e893 [/lib/libc.so.6] (offset 0x30893)
  [7] 0xf3b6e8f1 [/lib/libc.so.6] (offset 0x308f1)
  [8] __libc_start_main [/lib/libc.so.6] (offset 0x182d0)
  [9] 0x804cda1 [pdpd] (offset 0x4da1)
  [worker_1] Warning: Message ID 3 processing blocked on function  for 2395 milliseconds.
  [worker_1] Warning: Messages processing blocked for 2395 milliseconds.
  fwasync_create_socket_bindopt: failed to bind to a reserved port: Address already in use
  [TRACKER]: #1 -> INTERNAL -> INIT ->
  [worker_0] Warning: Message ID 1 processing blocked on function  for 22833 milliseconds.
  

• When you run the pidof pdpd command to obtain the process ID(s) of the PDPD daemon, the command may return multiple process IDs, as each VSX instance has its own unique process ID. Next, when you run the cat /proc/{pdpd process ID}/nsid command to determine the VSX instance (the returned number corresponds to the VSX number), the affected VSX instance has two PDPD process IDs, with one of them changing continuously.

Solution

This problem was fixed. The fix is included in:

• Jumbo Hotfix Accumulator for R81.20 starting from Take 89

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions: Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

• Access Level: General
• Status: Approved by TAC
• Date Created: 2024-08-30
• Last Modified: 2024-10-06