Version 9.8.1 -> fatal error
fs-plugins opened this issue · comments
Node.js: v18.18.2
JS controler: 5.0.16
NPM: 9.8.1
on start of Adapter:
`
2023-11-19 06:12:24.271 - error: host.fs-ubuntu2022 Caught by controller[0]: <--- Last few GCs --->
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[0]: [197240:0x600c970] 68 ms: Mark-sweep 4.7 (6.6) -> 4.2 (6.6) MB, 6.1 / 0.0 ms (average mu = 0.780, current mu = 0.819) allocation failure; GC in old space requested
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[0]: [197240:0x600c970] 101 ms: Mark-sweep 5.4 (7.1) -> 4.5 (7.4) MB, 8.2 / 0.0 ms (average mu = 0.765, current mu = 0.753) allocation failure; scavenge might not succeed
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[1]: <--- JS stacktrace --->
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[2]: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[3]: 1: 0xb85bc0 node::Abort() [/usr/bin/node]
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[4]: 2: 0xa94834 [/usr/bin/node]
2023-11-19 06:12:24.272 - error: host.fs-ubuntu2022 Caught by controller[5]: 3: 0xd66d10 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[6]: 4: 0xd670b7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[7]: 5: 0xf447c5 [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[8]: 6: 0xf56cad v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[9]: 7: 0xf313ae v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[10]: 8: 0xf32777 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[11]: 9: 0xf12cc0 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]
2023-11-19 06:12:24.273 - error: host.fs-ubuntu2022 Caught by controller[12]: 10: 0xf0a734 v8::internal::FactoryBase::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[13]: 11: 0xf0cac8 v8::internal::FactoryBase::NewRawTwoByteString(int, v8::internal::AllocationType) [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[14]: 12: 0xf15f7c v8::internal::Factory::NewStringFromUtf8(v8::base::Vector const&, v8::internal::AllocationType) [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[15]: 13: 0xd75dc3 v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[16]: 14: 0xc6f629 node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Local*) [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[17]: 15: 0xb5aaca [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[18]: 16: 0xdc4e00 [/usr/bin/node]
2023-11-19 06:12:24.274 - error: host.fs-ubuntu2022 Caught by controller[19]: 17: 0xdc633f v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]
2023-11-19 06:12:24.275 - error: host.fs-ubuntu2022 Caught by controller[20]: 18: 0x1705c39 [/usr/bin/node]
`
I can't currently see any connection to Backitup in your log.
What are you doing exactly?
Which version of Backitup is installed?
Did you run iob fix? Please post the output of iob diag here
What are you doing exactly?
start adapter in tab 'Instanzen'
Which version of Backitup is installed?
2.9.3
Did you run iob fix?
yes
Please post the output of iob diag here
======================= SUMMARY =======================
v.2023-10-10
Static hostname: fs-ubuntu2022
Icon name: computer-vm
Chassis: vm
Virtualization: kvm
Operating System: Ubuntu 22.04.3 LTS
Kernel: Linux 6.2.0-36-generic
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _i440FX + PIIX, 1996_
Installation: kvm
Kernel: x86_64
Userland: amd64
Timezone: Europe/Berlin (CET, +0100)
User-ID: 1000
X-Server: false
Boot Target: graphical.target
Pending OS-Updates: 0
Pending iob updates: 0
Nodejs-Installation: /usr/bin/nodejs v18.18.2
/usr/bin/node v18.18.2
/usr/bin/npm 9.8.1
/usr/bin/npx 9.8.1
/usr/bin/corepack 0.19.0
Recommended versions are nodejs 18.18.2 and npm 9.8.1
Your nodejs installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 11G 2.8G 7.2G 43M 1.9G 8.8G
Swap: 2.0G 0B 2.0G
Total: 13G 2.8G 9.3G
Active iob-Instances: 22
Active repo(s): stable
ioBroker Core: js-controller 5.0.16
admin 6.12.0
ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: jsonl
Status admin and web instance:
+ system.adapter.admin.0 : admin : fs-ubuntu2022 - enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.1 : web : fs-ubuntu2022 - enabled, port: 8083, bind: 0.0.0.0, run as: admin
Objects: 11353
States: 9586
Size of iob-Database:
21M /opt/iobroker/iobroker-data/objects.jsonl
14M /opt/iobroker/iobroker-data/states.jsonl
=================== END OF SUMMARY ====================
I can't do anything with the error and don't see it in connection with Backitup.
Reinstall the adapter and restart the system completely
ok, I have installed version 2.8.7 stable
the problem probably occurred after the JS controller was updated.
Unfortunately I have to start and stop the adapter via script, because backups should be executed by day of the week. Because it is not adjustable, I solved it this way.