@kuldan5853 commented on GitHub (Aug 8, 2024):
I can add that this behavior also happens on the windows build of ABS 2.12.1
@rpgdev commented on GitHub (Aug 8, 2024):
Had the same crash happened on 2.12.1: `{"timestamp":"2024-08-08 13:23:54.961","source":"Server.js:171","message":"[Server] Unhandled rejection:…
@rpgdev commented on GitHub (Aug 8, 2024):
Docker container. Became unreachable last night, saw there was an update, restarted (~7:50) and all was good, so ignored. Today (~8:07) it died again.…
@mantas3 commented on GitHub (Aug 8, 2024):
@mantas3 What's TOD? Me wants!
@rpgdev time of death 😄 monitoring - uptime kuma https://github.com/louislam/uptime-kuma
@skyzuma commented on GitHub (Aug 8, 2024):
same here on unraid 6.12.11 with docker, updated to the latest version and unreachable ... w/o any logs ... only notification was my uptime kuma…
@migol commented on GitHub (Aug 8, 2024):
I can confirm 2.12.1 hanging for me at certain hour (23 local, 21 UTC) with single core at full load. Rolling back docker image to 2.11.0 solved…
@TheOtherLinusNoNotThatOne commented on GitHub (Aug 8, 2024):
Seeing this exact behaviour in a Debian LXC install. Every few hours ABS becomes unresponsive and one core is pegged at 100% usage.…
@pjv commented on GitHub (Aug 8, 2024):
@migol Thanks - 2.11.0 running again and looks fine so far; nothing adverse in the logs.
@darthrater78 commented on GitHub (Aug 8, 2024):
Exact same issues as others here. Running in an LXC container, ABS goes unresponsive after a bit and restarting seems to fix it. Checking my…
@nichwall commented on GitHub (Aug 8, 2024):
It is only the CPU which is spiking for everyone, correct? RAM, disk, and network appear normal?
@darthrater78 commented on GitHub (Aug 8, 2024):
It is only the CPU which is spiking for everyone, correct? RAM, disk, and network appear normal?
It was only CPU for me.
@macr0dev commented on GitHub (Aug 8, 2024):
I have woken up the past two mornings to find my docker installation of ABS unresponsive in the same manner as everyone else here. No logs indicating…
@PulsarFTW commented on GitHub (Aug 8, 2024):
It is only the CPU which is spiking for everyone, correct? RAM, disk, and network appear normal?
My RAM was around ~500mb, but I have no idea if…
@die3lust1gen2 commented on GitHub (Aug 7, 2024):
Noticed the same after updating to 2.12.1. Happend two times so far after about 24h. My monitoring reported that the app timed out and the CPU…
@babatonga commented on GitHub (Aug 8, 2024):
I encountered a similar issue after updating to version 2.12.1 yesterday. Approximately 24 hours later, the instance became unreachable. There were…
@BerendWouters commented on GitHub (Aug 7, 2025):
It was a networking issue indeed. My
docker/daemon.jsonalso had the ip address of the docker server itself, which the internal networking…
@0o-IN10SE-o0 commented on GitHub (Aug 8, 2024):
Sadly same issue here. I would like to provide something to solve it but nothing shown. Server was running on previous update for some weeks…
@PulsarFTW commented on GitHub (Aug 8, 2024):
So, exactly 24 hours after last (re)starting the server it has become unreachable. CPU usage of the container has spiked to 12.5% (so one core). I am…
@mantas3 commented on GitHub (Aug 8, 2024):
Docker container. Became unreachable last night, saw there was an update, restarted (~7:50) and all was good, so ignored. Today (~8:07) it died again.…
@pjv commented on GitHub (Aug 8, 2024):
I’m running with docker and experiencing the same issue daily after upgrading from 2.11.0 to 2.12.1.
Can anyone tell me if it’s safe to simply…