09:31:49,832 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http–172.30.2.1-8080-1) Getting list of coverages for saved store /apps/data/250k: java.lang.RuntimeException: Could not list layers for this store, an error occurred retrieving them: This plugin accepts only File, URL and String pointing to a file
at org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123) [web-core-2.3.4.jar:2.3.4]
while ls on the filesystem says:
[root@anonymised.com 250k]# ls -ld /apps/data/
drwxr-xr-x 3 root root 4096 Aug 6 08:44 /apps/data/
[root@anonymised.com… 250k]# ls -ld /apps/data/250k/
drwxr-xr-x 7 jboss jboss 20480 Aug 6 08:52 /apps/data/250k/
[root@anonymised.com 250k]# ls -ld /apps/data/250k/0
drwxr-xr-x 2 jboss jboss 20480 Aug 6 09:21 /apps/data/250k/0
[root@anonymised.com 250k]#
So the logging seems backwards as the server should be running as jboss (and if not is running as root).
09:31:49,832 INFO [org.geotools.gce.imagepyramid]
(http--172.30.2.1-8080-1) Unable to build mosaic for the
directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid]
(http--172.30.2.1-8080-1) Unable to build mosaic for the
directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid]
(http--172.30.2.1-8080-1) Unable to build mosaic for the
directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid]
(http--172.30.2.1-8080-1) Unable to build mosaic for the
directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid]
(http--172.30.2.1-8080-1) Unable to build mosaic for the
directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http--172.30.2.1-8080-1) Getting
list of coverages for saved store /apps/data/250k:
java.lang.RuntimeException: Could not list layers for this store, an error
occurred retrieving them: This plugin accepts only File, URL and String
pointing to a file
at
org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123)
[web-core-2.3.4.jar:2.3.4]
Which root directory did you give to the pyramid store? It's normal that
it's checking the root directory for files, as gdal_retile puts tiles there
too,
but I'd be surprised if it's checking the parent of the folder you gave it.
That said, the true errors are reported for the directories that should
contain the data, it seems it's not able to generate a mosaic there, not
sure
why. You can try to put the logging level to "geotools developer logging"
and see if anything more interesting pops up
I’ve moved it within the geoserver data dir now (incase there was some sort of wierd chroot issue) so I set the root dir as file:coverages/250k. Nothing in the log leaps out at me but I’ve attached it.
09:31:49,832 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http–172.30.2.1-8080-1) Getting list of coverages for saved store /apps/data/250k: java.lang.RuntimeException: Could not list layers for this store, an error occurred retrieving them: This plugin accepts only File, URL and String pointing to a file
at org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123) [web-core-2.3.4.jar:2.3.4]
Which root directory did you give to the pyramid store? It’s normal that it’s checking the root directory for files, as gdal_retile puts tiles there too,
but I’d be surprised if it’s checking the parent of the folder you gave it.
That said, the true errors are reported for the directories that should contain the data, it seems it’s not able to generate a mosaic there, not sure
why. You can try to put the logging level to “geotools developer logging” and see if anything more interesting pops up
09:31:49,832 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http–172.30.2.1-8080-1) Getting list of coverages for saved store /apps/data/250k: java.lang.RuntimeException: Could not list layers for this store, an error occurred retrieving them: This plugin accepts only File, URL and String pointing to a file
at org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123) [web-core-2.3.4.jar:2.3.4]
Which root directory did you give to the pyramid store? It’s normal that it’s checking the root directory for files, as gdal_retile puts tiles there too,
but I’d be surprised if it’s checking the parent of the folder you gave it.
That said, the true errors are reported for the directories that should contain the data, it seems it’s not able to generate a mosaic there, not sure
why. You can try to put the logging level to “geotools developer logging” and see if anything more interesting pops up
09:31:49,832 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http–172.30.2.1-8080-1) Getting list of coverages for saved store /apps/data/250k: java.lang.RuntimeException: Could not list layers for this store, an error occurred retrieving them: This plugin accepts only File, URL and String pointing to a file
at org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123) [web-core-2.3.4.jar:2.3.4]
Which root directory did you give to the pyramid store? It’s normal that it’s checking the root directory for files, as gdal_retile puts tiles there too,
but I’d be surprised if it’s checking the parent of the folder you gave it.
That said, the true errors are reported for the directories that should contain the data, it seems it’s not able to generate a mosaic there, not sure
why. You can try to put the logging level to “geotools developer logging” and see if anything more interesting pops up
Just to add some more information - this seems to be a JBoss specific issue as I can run up 2.3.4 in jetty and all works fine. I can then switch back to JBoss and use the same data directory with no issues either so I suspect is it is a permissions issue. I’m going to punt this to the JBOss experts here and let them bang their heads on it for a while - if we do find an answer I’ll make sure to document it here and on the wiki.
09:31:49,832 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/0
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/4
09:31:49,833 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/1
09:31:49,834 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/3
09:31:49,841 INFO [org.geotools.gce.imagepyramid] (http–172.30.2.1-8080-1) Unable to build mosaic for the directory:/apps/data/250k/2
09:31:49,842 INFO [org.geoserver.web] (http–172.30.2.1-8080-1) Getting list of coverages for saved store /apps/data/250k: java.lang.RuntimeException: Could not list layers for this store, an error occurred retrieving them: This plugin accepts only File, URL and String pointing to a file
at org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:123) [web-core-2.3.4.jar:2.3.4]
Which root directory did you give to the pyramid store? It’s normal that it’s checking the root directory for files, as gdal_retile puts tiles there too,
but I’d be surprised if it’s checking the parent of the folder you gave it.
That said, the true errors are reported for the directories that should contain the data, it seems it’s not able to generate a mosaic there, not sure
why. You can try to put the logging level to “geotools developer logging” and see if anything more interesting pops up
On Thu, Aug 8, 2013 at 4:19 PM, Ian Turton <ijturton@anonymised.com> wrote:
Just to add some more information - this seems to be a JBoss specific
issue as I can run up 2.3.4 in jetty and all works fine. I can then switch
back to JBoss and use the same data directory with no issues either so I
suspect is it is a permissions issue. I'm going to punt this to the JBOss
experts here and let them bang their heads on it for a while - if we do
find an answer I'll make sure to document it here and on the wiki.
Sounds like a good plan, thanks for following up on this