On 28 May 2018 at 16:22, Mathieu Lonjaret <[email protected]> wrote: > On 28 May 2018 at 11:14, Matthias Teege <[email protected]> wrote: >> On Sat, May 26, 2018 at 01:48:40AM +0200, Mathieu Lonjaret wrote: >> >> Hi, >> >>> On 25 May 2018 at 23:54, Matthias Teege <[email protected]> wrote: >>> > On Fri, May 25, 2018 at 06:06:46PM +0200, Mathieu Lonjaret wrote: >>> > >>> > Thank you for clarifying. Is it possible to use more then one >>> > identity on a single perkeep instance? >>> >>> Not at the same time, no. Nothing prevents you from storing blobs from >>> different identities in the same blobserver, but you have to start a >>> different perkeepd for each identity (hence why you specify an >>> identity in the config file). >> >> Ah, that's okay. I think I should use different indexes too? > > Yes. > >>> > This is the stats output from perkeep: >>> > >>> > 2018/05/25 23:39:06 index/corpus: stats: 54.149 MiB mem: 104975 blobs >>> > (1.686 GiB) (58510 schema (1064 permanode, 36974 file (317 image), ...) >> >>> Yep, that looks good, no? >> >> Yes, perfect :) but I'm not sure if I can retrieve all images and files. >> >>> pk uses the client config file. Have you also set the correct identity >>> in your client config file? >> >> Yes, I've checked it again: >> >> New identity (almost empty): >> >> $ jq -r .identity .config/perkeep/server-config.json >> ~ >> B18487E09E6A321F >> $ jq -r .identity .config/perkeep/client-config.json >> ~ >> B18487E09E6A321F >> $ perkeepd -reindex >> 2018/05/28 10:26:51 index/corpus: stats: 53.993 MiB mem: 104975 blobs >> (1.686 GiB) (58510 schema (1064 permanode, 36974 file (317 image), ...) >> $ pk search 'is:image' | jq -r '.blobs[].blob' | wc -l >> 1 >> >> Thats ok. There is only one image for that identity. >> >> For the old identity it looks like this: >> >> $ jq -r .identity .config/perkeep/server-config.json >> 4F6E82AB >> $ jq -r .identity .config/perkeep/client-config.json >> 4F6E82AB >> $ perkeepd -reindex >> 018/05/28 10:16:05 index/corpus: stats: 47.446 MiB mem: 104975 blobs (1.686 >> GiB) (58510 schema (1064 permanode, 36974 file (317 image), ...) >> $ pk search 'is:image' | jq -r '.blobs[].blob' | wc -l >> 5 >> >> I'm not sure about the "missing" 311 images.
wait, I've just realized the answer could be very simple. Did you make permanodes for all these files and images? the 'is:image' query is looking for permanodes that have a camliContent image, not images by themselves. So if you stored these 311 images without making permanodes for them, it's normal that the index finds them, but that the search query does not. > Ok. I suppose it could be another bug with the switch to sha224, or > the switch to using the long form of the key ID fingerprint. Let me > think on how to debug that further. > What kind of index are you using? MySQL, or LevelDB, or ... ? > >> I've checked for another identity: >> >> $ grep -r camliSigner blobs/ | cut -d ':' -f3 | sort | uniq -c >> >> ~ >> 7 "sha1-1db6fc5e7add169face657fb6e53c6595dce0948" >> 4462 "sha1-1db6fc5e7add169face657fb6e53c6595dce0948", >> 4 "sha224-3368771ade1c68d6dc2444973be24e3bc99b0083fc33af8e82f28f4c", >> >> but there are only two. >> >> 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.
