Bonjour,
Nous notons une instabilité du service Consul qui nous renvoi régulièrement des mails type:
Description: failed protocol test [HTTP] at [localhost]:8500/v1/agent/services [TCP/IP] – HTTP: Error receiving data – Resource temporarily unavailable
Si je jette un coup d’oeil du coté de daemon.log, j’ai au même moment le message suivant:
daemon.log:Sep 17 12:18:10 xivo monit[1841]: ‘consul’ failed protocol test [HTTP] at [localhost]:8500/v1/agent/services [TCP/IP] – HTTP: Error receiving data – Resource temporarily unavailable
daemon.log:Sep 17 12:18:14 xivo monit[1841]: ‘consul’ trying to restart
daemon.log:Sep 17 12:18:14 xivo monit[1841]: ‘consul’ stop: ‘/bin/systemctl stop consul.service’
daemon.log:Sep 17 12:18:45 xivo monit[1841]: ‘consul’ failed to stop (exit status -1) – Program ‘/bin/systemctl stop consul.service’ timed out after 30 s
daemon.log:Sep 17 12:19:06 xivo consul[90647]: 2020/09/17 12:19:06 [ERR] agent: failed to sync changes: leadership lost while committing log
daemon.log:Sep 17 12:19:06 xivo consul[90647]: 2020/09/17 12:19:06 [ERR] agent: failed to sync changes: No cluster leader
daemon.log:Sep 17 12:19:06 xivo systemd[1]: consul.service: Main process exited, code=exited, status=1/FAILURE
daemon.log:Sep 17 12:19:06 xivo systemd[1]: consul.service: Failed with result ‘exit-code’.
daemon.log:Sep 17 12:20:51 xivo monit[1841]: ‘consul’ process is not running
daemon.log:Sep 17 12:20:51 xivo monit[1841]: ‘consul’ trying to restart
daemon.log:Sep 17 12:20:51 xivo monit[1841]: ‘consul’ start: ‘/bin/systemctl start consul.service’
daemon.log:Sep 17 12:20:51 xivo consul[232077]: BootstrapExpect is set to 1; this is the same as Bootstrap mode.
daemon.log:Sep 17 12:20:51 xivo consul[232077]: bootstrap = true: do not enable unless necessary
daemon.log:Sep 17 12:20:51 xivo consul[232077]: ==> Starting Consul agent…
daemon.log:Sep 17 12:20:51 xivo systemd[1]: consul.service: Can’t open PID file /run/consul/consul.pid (yet?) after start-post: No such file or directory
daemon.log:Sep 17 12:20:52 xivo consul[232077]: ==> Consul agent running!
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Version: ‘1.0.7-dev’
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Node ID: ‘a172b603-1ed6-5de0-46da-d631535a0d32’
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Node name: ‘xivo’
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Datacenter: ‘xivo’ (Segment: ‘’)
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Server: true (Bootstrap: true)
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: 8501, DNS: -1)
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Cluster Addr: 127.0.0.1 (LAN: 8301, WAN: 8302)
daemon.log:Sep 17 12:20:52 xivo consul[232077]: Encrypt: Gossip: false, TLS-Outgoing: false, TLS-Incoming: false
daemon.log:Sep 17 12:20:52 xivo consul[232077]: ==> Log data will now stream in as it occurs:
daemon.log:Sep 17 12:20:52 xivo monit[1841]: ‘consul’ started
daemon.log:Sep 17 12:22:54 xivo monit[1841]: ‘consul’ process is running with pid 232077
daemon.log:Sep 17 12:22:54 xivo monit[1841]: ‘consul’ connection succeeded to [localhost]:8500/v1/agent/services [TCP/IP]
Tout fonctionne correctement après ce redémarrage “automatique” mais ce genre d’incident avec envoi de mail se produit au minimum 2 fois par jours.
Auriez-vous une piste afin de me guider dans le debug ?
Merci d’avance
Bien cordialement
Jordi
PS: Wazo Stack en 20.12