Power-oracle-reporter error

Product Questions
1

Hi PowerPool,

I’ve been running the power-oracle-report script with mixed results and would like to get some help to make it run more consistently. I have been running it in the background on my raspberry pi and mostly am not seeing issues, but twice got this error:

I am not sure what it means or whether it can be ignored or not, any ideas?

handleError Error: Invalid JSON RPC response: ""
    at Object.InvalidResponse (/home/pi/Projects/power-oracle-reporter/node_modules/web3-core-helpers/src/errors.js:45:16)
    at XMLHttpRequest.request.onreadystatechange (/home/pi/Projects/power-oracle-reporter/node_modules/web3-providers-http/src/index.js:107:32)
    at XMLHttpRequestEventTarget.dispatchEvent (/home/pi/Projects/power-oracle-reporter/node_modules/xhr2-cookies/xml-http-request-event-target.ts:44:13)
    at XMLHttpRequest._setReadyState (/home/pi/Projects/power-oracle-reporter/node_modules/xhr2-cookies/xml-http-request.ts:219:8)
    at XMLHttpRequest._onHttpRequestError (/home/pi/Projects/power-oracle-reporter/node_modules/xhr2-cookies/xml-http-request.ts:379:8)
    at ClientRequest.<anonymous> (/home/pi/Projects/power-oracle-reporter/node_modules/xhr2-cookies/xml-http-request.ts:266:37)
    at ClientRequest.emit (events.js:198:13)
    at ClientRequest.EventEmitter.emit (domain.js:448:20)
    at TLSSocket.socketErrorListener (_http_client.js:401:9)
    at TLSSocket.emit (events.js:198:13)
    at TLSSocket.EventEmitter.emit (domain.js:448:20)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)

Much appreciated,

Kluebirby

2 Likes
2

Hey, as far as I recall it was fixed in the recent update, right?

1 Like
3

No, as far as I know, this hasn’t been fixed.

4

Ah, got it, confused it with the one you posted on Discord. Okey, sorry

1 Like
5

still getting the error. Got it twice in a row, exactly 45 min apart. Have gotten it a total of 4 times in about 2 days. Could it be that the price reporter should have been slashed but an error in the script is stopping it? The frequency of the errors leads me to assume this, so I’d love to get it fixed…

6

Hi, so a high level answer from our tech team:

It’s a node connection error, you need to check transaction during the error. If transaction is successful, the script successfully reconnected and performed it. If not, then we need to fix things.

You can dm me in discord, for faster communication and further details sharing.