NZ
ого, это какая версия консула?
Size: a a a
2020 December 11
S
последняя
S
$ consul --version
Consul v1.9.0
Revision a417fe510
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
Consul v1.9.0
Revision a417fe510
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
NZ
Спасибо, не буду её ставить)
A
$ consul --version
Consul v1.9.0
Revision a417fe510
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
Consul v1.9.0
Revision a417fe510
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
Что в логах?
c
у меня все ок на 1.9, нет подобной херни. OOM-ы бывают
c
там больше похоже что в рафте чето поломалось
A
там больше похоже что в рафте чето поломалось
+++
S
угу 🙁 в мониторе ток это:
$ consul monitor
2020-12-11T15:15:34.216+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.226+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.283+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:16:34.235+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
$ consul monitor
2020-12-11T15:15:34.216+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.226+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.283+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:16:34.235+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
NZ
Может какая-нибудь банальная причина типа место, права, selinux ?
S
Ну работало ж. причем если сейчас поднять таск в номаде то все ок - зарегается, потушить - пропадет
S
если руками сервис с чеками зарегать то тоже все ок, kv пашет, distributed локи тоже
S
т.е. трабл проявляется не сразу
NZ
А есть какие-то специфические настройки?
S
nope 😕 единственное что меня смущает - тут был export & import при переносе с другого кластера
S
snapshot
S
но все ок перенеслось и работало вот 2 недели уж как
A
угу 🙁 в мониторе ток это:
$ consul monitor
2020-12-11T15:15:34.216+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.226+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.283+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:16:34.235+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
$ consul monitor
2020-12-11T15:15:34.216+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.226+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:15:34.283+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
2020-12-11T15:16:34.235+0100 [WARN] agent.fsm: DeleteNode failed: error="failed to insert usage entry for "service-names": delta will cause a negative count"
А что покажет consul info
S
# root @ devops-1 in /var/consul [15:26:19]
$ consul info
agent:
check_monitors = 0
check_ttls = 1
checks = 6
services = 6
build:
prerelease =
revision = a417fe51
version = 1.9.0
consul:
acl = enabled
bootstrap = false
known_datacenters = 1
leader = false
leader_addr = 10.0.0.2:8300
server = true
raft:
applied_index = 210637
commit_index = 210637
fsm_pending = 0
last_contact = 18.990974ms
last_log_index = 210637
last_log_term = 72
last_snapshot_index = 205038
last_snapshot_term = 72
latest_configuration = [{Suffrage:Voter ID:8b7552c7-e710-b023-7d93-d3a8cebdf0d3 Address:10.0.0.2:8300} {Suffrage:Voter ID:5f385b9b-4f8f-7c68-c9e7-f548d2d298ff Address:10.0.0.4:8300} {Suffrage:Voter ID:06d4dfa3-c8ac-c7f5-7ad5-316b1941b848 Address:10.0.0.3:8300}]
latest_configuration_index = 0
num_peers = 2
protocol_version = 3
protocol_version_max = 3
protocol_version_min = 0
snapshot_version_max = 1
snapshot_version_min = 0
state = Follower
term = 72
runtime:
arch = amd64
cpu_count = 2
goroutines = 106
max_procs = 2
os = linux
version = go1.15.5
serf_lan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 9
failed = 0
health_score = 0
intent_queue = 0
left = 12
member_time = 9761
members = 15
query_queue = 0
query_time = 1
serf_wan:
coordinate_resets = 0
encrypted = true
event_queue = 0
event_time = 1
failed = 0
health_score = 0
intent_queue = 0
left = 0
member_time = 21
members = 3
query_queue = 0
query_time = 1
A
nope 😕 единственное что меня смущает - тут был export & import при переносе с другого кластера
Переименование нигде не делалось?