Hi David, you were correct, the django migration did not include every layer that GeoServer expected. Thanks, Ben
On Mar 14, 2012, at 2:55 PM, David Winslow wrote: > Updatelayers talks to GeoServer, restoring a database dump does not. Your > GeoServer instance is apparently not returning valid XML for one of its > layers, hence the expat error. This probably indicates a configuration > problem in GeoServer. > > -- > David Winslow > OpenGeo - http://opengeo.org/ > > On Wed, Mar 14, 2012 at 9:52 AM, Ben <[email protected]> wrote: > Hi there, > > I am using Django schemata and Django south to migrate database changes > within my GeoNode. I have made some small changes to my django models, and > then I rebuilt the database, everything seems to be in order. > However, after this process of rebuilding the database, I run python > ./manage.py updatelayers and I am getting this error > But when I restore a database dump, then updatelayers is successful. > > Any Ideas on this would be much appreciated. > Cheers, Ben > > -- > Ben Wyss > OpenQuake Community Manager > GEM Foundatio n > c/o Eucentre, Via Ferrata 1 > 27100 Pavia, Italy > www.openquake.org >
