I'm having trouble understanding how to achieve the following: I have a set of 15 global variables that I'd like to have restored after a system restart. I have the following section added to the settings,js file: contextStorage: { default: { module: "localfilesystem", config: { …

Yes, @Colin that was a brand new key "DateRefreshed" and it is not used anywhere else. DateRefreshed did make it into a global properly const _time = new Date() const Now = `${_time.toDateString()} ${_time.toTimeString()}` node.warn({Now}) global.set("DataRefreshed", Now) node.warn(global.get("Dat…

[image] UmbraLimi: results in {"Now":"Sun Aug 13 2023 21:04:02 GMT+0000 (Coordinated Universal Time)"} { DateRefreshed: undefined } I don't understand what you mean by that statement. Where are you seeing those values. Did both warn statements in the function show correctly? It would hav…

I edited my answer significantly just before yours as I noticed a typo DataRefreshed instead of DateRefreshed. The global did save properly . Stand by for whether DateRefreshed survives a restart. (and also, I don't know where to find the node-red log)

One thing I can tell you is that the datetime stamp on global.json and its size do not change throughout the globals creation / global.set flow. Even after waiting the current 2 mins flushInterval in settings.js

No DateRefreshed did not survive the restart of Node-Red. That seems consistent as global.json does not change on disk. It seems that something I've done is preventing the memory versions of my globals from being flushed to disk

[image] UmbraLimi: I don't know where to find the node-red log) You need to find that. I don't know how to do that on Digital Ocean. What versions of node-red and nodejs are you running?

node.js (v14.18.2) node-red (v2.1.4) Still looking into where the log is kept on D.O.

[image] UmbraLimi: node-red (v2.1.4) That is quite old, I don't know whether there have been context fixes since then. I suggest upgrading to the latest, and also upgrade nodejs to 18. How do you stop and start node-red?

Those upgrades are in the works I use sudo systemctl stop/start/status/restart node-red

Does this show the log? journalctl -f -u node-red If it does then leave that terminal open and in another window restart node-red. In the first window you should see it restarting node-red. Post the startup here, from the Welcome to Node-RED message.

Problems understanding and implementing Persistent Storage

General

TotallyInformation 15 August 2023 15:53 38

You must always check the log for errors. For example, is the context folder and its files owned correctly? If not, that could make the writes fail. That should be in the log. If not, that's probably a bug but the write failure should probably in the syslog as well.

1 Like

Topic		Replies	Views
A guide to understanding 'Persistent Context' General	90	45476	31 August 2022
Node-red won't start General	64	3582	23 November 2020
Context store 'localfilesystem' not saved to file system General	19	638	23 February 2023
Losing global context variable General	10	786	21 May 2022
Generate retain variables using global.set/get General	11	978	15 December 2019

Problems understanding and implementing Persistent Storage

Related topics