3. WARN: incoming conn *** was malformed

WARN: incoming conn *** was malformed

  • T

    I've been running for a bit with zero hosting contracts. I closed Sia and reopened it and I was able to find my host log file and this is what it has...

    "2016/02/05 18:42:52.358933 log.go:60: STARTUP: Logging has started.
    2016/02/05 18:42:56.723007 upnp.go:84: INFO: successfully forwarded port 9982
    2016/02/05 18:43:26.885857 announce.go:44: INFO: Successfully announced as 67.184.20.214:9982
    2016/02/05 18:43:48.016962 network.go:81: WARN: incoming conn 46.233.42.249:52666 was malformed
    2016/02/05 18:43:59.951977 network.go:81: WARN: incoming conn 178.154.2.113:63464 was malformed"

    And then the malformed message repeated over and over hundreds of times from different connetions. What am I doing wrong? I'm on Win 10, with 250GB offered at 50SB. Ports are forwarded correctly and wallet is unlocked.

    0
  • T

    Update: Few hours later and I've got 1 contract with 65.54KB used, but I now have this error over and over hundreds of times in my host log along with the malformed errors

    "network.go:128: WARN: incoming RPC "Upload" failed: <nil>"

    As of this post...

    0
  • admins

    Interesting. I'm not sure why so many malformed calls are happening, I've added a PR to give us more information: https://github.com/NebulousLabs/Sia/pull/976/files

    As for the <nil> errors, @allejuppa already created a PR (and it was merged) to give the correct error information.

    I can't be of too much help, except to suggest that most of the network is experiencing a similar number of errors in their logging. I think at this point we've addressed some of these errors, but we're continuing to work on the renter and host protocol right now.

    0
Log in to reply