You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.
follwing the discussion in issue #126 I removed all failover configurations for my broker. Without the failover configuration, the broker config file for the rrd file generator is not generated correctly anymore.
Steps to reproduce the issue:
For my central server I configured two broker accordingly to the best practices. One for the sql, perfdata and rrd forward output. And a second one for the rrd file generation. For both broker I removed all failover configurations. For the first broker the config file is generated correctly. For the second not.
Config file for the rrd broker with failover:
Config file for the rrd broker without failover:
Describe the results you expected: Correctly generated config files.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
OS: CentOS 7.4
centreon-broker: 3.0.13
centreon-engine 1.8.1
centreon-web: 2.8.19
follwing the discussion in issue #126 I removed all failover configurations for my broker. Without the failover configuration, the broker config file for the rrd file generator is not generated correctly anymore.
Steps to reproduce the issue:
For my central server I configured two broker accordingly to the best practices. One for the sql, perfdata and rrd forward output. And a second one for the rrd file generation. For both broker I removed all failover configurations. For the first broker the config file is generated correctly. For the second not.
Config file for the rrd broker with failover:
Config file for the rrd broker without failover:
Describe the results you expected: Correctly generated config files.
The text was updated successfully, but these errors were encountered: