Odd problem with missing node types?

General
1

So I just came to look at my flows and found this message, I have not changed any nodes :thinking:

Flows stopped due to missing node types.

image

I check in pallet manager and see this -

image

Can anyone think what is going on, before I try a reboot, as this not the first time I have had odd problems of late.

I'm running on a Pi5 with Nvme drive, and have a niggling feeling it may be related to the drive or memory issues.

2

I would normally have said look for an issue on your SD-Card - much less likely on an SSD but have you run a check on it recently?

3

I checked smartctl and nvme error-log, no issues there.

4

What upgrades have you done recently (specifically NodeJS versions)

Also if you look at the file in questions what is on that (and the previous) lines (given it's line 2, post the first 10 lines)

5

No changes since the system was last seen working OK.

There appears to be nothing wrong with that file visually at least.

Just ran an fsck on both partitions, it did fix a couple of issues so hopefully that may help, I will have to wait and see :grimacing:

I have rebooted and now everything is working again.

Thanks

6

If the problem is with a dependent module, do an npm rebuild in the .node-red folder. That may also help. More extreme, delete the node_modules folder and then do npm install.

7

Node red stopped again, with a new problem -

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7fff52bbe280
----- Native stack trace -----
 1: 0xd1eff8  [node-red]
 2: 0x1fdecb0 V8_Fatal(char const*, ...) [node-red]
 3: 0x1167594 v8::internal::Scavenger::Process(v8::JobDelegate*) [node-red]
 4: 0x1168e5c v8::internal::ScavengerCollector::JobTask::ProcessItems(v8::JobDelegate*, v8::internal::Scavenger*) [node-red]
 5: 0x1168fac v8::internal::ScavengerCollector::JobTask::Run(v8::JobDelegate*) [node-red]
 6: 0x1c4db08 v8::platform::DefaultJobWorker::Run() [node-red]
 7: 0xd1f1c4  [node-red]
 8: 0x7fff53452030  [/lib/aarch64-linux-gnu/libc.so.6]
 9: 0x7fff534bbf5c  [/lib/aarch64-linux-gnu/libc.so.6]
nodered.service: Main process exited, code=killed, status=5/TRAP
nodered.service: Failed with result 'signal'.

After this it failed to start as global context was corrupted

Sep 11 08:43:51 raspberrypi Node-RED[408810]: 11 Sep 08:43:51 - [error] Error: Error loading context store: Error: Invalid JSON in context file '/home/pi/.node-red/context/global/global.json'
Sep 11 22:03:32 raspberrypi Node-RED[429510]: 11 Sep 22:03:32 - [error] Failed to start server:

I manually fixed the context file and now back up and running.

Any ideas where to look for a cause, bearing in mind this may only be another random symptom of the underlying issue :thinking:

8

Given you are using an SSD, I'd suspect a poor power supply now. But it could equally be some other hardware issue.

9

Indeed I have some concern it maybe hardware related, possibly the drive or ram. It's running on the official Pi5 PSU so there should be plenty enough power.

If / when it happens again I think I will try rebuilding on another drive.
File corruption seems to be a common outcome, but maybe that is the root cause?

1 Like