If the war is not deployed automagically ( 'autodeploy' normally is true in normal Tomcat instances [0]),
then this seems to be an azure thing... IF you cannot connect to 8080 then your tomcat is not running, or you have a reverse proxy in front of it, OR your tomcat is configured to run on another port. Maybe you can try to deploy other war's to test if Tomcat is running at all? Else: You can 'unzip' the war.zip and just put the contents of geoserver.war (which is IN the geoserver.version-war.zip, and is also just a zip) in a directory named 'geoserver'. Regards, Richard Duivenvoorde [0] https://tomcat.apache.org/tomcat-8.0-doc/deployer-howto.html On 2/16/21 12:24 PM, Jelmer Baas wrote: > Richard, > >> So what exactly was *not* working? Tomcat should indeed 'extract' the war >> automagically and then make geoserver admin page usable. > In other examples I saw it being extracted to a relative path; not in my > case. No extra files appeared. And no, there was no admin page. > /site/wwwrooot/webapps still only contains the geoserver.war file. > > My steps: > Create new Azure App Service (Linux, Java 8, Tomcat 8.5) - the rest default. > Go to mytest.azurewebsites.net, see welcome page. Go to > mytest.azurewebsites.net/geoserver get 404. > Download publish package, start FTP client, create "webapps" folder in > /site/wwwroot, upload geoserver.war to /site/wwwroot/webapps. Restart > service. Go to mytest.azurewebsites.net/geoserver, see loading indicator. > Wait a few minutes, get "Service Unavailable", with App Service plan at 100% > CPU. > > Can't reach mytest.azurewebsites.net anymore: takes a few minutes and then > responds with "Service Unavailable". 15 minutes in, and CPU usage is still at > 100% (memory at 65%) according to Azure. Do see a slight dip every now and > then. > > After ~20 minutes, the /geoserver URL returns > 502 - Web server received an invalid response while acting as a gateway or > proxy server > >> Can you connect to (I presume) port 8080 of Tomcat? > No. > >> Did the geoserver admin interface come up? > No... > > [...] > > Attached are the only (semi-useful) logs I could find. Pulling out my hairs, > afraid I'm doing something very dumb, here... > > Regards, > Jelmer > > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to this > list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
