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.
