Closed Toucan-Sam closed 3 years ago
Probably same root cause as https://github.com/kartoza/docker-geoserver/issues/232 You'll have to re-pull again 2.18.2 or 2.19.0.
Thanks for the response @tlvu, unfortunately, same issue. Good idea though. The image was older than I thought it was.
01-Apr-2021 00:30:59.775 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
01-Apr-2021 00:30:59.800 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
01-Apr-2021 00:30:59.801 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/geoserver] startup failed due to previous errors
01-Apr-2021 00:30:59.856 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat/webapps/geoserver] has finished in [13,671] ms
01-Apr-2021 00:30:59.863 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
01-Apr-2021 00:30:59.936 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [15135] milliseconds
EDIT: For the sake of clarity, I'm using the latest
tag.
@tlvu But you were right in the end.
The latest
tag is not correctly updated and is using an older and broken image.
@kartoza Can this please be fixed? :)
EDIT: For the sake of clarity, I'm using the
latest
tag.
@Toucan-Sam
Maybe try using the 2.19.0
tag?
latest
tag probably track the master
branch and currently I still see Tomcat 10 on the master
branch https://github.com/kartoza/docker-geoserver/blob/6b08be47a6f170fe19f3d8210d42dd8da14d772c/Dockerfile#L2
The root cause of my issue was Tomcat 10. Downgrade back to Tomcat 9 fixed it, see comment https://github.com/kartoza/docker-geoserver/issues/232#issuecomment-810689167
@Toucan-Sam it should be sorted now. In production environments you should not be using latest because it can change anytime if a new version of geoserver becomes available.
@NyakudyaA Thank you very much. Understood.
We're using the latest tag to ensure that the development environment is always running the latest versions. This allows us to test for things (eg, a migration from 2.18 to 2.19) and more or less know exactly when things are broken and before they reach production environments. Dev teams can fix what they need ASAP and when they're ready, Ops can bump the production version.
Keeping the latest tag in line with latest stable release of geoserver is ideal to keeping our workflow... flowing. :)
Not to say that it's all your responsibility. It certainly is not. For extra sensitive stuff we do builds in house of course. For everything else, we hugely appreciate your work.
EDIT: Alternatively, it might be handy to publish 2.19.x tags to let folks stay within a certain major/minor version.
Hey guys, This appears to be related to #218 and #222 but neither of those provide an actual solution as far as I can tell.
When I start the geoserver container, server:8080/geoserver throws a 404 error.
I have not deployed with SSL as I intend to use a reverse proxy to do termination.
Any advice on where I can find more information/logs about why:
31-Mar-2021 22:42:41.114 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/geoserver] startup failed due to previous errors
Thanks guys.