-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with collector configuration #104
Comments
Hello @Fran765, The error you are receiving looks to be because you have configured MongoDB to use TLS authentication, but the provided certificate does not appear to work. Have you also configured MongoDB to accept TLS authentications? The default installation only sets up the password based authentication. As for configuring mTLS with the Security Server, more information on how to do that is available in the X-Road documentation: https://docs.x-road.global/Manuals/ug-ss_x-road_6_security_server_user_guide.html#9-communication-with-information-systems |
Hi @raits, Solved the previous problem by leaving password-based authentication. I have the following error when I run the command "xroad-metrics-collector collect": What is the problem due to? |
Hey, It looks like the Security Server does not have the operational monitoring addon installed. You should be able to resolve it by simply installing the |
Did you receive any errors during the installation process? Could you also try restarting all of the X-Road services and check the logs for any errors that might be occurring? |
Hi @raits, you can solve the problem by removing the service and reinstalling it. |
Hey @Fran765, It's possible, but by default, the report generation is meant to be run once a month. The way that the default installation sets it up is with this cron job: X-Road-Metrics/reports_module/etc/xroad-metrics-reports-cron Lines 7 to 9 in ce07b95
It just passes in the X-Road-Metrics/reports_module/opmon_reports/reports_arguments.py Lines 121 to 135 in ce07b95
It means that you would need to set up a cron job or some other scheduled task that also calculates the correct start and end dates for arguments based on your custom schedule. |
Greetings, @Fran765 I'd like to implement this architecture like you, could you provide me with the manuals that follow. CS(ip : x.x.x.x), SS Management(ip : x.x.x.x), SS1(ip : x.x.x.x), SS2(ip : x.x.x.x) and a server for Metrics(ip : x.x.x.x) containing the various modules (collector, corrector, reports) and mongodb. I already know the ansible project for CS and SS. I'm having a bit of trouble with SS Management and X-Road Metrics |
Hi @SowAbdoul I'm sorry I can't help you. The previous project was not continued, so I don't have any documentation available. Greetings and success. |
Hi!
I have a structure with a CS(ip: 10.114.80.16), SS Management(ip: 10.114.10.17), SS1(ip: 10.114.10.18), SS2(ip: 10.114.10.19) and a server for Metrics(ip: 10.114.80.20 ) in which the different modules (collector, corrector, reports) and mongodb are installed.
I have the 'setting.yaml' of the collector configured like this:
Where should I download the "tls-client-certificate" and "tls-client-key"? and then put 'true' in the "tls-server-certificate"
I also have the following error, when using the collector and executing "xroad-metrics-collector update" it returns the following error:
File "/usr/lib/python3/dist-packages/pymongo/topology.py", line 208, in _select_servers_loop
raise ServerSelectionTimeoutError(
pymongo.errors.ServerSelectionTimeoutError: SSL handshake failed: 127.0.0.1:27017: EOF occurred in violation of protocol (_ssl.c:1131)
But when I run "xroad-metrics-collector list" it works correctly.
This is how I currently have the mongo configuration:
The text was updated successfully, but these errors were encountered: