Windows 10: Failed to start server: Error: Error loading context store: SyntaxError: Unexpected token in JSON at position 0

Good day and Hello all,

My Node Red Stats: Windows 10, nodered 1.0.5, node.js v 12.16.2, npm v 6.14.4

Everything was working fine yesterday (22 April 2020), up till this morning node red was still running too. Until I ran into the Blue Screen, and my laptop automatically restarted.

After restart cycle completed, I tried to start node red again using powershell (as I do everyday) and I get the error log shown below. Before this I start using the same command every single day, it worked fine.

Here's how I start my node red everyday using the following command

PS C:\Users\my-login-name-goes-here\.node-red> node-red -s .\mysettings.js

And all would be running fine.

BUT today, I ran into this error instead...

PS C:\Users\my-login-name-goes-here\.node-red> node-red -s .\mysettings.js
23 Apr 08:13:14 - [info]

Welcome to Node-RED
===================

23 Apr 08:13:14 - [info] Node-RED version: v1.0.5
23 Apr 08:13:14 - [info] Node.js  version: v12.16.2
23 Apr 08:13:14 - [info] Windows_NT 10.0.17763 x64 LE
23 Apr 08:13:16 - [info] Loading palette nodes
23 Apr 08:13:36 - [info] +-----------------------------------------------------
23 Apr 08:13:36 - [info] | uibuilder initialised:
23 Apr 08:13:36 - [info] |   root folder: \Users\my-login-name-goes-here\.node-red\uibuilder
23 Apr 08:13:36 - [info] |   version . .: 2.0.7
23 Apr 08:13:36 - [info] |   packages . : vue,bootstrap,bootstrap-vue,socket.io,jquery
23 Apr 08:13:36 - [info] +-----------------------------------------------------
23 Apr 08:13:40 - [info] Dashboard version 2.21.0 started at /ui
23 Apr 08:13:41 - [info] Settings file  : C:\Users\my-login-name-goes-here\.node-red\mysettings.js
23 Apr 08:13:41 - [info] Context store  : 'default' [module=localfilesystem]
23 Apr 08:13:41 - [error] Failed to start server:
23 Apr 08:13:41 - [error] Error: Error loading context store: SyntaxError: Unexpected token   in JSON at position 0
    at C:\Users\my-login-name-goes-here\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\nodes\context\index.js:177:15

Funny thing is, if I just run the command node-red, my server could start OK. No problems. Which means, if starting node-red with the default settings.js it works OK.

Here is my mysettings.js content. Key changes I made in there (which I can recall of the top of my head), is to set my context to write to file instead of memory, added reference to moment.js library in global, the usual user login, login session timeout and setting CORS for server access within company network

/**
 * Copyright JS Foundation and other contributors, http://js.foundation
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 **/

// The `https` setting requires the `fs` module. Uncomment the following
// to make it available:
//var fs = require("fs");

module.exports = {
    // the tcp port that the Node-RED web server is listening on
    uiPort: process.env.PORT || 1880,

    // By default, the Node-RED UI accepts connections on all IPv4 interfaces.
    // To listen on all IPv6 addresses, set uiHost to "::",
    // The following property can be used to listen on a specific interface. For
    // example, the following would only allow connections from the local machine.
    //uiHost: "127.0.0.1",

    // Retry time in milliseconds for MQTT connections
    mqttReconnectTime: 15000,

    // Retry time in milliseconds for Serial port connections
    serialReconnectTime: 15000,

    // Retry time in milliseconds for TCP socket connections
    //socketReconnectTime: 10000,

    // Timeout in milliseconds for TCP server socket connections
    //  defaults to no timeout
    //socketTimeout: 120000,

    // Maximum number of messages to wait in queue while attempting to connect to TCP socket
    //  defaults to 1000
    //tcpMsgQueueSize: 2000,

    // Timeout in milliseconds for HTTP request connections
    //  defaults to 120 seconds
    //httpRequestTimeout: 120000,

    // The maximum length, in characters, of any message sent to the debug sidebar tab
    debugMaxLength: 1000,

    // The maximum number of messages nodes will buffer internally as part of their
    // operation. This applies across a range of nodes that operate on message sequences.
    //  defaults to no limit. A value of 0 also means no limit is applied.
    //nodeMessageBufferMaxLength: 0,

    // To disable the option for using local files for storing keys and certificates in the TLS configuration
    //  node, set this to true
    //tlsConfigDisableLocalFiles: true,

    // Colourise the console output of the debug node
    //debugUseColors: true,

    // The file containing the flows. If not set, it defaults to flows_<hostname>.json
    //flowFile: 'flows.json',

    // To enabled pretty-printing of the flow within the flow file, set the following
    //  property to true:
    //flowFilePretty: true,

    // By default, credentials are encrypted in storage using a generated key. To
    // specify your own secret, set the following property.
    // If you want to disable encryption of credentials, set this property to false.
    // Note: once you set this property, do not change it - doing so will prevent
    // node-red from being able to decrypt your existing credentials and they will be
    // lost.
    //credentialSecret: "a-secret-key",

    // By default, all user data is stored in a directory called `.node-red` under
    // the user's home directory. To use a different location, the following
    // property can be used
    //userDir: '/home/nol/.node-red/',

    // Node-RED scans the `nodes` directory in the userDir to find local node files.
    // The following property can be used to specify an additional directory to scan.
    //nodesDir: '/home/nol/.node-red/nodes',

    // By default, the Node-RED UI is available at http://localhost:1880/
    // The following property can be used to specify a different root path.
    // If set to false, this is disabled.
    //httpAdminRoot: '/admin',

    // Some nodes, such as HTTP In, can be used to listen for incoming http requests.
    // By default, these are served relative to '/'. The following property
    // can be used to specifiy a different root path. If set to false, this is
    // disabled.
    //httpNodeRoot: '/red-nodes',

    // The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot',
    // to apply the same root to both parts.
    //httpRoot: '/red',

    // When httpAdminRoot is used to move the UI to a different root path, the
    // following property can be used to identify a directory of static content
    // that should be served at http://localhost:1880/.
    //httpStatic: '/home/nol/node-red-static/',

    // The maximum size of HTTP request that will be accepted by the runtime api.
    // Default: 5mb
    //apiMaxLength: '5mb',

    // If you installed the optional node-red-dashboard you can set it's path
    // relative to httpRoot
    //ui: { path: "ui" },

    // Securing Node-RED
    // -----------------
    // To password protect the Node-RED editor and admin API, the following
    // property can be used. See http://nodered.org/docs/security.html for details.
    adminAuth: {
		sessionExpiryTime: 14400,
        type: "credentials",
        users: [
		{
            username: "my-user-name-goes-here",
            password: "my-password-hash-tag-goes-here",
            permissions: "*"
        },
		{
            username: "user",
            password: "user-hastag-password-goes-here",
            permissions: "read"			
		}
		]
    },

    // To password protect the node-defined HTTP endpoints (httpNodeRoot), or
    // the static content (httpStatic), the following properties can be used.
    // The pass field is a bcrypt hash of the password.
    // See http://nodered.org/docs/security.html#generating-the-password-hash
    //httpNodeAuth: {user:"user",pass:"$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN."},
    //httpStaticAuth: {user:"user",pass:"$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN."},

    // The following property can be used to enable HTTPS
    // See http://nodejs.org/api/https.html#https_https_createserver_options_requestlistener
    // for details on its contents.
    // See the comment at the top of this file on how to load the `fs` module used by
    // this setting.
    //
    //https: {
    //    key: fs.readFileSync('privatekey.pem'),
    //    cert: fs.readFileSync('certificate.pem')
    //},

    // The following property can be used to cause insecure HTTP connections to
    // be redirected to HTTPS.
    //requireHttps: true,

    // The following property can be used to disable the editor. The admin API
    // is not affected by this option. To disable both the editor and the admin
    // API, use either the httpRoot or httpAdminRoot properties
    //disableEditor: false,

    // The following property can be used to configure cross-origin resource sharing
    // in the HTTP nodes.
    // See https://github.com/troygoode/node-cors#configuration-options for
    // details on its contents. The following is a basic permissive set of options:
    httpNodeCors: {
        origin: "https://a-pi-server,https://another-pi-server,http://localhost:some-port-no-here",
        methods: "GET,OPTIONS,POST,PATCH,PUT",
		exposedHeaders: "Allow,Content-Encoding,Content-Length,Date,Location",
		allowedHeaders: "content-type,requestverificationtoken,x-requested-with,accept, Access-Control-Allow-Origin",
		credentials: true
    },
	

    // If you need to set an http proxy please set an environment variable
    // called http_proxy (or HTTP_PROXY) outside of Node-RED in the operating system.
    // For example - http_proxy=http://myproxy.com:8080
    // (Setting it here will have no effect)
    // You may also specify no_proxy (or NO_PROXY) to supply a comma separated
    // list of domains to not proxy, eg - no_proxy=.acme.co,.acme.co.uk

    // The following property can be used to add a custom middleware function
    // in front of all http in nodes. This allows custom authentication to be
    // applied to all http in nodes, or any other sort of common request processing.
    //httpNodeMiddleware: function(req,res,next) {
    //    // Handle/reject the request, or pass it on to the http in node by calling next();
    //    // Optionally skip our rawBodyParser by setting this to true;
    //    //req.skipRawBodyParser = true;
    //    next();
    //},

    // The following property can be used to pass custom options to the Express.js
    // server used by Node-RED. For a full list of available options, refer
    // to http://expressjs.com/en/api.html#app.settings.table
    //httpServerOptions: { },

    // The following property can be used to verify websocket connection attempts.
    // This allows, for example, the HTTP request headers to be checked to ensure
    // they include valid authentication information.
    //webSocketNodeVerifyClient: function(info) {
    //    // 'info' has three properties:
    //    //   - origin : the value in the Origin header
    //    //   - req : the HTTP request
    //    //   - secure : true if req.connection.authorized or req.connection.encrypted is set
    //    //
    //    // The function should return true if the connection should be accepted, false otherwise.
    //    //
    //    // Alternatively, if this function is defined to accept a second argument, callback,
    //    // it can be used to verify the client asynchronously.
    //    // The callback takes three arguments:
    //    //   - result : boolean, whether to accept the connection or not
    //    //   - code : if result is false, the HTTP error status to return
    //    //   - reason: if result is false, the HTTP reason string to return
    //},

    // The following property can be used to seed Global Context with predefined
    // values. This allows extra node modules to be made available with the
    // Function node.
    // For example,
    //    functionGlobalContext: { os:require('os') }
    // can be accessed in a function block as:
    //    global.get("os")
    functionGlobalContext: {
		moment:require('moment'), //Added moment.js functionallity into function block by installing "moment" library into node_modules directory
        moment_timezone:require('moment-timezone')
		
		// os:require('os'),
        // jfive:require("johnny-five"),
        // j5board:require("johnny-five").Board({repl:false})
    },
    // `global.keys()` returns a list of all properties set in global context.
    // This allows them to be displayed in the Context Sidebar within the editor.
    // In some circumstances it is not desirable to expose them to the editor. The
    // following property can be used to hide any property set in `functionGlobalContext`
    // from being list by `global.keys()`.
    // By default, the property is set to false to avoid accidental exposure of
    // their values. Setting this to true will cause the keys to be listed.
    exportGlobalContextKeys: false,


    // Context Storage
    // The following property can be used to enable context storage. The configuration
    // provided here will enable file-based context that flushes to disk every 30 seconds.
    // Refer to the documentation for further options: https://nodered.org/docs/api/context/
    //
    contextStorage: {
        default: {
            module:"localfilesystem",
			config: {
				//"dir" :"~/.node-red",
				//"base" : "context",
				//"cache" : true,
				"flushInterval" : 1
			}
        },
    },
	
    // The following property can be used to order the categories in the editor
    // palette. If a node's category is not in the list, the category will get
    // added to the end of the palette.
    // If not set, the following default order is used:
    //paletteCategories: ['subflows','flow','input','output','function','parser','social','mobile','storage','analysis','advanced'],

    // Configure the logging output
    logging: {
        // Only console logging is currently supported
        console: {
            // Level of logging to be recorded. Options are:
            // fatal - only those errors which make the application unusable should be recorded
            // error - record errors which are deemed fatal for a particular request + fatal errors
            // warn - record problems which are non fatal + errors + fatal errors
            // info - record information about the general running of the application + warn + error + fatal errors
            // debug - record information which is more verbose than info + info + warn + error + fatal errors
            // trace - record very detailed logging + debug + info + warn + error + fatal errors
            // off - turn off all logging (doesn't affect metrics or audit)
            level: "info",
            // Whether or not to include metric events in the log output
            metrics: false,
            // Whether or not to include audit events in the log output
            audit: false
        }
    },

    // Customising the editor
    editorTheme: {
        projects: {
            // To enable the Projects feature, set this value to true
            enabled: false
        }
    }
}

BTW, I did install the fastcsv node and used it in my flow in place of the default csv node. And I've been trying it out with no problems so far. So, I doubt that would be the problem.

Appreciate any troubleshooting tips from the experts in here.

Thanks again for reading through my post.

OK I've done a bit more troubleshooting, and I could confirm that if I change mysettings.js to revert back to in memory context (by commenting out my context settings), instead of writing to file, my node-red server would start just fine.

    // Context Storage
    // The following property can be used to enable context storage. The configuration
    // provided here will enable file-based context that flushes to disk every 30 seconds.
    // Refer to the documentation for further options: https://nodered.org/docs/api/context/
    //
    //contextStorage: {
    //    default: {
    //        module:"localfilesystem",
	//		config: {
	//			"dir" :"~/.node-red",
	//			"base" : "context",
	//			"cache" : true,
	//			"flushInterval" : 1
	//		}
    //    },
    //},

OK since I've narrowed down the problem to the context storage in localfilesystem... I deleted ALL existing context files within the context directory and my node red server can start again.

Upon looking into the content of my context files, I notices that within some of the flow.json files I only "see" NULNULNULNULNULNULNULNUL ...

"see" in quotation marks because I viewed the file using notepad++. Initially, the file looks like its all blank, but when I make a selection of the top row using my mouse, it revealed in very faint light yellow font to make out the combination of letters... NULNULNULNULNULNUL ... Don't know if it fits into any of JavaScript Variables oftype string, numbers, null, undefined, or object

I tried copy pasting these NULNULNULNULNUL... into my notepad and wordpad, it just turns out to be blank spaces or invisible text...

A bug maybe? caused by The Blue screen attack?

Appreciate any feedback on this issue

For now, deleting my context files resolved my Failed to start server problem

Sorry I didn't remember :woozy_face: I hit this edge case issue back in October and opened an issue about it.

In my case it was caused by swapping projects, but as you have found out, if you delete the presistant data file for the occurance of NR, it will work but the persistent data will be gone.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.