On 25 May 2018 at 17:44, Matthias Teege <[email protected]> wrote: > On Fri, May 25, 2018 at 03:53:20PM +0200, Mathieu Lonjaret wrote: > > Hi, > >> Did you change anything about your config? If you're using a different >> config file or config dir, did you make sure to copy over your GPG key >> as well? > > No, I did not copy the GPG key from the old setup. My goal is to > merge three different perkeep/camlistore instances and I assumed, > that I can rebuild the index from the blobs only. Would be nice for > a long term archive. :)
your GPG identity is your proof of ownership. the blobs and files themselves are still accessible wherever your move them, but the index respects the ownership of any mutation made, i.e. of any claim or permanode created. So if you're using your new perkeepd with a new GPG key, when you're browsing with the web UI, you're asking the index to show you the permanodes that you (i.e. the new GPG key) are the owner of. It cannot show you the old permanodes, because you're not the owner of them anymore. Long story short, if you've lost your old GPG keys you still have your contents/files/data, but you'll have to recreate all the permanodes for them with the new GPG key. >> Do the server logs say anything relevant? What about the javascript > > Looks like the reindexing stops after some blobs. The old blobs are > hashed with SHA1. The blobdir looks like this: > > drwx------. 3 mt user 4096 May 25 15:57 cache > -rw-------. 1 mt user 707 May 25 10:40 GENERATION.dat > drwx------. 3 mt user 4096 May 25 15:57 packed > drwx------. 258 mt user 4096 May 25 11:18 sha1 > drwx------. 15 mt user 4096 May 25 13:44 sha224 > drwx------. 2 mt user 4096 May 25 15:57 sync-to-index-queue.leveldb > drwx------. 2 mt user 4096 May 25 15:57 thumbmeta.leveldb > > % perkeepd -reindex -keep-going > ~ > 2018/05/25 15:57:25 Starting perkeepd version master, 2018-05-24-a140b28f5d; > Go go1.10.2 (linux/amd64) > 2018/05/25 15:57:25 Starting to listen on http://localhost:3179 > 2018/05/25 15:57:25 Index wiped. > 2018/05/25 15:57:25 blobpacked: checking integrity of packed blobs against > index... > 2018/05/25 15:57:25 blobpacked: 0 large blobs found in index, 0 missing from > index > 2018/05/25 15:57:25 Reindexing /index/ ... > 2018/05/25 15:57:25 Rebuilding index... > 2018/05/25 15:57:25 Reindexing at > sha1-00010ede8ad52b7058b0f13edda52e9e507aa9a5 > 2018/05/25 15:57:26 Reindexing at > sha1-0b39b8fb29f165151e6795605e50576e4815b080 > 2018/05/25 15:57:27 Reindexing at > sha1-153b36dd882c715c88b074f38f8282795ef59243 > 2018/05/25 15:57:28 Reindexing at > sha1-191022a84941213748f09578ef2da503ab704c79 > 2018/05/25 15:57:29 Reindexing at > sha1-2504c9a027481489afd5e8e2b79ff9d704d771b0 > 2018/05/25 15:57:30 Reindexing at > sha1-31338a3e59e19dbe72b1ddbb59650d2b406fd12b > 2018/05/25 15:57:31 Reindexing at > sha1-3932f036baa715a149ced9152db608ed981ead20 > 2018/05/25 15:57:32 Reindexing at > sha1-3ff471a21a2e03e8ec0cb234f90fbd5110abe9b3 > 2018/05/25 15:57:33 Reindexing at > sha1-4bd5fdb2ad4020aeac3cedd958cd0cdb9aab4682 > 2018/05/25 15:57:34 Reindexing at > sha1-548adc982d90338bef6cfe91c49d4ff33691c997 > 2018/05/25 15:57:35 Reindexing at > sha1-5e70312c9cb86fa3a37610659da298a700cfaab1 > 2018/05/25 15:57:36 Reindexing at > sha1-6a970e17001b5ad2e6101dce2435de704bc572b4 > 2018/05/25 15:57:37 Reindexing at > sha1-759122320b96ae9e025cff107066b4277b6f19b3 > 2018/05/25 15:57:38 Reindexing at > sha1-7aca3dc69f464e777b422cdc616bc8998c55f6ca > 2018/05/25 15:57:39 Reindexing at > sha1-85f0e32697f2a06e3541390626467d225e45758b > 2018/05/25 15:57:40 Reindexing at > sha1-8ffe939a78c9a475ba6246e8a22946d964bfddb8 > 2018/05/25 15:57:41 Reindexing at > sha1-974f356b03601dd477601b3d773b7ba450ad3a0f > 2018/05/25 15:57:42 Reindexing at > sha1-a229dc412e621bdeff74bfff6e1f80707f7df214 > 2018/05/25 15:57:43 Reindexing at > sha1-ab87b524eea2bf4dd6e904cc2e87f7bf749481e2 > 2018/05/25 15:57:44 Reindexing at > sha1-b43e7b2a750b4c1f49f50024f989e7be3694dd03 > 2018/05/25 15:57:45 Reindexing at > sha1-b9e2ffd75055d922760e5c983906f0ce1c61895b > 2018/05/25 15:57:46 Reindexing at > sha1-c3f69a5086b391794f835ced8faba56700b2ef7e > 2018/05/25 15:57:47 Reindexing at > sha1-ccc22e2409bc21c1f4ae1a8d04154508507f7065 > 2018/05/25 15:57:48 Reindexing at > sha1-d608a81e426c3a2e8757068c6741fa6f946f9a65 > 2018/05/25 15:57:49 Reindexing at > sha1-df5e761f6edfd8413f69745c3bc306e77c4d876f > 2018/05/25 15:57:50 Reindexing at > sha1-e91c136ee0b6623c4b76cae7970236a80a30c918 > 2018/05/25 15:57:51 Reindexing at > sha1-f1721c26cc21b41f41be41ef376b0238fa6a37fe > 2018/05/25 15:57:52 Reindexing at > sha1-fa8f698d8452a7fc752c5a36e8e7a19326cc4999 > 2018/05/25 15:57:53 Index rebuild complete. yeah I would guess these are only the blobs your created with the new GPG identity. > Thats all but there are a lot more blobs. > > % pk list | grep sha1 | wc -l > 104961 > > % pk list | grep sha224 | wc -l > 13 > > There is no explicit error message. > > Thanks, > Matthias > > -- > You received this message because you are subscribed to the Google Groups > "Perkeep" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
