Consul 1.16.1是否在Ubuntu 20.04上正确实现了os_service检查?

0aydgbwb  于 2023-10-17  发布在  其他
关注(0)|答案(1)|浏览(133)

Ubuntu:20.04 qemu,领事:1.16.1,Vault 1.14.1
我尝试使用Consul来监控Vault的systemD服务,按照https://developer.hashicorp.com/consul/docs/services/usage/checks#osservice-check,但结果是一个“未实现”错误。
我领事的服务配置:

services = [
{
  name = "vault"
  port = 8200
    checks = [
      {
        http = "vault1.foo.bar.com:8200/sys/health"
        interval = "15s"
        timeout = "10s"
      },
      {
        name = "Vault Service"
        os_service = "vault.service"
        interval = "15s"
      },
      {
        name = "Vault gRPC health check"
        grpc = "vault1.foo.bar.com:8201"
        grpc_use_tls = true
        interval = "10s"
      },
    ]
}
]

我尝试了示例条目的几次迭代,以及只包含os_serviceinterval的基本条目。很快,我又回到了同样的原木旁:

consul[82355]: ==> Starting Consul agent...
consul[82355]:                Version: '1.16.1'
consul[82355]:             Build Date: '2023-08-05 21:56:29 +0000 UTC'
consul[82355]:                Node ID: '3e269875-156b-d7e7-8cfa-2b84c9487ef9'
consul[82355]:              Node name: 'vault1'
consul[82355]:             Datacenter: 'west' (Segment: '')
consul[82355]:                 Server: false (Bootstrap: false)
consul[82355]:            Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: 8502, gRPC-TLS: -1, DNS: 8600)
consul[82355]:           Cluster Addr: 10.12.1.94 (LAN: 8301, WAN: 8302)
consul[82355]:      Gossip Encryption: true
consul[82355]:       Auto-Encrypt-TLS: false
consul[82355]:            ACL Enabled: false
consul[82355]:     ACL Default Policy: allow
consul[82355]:              HTTPS TLS: Verify Incoming: false, Verify Outgoing: false, Min Version: TLSv1_2
consul[82355]:               gRPC TLS: Verify Incoming: false, Min Version: TLSv1_2
consul[82355]:       Internal RPC TLS: Verify Incoming: false, Verify Outgoing: false (Verify Hostname: false), Min Version: TLSv1_2
consul[82355]: ==> Log data will now stream in as it occurs:
consul[82355]: 2023-08-30T21:46:51.171Z [WARN]  agent: skipping file /etc/consul.d/.vault.hcl.swp, extension must be .hcl or .json, or config format must be set
consul[82355]: 2023-08-30T21:46:51.171Z [WARN]  agent: skipping file /etc/consul.d/consul.env, extension must be .hcl or .json, or config format must be set
consul[82355]: 2023-08-30T21:46:51.184Z [WARN]  agent.auto_config: skipping file /etc/consul.d/.vault.hcl.swp, extension must be .hcl or .json, or config format must be set
consul[82355]: 2023-08-30T21:46:51.184Z [WARN]  agent.auto_config: skipping file /etc/consul.d/consul.env, extension must be .hcl or .json, or config format must be set
consul[82355]: 2023-08-30T21:46:51.186Z [INFO]  agent.client.serf.lan: serf: EventMemberJoin: vault1 10.12.1.94
consul[82355]: 2023-08-30T21:46:51.186Z [INFO]  agent.router: Initializing LAN area manager
consul[82355]: 2023-08-30T21:46:51.189Z [WARN]  agent.client.serf.lan: serf: Failed to re-join any previously known node
consul[82355]: 2023-08-30T21:46:51.189Z [ERROR] agent: error creating OS Service client: error="not implemented"
consul[82355]: 2023-08-30T21:46:51.190Z [ERROR] agent: Error starting agent: error="Failed to register service \"vault\": not implemented"
consul[82355]: 2023-08-30T21:46:51.190Z [INFO]  agent: Exit code: code=1
systemd[1]: consul.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: consul.service: Failed with result 'exit-code'.
systemd[1]: Failed to start "HashiCorp Consul - A service mesh solution".
systemd[1]: consul.service: Scheduled restart job, restart counter is at 5.
systemd[1]: Stopped "HashiCorp Consul - A service mesh solution".
systemd[1]: consul.service: Start request repeated too quickly.
systemd[1]: consul.service: Failed with result 'exit-code'.
systemd[1]: Failed to start "HashiCorp Consul - A service mesh solution".

在谷歌上搜索这一点只能得到很少的结果,阅读代码也没有给我带来启发。
这是个窃听器吗?佩卡克?

d5vmydt9

d5vmydt91#

我也一直在努力解决这个问题,直到我在Consul源代码中做了一些挖掘:https://github.com/hashicorp/consul/blob/ac867d67e8240d64333483fdf3e234399740a189/agent/checks/os_service_unix.go#L15C43-L15C43

type OSServiceClient struct {
}

func NewOSServiceClient() (*OSServiceClient, error) {
    return nil, fmt.Errorf("not implemented")
}

func (client *OSServiceClient) Check(serviceName string) error {
    return fmt.Errorf("not implemented")
}

似乎只是...未执行。对于非Windows系统。有趣的是,文档表明它可用于systemd单元。
作为一种变通方法,在它可用之前,您可以始终执行systemctl is-active vault.service,如下所示:

{
  name = "Vault Service"
  args = [
    "systemctl",
    "is-active",
    "vault.service",
  ]
  interval = "15s"
},

相关问题