In the user-data metadata, in addition to the image name (perkeep/server), did you also change the tarball it was fetching as I instructed above? If not, you're still going to get an "old" server, instead of the latest image. In other words, are you seeing that the running version is indeed 66e6766571f12e0122b1c1aaf762ba62c54bb630 ?
On 29 April 2018 at 14:51, Tyler Stalder <[email protected]> wrote: > I'm having similar issues going from a camlistore build from 09/2017 to the > latest perkeep. I was able to upgrade by modifying the 'user-data' key of > the GCE instance's custom metadata (changing camlistore/server to > perkeep/server on the last ExecStart line) and resetting the instance. > > Now it seems like I'm having a sha1 vs sha224 issue. > * My importer accounts are no longer running or listed in status (though the > the blobs are still there by ref, but don't have any attributes). > * My web ui shows folders without names and no nodes. https://d.pr/i/JXx3vj > > Possibly similar to: > https://github.com/perkeep/perkeep/issues/1069 > https://groups.google.com/forum/#!searchin/camlistore/selenium%7Csort:date/camlistore/yGwsg3-9ou4/h-gZsWWwBQAJ > > I'm now copying a few blobs from GCE to my local instance to be able to test > code changes. Is there any kind of migration process that needed to take > place? Or what have other pre-sha244 users done? > > > > > > On Sunday, April 29, 2018 at 2:14:51 PM UTC-7, jason gessner 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.
