Excellent, thanks for the update. Sorry you had to be our guinea pig, that was unintended.
I have a plan for an automatic camlistore -> perkeep migration, and I hope to have it ready tomorrow, so hopefully no one else will have to suffer the same woes you did. On 29 April 2018 at 21:34, jason gessner <[email protected]> wrote: > thanks for the tip on the user-data. I updated things there and the image > is stable. > > The recovery printed a warning about unindexed blobs. I restarted the > server with a reindex and things came back, so I think i'm back in business. > > -jason > > > On Sun, Apr 29, 2018 at 8:25 PM Mathieu Lonjaret > <[email protected]> wrote: >> >> Can you please paste the log lines that the server prints when it's >> doing the recovery? >> >> >> On 29 April 2018 at 14:14, jason gessner <[email protected]> wrote: >> > i threw a new name on there and things came up with no letsencrypt >> > errors, >> > so that was unrelated. >> > >> > However, after recovery, there is no data visible in the UI. :/ >> > >> > -jason >> > >> > >> > On Sun, Apr 29, 2018 at 3:37 PM jason gessner <[email protected]> >> > wrote: >> >> >> >> i made this diff: >> >> >> >> < ExecStartPre=/bin/bash -c '/usr/bin/curl >> >> >> >> https://storage.googleapis.com/camlistore-release/docker/perkeepd.tar.gz | >> >> /bin/gunzip -c | /usr/bin/docker load' >> >> --- >> >> > ExecStartPre=/bin/bash -c '/usr/bin/curl >> >> > >> >> > https://storage.googleapis.com/camlistore-release/docker/camlistored.tar.gz >> >> > | /bin/gunzip -c | /usr/bin/docker load' >> >> >> >> for a full file containing: >> >> >> >> $ cat /etc/systemd/system/camlistored.service >> >> [Unit] >> >> Description=Camlistore >> >> After=docker.service mysql.service >> >> Requires=docker.service mysql.service >> >> >> >> [Service] >> >> ExecStartPre=/usr/bin/docker run --rm -v /opt/bin:/opt/bin >> >> camlistore/systemd-docker >> >> ExecStartPre=/bin/bash -c '/usr/bin/curl >> >> >> >> https://storage.googleapis.com/camlistore-release/docker/perkeepd.tar.gz | >> >> /bin/gunzip -c | /usr/bin/docker load' >> >> ExecStart=/opt/bin/systemd-docker run --rm -p 80:80 -p 443:443 --name >> >> %n >> >> -v /run/camjournald.sock:/run/camjournald.sock -v >> >> /var/lib/camlistore/tmp:/tmp --link=mysql.service:mysqldb >> >> perkeep/server >> >> RestartSec=1s >> >> Restart=always >> >> Type=notify >> >> NotifyAccess=all >> >> >> >> [Install] >> >> WantedBy=multi-user.target >> >> >> >> I restarted the instance, but it lost the changes to the file. I tried >> >> again and was able to catch the logs, which told me to do the recovery >> >> with >> >> camlistore-recovery metadata. I did that and it looks like the >> >> recovery >> >> worked, but i can't load the website. Chrome says it isn't secure and >> >> i see >> >> this in the logs: >> >> >> >> 2018/04/29 20:35:40 http: TLS handshake error from >> >> 184.58.251.229:63903: >> >> 429 urn:acme:error:rateLimited: Error creating new cert :: too many >> >> certificates already issued for exact set of domains: >> >> #######.#####.###: see >> >> https://letsencrypt.org/docs/rate-limits/ >> >> 2018/04/29 20:35:40 http: TLS handshake error from >> >> 184.58.251.229:63904: >> >> acme/autocert: missing certificate >> >> 2018/04/29 20:35:42 http: TLS handshake error from >> >> 184.58.251.229:63905: >> >> acme/autocert: missing certificate >> >> 2018/04/29 20:35:42 http: TLS handshake error from >> >> 184.58.251.229:63906: >> >> acme/autocert: missing certificate >> >> 2018/04/29 20:35:43 http: TLS handshake error from >> >> 184.58.251.229:63907: >> >> acme/autocert: missing certificate >> >> 2018/04/29 20:35:43 http: TLS handshake error from 184 >> >> >> >> yesterday it looked like my cert was already renewed - it was valid >> >> from >> >> 2018-04-28 to 2018-07-27. >> >> >> >> So, some progress, i guess? >> >> >> >> -jason >> >> >> >> >> >> On Sun, Apr 29, 2018 at 1:06 PM Mathieu Lonjaret >> >> <[email protected]> wrote: >> >>> >> >>> ok, I think that should get you unstuck for now: >> >>> >> >>> sudo vim /etc/systemd/system/camlistored.service >> >>> >> >>> On the ExecStartPre line, change the downloaded tarball from >> >>> camlistored.tar.gz to perkeepd.tar.gz >> >>> On the ExecStart line, if the image name at the end is >> >>> camlistore/server, change it to perkeep/server >> >>> save and quit >> >>> >> >>> sudo systemctl daemon-reload >> >>> sudo systemctl restart camlistored >> >>> >> >>> Let me know how that goes please. >> >>> >> >>> >> >>> >> >>> On 29 April 2018 at 10:36, jason gessner <[email protected]> wrote: >> >>> > cool, thanks for getting back to me, Mathieu. No worries. >> >>> > >> >>> > Drop me a note and i'm happy to try whatever. >> >>> > >> >>> > -jason >> >>> > >> >>> > >> >>> > On Sun, Apr 29, 2018 at 12:21 PM Mathieu Lonjaret >> >>> > <[email protected]> wrote: >> >>> >> >> >>> >> Yeah, my bad, sorry. >> >>> >> We also changed the service name, which is now perkeepd. But of >> >>> >> course >> >>> >> I did not think of an automatic transition, so you're now stuck >> >>> >> with >> >>> >> the old camlistored service while the launcher uses the perkeepd >> >>> >> service, which is why restarting does not do anything for you. >> >>> >> I'll try to work on an automatic transition, but in the meantime >> >>> >> I'm >> >>> >> first going to see how to help you migrate manually. More on that >> >>> >> soon >> >>> >> hopefully. >> >>> >> >> >>> >> >> >>> >> On 29 April 2018 at 09:58, jason.gessner <[email protected]> >> >>> >> wrote: >> >>> >> > I see there is a new version published at perkeep.org/launch >> >>> >> > (66e6766571f12e0122b1c1aaf762ba62c54bb630). My GCE instance >> >>> >> > seems >> >>> >> > to be >> >>> >> > stuck on e9e9da4bf840b1616a78c9fda5a1b26b775b9b98. >> >>> >> > >> >>> >> > Resetting the VM and running "sudo systemctl restart camlistored" >> >>> >> > doesn't >> >>> >> > seem to help - it stays on the e9 version. >> >>> >> > >> >>> >> > What should i be looking at to troubleshoot? >> >>> >> > >> >>> >> > -jason >> >>> >> > >> >>> >> > -- >> >>> >> > 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. >> >>> > >> >>> > -- >> >>> > 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. >> > >> > -- >> > 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. > > -- > 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.
