Pimatic dumps - JS stack trace

---

Hi all,
hope someone can help me with this. My SSD has crash. Fortunately I run my pimatic system on a VM in Proxmox. After I restored my system on a new installed proxmox on a new SSD. I went into following problem. I have a similar problem on a Raspi when I copy the last config.json to a fresh installed pimatic.

<--- Last few GCs --->

[3524:0x3dd18f0]   121812 ms: Mark-sweep 1255.7 (1420.5) -> 1255.7 (1384.0) MB, 1468.0 / 0.0 ms  (average mu                  = 0.337, current mu = 0.000) last resort GC in old space requested
[3524:0x3dd18f0]   123343 ms: Mark-sweep 1255.7 (1384.0) -> 1255.7 (1379.0) MB, 1530.3 / 0.0 ms  (average mu                  = 0.194, current mu = 0.000) last resort GC in old space requested


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x2aaa5a25be1d]
Security context: 0x2c98e141e6e9 <JSObject>
    1: arrayMove(aka arrayMove) [0x291cf15ca7c9] [/home/ortin/pimatic-app/node_modules/pimatic/node_modules/                 bluebird/js/release/queue.js:~2] [pc=0x2aaa5a674dd5](this=0x0cd430e026f1 <undefined>,src=0x02b11ecc6229 <Que                 ue map = 0x21a2ba40f041>,srcIndex=0,dst=0x02b11ecc6229 <Queue map = 0x21a2ba40f041>,dstIndex=4194304,len=171                 3096)
    2: _resizeTo [0x872f36ea17...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: 0x8fa0c0 node::Abort() [node]
 2: 0x8fa10c  [node]
 3: 0xb0026e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xb004a4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xef49b2  [node]
 6: 0xf041cf v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal                 ::AllocationAlignment) [node]
 7: 0xecd226 v8::internal::Factory::AllocateRawArray(int, v8::internal::PretenureFlag) [node]
 8: 0xecdaaa v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::inte                 rnal::Object*, v8::internal::PretenureFlag) [node]
 9: 0xece067 v8::internal::Factory::NewUninitializedFixedArray(int, v8::internal::PretenureFlag) [node]
10: 0xe8f7e0  [node]
11: 0xe8fa9f  [node]
12: 0x100684e v8::internal::JSObject::AddDataElement(v8::internal::Handle<v8::internal::JSObject>, unsigned                  int, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::ShouldThrow                 ) [node]
13: 0x101ffb2 v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::                 internal::Object>, v8::internal::PropertyAttributes, v8::internal::ShouldThrow, v8::internal::Object::StoreF                 romKeyed) [node]
14: 0x103aacd v8::internal::Object::SetProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::inte                 rnal::Object>, v8::internal::LanguageMode, v8::internal::Object::StoreFromKeyed) [node]
15: 0x1195c75 v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::inte                 rnal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::i                 nternal::LanguageMode) [node]
16: 0x1196dd0 v8::internal::Runtime_SetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [node]
17: 0x2aaa5a25be1d
Aborted

I am on node version:

ortin@proxmox-pimatic:~$ node -v
v10.16.3

Any idea?

I found the problem. My old config contains an external HDD where I have stored my cam recordings. In the current intermediate solution I skipped this HDD.
I have three related rules for this missing HDD in my pimatic config. The system was not able to start due to this simple rules like:

    {
      "id": "festplattenspeicher-alarm",
      "name": "Festplattenspeicher Alarm",
      "rule": "when $festplatte >= 90 then execute \"$sendeTelegramText 'Festplattenbelegung liegt bei über $festplatte%!' Daniel\"",
      "active": true,
      "logging": true
    },

Any idea how I can extend the command df -h | grep motionEye | awk '{print $5}' | cut -c 1-2 so that it works regardless of whether the disk is attached or not?

    {
      "attributeName": "festplattenspeicher",
      "attributeType": "number",
      "command": "df -h | grep motionEye | awk '{print $5}' | cut -c 1-2",
      "interval": 60000,
      "id": "festplattenspeicher",
      "name": "Festplatte",
      "class": "ShellSensor",
      "echo": {}
    },

Currently I put there an echo 0 to bring the system up…