[ANN] Sia - Decentralized Storage

[ol92]

Hello,
I am mining on windows. The new wallet has a strange behaviour :
- correct amount on "overview" (without the new block mined which is normal I presume)
- On the wallet tab (the wallet is unlocked)  : "Balance: Locked       Pending: Locked     Unlock"
Is this normal?

Hey, yes I am seeing that as well in the wallet page. Not real sure why it looks like that. I think everyone most likely sees that as well right now.

Mined blocks wont post until 144 blocks if I am thinking right lol still drinking my morning coffee  

Thanks

[MinermanNC]

Loaded my wallet up just now, first time today since closing out last night. Now it opens and all, but is just sitting there as if its not connecting to the network? no peers, no balance, no host, no blocks, no addresses and when I click on LOCKED_STATE it does nothing.  

Anyone else seeing this after completely closing out SIA -UI? today? Seemed it closed and opened fine yesterday a few times after initial run and getting password etc.

[pallas]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

[MinermanNC]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

Ya I am noticing now when I launch wallet I am getting a pop up message saying "siad exited with code: 0

What to do? lol And I have coins and a file in wallet  

Now 0.3.3.3 seems to load fine, siad included. Of course that wallet is now empty cause I did the load legacy wallet option yesterday. Weird because all was working so good. And yes I am closing out siad after starting 0.3.3.3. Even did a reboot 4.2 won't load up... it opens and that's it with that error code.

[NASdaq]

Can sia run over the TOR network?

[chrysophylax]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

i have had the sia wallet open AND unlocked and left it over night after importing all the coins from the old wallets ...

at first the new wallet ( 0.4.2 )  didnt show any sign of having anything done except for the acknowledgment that the legacy wallets were imported ... shortly after - about an hour i guess - it showed all the coins in the wallet ... and the 'current' block height ... since we cant check via the sia explorer - i took it as working and current ...

bed - sleep - woke ... i find the wallet has increased by 5 blocks only - and that all still seems well with it as far as i can tell ...

im now worried about shutting the wallet down - 'just in case' there really is something wrong ... too many coins to lose now - all consolodated into one wallet ...

will leave it open until taek comes out with some announcement of what to do ...

i still have a great deal of work left on my end - and will be working through the weekend to get them all running for GRN and thefarm and the donation sevrers ...

ive stopped mining sia for the time being - but still VERY interetsed in the project ...

ive pmd you back pallas - let me know what your thoughts are please mate ... as we can implement a few ideas with sia also ...

tanx ...

#crysx

[andyatcrux]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

i have had the sia wallet open AND unlocked and left it over night after importing all the coins from the old wallets ...

at first the new wallet ( 0.4.2 )  didnt show any sign of having anything done except for the acknowledgment that the legacy wallets were imported ... shortly after - about an hour i guess - it showed all the coins in the wallet ... and the 'current' block height ... since we cant check via the sia explorer - i took it as working and current ...

bed - sleep - woke ... i find the wallet has increased by 5 blocks only - and that all still seems well with it as far as i can tell ...

im now worried about shutting the wallet down - 'just in case' there really is something wrong ... too many coins to lose now - all consolodated into one wallet ...

will leave it open until taek comes out with some announcement of what to do ...

i still have a great deal of work left on my end - and will be working through the weekend to get them all running for GRN and thefarm and the donation sevrers ...

ive stopped mining sia for the time being - but still VERY interetsed in the project ...

ive pmd you back pallas - let me know what your thoughts are please mate ... as we can implement a few ideas with sia also ...

tanx ...

#crysx

Both Minerman and Pallas corrupted the database. You CANNOT kill the Siad process in the task manager. You MUST use Siac to close Siad. Simply delete the database file and reload. It is planned for a fix in the next GUI I think.

[chrysophylax]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

i have had the sia wallet open AND unlocked and left it over night after importing all the coins from the old wallets ...

at first the new wallet ( 0.4.2 )  didnt show any sign of having anything done except for the acknowledgment that the legacy wallets were imported ... shortly after - about an hour i guess - it showed all the coins in the wallet ... and the 'current' block height ... since we cant check via the sia explorer - i took it as working and current ...

bed - sleep - woke ... i find the wallet has increased by 5 blocks only - and that all still seems well with it as far as i can tell ...

im now worried about shutting the wallet down - 'just in case' there really is something wrong ... too many coins to lose now - all consolodated into one wallet ...

will leave it open until taek comes out with some announcement of what to do ...

i still have a great deal of work left on my end - and will be working through the weekend to get them all running for GRN and thefarm and the donation sevrers ...

ive stopped mining sia for the time being - but still VERY interetsed in the project ...

ive pmd you back pallas - let me know what your thoughts are please mate ... as we can implement a few ideas with sia also ...

tanx ...

#crysx

Both Minerman and Pallas corrupted the database. You CANNOT kill the Siad process in the task manager. You MUST use Siac to close Siad. Simply delete the database file and reload. It is planned for a fix in the next GUI I think.

ok - so a clean replacement of the database after siad is closed with siac ... where is the database? ... just a straight delete? ...

as for the blame to be placed squarely on pallas and minerman ... well - i can only say that those who actually contribute to the improvement of the code and functionality ( with the full approval of taek dont forget ) means that these people are actually taking an active involvement ... not just a 'watching' stance - like me   ...

this means that issue wil arise and bugs need to be squashed ... sia is still in beta afterall - so these things are expected ...

i appreciate the heads up on the killing process ... i was only 'killing' the actual siad process in lunux - which probably doesnt help either ...

#crysx

[MinermanNC]

Ah, I have been killing siad from task manager (after closing out wallet) since day 1 (as needed) with no problems until today after reopening my wallet... IF that even is the cause for sure? so suddenly doing that corrupts the database? how or why would anyone have known differently? I mean there should be a high level alert - "not to kill siad from task manager" if that's all it takes to corrupt your database lol, anyways I am installing another 4.2 on another PC ..its seems fine so far. Will experiment on that wallet see if I can corrupt it. 

[chrysophylax]

Hah, this is peculiar... I just went to copy my wallet.dat file from the "corrupted" wallet folder and its not there? its gone.. so where did it go?  

I guess this partially explains why I was getting that error message " siad exited with code: 0 ,, strange lol

its not a .dat file anymore ... its a .json file ...

so where the original .dat was - is now the .json file ...

btw - just checked the wallet and it seems to be running fine ... at block 16427 currently shown - so its progressing but very slowly ...

#crysx

[MinermanNC]

Hah, this is peculiar... I just went to copy my wallet.dat file from the "corrupted" wallet folder and its not there? its gone.. so where did it go?  

I guess this partially explains why I was getting that error message " siad exited with code: 0 ,, strange lol

its not a .dat file anymore ... its a .json file ...

so where the original .dat was - is now the .json file ...

#crysx

lol I just remembered that and had looked on that new wallet I was installing just now... I forgot

But thx for that heads up... I'm about to fall asleep lol 

[chrysophylax]

Hah, this is peculiar... I just went to copy my wallet.dat file from the "corrupted" wallet folder and its not there? its gone.. so where did it go?  

I guess this partially explains why I was getting that error message " siad exited with code: 0 ,, strange lol

its not a .dat file anymore ... its a .json file ...

so where the original .dat was - is now the .json file ...

#crysx

lol I just remembered that and had looked on that new wallet I was installing just now... I forgot

But thx for that heads up... I'm about to fall asleep lol 

hehehe ... i know how you feel ... bed at 0600 this morning - then awake today at 1100 - and been flat out since ...

need another strong coffee and food and back into it again till late tonight to finish parts of the project im working on also ...

so i really do KNOW how you feel ...

coffee - the magic mushroom of peakdom ... the black gold of awakedness ... the - ummm - you know what i mean ...

#crysx

[andyatcrux]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

i have had the sia wallet open AND unlocked and left it over night after importing all the coins from the old wallets ...

at first the new wallet ( 0.4.2 )  didnt show any sign of having anything done except for the acknowledgment that the legacy wallets were imported ... shortly after - about an hour i guess - it showed all the coins in the wallet ... and the 'current' block height ... since we cant check via the sia explorer - i took it as working and current ...

bed - sleep - woke ... i find the wallet has increased by 5 blocks only - and that all still seems well with it as far as i can tell ...

im now worried about shutting the wallet down - 'just in case' there really is something wrong ... too many coins to lose now - all consolodated into one wallet ...

will leave it open until taek comes out with some announcement of what to do ...

i still have a great deal of work left on my end - and will be working through the weekend to get them all running for GRN and thefarm and the donation sevrers ...

ive stopped mining sia for the time being - but still VERY interetsed in the project ...

ive pmd you back pallas - let me know what your thoughts are please mate ... as we can implement a few ideas with sia also ...

tanx ...

#crysx

Both Minerman and Pallas corrupted the database. You CANNOT kill the Siad process in the task manager. You MUST use Siac to close Siad. Simply delete the database file and reload. It is planned for a fix in the next GUI I think.

ok - so a clean replacement of the database after siad is closed with siac ... where is the database? ... just a straight delete? ...

as for the blame to be placed squarely on pallas and minerman ... well - i can only say that those who actually contribute to the improvement of the code and functionality ( with the full approval of taek dont forget ) means that these people are actually taking an active involvement ... not just a 'watching' stance - like me   ...

this means that issue wil arise and bugs need to be squashed ... sia is still in beta afterall - so these things are expected ...

i appreciate the heads up on the killing process ... i was only 'killing' the actual siad process in lunux - which probably doesnt help either ...

#crysx

Yeah, same thing happened to me before someone told me about it. It was not a problem in 0.3.3.3 but is now. The database is in the resources\app\Sia\consensus folder. Yes it is a straight delete.

[chrysophylax]

I couldn't get past block 16420, so I stopped the gui and killed the daemon.
Now when I run it I get this error and it stops:

database guard indicates inconsistency within database

What to do?

i have had the sia wallet open AND unlocked and left it over night after importing all the coins from the old wallets ...

at first the new wallet ( 0.4.2 )  didnt show any sign of having anything done except for the acknowledgment that the legacy wallets were imported ... shortly after - about an hour i guess - it showed all the coins in the wallet ... and the 'current' block height ... since we cant check via the sia explorer - i took it as working and current ...

bed - sleep - woke ... i find the wallet has increased by 5 blocks only - and that all still seems well with it as far as i can tell ...

im now worried about shutting the wallet down - 'just in case' there really is something wrong ... too many coins to lose now - all consolodated into one wallet ...

will leave it open until taek comes out with some announcement of what to do ...

i still have a great deal of work left on my end - and will be working through the weekend to get them all running for GRN and thefarm and the donation sevrers ...

ive stopped mining sia for the time being - but still VERY interetsed in the project ...

ive pmd you back pallas - let me know what your thoughts are please mate ... as we can implement a few ideas with sia also ...

tanx ...

#crysx

Both Minerman and Pallas corrupted the database. You CANNOT kill the Siad process in the task manager. You MUST use Siac to close Siad. Simply delete the database file and reload. It is planned for a fix in the next GUI I think.

ok - so a clean replacement of the database after siad is closed with siac ... where is the database? ... just a straight delete? ...

as for the blame to be placed squarely on pallas and minerman ... well - i can only say that those who actually contribute to the improvement of the code and functionality ( with the full approval of taek dont forget ) means that these people are actually taking an active involvement ... not just a 'watching' stance - like me   ...

this means that issue wil arise and bugs need to be squashed ... sia is still in beta afterall - so these things are expected ...

i appreciate the heads up on the killing process ... i was only 'killing' the actual siad process in lunux - which probably doesnt help either ...

#crysx

Yeah, same thing happened to me before someone told me about it. It was not a problem in 0.3.3.3 but is now. The database is in the resources\app\Sia\consensus folder. Yes it is a straight delete.

if i come across this issue - ill do just that ... but as it stands - so far - so good ...

tanx for that ...

#crysx

[nextgencoin]

I'm using the mac wallet, a few questions.


Do I need sia coins to let my hard drive space be used?

Will it be used instantly or must i wait for it to be actually used?


I'm getting error 400, ensure forward port 9982?

[bitspill]

Do I need sia coins to let my hard drive space be used?
No, however later down the line it will be possible to offer your own coins as collateral to back file contracts.

Will it be used instantly or must i wait for it to be actually used?
Disk space will be used as contracts are uploaded, not allocated in one shot.

I'm getting error 400, ensure forward port 9982?
Is the port forwarded? Firewalls? UPNP enabled? Other than that I'm not much help on this question, sorry.

[nextgencoin]

no idea what port forwarded means at all....some layman terms please if anyone knows, I'm on a mac.

[chrysophylax]

Do I need sia coins to let my hard drive space be used?
No, however later down the line it will be possible to offer your own coins as collateral to back file contracts.

Will it be used instantly or must i wait for it to be actually used?
Disk space will be used as contracts are uploaded, not allocated in one shot.

I'm getting error 400, ensure forward port 9982?
Is the port forwarded? Firewalls? UPNP enabled? Other than that I'm not much help on this question, sorry.

the port forward error is an old one and - as we can see - a persistent one ...

taek has issued an addendum to the instructions ( which for the life of me i cannot find ) that specifies how to force an announce fromt he wallet - even though sia itself cant see an open port ...

its the same issue we have here - and i cant announce the storage space due to this issue - but the forwarding and network components are all setup ... we have a very different network setup from the average user anyway - but a port forward to a static ip should work ... it doesnt ...

im looking for the instructions on how to force announce your host ... can anyone help here? ...

#crysx

[bitspill]

no idea what port forwarded means at all....some layman terms please if anyone knows, I'm on a mac.

Port forwarding is a setting on your internet router/modem and not a setting of the computer.

The procedure will vary depending on make/model of the router/modem, at the below link you can find guides for most devices.

http://portforward.com/english/routers/port_forwarding/routerindex.htm

[bitspill]

Do I need sia coins to let my hard drive space be used?
No, however later down the line it will be possible to offer your own coins as collateral to back file contracts.

Will it be used instantly or must i wait for it to be actually used?
Disk space will be used as contracts are uploaded, not allocated in one shot.

I'm getting error 400, ensure forward port 9982?
Is the port forwarded? Firewalls? UPNP enabled? Other than that I'm not much help on this question, sorry.

the port forward error is an old one and - as we can see - a persistent one ...

taek has issued an addendum to the instructions ( which for the life of me i cannot find ) that specifies how to force an announce fromt he wallet - even though sia itself cant see an open port ...

its the same issue we have here - and i cant announce the storage space due to this issue - but the forwarding and network components are all setup ... we have a very different network setup from the average user anyway - but a port forward to a static ip should work ... it doesnt ...

im looking for the instructions on how to force announce your host ... can anyone help here? ...

#crysx

If you have Sia 0.4.x then manually announcing from the command line should force the announce.

Code:

siac host announce ip:port