Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
NahelFalhout1
Contributor

Grafana Skyline : OpenTelemetry Components are not up yet Maestro

I am trying to configure the Grafana Skyline on one of my maestro FW. 
All other FWs it runs fine. Except for the maestro FW, it is on Take 139 

 

 

[Expert@xxx1-ch01-01:3]# /opt/CPotelcol/REST.py --set_open_telemetr                                                                                                                                                            y "$(cat /home/fwadmin/payload-no-tls.json)"
WARNING: REST.py is being deprecated, please use sklnctl (refer to sk17856                                                                                                                                                            6)
Error: OpenTelemetry Components are not up yet
Traceback (most recent call last):
  File "/opt/CPotelcol/REST.py", line 1428, in main
    request.commit()
  File "/opt/CPotelcol/REST.py", line 1296, in commit
    stage[2](*stage[3:])(REATTEMPT=True,OLD_CONFIG=oldConfiguration)
  File "/opt/CPotelcol/REST.py", line 1150, in __call__
    raise Exception(self._error_msg)
Exception: OpenTelemetry Components are not up yet

 

And in the Logs : 

 

024-06-05T12:36:32.777+0200    info    extensions/extensions.go:37     Extension started.      {"kind": "extension", "name": "health_check"}
2024-06-05T12:36:32.777+0200    info    otlpreceiver@v0.82.0/otlp.go:83 Starting GRPC server    {"kind": "receiver", "name": "otlp", "data_type": "metrics", "endpoint": "/opt/CPotelcol/grpc_otlp.sock"}
2024-06-05T12:36:32.777+0200    info    healthcheck/handler.go:129      Health Check state change       {"kind": "extension", "name": "health_check", "status": "ready"}
2024-06-05T12:36:32.777+0200    info    service/service.go:149  Everything is ready. Begin running and processing data.
2024-06-05T12:45:35.319+0200    info    service/telemetry.go:84 Setting up own telemetry...
2024-06-05T12:45:35.320+0200    info    service/telemetry.go:201        Serving Prometheus metrics      {"address": ":8888", "level": "Basic"}
2024-06-05T12:45:35.322+0200    info    service/service.go:132  Starting otelcol...     {"Version": "CPotelcol_0.82.0", "NumCPU": 3}
2024-06-05T12:45:35.322+0200    info    extensions/extensions.go:30     Starting extensions...
2024-06-05T12:45:35.322+0200    info    extensions/extensions.go:33     Extension is starting...        {"kind": "extension", "name": "health_check"}
2024-06-05T12:45:35.322+0200    info    healthcheckextension@v0.82.0/healthcheckextension.go:34 Starting health_check extension {"kind": "extension", "name": "health_check", "config": {"Endpoint":"0.0.0.0:13133","TLSSetting":null,"CORS":null,"Auth":null,"MaxRequestBodySize":0,"IncludeMetadata":false,"ResponseHeaders":null,"Path":"/","ResponseBody":null,"CheckCollectorPipeline":{"Enabled":false,"Interval":"5m","ExporterFailureThreshold":5}}}
2024-06-05T12:45:35.352+0200    warn    internal@v0.82.0/warning.go:40  Using the 0.0.0.0 address exposes this server to every network interface, which may facilitate Denial of Service attacks        {"kind": "extension", "name": "health_check", "documentation": "https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md#safeguards-against-denial-of-service-attacks"}
2024-06-05T12:45:35.352+0200    info    extensions/extensions.go:37     Extension started.      {"kind": "extension", "name": "health_check"}
2024-06-05T12:45:35.352+0200    info    otlpreceiver@v0.82.0/otlp.go:83 Starting GRPC server    {"kind": "receiver", "name": "otlp", "data_type": "metrics", "endpoint": "/opt/CPotelcol/grpc_otlp.sock"}
2024-06-05T12:45:35.352+0200    info    healthcheck/handler.go:129      Health Check state change       {"kind": "extension", "name": "health_check", "status": "ready"}
2024-06-05T12:45:35.352+0200    info    service/service.go:149  Everything is ready. Begin running and processing data.
~

 

 

 

 

 

0 Kudos
1 Reply
Elad_Chomsky
Employee
Employee

Hi @NahelFalhout1 , 

Please open a ticket to CheckPoint, so we can try to assist you directly - In general a few recommendations to try:

- Make sure to update to T93 . https://support.checkpoint.com/results/sk/sk180522 - See here. In any case of an upgrade issue, run '/opt/CPotelcol/CPotelcolCli.sh stop', in case it doesn't work try to run '/opt/CPotelcol/CPotelcolCli.sh set_dynamic_config "$(cat /opt/CPotelcol/config.yaml)"'.

- Try to use the new sklnctl tool and not REST.py, as it is slowly being deprecated. 

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events