ot-node icon indicating copy to clipboard operation
ot-node copied to clipboard

Published 20 hours ago • verified publisher icon OriginTrail

SyntaxError: Unexpected token B in JSON at position 0 at node power up

Open botnumberseven opened this issue 3 years ago • 2 comments

Issue description

There is an error right after node power up process - "SyntaxError: Unexpected token B in JSON at position 0" However it doesn't prevent node from running and spamming jobs.

Expected behavior

run with no error

Actual behavior

run with an error

Steps to reproduce the problem

  1. Start the node
  2. ???
  3. Error

Sorry, but i haven't done anything special to get this error, just started the node. I checked my noderc file, but it looks fine. And i do not understand what JSON it complains about.

Specifications

  • Node version: v6.0.0-beta.1.19
  • Platform: Ubuntu 20.04
  • Node wallet: 0x490618BE2457f2789e580335F7171C70E7E511b1
  • Node libp2p identity: QmZwiL4gYeemM1kHUX76g9VbsiCkHZFBn3rzWsGs6aFTJH

Contact details

  • Email:

Error logs

image

Disclaimer

Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to [email protected].

botnumberseven avatar Jan 07 '22 01:01 botnumberseven

We had seen this issue only twice. First time solution was for user to delete files in log director and create again them empty. Can you share how did you resolved the issue?

NZT48 avatar Jan 24 '22 18:01 NZT48

Well, I do not know ^_^

First - this error did not prevent node from starting and running. It threw this error in the log and then continued running.

I've just restarted my node and i do not see this error anymore (it was reliably reproducible before). One potential explanation here - deleted out.log file. As my out.log file grew too big, i deleted it a few days ago. Do you know what JSON file it complains about?

Sorry, but i do not know how to reproduce this issue anymore.

botnumberseven avatar Jan 24 '22 20:01 botnumberseven

This issue is being closed as inactive due to the date of the last activity on it. If you believe this is still a problem, please create a new issue and confirm that it is reproducible in the current ot-node release version. We are working towards closing open issues that meet specific criteria and ask you to create a new one for those that that are truly bugs in current release. We'll be monitoring those issues so that they are properly managed.

Thank you, OriginTrail Team

NZT48 avatar Dec 26 '22 16:12 NZT48