MineOS stuck in deploying

[Gulli03]

The Kubernetes Events:

09.08.2024 12:19:37
Startup probe failed: dial tcp 172.16.0.178:30015: connect: connection refused
09.08.2024 12:19:23
Created container mineos
09.08.2024 12:19:23
Started container mineos
09.08.2024 12:19:22
Add eth0 [172.16.0.178/16] from ix-net
09.08.2024 12:19:22
Container image "hexparrot/mineos:latest" already present on machine
09.08.2024 12:19:21
Scaled up replica set mineos-5cc75b894d to 1
09.08.2024 12:19:21
Created pod: mineos-5cc75b894d-84w64
09.08.2024 12:19:21
Successfully assigned ix-mineos/mineos-5cc75b894d-84w64 to ix-truenas
09.08.2024 12:13:17
Scaled down replica set mineos-595b7cb857 to 0 from 1
09.08.2024 12:13:17
Deleted pod: mineos-595b7cb857-2mzvs
08.08.2024 23:28:32
Startup probe failed: dial tcp 172.16.0.55:30015: connect: connection refused

The Logs:

2024-08-09T12:29:49.350349329+02:00 Created group: minecraft (gid: 568)
2024-08-09T12:29:50.157422169+02:00 Created user: minecraft (uid: 568, gid: 568)
2024-08-09T12:29:50.157521321+02:00 Setting user password for 'minecraft'
2024-08-09T12:29:50.202031344+02:00 Setting use_https to:  false
2024-08-09T12:29:50.207573593+02:00 Setting server port to: 30015
2024-08-09T12:29:50.212508055+02:00 Skipping Self-Signed SSL, it either exists or is disabled.
2024-08-09T12:29:50.212774942+02:00 Setting https to false
2024-08-09T12:29:50.373668805+02:00 2024-08-09 10:29:50,373 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-08-09T12:29:50.373695989+02:00 2024-08-09 10:29:50,373 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2024-08-09T12:29:50.376973525+02:00 2024-08-09 10:29:50,376 INFO RPC interface 'supervisor' initialized
2024-08-09T12:29:50.377029435+02:00 2024-08-09 10:29:50,377 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-08-09T12:29:50.377280013+02:00 2024-08-09 10:29:50,377 INFO supervisord started with pid 1
2024-08-09T12:29:51.382391688+02:00 2024-08-09 10:29:51,381 INFO spawned: 'mineos' with pid 32
2024-08-09T12:29:51.593831460+02:00 2024-08-09 10:29:51,593 INFO exited: mineos (exit status 1; not expected)
2024-08-09T12:29:52.595148491+02:00 2024-08-09 10:29:52,594 INFO spawned: 'mineos' with pid 43
2024-08-09T12:29:52.797056539+02:00 2024-08-09 10:29:52,796 INFO exited: mineos (exit status 1; not expected)
2024-08-09T12:29:54.799956003+02:00 2024-08-09 10:29:54,799 INFO spawned: 'mineos' with pid 54
2024-08-09T12:29:55.009683569+02:00 2024-08-09 10:29:55,009 INFO exited: mineos (exit status 1; not expected)
2024-08-09T12:29:58.017160331+02:00 2024-08-09 10:29:58,016 INFO spawned: 'mineos' with pid 65
2024-08-09T12:29:58.236742038+02:00 2024-08-09 10:29:58,236 INFO exited: mineos (exit status 1; not expected)
2024-08-09T12:29:59.238406703+02:00 2024-08-09 10:29:59,238 INFO gave up: mineos entered FATAL state, too many start retries too quickly

If there is any more information I can give, just let me know.

[stavros-k]

Hello, I cannot reproduce locally. And logs does not seem to give any indications on what's wrong.
You could try reaching to the upstream developer to see if they can give details on how to access more verbose logs.

Thanks