Hi!
I pulled down the latest from kittystore, hyperkitty, and hyperkitty_standalone today and got this error when trying to run the app:
'SchemaUpgradeNeeded at /'
I couldn't figure out how to upgrade the schema (the manage.py migrate command didn't seem to work) so I just blew away my db and re-imported from scratch.
Is there a better way to do this or is reimporting the best thing to do for now?
~m
Hi!
Is there a better way to do this or is reimporting the best thing to do for now?
A few things about that:
- this error is actually an improvement, it means that HyperKitty does not try to auto-update the KittyStore database anymore, which can take a long time while the browser is loading, and is better for security because it allows setting HyperKitty to have a read-only access to the search index in KittyStore.
- HyperKitty should actually redirect you to an explicit error page if the schema is not up-to-date, but it would only do that if you changed the MIDDLEWARE_CLASSES in settings.py as it was updated recently in hyperkitty_standalone (the KittyStoreDjangoMiddleware class was moved, its path has changed: https://github.com/hyperkitty/hyperkitty_standalone/commit/fee700b39b7738f26...)
- I've tried to keep the docs in sync, so the command to update your KittyStore schema is here: https://hyperkitty.readthedocs.org/en/latest/install.html#upgrading
So yeah, there's a better way :-) Hope this will help next time, I wish I'd been around on IRC but that was at about 4:30AM for me...
Cheers! Aurélien
On 11/22/2013 02:16 AM, Aurelien Bompard wrote:
- I've tried to keep the docs in sync, so the command to update your
KittyStore schema is here: https://hyperkitty.readthedocs.org/en/latest/install.html#upgrading
I stared at this doc last night and somehow just completely missed the upgrading section - thank you :)
So yeah, there's a better way :-) Hope this will help next time, I wish I'd been around on IRC but that was at about 4:30AM for me...
Definitely, thank you!
~m
On 11/22/2013 11:24 AM, Máirín Duffy wrote:
On 11/22/2013 02:16 AM, Aurelien Bompard wrote:
- I've tried to keep the docs in sync, so the command to update your
KittyStore schema is here: https://hyperkitty.readthedocs.org/en/latest/install.html#upgrading
I stared at this doc last night and somehow just completely missed the upgrading section - thank you :)
Okay, so that worked the first time. When I did another pull today and had to do an upgrade, I tried it (kittystore-updatedb -p . -s settings) again but I keep getting this error:
sqlite3.OperationalError: database is locked
Normally I get this if I try to visit the page when a database import is still running or something like that but I'm not doing anything like that. I've even rebooted the computer to try to see if it would help but it doesn't. :( Any ideas?
~m
I noticed it too, requests are very long in postgresql and it triggers write-locks for update on tables at each run.
I and it's not a matter of upgrading a first time.
If I wait long enough, my page shows up and I can try a new request, but then it starts again updating.
but if I don't wait, I have the same message as yours.
It occurs since the merge of "list privacy" update with postgresql 9.1.9 from deb7 system
Hope this report helps
regards
Hmm, interesting, I'll look into it. This should never happen with postgresql, so that's surprising.
Oh, by the way, I've deployed the latest code on https://lists.stg.fedoraproject.org, if you want to take a look... ;-) The front page and the overview page are the main changes, the overview page being mainly the result of Mo's work.
I'm still working on making it faster (by adding a cache) so it may crash sometimes, but baring any bad luck it should display properly when you look at it.
Aurélien
2013/11/27 nkarageuzian@gmail.com nkarageuzian@gmail.com:
I noticed it too, requests are very long in postgresql and it triggers write-locks for update on tables at each run.
I and it's not a matter of upgrading a first time.
If I wait long enough, my page shows up and I can try a new request, but then it starts again updating.
but if I don't wait, I have the same message as yours.
It occurs since the merge of "list privacy" update with postgresql 9.1.9 from deb7 system
Hope this report helps
regards
hyperkitty-devel mailing list hyperkitty-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/hyperkitty-devel
Haha, I found where that came from, it's fixed in the latest Git: https://github.com/hyperkitty/kittystore/commit/5983de49753ffd6bd86e43673a5f...
Thanks for reporting :-)
Aurélien
2013/11/28 Aurelien Bompard abompard@fedoraproject.org:
Hmm, interesting, I'll look into it. This should never happen with postgresql, so that's surprising.
Oh, by the way, I've deployed the latest code on https://lists.stg.fedoraproject.org, if you want to take a look... ;-) The front page and the overview page are the main changes, the overview page being mainly the result of Mo's work.
I'm still working on making it faster (by adding a cache) so it may crash sometimes, but baring any bad luck it should display properly when you look at it.
Aurélien
2013/11/27 nkarageuzian@gmail.com nkarageuzian@gmail.com:
I noticed it too, requests are very long in postgresql and it triggers write-locks for update on tables at each run.
I and it's not a matter of upgrading a first time.
If I wait long enough, my page shows up and I can try a new request, but then it starts again updating.
but if I don't wait, I have the same message as yours.
It occurs since the merge of "list privacy" update with postgresql 9.1.9 from deb7 system
Hope this report helps
regards
hyperkitty-devel mailing list hyperkitty-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/hyperkitty-devel
Le 2013-12-02 08:11, Aurelien Bompard a écrit :
Haha, I found where that came from, it's fixed in the latest Git:
https://github.com/hyperkitty/kittystore/commit/5983de49753ffd6bd86e43673a5f...
Thanks for reporting :-)
How dear ? just THANKS TO YOU for commiting :) :) !!
Cheers
Aurélien
2013/11/28 Aurelien Bompard abompard@fedoraproject.org:
Hmm, interesting, I'll look into it. This should never happen with postgresql, so that's surprising.
Oh, by the way, I've deployed the latest code on https://lists.stg.fedoraproject.org, if you want to take a look... ;-) The front page and the overview page are the main changes, the overview page being mainly the result of Mo's work.
I'm still working on making it faster (by adding a cache) so it may crash sometimes, but baring any bad luck it should display properly when you look at it.
Aurélien
2013/11/27 nkarageuzian@gmail.com nkarageuzian@gmail.com:
I noticed it too, requests are very long in postgresql and it triggers write-locks for update on tables at each run.
I and it's not a matter of upgrading a first time.
If I wait long enough, my page shows up and I can try a new request, but then it starts again updating.
but if I don't wait, I have the same message as yours.
It occurs since the merge of "list privacy" update with postgresql 9.1.9 from deb7 system
Hope this report helps
regards
hyperkitty-devel mailing list hyperkitty-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/hyperkitty-devel
hyperkitty-devel mailing list hyperkitty-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/hyperkitty-devel
hyperkitty-devel@lists.fedorahosted.org
-
Aurelien Bompard -
Máirín Duffy -
nicolas＠karageuzian.com -
nkarageuzian＠gmail.com