What is this error ?
looking my files the trust-cache.json is in strage state:
fabrizio@snode:/mnt$ ll
ls: cannot access ‘trust-cache.json’: Structure needs cleaning
total 208
drwxr-xr-x 8 root root 4096 Apr 4 23:24 ./
drwxr-xr-x 26 root root 4096 Mar 31 10:59 …/
drwxrwxrwx 2 root root 4096 Sep 25 2019 certs/
drwxr-xr-x 2 root root 4096 Sep 25 2019 config/
-rw-r–r-- 1 root root 877 Mar 9 14:58 config.yaml
drwxr-xr-x 3 root root 4096 Sep 19 2019 identity/
-rw------- 1 root root 131072 Oct 4 2019 kademlia
drwx------ 2 root root 16384 Sep 25 2019 lost+found/
drwxr-xr-x 7 root root 4096 Apr 1 03:46 mnt/
-rw------- 1 root root 32768 Apr 5 00:02 revocations.db
drwxr-xr-x 7 root root 4096 Apr 4 23:39 storage/
-??? ? ? ? ? ? trust-cache.json
How I can fix it ?
thx
My trust-cache.json
has permissions 600
Here are the contents of my file you may be able to simply copy/paste:
{
"entries": {
"https://tardigrade.io/trusted-satellites": [
{
"SatelliteURL": {
"id": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S",
"host": "us-central-1.tardigrade.io",
"port": 7777
},
"authoritative": true
},
{
"SatelliteURL": {
"id": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs",
"host": "europe-west-1.tardigrade.io",
"port": 7777
},
"authoritative": true
},
{
"SatelliteURL": {
"id": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6",
"host": "asia-east-1.tardigrade.io",
"port": 7777
},
"authoritative": true
},
{
"SatelliteURL": {
"id": "118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW",
"host": "satellite.stefan-benten.de",
"port": 7777
},
"authoritative": false
},
{
"SatelliteURL": {
"id": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE",
"host": "saltlake.tardigrade.io",
"port": 7777
},
"authoritative": true
}
]
}
}
I have solve using fsck.ext4 that delete the corrupted trust-cache.json and than I have restore this file from a backup
Did your OS unexpectedly shutdown? Power outage? Some external event that would result in your filesystem corrupting files? Or did the problem just occur somewhat randomly?
EXT4 is a journaling filesystem and is usually configured to perform an fsck every 50 or so boots. Usually, the only time I see corrupted files is when I forget to set an fsck interval or when a hard drive begins to fail.