首页 > 解决方案 > Hashicorp - 保管库服务无法启动

问题描述

我在 Ubuntu 18.04 上设置了 Hashicorp - Vault (Vault v1.5.4)。我的后端是 Consul(与保险库在同一台服务器上运行的单个节点) - 领事服务已启动。

我的保管库服务无法启动

systemctl list-units --type=service | grep "vault"
vault.service                        loaded failed failed  vault service  

journalctl -xe -u vault
Oct 03 00:21:33 ubuntu2 systemd[1]: vault.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
- Unit vault.service has finished shutting down.
Oct 03 00:21:33 ubuntu2 systemd[1]: vault.service: Start request repeated too quickly.
Oct 03 00:21:33 ubuntu2 systemd[1]: vault.service: Failed with result 'exit-code'.
Oct 03 00:21:33 ubuntu2 systemd[1]: Failed to start vault service.
-- Subject: Unit vault.service has failed

vault config.json

 "api_addr": "http://<my-ip>:8200",
  storage "consul" {
   address = "127.0.0.1:8500"
    path    = "vault"
  },

Service config

StandardOutput=/opt/vault/logs/output.log
StandardError=/opt/vault/logs/error.log


cat /opt/vault/logs/error.log
cat: /opt/vault/logs/error.log: No such file or directory
cat /opt/vault/logs/output.log
cat: /opt/vault/logs/output.log: No such file or directory
sudo tail -f /opt/vault/logs/error.log  
tail: cannot open '/opt/vault/logs/error.log' for reading: No such file or 
directory


:/opt/vault/logs$ ls -al
total 8
drwxrwxr-x 2 vault vault 4096 Oct  2 13:38 .
drwxrwxr-x 5 vault vault 4096 Oct  2 13:38 ..

标签: consulhashicorp-vault

解决方案


经过多次调试,问题是愚蠢的混合 .hcl 和 .json (它们非常相似 - 但不同) - 在存储(如发布的)需要为 json 格式的东西之间剪切-粘贴。当错误消息什么也没说并且日志中没有任何内容时,问题当然会更加复杂。

"storage": {
    "consul": {
        "address": "127.0.0.1:8500",
         "path" : "vault"
    }
 },

有几个其他问题需要解决才能让它继续运行disable_mlock : true——打开 8200 的防火墙:sudo ufw allow 8200/tcp

终于完成了(相当开始)。


推荐阅读