node-red corruption ??
- This topic has 2 replies, 2 voices, and was last updated 6 years, 1 month ago by
.
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › node-red corruption ??
Lawrence Griffiths.
Lawrence GriffithsI’ve got an Access point AEP
Been running fine for a month on v1.6.4
Today it stopped posting via http to a cloud endpoint
All I see is the blue status dot saying Requesting on the [http request] node
I’ve rebooted countless times.
I’ve now have simple 3 node flow
[inject]–[http request]–[debug]
connecting to http://www.google.com just sits there Nothing.
I can ping http://www.google.com from the shell no problem
The [http request] node is working as I can access
http://127.0.0.1/api/system/deviceId
I also get Failed to deploy error messages
I’ve tried open DNS in place of default google
The logs don’t tell me anything!!
The GW is connected via 3G,
I enabled ssh via wan to debug
There is plenty of free memory
I’ve compared process list with another GW running the same setup all ok
So I’m at a dead end with a un-happy client.
Any thoughts??
Jeff HatchLawrence,
I don’t have any ideas other than at the URL below we have a “stock” Node-RED image for Conduit:
http://multitech.net/downloads/node-red-0.15.3.tgz
If you cannot access this download I can upload it to the Multitech Support Portal.
You can untar this image in the /opt directory. It will overwrite what you currently have there, so back up /opt/node-red if you feel the need to.
Jeff
Lawrence GriffithsJeff thanks I’m try this in the office as I’ve arranged to swap the GW out.
Lawrence