This article explains why some logs are flooded with bdbrepd messages. These messages are generated when the configuration has “no-split-detection” enabled and GRES, Non-stop routing and Non-stop bridging disabled. These log messages are normal and will not create any impact.

The log message below is flooding and seen in huge numbers.

init: bdbrepd (PID 1699) exited with status=1
init: bdbrepd (PID 2040) started
init: bdbrepd (PID 2040) exited with status=1
init: bdbrepd (PID 2048) started
init: bdbrepd (PID 2048) exited with status=1
init: bdbrepd (PID 2056) started
init: bdbrepd (PID 2056) exited with status=1
init: bdbrepd (PID 2066) started
init: bdbrepd (PID 2066) exited with status=1
init: bdbrepd (PID 2076) started
init: bdbrepd (PID 2076) exited with status=1
init: bdbrepd (PID 2082) started
init: bdbrepd (PID 2082) exited with status=1
init: bdbrepd (PID 2088) started
init: bdbrepd (PID 2088) exited with status=1
init: bdbrepd (PID 2094) started
init: bdbrepd (PID 2094) exited with status=1
init: bdbrepd (PID 2106) started
init: bdbrepd (PID 2106) exited with status=1
init: bdbrepd (PID 2112) started

This log message is generated when the configuration has “no-split-detection” enabled and GRES, Non-stop routing and Non-stop bridging disabled.

These log messages are normal and will not create any impact.

Refer KB22177 - How to filter two or more specific messages from being written to the syslog file? [juniper.net] to filter these log messages.

Example: root#set system syslog file messages match "! (bdbrepd)"

19-11-2025: Minor, non-technical edit

KB22177 - How to filter two or more specific messages from being written to the syslog file? [juniper.net]