Ladies and Gentlemen:
I am once again attempting to get our development AWS box switched over
to Let's Encrypt.
This time, I've managed to get the httpd server working with the Let's
Encrypt cert. And this time, I've even managed to get Tomcat 8.5 to use
it without crashing on takeoff. It's not yet on speaking terms with
Chrome, but Firefox can access it just fine. And that's when I noticed
the weirdness:
The mere act of spinning up a spot instance from last night's backup
caused Tomcat to update itself to the latest version (from 8.5.40 to
8.5.57).
This would not be a bad thing in and of itself, except for two side effects:
First, the default ROOT context was overlaid onto our ROOT context!
Second, Manager was disabled!
I spun up a new spot instance, the same way I did the one I'm using for
my experiments, and sure enough, the ROOT context was changed: eleven
files were added, and an undetermined number were changed.
The other contexts appear to all be there, but the "examples" context,
which we remove from all our working Tomcat installations, was added
back in.
But our server.xml appears to be completely intact, and so does our
tomcat-users.xml.
Yet, as I said, Manager is disabled.
Can anybody shed any light on what happened?
--
James H. H. Lampert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
