Make your own. 1c4
Critter commuicanion chaos community
@mjay it’s gotten to the point they start pre-ddossing continental chokepoints, they should move that onto a tor hidden service as that’s not a fun side effect anymore
@fydel I like your hamster videos. Never change.
hehe
hamsters are like little dogs
is it enough to backup wallet.db?
No
You should have a new enough version to not have a wallet.db
You want to backup everything in that directory
Should usually be a small number of files
With random names
ah. okay. thanks.
it does that so it can merge files into new files and leave the old files there until the merge is done
and is always safe
and you can combine wallets by simply copying the files into one directory
it is fun
and on load it will merge all the files into one new file and delete the old ones
Hi guys
After some weeks tried to sync a fresh node on Debian 9, running within a Proxmox VM, and got some strange "errors".
There are more lines below but here are the first three. Have to start the node again after that message
@Ghadras try removing your node db and trying again
that is odd
Tried it already in a second fresh VM, same issue. Should I try instead jre-headless?
Shouldn't matter as long as you have jvm 8 or later
You can put db_type=lobstack in your config
but that is strange error
@Ghadras default-jre or some specific jre variant? on d9, default-jre-headless works
Sync still in progress now with openjdk-8-jre-headless :slightly_smiling_face:
were you using jdk9 by any chance?
8 is good, 10 is good
9 is failure in strange ways
used 8 before as well
stopped again. Now using db_type=lobstack
I did change some db stuff recently, not impossible that I screwed something up and only people syncing from scratch are hitting it
I'll go nuke a few nodes and see if i can reproduce
Checked slack history and found some user with similar issues and after switching from rocksdb the issue was gone. But I don't think it's up to some changes you have done. Tomorrow I will try it on a Ubuntu 16.04 VM.
@Fireduck i’ve had weird issues with openjdk from debian over the years, so better fire up a debian somewhere and check