我的MinIO API正在监听服务器的IP和端口9000。效果很好。
但是,如果我试图将端口更改为80并重新启动服务,则无法启动:
● minio.service - MinIO
Loaded: loaded (/etc/systemd/system/minio.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-10-25 12:37:04 CEST; 1s ago
Docs: https://docs.min.io
Process: 27026 ExecStartPre=/bin/bash -c if [ -z "${MINIO_VOLUMES}" ]; then echo "Variable MINIO_VOLUMES not set in>
Process: 27027 ExecStart=/usr/local/bin/minio server $MINIO_OPTS $MINIO_VOLUMES (code=exited, status=1/FAILURE)
Main PID: 27027 (code=exited, status=1/FAILURE)
Oct 25 12:37:03 hel-sto-01 systemd[1]: minio.service: Main process exited, code=exited, status=1/FAILURE
Oct 25 12:37:03 hel-sto-01 systemd[1]: minio.service: Failed with result 'exit-code'.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Scheduled restart job, restart counter is at 5.
Oct 25 12:37:04 hel-sto-01 systemd[1]: Stopped MinIO.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Start request repeated too quickly.
Oct 25 12:37:04 hel-sto-01 systemd[1]: minio.service: Failed with result 'exit-code'.
Oct 25 12:37:04 hel-sto-01 systemd[1]: Failed to start MinIO.这是一个全新的Ubuntu20.04服务器,我没有任何监听端口80的内容。
当我回到端口9000时,MinIO就正常工作了。
请协助。
发布于 2021-10-25 11:24:45
是否在minio.service单元文件中设置了非特权用户?
默认minio.service使用非特权用户。
注意:如果要绑定到端口< 1024,且服务以常规用户的身份运行,则需要通过AmbientCapabilities文件中的minio.service指令添加绑定功能:
[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
WorkingDirectory=/usr/local/https://serverfault.com/questions/1081607
复制相似问题