A sia-ui error has occured error: sia closed unexpected



  • @brwainer I've checked listening ports in resource monitor and the only entry for port 9980 is:
    Image: siad.exe process ID: 7476 address: IPv4 loopback

    The same siad.exe process ID are listed on ports 9981 & 9982. How should I proceed?



  • @Taek I am having a similar problem on my linux machine (elementary OS)



  • @augustus it sounds to me like you already have one said instance running (in the background?) and are trying to launch another. If that's not the case then you'll have to wait for someone more knowledgeable to answer and let you know what needs to be deleted in order to reset the state of sia.



  • I've restarted several times and checked that no siad processes are running, so not sure why siad.exe is being listed as listening to port 9980. @Taek can you shed some light? My hosting has been offline for over a week now!



  • @augustus if a process is bound to a port, and you can't close it via normal means (i.e. you don't have a command prompt open for it, and it isn't showing in the taskbar tray as an icon you can right click) then you have to kill the process from task manager or a similar program. Or restart the computer, that closes all processes. Sai doesn't have any automatic startup, so it wouldn't start on boot/login unless you manually set that up yourself.



  • @brwainer I'm struggling to see how what your stating fixes the problem. I've restarted my computer several times which does indeed free up port 9980, but Sia-UI still won't start. The same problem still occurs.


  • admins

    @augustus sorry for the slow reply. Been buried. if you are getting the error: "listen tcp 127.0.0.1:9980: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted." when you try to start the UI, it means that there's another program somewhere using that port.

    It is a weird error though, if Sia is already available at port :9980 the UI should just automatically connect to it, instead of complain.



  • @Taek so to clarify, this means you have no idea how to fix the issue? In which case I will reinstall so I can access my wallet. But I'll no longer be hosting. I've experienced far too many problems and am tired of software issues outside of my control leading to financial penalties.


  • admins

    Sorry to hear that. But the error you are reporting is very unusual.



  • @Taek I've managed to get the Sia-UI working again. I backed up the storage folder & Sia-UI folder (containing GPUCache, consensus, gateway, host, etc folders) wiped Sia and re-downloaded and reinstalled. Copying over the backed up files seems to have worked as the block is almost fully synced, wallet seed is present and can be accessed. I've proceeded to add the old storage folder however I'm unsure if this is enough to make previous client data accessible. Is there any way I can determine if clients are able to access their data and that everything is running as it should be?



  • @Petar1989 I'm in the same situation too.I've already solved the problem by finding the corrupted json file.My host.json file which is in the host folder is corrupted! So I delete the file and restart sia-ui,it goes well now!
    The corrupted file maybe not host.json file ,it can be other json file.So we just need to check the json files in the AppData folder.



  • @Taek same issue on my mac right now, I am unable to begin buy and using sia because i am unable to download you client.



  • Win 7 Ult 64x

    this is what I get when I launch:

    A critical error loading Sia has occured: Siad unexpectedly exited. Error log: Loading...
    (0/6) Loading siad...
    (1/6) Loading gateway...
    (2/6) Loading consensus...
    (3/6) Loading transaction pool...
    (4/6) Loading wallet...
    (5/6) Loading host...
    (6/6) Loading renter...
    Closing host...
    Closing wallet...
    Closing transaction pool...
    Closing consensus set...
    Closing gateway...
    invalid argument



  • A critical error loading Sia has occured: Siad unexpectedly exited. Error log: Loading...
    (0/6) Loading siad...
    (1/6) Loading gateway...
    unable to read persisted json object from disk: open C:\Users\dylan\AppData\Roaming\Sia-UI\sia\gateway\nodes.json_temp: The system cannot find the file specified.



  • Can relate running 1.22-Windows, had system reboot after being stable for a few weeks. Roughly 2K contracts with about 200GB, hate to think how many SIAcoin I might have lost... Ran this....

    C:\Users\miner1\Desktop\Sia\resources\app\Sia>siad --sia-directory %APPDATA%/Sia-UI/sia
    Loading...
    (0/6) Loading siad...
    (1/6) Loading gateway...
    (2/6) Loading consensus...
    (3/6) Loading transaction pool...
    (4/6) Loading wallet...
    (5/6) Loading host...
    Closing wallet...
    Closing transaction pool...
    Closing consensus set...
    Closing gateway...
    error while loading contract manager atomic data: error loading the contract manager settings file: unable to read persisted json object from disk: unexpected end of JSON input

    So here's the SH*TY part - I didn't backed up my running config (note to self, create a batch file that BACKS up all your JSON data files and versions them for say XX copies incase you ever need to roll back).

    So I went looking for what would let me load my wallet. Made a few test changes and finally landed to move the "contractmanager" folder to a tmp subdirectory, let it become fresh and yeah I see my wallet. No storage shows up (uh oh) - so I added in some more storage and verify the changes to the json files. Sure enough contractmanager.json has my new share, and upon comparing the new contractmanager.json to my old contractmanager.json I get that gut feeling. Here's my old file below.

    C:\Users\miner1\AppData\Roaming\Sia-UI\sia\host\contractmanager\tmp>type contractmanager.json
    "Sia Contract Manager"
    "1.2.0"

    So somehow on a reboot/crash of my desktop this was running on (mining rig, I don't usually touch it), it wiped out the JSON data for my NAS1 3TB, and NAS 2 4TB share. This really does piss me off, yes, I should do better to backup a guest OS, but the corruption of a single json file and it restored fate is not what I would call a trustworthy product without the ability to self-heal itself from a backup it made itself, or somehow from the cloud. I would be happy to donate a few SIA to a self-backup mechanism within SIA. Just having the ability to say, your config looks corrupted, would you like to backup your correct config to a temp area and restore backup X, Y, or Z from the SIAcloud.
    OR
    Have the ability to have a something saved automagically where your shares are with the BIG file, and let it re-scan your shared contracts from those files and re-import (yes I know TB's of data files could take hours to read), but a small price to pay to recover lost JSON data.

    This could really help other hosts from losing coins (minus data corruption of hard local disk etc. ). I'm not out a ton, but I did loose 20-30K of SIA coin in contracts, so poof.

    Details here of my Host rig: https://siahub.info/host/2190


Log in to reply