Error: Server responded with a non-101 status: 429

#1

I am getting this error in my debug panel:

Error: Server responded with a non-101 status: 429 
Too Many Requests
Response Headers Follow:
date: Sat, 22 Sep 2018 22:51:23 GMT
content-length: 0
content-type: text/plain; charset=utf-8

And, I don't have a clue which node is causing it.
I would appreciate some pointers toward finding the cause of this error, and, please, if you say "Check the logs", please tell me which log files and where are they.

Thanks

0 Likes

#2

The log location is dependent on which OS you have installed Node-RED and how you have decided to run it.

0 Likes

#3

What nodes do you have in your flow that make http requests to online services? That will help narrow it down.

0 Likes

#4

Thanks for the reply. I forgot to add my sig file- But it's the Node-Red that comes with Stretch. I don't see any log files in ~/.node-red

Sig

0 Likes

#5

Thanks, I appreciate the reply.
I must be slow today, but it's either my IP camera or Weather Underground.

EDIT: Turns out to be my PushBullet node.

Sig

0 Likes

#6

If it’s on stretch you probably need to update your signature.

If you run Node-RED using node-red-start the location of the log file is listed on the raspberry pi page in the docs under the systemd part.

0 Likes

#7

To view the log if running under systemd (typical now for nearly all Linux OS's I think), use the journalctl command.

For example, I have a small flow that issues the following in an exec node:

sudo journalctl -u nrlive -f -n 0 -o cat

nrlive is my instance of Node-RED (slightly different to the default). You can play with the parameters to get different outputs.

I also add a log command to my package.json file since I can never remember the actual command. That way I can do something like npm run log in my userDir folder.

0 Likes

#9

Thanks. The sig is correct. It can't be Stretch because the good people at Raspberry decided to not make Node-Red preinstalled beginning with Stretch.

0 Likes

#10

In my opinion, that's for the best. Previously, the default Node.JS installation was a mess because they needed to keep the archive size low. It caused lots of confusion. Though it also resulted in Dave's excellent update script so ...

Also, there are more than one ways to install Node-RED. Either way, unpicking the default install was a pain.

Of course, it did have the impact of raising the awareness of Node-RED with Pi users which was very good. Not sure we need that quite so much though now that NR is much more visible.

0 Likes