<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
first it seemed to work fine, all layers are back and accessible,
but I cant edit the metadata of existing layers vie the geonode
webapp anymore.<br>
The frontend dies and gives an "Internal Server Error".<br>
<br>
The apache error messages look like:<br>
[Thu Jul 09 09:50:53.648422 2015] [:error] [pid 2080:tid
140415632357120] Internal Server Error:
/layers/geonode:sealevels_10_150m/metadata<br>
[Thu Jul 09 09:50:53.648484 2015] [:error] [pid 2080:tid
140415632357120] Traceback (most recent call last):<br>
[...]<br>
[Thu Jul 09 09:50:53.648652 2015] [:error] [pid 2080:tid
140415632357120] IOError: [Errno 13] Permission denied:
u'/var/www/geonode/uploaded/thumbs/layer-d680d189-b46f-468e-8267-e8e5b497988c-thumb.png'<br>
[Thu Jul 09 09:50:53.664269 2015] [:error] [pid 2080:tid
140415632357120] [remote 134.95.150.136:14361] mod_wsgi (pid=2080):
Exception occurred processing WSGI script
'/var/www/geonode/wsgi/geonode.wsgi'.<br>
[...]<br>
[Thu Jul 09 09:50:53.665753 2015] [:error] [pid 2080:tid
140415632357120] [remote 134.95.150.136:14361] File
"/usr/lib/python2.7/dist-packages/django/template/context.py", line
56, in __getitem__<br>
[Thu Jul 09 09:50:53.665849 2015] [:error] [pid 2080:tid
140415632357120] [remote 134.95.150.136:14361] raise
KeyError(key)<br>
[Thu Jul 09 09:50:53.665872 2015] [:error] [pid 2080:tid
140415632357120] [remote 134.95.150.136:14361] KeyError: 'request'<br>
<br>
<br>
It is the same account name for the superuser.<br>
<br>
Additionally all the Categories and Keywords are gone... (that's why
I wanted to edit the metadata in the first place...)<br>
<br>
Any hint on how I can fix this?<br>
<br>
Thanks and regards,<br>
Christian<br>
<br>
<br>
<div class="moz-cite-prefix">Am 07.07.2015 um 15:49 schrieb Simone
Dalmasso:<br>
</div>
<blockquote
cite="mid:CAAHAC+dcvczHmPAjkfrkgLFrmF6S_ozMpJqiOs5Yg6cqSvj2Ow@mail.gmail.com"
type="cite">
<div dir="ltr">Christian, in your case the backup preserver the
old schema. Although since the difference in the new schema is a
single column being added, you can use the "geonode
syncdb --no-initial-data" before loading back the backup. The
syncdb will create the new schema and the backup should load
leaving the new column blank. The --no-initial-data will make
sure that syncdb only creates the schema without loading any
fixture.
<div><br>
</div>
<div>Hope this helps.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-07-07 14:48 GMT+02:00 Christian
Willmes <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:christian.willmes@googlemail.com"
target="_blank">christian.willmes@googlemail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
following up on this thread: <a moz-do-not-send="true"
href="https://github.com/GeoNode/geonode/issues/2046"
rel="noreferrer" target="_blank">https://github.com/GeoNode/geonode/issues/2046</a><br>
<br>
I did the sugested steps, but the upload problem persits. No
wonder, because in which step should the
'layers_uploadsession' session be created?<br>
<br>
The erreor inthe apache log looks like:<br>
[Tue Jul 07 07:39:11.377817 2015] [:error] [pid 22673:tid
139958275774208] column "context" of relation
"layers_uploadsession" does not exist<br>
[Tue Jul 07 07:39:11.377877 2015] [:error] [pid 22673:tid
139958275774208] LINE 1: ...e", "user_id", "processed",
"error", "traceback", "context")...<br>
[Tue Jul 07 07:39:11.377884 2015] [:error] [pid 22673:tid
139958275774208] ^<br>
[Tue Jul 07 07:39:11.377898 2015] [:error] [pid 22673:tid
139958275774208] Traceback (most recent call last):<br>
[Tue Jul 07 07:39:11.377904 2015] [:error] [pid 22673:tid
139958275774208] File
"/usr/local/lib/python2.7/dist-packages/geonode/layers/views.py"<br>
[....]<br>
<br>
<br>
I did exactly the following (from <a moz-do-not-send="true"
href="http://docs.geonode.org/en/master/tutorials/admin/backup/index.html"
rel="noreferrer" target="_blank">http://docs.geonode.org/en/master/tutorials/admin/backup/index.html</a>):<br>
<br>
sudo -u postgres -i pg_dump -c -Fc geonode >
geonodedb.backup<br>
<br>
<br>
sudo service apache2 stop<br>
sudo /etc/init.d/tomcat7 stop<br>
<br>
sudo service postgresql start<br>
sudo -u postgres -i "psql -c 'drop database geonode;'"<br>
sudo -u postgres -i "psql -c 'create database geonode;'"<br>
sudo -u postgres -s "pg_restore -Fc -d geonode
/path/to/geonodedb.backup"<br>
<br>
sudo service apache2 start<br>
sudo /etc/init.d/tomcat7 start<br>
<br>
----<br>
<br>
How can I solve this problem?<br>
<br>
Best regards,<br>
Christian<br>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Simone </div>
</div>
</blockquote>
<br>
</body>
</html>