i've just migrated to 1.6 because of problems i was having with 1.5.2. i
don't seem to be able to login to the admin console. it recognises the
username and password but when i go to the config link it just takes me to
the login page again.
i've checked on the docs and created the user.properties and
service.properties file in the security folder in the data directory. it
still seems to be reading the admin user details from the service.xml file.
i've also tried from both mozilla and ie7 in case it was some kind of
session creation problem.
can anyone suggest anything else i can try to remedy this? is there a page
specifically about migrating 1.5.x to 1.6?
I think I’ve had this problem and its been down to the old data directory still being around. Where does the GEOSERVER_DATA_DIR (?) env variable point to?
i’ve just migrated to 1.6 because of problems i was having with 1.5.2. i
don’t seem to be able to login to the admin console. it recognises the
username and password but when i go to the config link it just takes me to
the login page again.
i’ve checked on the docs and created the user.properties and
service.properties file in the security folder in the data directory. it
still seems to be reading the admin user details from the service.xml file.
i’ve also tried from both mozilla and ie7 in case it was some kind of
session creation problem.
can anyone suggest anything else i can try to remedy this? is there a page
specifically about migrating 1.5.x to 1.6?
I think I've had this problem and its been down to the old data directory
still being around. Where does the GEOSERVER_DATA_DIR (?) env variable
point to?
Hi Rob. I am trying to use my 1.5.2 data directory but I've tried without
the env var, with it pointing to the default location and with it pointing
somewhere else and I've made sure there's a security folder with the
properties files in wherever it points. I've had to go back to 1.5.2 for now
as I was also having problems with non-spatial tables. Cheers. Dan
--
View this message in context: http://www.nabble.com/admin-console-login-failure-in-1.6-tp15576452p15615503.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
I think I've had this problem and its been down to the old data directory
still being around. Where does the GEOSERVER_DATA_DIR (?) env variable
point to?
Hi Rob. I am trying to use my 1.5.2 data directory but I've tried without
the env var, with it pointing to the default location and with it pointing
somewhere else and I've made sure there's a security folder with the
properties files in wherever it points. I've had to go back to 1.5.2 for
now as I was also having problems with non-spatial tables. Cheers. Dan
Problems with non spatial tables? Can you elaborate? If we don't know
about the problem we cannot fix it...
Hi Andrea.
I have a number of non-spatial views derived from the spatial tables which I
use as lookups for building ogc:filters and query via geoserver. So for
example I have a table of species sightings and a non-spatial view of
distinct recorded species which I can use to set a filter which pulls back a
map showing only sightings of that species.
In 1.5.2 I could set up non-spatial tables by sticking -1 in EPSG and then I
could happily query them using non-spatial ogc:filters. When I moved to 1.6
all the featureTypes with EPSG -1 were invalid which was OK because I could
just set them to 4326 even though it didn't actually make any sense.
What I couldn't do though was query them using the ogc:filters. I kept
getting out of memory errors. Querying other much larger tables worked fine
with both property and/or spatial filters but as soon as I tried any kind of
property filter on a non-spatial table I got an out of memory error.
Problems with non spatial tables? Can you elaborate? If we don't know
about the problem we cannot fix it...
Hi Andrea.
I have a number of non-spatial views derived from the spatial tables which I
use as lookups for building ogc:filters and query via geoserver. So for
example I have a table of species sightings and a non-spatial view of
distinct recorded species which I can use to set a filter which pulls back a
map showing only sightings of that species.
In 1.5.2 I could set up non-spatial tables by sticking -1 in EPSG and then I
could happily query them using non-spatial ogc:filters. When I moved to 1.6
all the featureTypes with EPSG -1 were invalid which was OK because I could
just set them to 4326 even though it didn't actually make any sense.
We improved reprojection support but we had to become more strict in the srs we accept.
The WFS standard requires us to publish a LatLon bounding box for the data too, and that does not make any sense either for non geom data...
let's just say handling data without geometries in WFS is a little stretched
What I couldn't do though was query them using the ogc:filters. I kept
getting out of memory errors. Querying other much larger tables worked fine
with both property and/or spatial filters but as soon as I tried any kind of
property filter on a non-spatial table I got an out of memory error.
I just tried with various filters on a non spatial table I have here, got no errors.
Can you open a jira issue (jira.codehaus.org) and attach there a dump
of your table and the request that makes it throw the OOM?
