Strange AR1 problems with Node Red out the box


#1

Hi guys and gals

I opened and registered a new AR1 today. When I try and access Node Red I get this error:

Unexpected token in JSON at position 0
404
SyntaxError: Unexpected token in JSON at position 0
at Object.parse (native)
at /usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/session-file-store/lib/session-file-helpers.js:148:25
at /usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/graceful-fs/graceful-fs.js:78:16
at tryToString (fs.js:455:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:442:12)

Please Help?


#2
Also get this error when trying to update groov ADMIN:

Verifying update… Failed to update from uploaded file : Unable to verify package signature

I can’t access the Node Red page at all now…


#3
groov Part Number GROOV-AR1
groov Image Version 35
groov Admin Version 1.570.49.45978
groov App Version R4.0a (r48253)
Node-RED Update Version 4
Power-Loss Tolerant File System Yes
Hardware Date June 28, 2015
Time on System Mon May 28 16:26:22 2018
System Uptime 0 hours, 23 minutes
CPU Load Averages 0.44 (1 min) 0.62 (5 mins) 0.59 (15 mins)
CPU Usage 0% user, 0% kernel, 0% IO, 100% idle

#4

Cannot create property ‘status’ on boolean 'true’
TypeError: Cannot create property ‘status’ on boolean 'true’
at expressApp.use (/usr/local/lib/node_modules/@opto22/src/server/ServerApp.ts:204:27)
at Layer.handle_error (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/layer.js:71:5)
at trim_prefix (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:310:13)
at /usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:330:12)
at next (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:271:10)
at Layer.handle_error (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/layer.js:67:12)
at trim_prefix (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:310:13)
at /usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/usr/local/lib/node_modules/@opto22/node-appliance-ui/node_modules/express/lib/router/index.js:330:12)


#5

ending up giving the unit a factory reset, will try again… strange


#6

Did the factory reset do the trick?


#7

Hi there, yip. Factory reset did it. Rolled back a version as suggested by support and all ok now.
Cheers