After adding a new destination to an existing path, Error "Can not revert config after bad candidate" is shown (4383830)

When adding a new destination rule in Log/Paths the SSB can hang for some time and then the following error is displayed “The configuration has not been changed because the changes you want to apply would result in an invalid configuration”

After this error is displayed, error "Can not revert config after bad candidate" is shown not allowing the user to navigate from the Log/Paths screen, WEBUI can freeze.

This is sometimes caused when using a UDP balancer on the source linked to the affected path.

Syslog-ng's handler and the SSB's way of syslog-ng reload procedure can create a race condition where the syslog-ng reload process can loop.

As a result, the syslog-ng reloaded thousands of times in 10 minutes, which creates system-wide issues as kernel  is being tot busy to operate other services like WEBUI correctly.

This has been identified as defect 713040

This is currently being investigated for a fix to be included in a future release of the SSB. 

Until then, the configuration change can potentially cause the issue if a UDP balancer is also defined in configuration.

Workaround:

The issue can be cleared with reboot, or in CLI by issuing `kill -9` to the main syslog-ng process, removing the UDP balancer will fix this issue altogether.

The other possible workaround is to restart syslog-ng instead of reload every single time.

Service restart by nature causes minor data loss, especially in the case of UDP.

Use the command

`systemctl edit syslog-ng.service`

and add these lines:

```

[Service]

ExecReload=

```

Please note this taints the core Firmware.