Andrea Aime <andrea.aime <at> geo-solutions.it> writes: > Hmmm... I don't see a direct connection between the two, bringing up > the layers page just requires to read metadata, actual access to data is not > required (it happens during the startup, but that's another story). > > It's probably more likely that the on disk configuration is ruined enough > to prevent the layers page to successfully come up.... one of the downsides > of using a file basic config mechanism, there are no transactions so files > can end up being stuck in an invalid state. > > Do you have anything else in the geoserver logs? Otherwise you can try > to post the contents of your workspaces directory (mind, it will contain > username/passwords in clear text if you are connecting to database > and the like) and we can try to see if there is something obviously > out of place. > > Cheers > Andrea >
Thanks for your reply Andrea. It didn't make sense to me that the two would be connected either. Your reply gave me the confidence I needed to look elsewhere. In the geoserver.log, well above where the lock file problem was listed, there is a message about not having write access to the directory where the server is trying to create *.fix files. I fixed the permission problem, restarted the server, and this is allowing access to the Layers page. Thanks for your prod. It's always good to get someone else's perspective. ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
