Check is now critical for service-discover.service - Install & Setup

RE: Check is now critical for service-discover.service

sigtrap — Sun, 04 Feb 2024 11:46:23 +0000

So I have the log level for carbonio-storages back to debug after upgrading to Carbonio CE to version 24.01.

I accidentally cross posted it in the upgrade forum thread but then remembered the problem.

I added SyslogLevel=warning to the section in /lib/systemd/system/carbonio-storages.service and changed "defaultLevel": "debug" to "defaultLevel": "warn" in /etc/carbonio/storages/config.json

I don't like to change the Carbonio system files, but I don't want my SSD to be flooded with not needed log entries.

And I still got warning messages every 5 seconds buy it is nothing to be worried about?

Feb 4 12:42:10 master service-discoverd: 2024-02-04T12:42:10.251+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:15 master service-discoverd: 2024-02-04T12:42:15.253+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:20 master service-discoverd: 2024-02-04T12:42:20.255+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:25 master service-discoverd: 2024-02-04T12:42:25.256+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:30 master service-discoverd: 2024-02-04T12:42:30.257+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:35 master service-discoverd: 2024-02-04T12:42:35.259+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:40 master service-discoverd: 2024-02-04T12:42:40.260+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:45 master service-discoverd: 2024-02-04T12:42:45.262+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:50 master service-discoverd: 2024-02-04T12:42:50.264+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:42:55 master service-discoverd: 2024-02-04T12:42:55.265+0100  agent: Check is now critical: check=service:carbonio-tasks
Feb 4 12:43:00 master service-discoverd: 2024-02-04T12:43:00.267+0100  agent: Check is now critical: check=service:carbonio-tasks

//Sigtrap

RE: Check is now critical for service-discover.service

sigtrap — Fri, 29 Dec 2023 09:15:33 +0000

@stefanodavid , Any success on forwarding the problem to the developers?

RE: Check is now critical for service-discover.service

stefanodavid — Wed, 06 Dec 2023 14:25:13 +0000

@sigtrap I can't find any reference to this error i nthe web, so I will try to forward this to our developers and see if they have some clue

Check is now critical for service-discover.service

sigtrap — Sun, 03 Dec 2023 15:07:44 +0000

I have just installed Carbonio and been running it for one day. Had to fix the carbonio-prometheus-nginx-exporter.service so it starts. The carbonio-storages.service is running in debug log level and I changed it to warning.

When I now read the syslog there are lots of warnings from service-discover.service.

root@master:/home/sigtrap# systemctl status service-disc*
● service-discover.service - Service discover server for Zextras
Loaded: loaded (/lib/systemd/system/service-discover.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2023-12-03 15:01:41 CET; 26min ago
Docs: https://docs.zextras.com/
Main PID: 1804 (consul)
Tasks: 14 (limit: 18810)
Memory: 63.5M
CGroup: /system.slice/service-discover.service
└─1804 /usr/bin/consul agent -bootstrap-expect 1 -config-dir /etc/zextras/service-discover/ -server -retry-join=master.sigtrap.org

Dec 03 15:27:37 master.sigtrap.org service-discoverd: 2023-12-03T15:27:37.470+0100  agent: Check is now critical: check=service:carbonio-storages
Dec 03 15:27:41 master.sigtrap.org service-discoverd: 2023-12-03T15:27:41.794+0100  agent: Check is now critical: check=service:carbonio-files
Dec 03 15:27:41 master.sigtrap.org service-discoverd: 2023-12-03T15:27:41.845+0100  agent: Check is now critical: check=service:carbonio-tasks
Dec 03 15:27:42 master.sigtrap.org service-discoverd: 2023-12-03T15:27:42.471+0100  agent: Check is now critical: check=service:carbonio-storages
Dec 03 15:27:46 master.sigtrap.org service-discoverd: 2023-12-03T15:27:46.799+0100  agent: Check is now critical: check=service:carbonio-files
Dec 03 15:27:46 master.sigtrap.org service-discoverd: 2023-12-03T15:27:46.847+0100  agent: Check is now critical: check=service:carbonio-tasks
Dec 03 15:27:47 master.sigtrap.org service-discoverd: 2023-12-03T15:27:47.473+0100  agent: Check is now critical: check=service:carbonio-storages
Dec 03 15:27:51 master.sigtrap.org service-discoverd: 2023-12-03T15:27:51.804+0100  agent: Check is now critical: check=service:carbonio-files
Dec 03 15:27:51 master.sigtrap.org service-discoverd: 2023-12-03T15:27:51.848+0100  agent: Check is now critical: check=service:carbonio-tasks
Dec 03 15:27:52 master.sigtrap.org service-discoverd: 2023-12-03T15:27:52.476+0100  agent: Check is now critical: check=service:carbonio-storages

Does not sound OK. I am pretty sure that I installed the "service-discover setup-wizard" the correct way (ip/mask) and I remember the password.

I can see the Mesh Administration Interface, but I don't know what to do. Yes, the files, storages and tasks are red. But how to fix it? Or do I need to fix it? Can just change log level to error?

//Sigtrap