我用https://www.digitalocean.com/community/tutorials/how-to-set-up-an-object-storage-server-using-minio-on-ubuntu-18-04.的指南在ubuntu18.04上配置了一个minio实例服务器
安装后,服务器无法使用命令"sudo systemctl start minio“启动,错误是:
root@iZbp1icuzly3aac0dmjz9aZ:~# sudo systemctl status minio
● minio.service - MinIO
Loaded: loaded (/etc/systemd/system/minio.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-12-23 17:11:56 CST; 4s ago
Docs: https://docs.min.io
Process: 9085 ExecStart=/usr/local/bin/minio server $MINIO_OPTS $MINIO_VOLUMES (code=exited, status=1/FAILURE)
Process: 9084 ExecStartPre=/bin/bash -c if [ -z "${MINIO_VOLUMES}" ]; then echo "Variable MINIO_VOLUMES not set in /etc/default/minio"; exit 1; fi (code=exited, status=0/SUCCESS)
Main PID: 9085 (code=exited, status=1/FAILURE)
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Failed with result 'exit-code'.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Service hold-off time over, scheduling restart.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Scheduled restart job, restart counter is at 5.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: Stopped MinIO.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Start request repeated too quickly.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: minio.service: Failed with result 'exit-code'.
Dec 23 17:11:56 iZbp1icuzly3aac0dmjz9aZ systemd[1]: Failed to start MinIO.
It looks like the reason is the Variable MINIO_VOLUMES not set in /etc/default/minio.但是,我再次检查了/etc/default/minio中的文件
MINIO_ACCESS_KEY="minioadmin"
MINIO_VOLUMES="/usr/local/share/minio/"
MINIO_OPTS="-C /etc/minio --address localhost:9001"
MINIO_SECRET_KEY="minioadmin"
I have set the value MINIO_VOLUMES.我试着用minio服务器手动启动--地址:9001 /usr/local/share/minio/,它可以工作。
现在我不知道通过使用systemctl启动minio启动minio服务器出了什么问题
发布于 2022-04-18 16:31:19
我建议尽可能坚持正式文件。它用于分布式部署,但唯一真正的改变是,您的MINIO_VOLUMES将用于单个节点/驱动器。
我建议在这里尝试多种方法:
minio.service并确保用户/组的存在MINIO_VOLUMES值的文件路径权限下面是为什么:
我猜想,如果没有看到更多的日志(这里的journalctl -u minio会有所帮助),这是两种情况的结合:
minio.service用户/组在/usr/local/share/minio路径上没有rwx权限,看看这些线文件中的minio.service --我假设这是根据DO指南中的说明使用的。
如果您的ls -al /usr/local/share/minio,我将冒险,它有用户和组的根权限,并限制写访问(如果有的话)。
希望这有助于进一步排除来自journalctl的至少10-20行的故障,因为它将显示实际的错误,而不仅仅是最终的退出消息。
https://stackoverflow.com/questions/71892066
复制相似问题