3. 0.5.0 RC troubleshooting

0.5.0 RC troubleshooting

  • T

    0.5.0 RC:

    Files Panel:

    I'm trying to upload a file, but it has been stuck on "processing" for something like an hour now. It's a 30 kb jpg that I'm using as a test. My wallet is appropriately funded and unlocked.

    It looks like it's related to this other issue:

    Wallet Panel:

    I have now 112 pages of addresses, and the number keeps growing. I am now at 114 after the time it took me to write this sentence and refresh the panel. 115 now. The file upload is still "processing..."

    Unrelated/minor, but still: I got that you can manually enter the page number for the list ( x / y ), but that isn't very clear. At first, I thought I just couldn't see past the first 25 addresses.

    Unrelated/minor: The Transactions list just seems to always display all the transactions. Clicking on the "Show related transactions" button on one of the addresses doesn't change anything.

    119 pages of addresses now... I feel like I'd better close the app now. I'm using the Darwin release.

    I ended up relaunching the app, getting some errors in a row while "siad:running"
    ERROR: connect ECONNREFUSED 127.0.0.1:9980

    Then the app manages to right itself. Or sometimes it seems like it's stuck in a kind of error loop and you have to close the app again and relaunch it. I killed the upload by deleting the file. It's all back to "normal", at least there don't seem to be a lot of addresses being generated for nothing anymore.

    0
  • admins

    Wanted to let you know that we've seen your post and are working through the code to try and figure out what's causing the behavior you are describing.

    We don't have much more to say than that, but we're looking into it.

    0
  • T

    Hey, no problem. Can you replicate the issue? Here are my renter log files in case. http://pixeldra.in/u/dCmqBI

    0
  • L

    I guess it's probably not this, but it reminded me that a file I had was stuck on pretend-uploading (but at 0% forever) because I had not realized that the sia user didn't have the right permissions to read it.
    Perhaps it should realize this and refuse to try, instead of being stuck forever.

    0
  • admins

    Hmm, I'm surprised it didn't handle that error correctly. We'll have to look into it further.

    0
  • T

    Still getting the same bug with the new Beta release. Upload was showing a percentage (42%), and addresses kept being generated. I killed the file in the uploader to fix the problem.

    0
  • admins

    I have over 250,000 addresses in my wallet at this point. That's clearly undesirable, but it does mean that I don't think the address explosion you are seeing is unusual. We're working on improvements to the wallet software that will make using large quantities of addresses unimportant. In the meantime, sorry for the inconvenience.

    I will also note that the more addresses you have, the longer it will take to unlock the wallet. =/ sorry about that. We are working on getting HD wallets now so that we can support greater numbers of addresses wtihout impacting UX.

    0
  • T

    Fair enough, but it used more than 1000 transactions for a single 48.05 kb file upload. It was stuck on 96% for an hour or two, and it kept generating addresses. I think there's more going on than simply the usual addresses being generated. I'm not sure what it's struggling with. The upload did eventually complete and things seem to be purring along fine now.

    Yeah, there should probably be a difference in the UX between wallet addresses you use to send and receive SC, and renter/host logic addresses that the user doesn't really need to know about unless troubleshooting/curiousing.

    0
  • admins

    Noted. v0.5.2 (or maybe v0.6.0, since it's a pretty big upgrade) should handle this stuff a lot better, creating both fewer file contracts and fewer addresses.

    0
  • A

    @TacoByte

    Found the solution for the error: connect ECONNREFUSED 127.0.0.1:9980 is in the config.json file. Edit the file replacing "address": "localhost:9980", with "address": ":9980", then resave file voila, no more ECCONREFUSED. :)

    0
  • admins

    I wonder why that is necessary. Are you behind a VPN or firewall? If you change the address from 'localhost:9980' to ':9980' I worry that you are exposing the api to the public, which means people can get in and mess with your coins. The API currently does not have any authentication, which means that an attacker is not going to have many problems stealing your coins if they can get talking to the sia api.

    We do plan on adding authentication to the api in the near future, but I still think it's a bad idea to expose your api to the public.

    0
  • A

    @Taek

    OK, it stopped working anyway so changed it back....so disregard previous solution. Don't know what's up with that econnrefused 127.0.0.1:1980 error. Hope you guys can figure it out.

    0
Log in to reply