search

fmartinou / whats-up-docker

What's up Docker ( aka WUD ) gets you notified when a new version of your Docker Container is available.
https://fmartinou.github.io/whats-up-docker
MIT License
983 stars 32 forks source link

WUD container is crashing #275

Open attilabalazsy opened 1 year ago

attilabalazsy commented 1 year ago

I'm having issues with WUD as it continuesly crashing after couple of days/hours. The crash is mostly related to some communication or parsing issues, so most probably because of an incorrect error handling.

WUD is monitoring 3 docker instances, one is running locally and 2 are accessed through TCP. WUD is running on RPI4 (ARMv8)

This is the stack trace from the last crash: 23:00:00.742 INFO whats-up-docker/watcher.docker.rpi4: Cron started (0 ) 23:00:13.565 INFO whats-up-docker/watcher.docker.rpi2: Cron finished (6 containers watched, 0 errors, 1 available updates) 23:00:15.464 INFO whats-up-docker/watcher.docker.rpi4: Cron finished (12 containers watched, 0 errors, 3 available updates) 23:00:15.633 WARN whats-up-docker/watcher.docker.docker02: Error when processing (502 - "

502 Bad Gateway

\nThe server returned an invalid or incomplete response.\n\n\n") (container=docker02_Container-health-check) 23:00:15.637 WARN whats-up-docker/watcher.docker.docker02: Error when processing some containers (Cannot read properties of undefined (reading 'tag')) 23:00:15.637 INFO whats-up-docker/watcher.docker.docker02: Cron finished (0 containers watched, 0 errors, 0 available updates) 23:15:53.534 INFO whats-up-docker/watcher.docker.docker02: Status changed from running to exited (container=docker02_ntfy) 23:15:57.605 INFO whats-up-docker/watcher.docker.docker02: Status changed from running to exited (container=docker02_uptime-kuma) 23:15:57.790 INFO whats-up-docker/watcher.docker.docker02: Status changed from running to exited (container=docker02_apprise) undefined:1 {"status":"create","id":"1a334ca38afd163d150f843df9c3c8ad218613b55e153ea74deb579dc5d49c16","from":"linuxserver/apprise-api","Type":"container","Action":"create","Actor":{"ID":"1a334ca38afd163d150f843df9c3c8ad218613b55e153ea74deb579dc5d49c16","Attributes":{"build_version":"Linuxserver.io version:- v0.9.0-ls67 Build-date:- 2023-04-03T05:02:18-05:00","com.docker.compose.config-hash":"30bccceeb345cb4d152861613bb376068abd38e7d626354329dc30280ffa507d","com.docker.compose.container-number":"1","com.docker.compose.depends_on":"","com.docker.compose.image":"sha256:48cac8ed2b836ba0c44d96d1d8e6ac86c7d12b285495e70d4ac8fee4237d6964","com.docker.compose.oneoff":"False","com.docker.compose.project":"tools","com.docker.compose.project.config_files":"/data/compose/48/docker-compose.yml","com.docker.compose.project.working_dir":"/data/compose/48","com.docker.compose.service":"apprise","com.docker.compose.version":"2.13.0","image":"linuxserver/apprise-api","maintainer":"Roxedus","name":"apprise","org.opencontainers.image.authors":"linuxserver.io","org.opencontainers.image.created":"2023-04-03T05:02:18-05:00","org.opencontainers.image.description":"Apprise-api Takes advantage of Apprise through your network with a user-friendly API. Send notifications to more then 65+ services. An incredibly lightweight gateway to Apprise. * A production ready micro-service at your disposal. Apprise API was designed to easily fit into existing (and new) eco-systems that are looking for a simple notification solution. ","org.opencontainers.image.documentation":"https://docs.linuxserver.io/images/docker-apprise-api","org.opencontainers.image.licenses":"GPL-3.0-only","org.opencontainers.image.ref.name":"9b00490ab0f3e7373807c8e0e6e3c71e4eb66d56","org.opencontainers.image.revision":"9b00490ab0f3e7373807c8e0e6e3c71e4eb66d56","org.opencontainers.image.source":"https://github.com/linuxserver/docker-apprise-api","org.opencontainers.image.title":"Apprise-api","org.opencontainers.image.url":"https://github.com/linuxserver/docker-apprise-api/packages","org.opencontainers.image.vendor":"linuxserver.io","org.opencontainers.image.version":"v0.9.0-ls67","traefik.docker.network":"proxy","traefik.enable":"true","traefik.http.middlewares.notify-https-redirect.redirectscheme.scheme":"https","traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto":"https","traefik.http.routers.notify-secure.entrypoints":"https","traefik.http.routers.notify-secure.middlewares":"cloudflare-real-ip@file, authelia@file","traefik.http.routers.notify-secure.rule":"Host(*****.cloud)","traefik.http.routers.notify-secure.tls":"true","traefik.http.routers.notify.entrypoints":"http","traefik.http.routers.notify.middlewares":"notify-https-redirect","traefik.http.routers.notify.rule":"Host(`notify. SyntaxError: Unexpected end of JSON input at JSON.parse () at Docker.onDockerEvent (/home/node/app/watchers/providers/docker/Docker.js:324:34) at IncomingMessage. (/home/node/app/watchers/providers/docker/Docker.js:313:51) at IncomingMessage.emit (node:events:513:28) at IncomingMessage.emit (node:domain:489:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at IncomingMessage.Readable.push (node:internal/streams/readable:228:10) at HTTPParser.parserOnBody (node:_http_common:140:24) at HTTPParser.execute () at Socket.socketOnData (node:_http_client:534:22) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at addChunk (node:internal/streams/readable:315:12) at readableAddChunk (node:internal/streams/readable:289:9) at Socket.Readable.push (node:internal/streams/readable:228:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

mcarlosro commented 1 year ago

I also have the same error. Restarting WUD solve the problem but not sure why this is happening. I have WUD working all day but on a NAS restart (every morning) WUD crashes.