# Node-red-contrib-inspector fail with 32 bits os?

**URL:** <https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461>\
**Category:** General\
**Tags:** function-node\
**Created:** [1 October 2022 16:51 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461 "2022-10-01T16:51:56Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [7 October 2022 11:45 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/61 "2022-10-07T11:45:54Z")

</div>

I'm no expert in tuning a Raspberry Pi but the 100% swap space usage looks really bad news.  
I suspect that until you fix that, there's little point in hunting for guilty processes.

Maybe you can find something useful in [https://haydenjames.io/raspberry-pi-performance-add-zram-kernel-parameters/](https://haydenjames.io/raspberry-pi-performance-add-zram-kernel-parameters/)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2022 12:41 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/62 "2022-10-07T12:41:52Z")

</div>

You can change the htop display to view as a process hierarchy which is useful when trying to make sense of more complex applications.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/f/afe45aed041a87c2d2c257b9048f3f39fc56eb59.png)

It is best to look at the mem % rather than virtual mem.

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/e/3e01e22ccfc274223ff653c1a75dd7e3a62cc46a.png)

You seem to have a lot of InfluxDB threads running. My live system only has 1.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/1/c1e915314aa5592c697e14c7f68c03fe0bd191e0.png)

* * *

OK, I've spotted your problem.

You are running a Linux desktop - you need to get rid of that and run headless only.

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 13:18 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/63 "2022-10-07T13:18:24Z")

</div>

> [@TotallyInformation](#):
>
> OK, I've spotted your problem.
> 
> You are running a Linux desktop - you need to get rid of that and run headless only.

Do I really get rid of that, does that make all the difference in the world, or just a bit better?

I just love the desktop!! I also make use of SD Card copier. With this tool I can easily make perfect backups while running Node-red etc.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2022 13:43 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/64 "2022-10-07T13:43:37Z")

</div>

> [@henkkas](#):
>
> Do I really get rid of that, does that make all the difference in the world, or just a bit better?

It makes a MASSIVE difference 🙂 On a Pi3 with limited memory and cores, it is devastating to overall performance.

> [@henkkas](#):
>
> I just love the desktop!!

Get another Pi3 😉

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 13:56 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/65 "2022-10-07T13:56:53Z")

</div>

> [@TotallyInformation](#):
>
> You seem to have a lot of InfluxDB threads running. My live system only has 1.

Why do I have so many threads (17) running? And you only one?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2022 14:13 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/66 "2022-10-07T14:13:51Z")

</div>

Not sure, I think it has something to do with sharding in the database but I'm no expert in this area I'm afraid. I think that the db just got too complex. At least as an experiment, you might want to create a new db with the config as recommended previously and see how that looks. Also check the db sizes. My combined size for all dbs is currently 378M.

This command will show you the total size:

```auto
sudo du -sh /var/lib/influxdb/data/

```

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 14:16 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/67 "2022-10-07T14:16:31Z")

</div>

My size is 185M

Seem to be smaller then yours.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [7 October 2022 14:24 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/68 "2022-10-07T14:24:36Z")

</div>

OK. Here is my breakdown:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/a/0ad5913407b3d9007d19b85459a712aa6bc9dc24.png)

Unsurprisingly, the Telegraf db is largest since it is capturing loads of system data every 10s or so. Even though I only keep the data for a week. The `home` db is split into 2 as mentioned previously.

How often are you writing to the db?

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 14:37 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/69 "2022-10-07T14:37:58Z")

</div>

![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/8/88724ce9081d80a6fbacf91eea6758a9fe5073e6.png)

 ![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/6/d658262b440b29cf3a8e190dcb852777dfeef115.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2022 14:58 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/70 "2022-10-07T14:58:24Z")

</div>

Have a look at the influx log and see what it is doing.

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 15:12 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/71 "2022-10-07T15:12:07Z")

</div>

I don't see weird things, looks good to me, Colin

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2022 15:17 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/72 "2022-10-07T15:17:56Z")

</div>

If you tail the log is it running continuously or are there time gaps in it? Have you got it set to show the queries being run?

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [7 October 2022 16:59 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/73 "2022-10-07T16:59:16Z")

</div>

I used this command:

> sudo journalctl -u influxdb.service

And in the output log I see indeed the queries that I run, I don't know what you mean by time gaps?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [7 October 2022 20:03 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/74 "2022-10-07T20:03:28Z")

</div>

I mean was it continually outputing log lines (as if maybe it cannot keep up) or ws it intermittent, with at least short gaps of inactivity.

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [8 October 2022 13:00 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/75 "2022-10-08T13:00:53Z")

</div>

Yes, indeed, Colin, it is continuously outputing data as expected. I don't see any gaps.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 October 2022 13:31 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/76 "2022-10-08T13:31:12Z")

</div>

> [@henkkas](#):
>
> it is continuously outputing data as expected

If it is continually outputing data then perhaps it is not keeping up with what it is trying to do.

Running `sudo iotop` may be interesting. That will show you (in the IO\> column) how much of a processes time is spent waiting for IO (so waiting for the SD card in this case).  
If iotop is not installed then  
`sudo apt install iotop`

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [8 October 2022 14:18 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/77 "2022-10-08T14:18:08Z")

</div>

![afbeelding](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/7/375c112a8ffee1713458e4db020debdf8964e199.png)

In IO column I sometimes see max.value of about 2% for Influxd

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 October 2022 14:25 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/78 "2022-10-08T14:25:00Z")

</div>

> [@henkkas](#):
>
> I sometimes see max.value of about 2% for Influxd

That's ok, if it were tens of percent then I would be worried.

---

<div class="post-metadata">

**Author:** ![henkkas](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/henkkas/32/39844_2.png) [@henkkas](https://discourse.nodered.org/u/henkkas)\
**Post date:** [8 October 2022 14:38 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/79 "2022-10-08T14:38:20Z")

</div>

@Colin @jbudd @dceejay @TotallyInformation @BartButenaers

I now think that something went wrong about 2 or maybe 3 weeks ago during minor change and consecutive incremental compile. I have experienced wrongful compiles before, but only minor faults. One time a changed node gives completely weird messages, after replacing node with new one and compile problem was over. One time a changed or placed new node and after compile this node gave 2 output messages with 1 input message. So I am worried something must have gone wrong during this minor change, that resulted in high cpu usage.

As I might never find this problem, I have decided to rebuild my project on second RPI. And I am now in the process of doing just that.

I think I can manage that, but I have just one question for now. I have a lot of settings in global data.  
Is it possible to backup the data to a file in order to restore later on new system?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [8 October 2022 14:41 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/80 "2022-10-08T14:41:30Z")

</div>

> [@henkkas](#):
>
> after compile this node gave 2 output messages with 1 input message

What do you mean by 'compile'?

[Previous page](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461.md?page=3)

[Next page](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461.md?page=5)