We have a centreon 22.10.04 on Debian 11, we have an error when using the “Export Configuration” button.
I found another issue for this feature, but we do not have the same error.
The error we have:
There was an consistency error in the exported files - please use the legacy export menu to troubleshoot. Generation error on monitoring server #1: Response empty
In the log I did not get many usefull informations:
r16-Jan-2023 10:28:41 Europe/Paris] CRITICAL: There was an consistency error in the exported files - please use the legacy export menu to troubleshoot. Generation error on monitoring server #1: Response empty {"context":"oobject] (Centreon\\Domain\\MonitoringServer\\Exception\\MonitoringServerException(code: 0): There was an consistency error in the exported files - please use the legacy export menu to troubleshoot. Generation error on monitoring server #1: Response empty at /usr/share/centreon/src/Centreon/Application/Controller/Configuration/MonitoringServerController.php:230)"}
Does somebody have an idea?
Page 1 / 1
Hello @delaf,
You need to place your pem or crt file in /usr/local/share/ca-certificates/ and then launch the update-ca-certificates command.
Regards,
itoussies.
It does not work, but it put me on the right track to solve it.
In my setup I have a HAProxy in front of centreon that is doing SSL termination. Centron though it was access via HTTP so was doing request in HTTP ending to some 301 Redirect from HAProxy.
Adding mod_rpaf (and configuring it) in the centreon node solved this problem.
Thank you.
I have the same problem and I couldn’t find any solution.
Hi.
I had the same issu , and I finaly found what’s wrong for me.
When the menu, ask to use the “legacy mode” , it’s mean using the top button.
And then export:
You will get a full and precise message.
.
It does not work, but it put me on the right track to solve it.
In my setup I have a HAProxy in front of centreon that is doing SSL termination. Centron though it was access via HTTP so was doing request in HTTP ending to some 301 Redirect from HAProxy.
Adding mod_rpaf (and configuring it) in the centreon node solved this problem.
Thank you.
Hi! Can you explain how you did it? I also have a HAProxy but I am not able to make it work.
backend centreon_ipvANY mode http id 149 log global stick-table type ip size 50k expire 30m stick on src timeout connect 30000 timeout server 30000 retries 3
RPAFenable On RPAFsethostname On RPAFsethttps On RPAFproxy_ips 192.168.X.X 192.168.X.XX 127.0.0.1 #ProxyIP #CentreonServerIP RPAFheader X-Forwarded-For