3. Serious Wallet Problem

Serious Wallet Problem

  • R

    Hi Everybody,

    Have been following and mining SIA for a while. Since two days ago I have the problem that Sia Wallet (without mining on this Machine) causing my Computer to freeze. Using Sia version 1.0.0, Sia UI version v1.0.1. Didn't have any problems before. The following is the error message I get on the screen when it freezes:

    Error Fetching Data
    connect ETIMEDOUT 127.0.0.1:9980

    The crash happens randomly, meaning no specific time, no other things happening at the time which has anything to do with SIA.

    My Machine has enough resources:
    Intel Xeon E5--2696v2 @ 2.50GHz
    128 GB RAM
    Several TB of HD
    Network:
    fixed Ip
    240 Mb Down
    20 MB UP
    All wired with cat 6 and connected through GB Switches

    So any help would be appreciated!

    Cheers!

    0

  • Hmmm, difficult to say what is wrong. When you use the UI and get that message: connect ETIMEDOUT 127.0.0.1:9980 it normally means that siad has crashed in the background.

    Now the question is if your computer crashes because siad crashes or if both crash because of some other problem on your PC.

    Are you familiar with running Sia in a command window? If yes, open a command window, navigate to the folder where siad is and run it. Maybe next time the crash happens there will be some additional error output in the command window...

    0
  • R

    @betaboot

    Thanks for the reply! I will try that. What is odd is that before that happened I have been, for weeks, mining on this machine, had several VM's running, several development platform's running, media server/streaming (local home use only) running, multiple of different browser with dozens of open tabs running nothing ever happened.
    Another note is that is started to happen when I reached my target of 50k SIA coins which I need for starting hosting (have about 30 TB) but the reason for the hosting is that I want to evaluate SIA from a point of view of implementing the hosting side within a project I am currently working on.

    Cheers!

    0

  • Actually, i just remembered that i had a similar problem some months ago...

    I had several disks in my computer and on one of them i installed Sia. It was an old disk that i just used for some data backup. From time to time siad would crash and at the same time the disk on which i installed Sia was gone (e.g. i could not see it anymore in the Windows explorer, had to reboot to see it again). The computer was still running because it did not affect the operating system but i could imagine that if you installed Sia on the same disk as the OS it would just freeze.

    I could not find out what was the problem but i think it was just an old/bad disk. Afterwards i installed Sia on an SSD and never had that problem again. So i think that it's not a Sia bug. But you never know, maybe just a really strange and rare one...

    0
  • R

    Again, thanks for reply!

    I think I can rule out the old disk issue, it's running on a 9 month old ssd which is also my OS drive. Than again, in your case Sia wasn't located on your system drive, so when it crashed it did not freeze your system, whereas mine is located on the system drive and brought down the whole system.
    I just killed the siad process in task manager (just to see what happens) and the same message came up, this time without freezing the system, the message stood till I killed all sia processes.
    Have to think about that ;)

    Cheers!

    0

  • that's normal! you will always get that message in the UI if you kill siad.

    another thing i remember is that i could sometimes trigger it if i copied files around. especially the large consensus.db file. I could just copy-paste it to another folder on that disk and then the disk would crash, also without Sia running. That's why i first thought it's a Sia problem but later i saw that it also happens with other files and then i concluded it's a disk problem.

    I guess it's best to just run siad in the command window and see if you get some error message. Maybe also delete all the *.log files first so that new ones will be created. Then it's easier to see if there are any messages in the logs.

    0
Log in to reply