Hi there, on OMV with latest updates, the S3 plugin doesn't show up it's interface and doesn't provide the API service.
I restarted the plugin, rebooted OMV, uninstalled the plugin, reinstalled, to no avail.
Any ideas to help please?
I used it correctly 15 days ago, the only change I did in between is apply latest OMV updates
Many thanks!
There was a community contribution. I hope it does not introduce a regression.
Thanks votdev. I suspect this is the issue but I don't know where to look for it. I will restore my previous backup of OMV's VM
Humm, I restored my OMV backup and I the issue is there already. The strange thing is that I backed up to it a bit less than 3 weeks ago without issue (this machine isn't live all the time)
I don't understand what's going on my system
Shouldn't podman run for the minio container to run? By logs seem to say otherwise:
○ podman.service - Podman API Service
Loaded: loaded (/lib/systemd/system/podman.service; enabled; preset: enabled)
Active: inactive (dead) since Wed 2024-08-14 17:46:11 CEST; 5min ago
Duration: 5.093s
TriggeredBy: ● podman.socket
Docs: man:podman-system-service(1)
Process: 2720 ExecStart=/usr/bin/podman $LOGGING system service (code=exited, status=0/SUCCESS)
Main PID: 2720 (code=exited, status=0/SUCCESS)
CPU: 151ms
Aug 14 17:46:05 charybde systemd[1]: Starting podman.service - Podman API Service...
Aug 14 17:46:05 charybde systemd[1]: Started podman.service - Podman API Service.
Aug 14 17:46:05 charybde podman[2720]: time="2024-08-14T17:46:05+02:00" level=info msg="/usr/bin/podman filtering at log level info"
Aug 14 17:46:06 charybde podman[2720]: time="2024-08-14T17:46:06+02:00" level=info msg="[graphdriver] using prior storage driver: overlay"
Aug 14 17:46:06 charybde podman[2720]: time="2024-08-14T17:46:06+02:00" level=info msg="Setting parallel job count to 7"
Aug 14 17:46:06 charybde podman[2720]: time="2024-08-14T17:46:06+02:00" level=info msg="Using systemd socket activation to determine API endpoint"
Aug 14 17:46:06 charybde podman[2720]: time="2024-08-14T17:46:06+02:00" level=info msg="API service listening on \"/run/podman/podman.sock\". URI: \"/run/podman/podman.sock\""
Aug 14 17:46:11 charybde systemd[1]: podman.service: Deactivated successfully.
I had to remove all cookies to be able to log into the UI.
Not sure what is going on. I tried to restart the services, but they keep dying almost instantly:
systemctl status container-minio-app.service
○ container-minio-app.service - Podman container-minio-app.service
Loaded: loaded (/etc/systemd/system/container-minio-app.service; disabled; preset: enabled)
Active: inactive (dead) (Result: exit-code) since Wed 2024-08-14 19:25:33 CEST; 2s ago
Duration: 610ms
Process: 24764 ExecStartPre=/bin/rm -f /run/container-minio-app.pid /run/container-minio-app.ctr-id (code=exited, status=0/SUCCESS)
Process: 24765 ExecStart=/usr/bin/podman run --conmon-pidfile /run/container-minio-app.pid --cidfile /run/container-minio-app.ctr-id --cgroups=no-conmon --pod-id-file /run/p>
Process: 24791 ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile /run/container-minio-app.ctr-id (code=exited, status=0/SUCCESS)
Main PID: 24775 (code=exited, status=127)
CPU: 613ms
and
pod-minio.service - Podman pod-minio.service
Loaded: loaded (/etc/systemd/system/pod-minio.service; enabled; preset: enabled)
Active: activating (start) since Wed 2024-08-14 19:27:04 CEST; 554ms ago
Process: 32901 ExecStartPre=/bin/rm -f /run/pod-minio.pid /run/pod-minio.pod-id (code=exited, status=0/SUCCESS)
Process: 32902 ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile /run/pod-minio.pid --pod-id-file /run/pod-minio.pod-id --name=minio -p 9010:9000 -p 9001:9001 ->
Cntrl PID: 32950 (podman)
Tasks: 9 (limit: 8254)
Memory: 12.1M
CPU: 492ms
CGroup: /system.slice/pod-minio.service
├─32950 /usr/bin/podman pod start --pod-id-file /run/pod-minio.pod-id
└─32976 /usr/lib/cni/firewall
I'm not sure I understand what the contribution was but if using Caddy, as I'm using Traefik in a container using of course port 443, could it be a conflict between Caddy and Traefik?
If you have not enabled SSL in the S3 plugin nothing will change for you.
I did self-issued the certificate and therefore SSL back in 2023. The certificate has expired, I just realized that and I recreated it.
But now that I have restored the VM, the past month updates have not been applied, so I suspect the changes to the S3 plugin might not be the cause
If it can help the plugin devs, I get these errors messages:
Aug 21 13:24:33 charybde minio-app[1283]: Fatal glibc error: CPU does not support x86-64-v2
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.6590006,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"c>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"warn","ts":1724239474.6677349,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies",>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"warn","ts":1724239474.668371,"logger":"admin","msg":"admin endpoint disabled"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.67381,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"warn","ts":1724239474.6880357,"logger":"tls","msg":"stapling OCSP","error":"no OCSP stapling for [charybde]: no OCSP server>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.6882966,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7090623,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/data/caddy"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7092001,"logger":"tls","msg":"finished cleaning storage units"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7104805,"logger":"http.log","msg":"server running","name":"remaining_auto_https_redirects","protocols>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7106247,"logger":"http","msg":"enabling HTTP/3 listener","addr":":9001"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.712585,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, go>
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.712789,"logger":"http.log","msg":"server running","name":"srv0","protocols":["h1","h2","h3"]}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7159166,"msg":"autosaved config (load with --resume flag)","file":"/config/caddy/autosave.json"}
Aug 21 13:24:34 charybde minio-proxy[1299]: {"level":"info","ts":1724239474.7159798,"msg":"serving initial configuration"}
Aug 21 13:24:35 charybde minio-proxy[1299]: {"level":"info","ts":1724239475.6454875,"msg":"shutting down apps, then terminating","signal":"SIGTERM"}
Aug 21 13:24:35 charybde minio-proxy[1299]: {"level":"warn","ts":1724239475.6455936,"msg":"exiting; byeee!! 👋","signal":"SIGTERM"}
Aug 21 13:24:35 charybde minio-proxy[1299]: {"level":"info","ts":1724239475.6481125,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":">
Aug 21 13:24:35 charybde minio-proxy[1299]: {"level":"info","ts":1724239475.6482327,"msg":"shutdown complete","signal":"SIGTERM","exit_code":0}
Aug 21 13:24:42 charybde minio-app[2278]: Fatal glibc error: CPU does not support x86-64-v2
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"info","ts":1724239482.7308319,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":"c>
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"warn","ts":1724239482.7485042,"msg":"Caddyfile input is not formatted; run the 'caddy fmt' command to fix inconsistencies",>
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"warn","ts":1724239482.751133,"logger":"admin","msg":"admin endpoint disabled"}
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"info","ts":1724239482.7515512,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":">
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"warn","ts":1724239482.7528656,"logger":"tls","msg":"stapling OCSP","error":"no OCSP stapling for [charybde]: no OCSP server>
Aug 21 13:24:42 charybde minio-proxy[2276]: {"level":"info","ts":1724239482.7543252,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}Don’t have an account yet? Register yourself now and be a part of our community!