search

louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
55.84k stars 5.02k forks source link

[docker] `exec /usr/bin/dumb-init: input/output error` #4259

Closed miselve closed 6 months ago

miselve commented 9 months ago

⚠️ Please verify that this bug has NOT been raised before.

🛡️ Security Policy

📝 Describe your problem

I was using Uptime Kuma on docker for sometime now. After I updated to 1.23.10 It refused to start stating exec /usr/bin/dumb-init: input/output error . Some system details: Raspberry Pi 5 4GB running Raspbian. If I leave it running it crashes my whole Raspberry.

I use the following command to run the container: (as suggested in the documentation) docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

PS. I am using portainer to manage all my containers.

📝 Error Message(s) or Log

exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error exec /usr/bin/dumb-init: input/output error And it keeps going...

🐻 Uptime-Kuma Version

1.23.10

💻 Operating System and Arch

Raspbian ARM64

🌐 Browser

Chrome 120.0.6099.72

🐋 Docker Version

24.0.7

🟩 NodeJS Version

No response

louislam commented 9 months ago

According to this, you are using a image of wrong arch for some reason.

https://github.com/apache/airflow/discussions/30925

How did you update the image?

miselve commented 9 months ago

According to this, you are using a image of wrong arch for some reason.

apache/airflow#30925

How did you update the image?

I rm'ed the old container and pulled the :latest again. I kept the persistent storage and the new container was executed with docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

Any suggestions?

louislam commented 9 months ago

Check the image hash first, see if it is using the correct arch.

miselve commented 9 months ago

Check the image hash first, see if it is using the correct arch.

The image issha256:ac6ddd03f1217030c36fc06c0894ceb840ffb9fa1414104db7b6941010714506

image
louislam commented 8 months ago

Check the image hash first, see if it is using the correct arch.

The image issha256:ac6ddd03f1217030c36fc06c0894ceb840ffb9fa1414104db7b6941010714506 image

It's a correct image. I have no idea actually and cannot reproduce.

My instance https://uptime.kuma.pet is working fine and it is also on arm64.

chakflying commented 8 months ago

With how little information is related to this error, I think it's more likely a disk corruption issue:

https://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory

The fact that your whole OS crashes also support this theory. Are you using an old SD card for storage? Maybe you should check the linux logs for disk errors.

github-actions[bot] commented 6 months ago

We are clearing up our old help-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

prljav commented 4 months ago

pretty sure, for some reason(???) uptime kuma does a lotttttt of mostly writes probably and reads which either damages your sd card or does something weird to the controller, just happened to me as well.

CommanderStorm commented 4 months ago

uptime kuma does mostly writes

In v1 the heartbeats are stored in an unaggregated fassion. => one heartbeat = one column in the heatbeat table

In v2 we changed this to be agregated. See #4500 for futrther details

Generally, I would not use a SD-Card to run a production project on if it includes persistent IO. The reliability of SD cards is just too low imo and the price of cheap name/.. ssds too good

prljav commented 4 months ago

Generally, I would not use a SD-Card to run a production project on if it includes persistent IO. The reliability of SD cards is just too low imo and the price of cheap name/.. ssds too good

yea... tell that to rpi foundation

CommanderStorm commented 4 months ago

tell that to rpi foundation

They offer a hat which integrates with their case and everything. See @geerlingguy's video on this topic https://youtu.be/GYN3ub8Qb_I

There are also many boards that build ontop of the compute module offer ssd as a first classs citizen.