Core CLI access failing

Troubleshooting
1

I cannot monitor either of my cores using the spark CLI. I used to be able to. For example
"spark subscribe mine" now immediately exits even though I know that my two cores are interchanging on a Spark.publish channel. Similarly I cannot monitor a Spark.variable.

spark list returns the following:

Checking with the cloud...
Retrieving cores... (this might take a few seconds)
listDevices got error:  invalid_token
Potentially unhandled rejection [2] invalid_token (WARNING: non-Error used)

This has been reported before > https://community.spark.io/t/cli-produces-error-of-invalid-token/10723 but the solution there has no effect for me though it led me to conclude I have some form of token error, though how that comes about I have no idea. In the Command Line documentation there is a “spark keys doctor” section but I think that relies on a USB connection - which is going to be a problem!

How do I get out of this, and how do I avoid it in the first place - whatever it is.

Has what I am doing here got any relevance perhaps? > https://community.spark.io/t/maintaining-publish-subscribe-connections/10743/10

My thanks.

2

Can you try performing a spark login?

3

spark login did the trick thankyou. That is strange because earlier I tried:

spark setup

and received:

You are already logged in as goinxxxxx
Do you want to switch accounts? (y/N):

Anyway it is fixed.

2 Likes