3. Help! Sia Not Synchronizing/No Hosts Found (OSX)

Help! Sia Not Synchronizing/No Hosts Found (OSX)

  • S

    Hey,
    I'm not sure where to post this, but the Sia OSX build from the site isn't working for me.

    Over the last few days, I went through the long process of synchronizing the blockchain, got some SC, put it in the wallet, and started up a contract.

    Today, when I opened up the app, it won't synchronize. When I click on "Create Allowance" it says that no hosts are available.

    Is this a known issue? What can I do to get up and working?

    Screenshot

    0
  • admins

    Given both of those things combined, it seems like you are not connected to the internet. Or, at least Sia is unable to connect to the internet.

    Do you have a firewall with rules set up? Sia needs access to ports 9981 and 9982 to connect to the network.

    Can you think of other reasons that your node might be unable to connect to the internet? It's not likely a Sia bug because it's a completely different set of code that handles the Synchronizing and the host negotiation.

    Also, looks like there's another bug in your screenshot, though you may have missed it. Your allowance says '2719 spent, 2803 allocated, 1 contract'. Can you check in the 'About' plugin that you are running v1.1.0? I am quite certain that you have not spent 2719 out of 2803 coins in a single contract. I think I know where the bug is but want to confirm that you are running the latest version.

    0
  • S

    Sure thing! Thanks so much for the quick reply.

    Strange, I'm posting on the same computer, and no firewall settings were changed since I synchronized everything. I disabled my firewall settings and now I'm stuck at "Synchronizing: Block Height 88064" for the last hour or so.

    You're right! I'm running v1.0.4. I downloaded v1.1.0 and the Spent/Allocated updated. It's switching between "Synchronizing" and "Not Synchronizing" at Block Height 88065.

    Based on what you're saying, you think something changed on my computer within the last day to block Sia from accessing the internet, is that correct? If so I can start digging around and see if anything was modified I may not have noticed.

    Edit: We are now at Block Height 88067. Not sure if it's running super slow or what? On Speedtest.net I'm getting over 100mbs down and 15mbps up.

    Another thing that might be a factor: My computer didn't shut down gracefully last night when Sia was searching for contracts. It shut down right after I had used the funds I transfered. Could that be causing an issue?

    Edit 2: I "uninstalled" Sia and restarted with a new wallet. Everything's synchronizing just fine. It seems like something may have been messed up when my computer shut down while Sia was looking for contracts. That could also explain why my contracts were stuck at 1.

    Is there a way to recover my old wallet info? Or copy over the blockchain so I don't have to resync everything?

    Edit 3: I decided to resync everything since it was working when I started from scratch. My computer got to Block Height 71375 before going to sleep (because it takes so long to sync everything) and after waking it up it's stuck at "Not Synchronizing: Block Height: 71375". Even though it was working without issue 10 minutes ago. This leads me to believe it's not a network issue, and something to do with how the app isn't able to handle getting stopped in the middle of something.

    The .log in the Consensus folder has a ton of lines with similar errors:
    2017/01/22 16:14:58.138974 synchronize.go:554: WARN: disconnecting from peer 193.91.196.227:9981 because IBD failed: Session closed

    To confirm it's not my network I removed the Sia UI folder from /Libraries/Application Support, restarted the program so it wouldn't carry over any info from previous installs, and it starts synchronizing right away (from Block Height 0, though...).

    Edit 4: Ok. Third time's a charm. I changed all my power settings so my laptop never shut down/went to sleep even if I wasn't using it. Six hours later and Sia is up and running. Fully synchronized, imported my old wallet, 33 contracts, and I'm uploading my first file. I'm still afraid to shut it down ungracefully, though.

    My big concern is it not working after the whole computer shuts down/pauses ungracefully. At least, that's what I've experienced. Is there anything from me that you might need to help find the bug (if it is one)? I can send the log if you need, but the errors are mostly the same as the one I coppied.

    Edit 5: Yup... restarted my computer and now I'm right back at "Not Synchronizing"/"Synchronizing" block height 88235. Same issue as before.

    Weirdly, I can still upload files. I just uploaded a small text file and currently have 3.5x redundancy. Maybe the message in the top right is just wrong/a bug?

    0
  • admins

    Can you go to the terminal plugin, type hostdb, and share the results?

    0
  • S

    @Taek Sure. Here's the output:

    hostdb

    Active hosts:
    lord.network:9982 - 430 SC / TB / Month
    94.137.131.2:9982 - 1000 SC / TB / Month
    75.82.191.146:9982 - 600 SC / TB / Month
    sianet.punked.us:5982 - 4.95 KS / TB / Month
    85.255.197.69:19982 - 500 SC / TB / Month
    79.172.204.10:9982 - 1000 SC / TB / Month
    85.255.197.69:9982 - 500 SC / TB / Month
    194.135.83.229:9982 - 1.991 KS / TB / Month
    149.62.176.238:9982 - 5 KS / TB / Month
    122.114.81.211:9982 - 1000 SC / TB / Month
    80.234.37.94:9982 - 999 SC / TB / Month
    super3.punked.us:9982 - 19 KS / TB / Month
    82.220.99.82:9982 - 30 KS / TB / Month
    184.58.225.125:9982 - 660 SC / TB / Month
    sia.internet-box.ch:9982 - 999 SC / TB / Month
    162.210.249.170:9982 - 1000 SC / TB / Month
    138.201.172.38:9982 - 1.8 KS / TB / Month

    0
  • admins

    That would do it. No easy fix at the moment, but v1.1.1 will have a much better host discovery mechanism.

    0
  • S

    Ok, so at least you know what it is and it'll be fixed. It's still usable AFTER getting everything synced, just wanted to make sure the team was aware.

    1
Log in to reply