Re: Strange crash-on-takeoff, Tomcat 7.0.104
James, On 11/18/2020 5:06 PM, James H. H. Lampert wrote: Ladies and Gentlemen: The same customer installation that required 104 (but with the 103 catalina.sh, to avoid Bug 64501) back in June is now demanding an update to 106 because of the CVE-2020-13935 vulnerability. Two questions: 1. Is the problem from June fixed in 106? 2. Does 106 take care of CVE-2020-13935? -- JHHL http://tomcat.apache.org/tomcat-7.0-doc/changelog.html http://tomcat.apache.org/security-7.html . . . just my two cents /mde/ OpenPGP_0x41466EC60D793C2D.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Re: Strange crash-on-takeoff, Tomcat 7.0.104
Ladies and Gentlemen: The same customer installation that required 104 (but with the 103 catalina.sh, to avoid Bug 64501) back in June is now demanding an update to 106 because of the CVE-2020-13935 vulnerability. Two questions: 1. Is the problem from June fixed in 106? 2. Does 106 take care of CVE-2020-13935? -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On Mon, Jun 22, 2020, 11:56 James H. H. Lampert wrote: > On 6/20/20 8:41 AM, Mark Thomas wrote: > > > 7.0.105 hasn't been released yet. You can use catalina.sh from 7.0 > > 103 or the latest version from source control. > > Where would I find "the latest version from source control"? > https://gitbox.apache.org/repos/asf?p=tomcat.git Found at https://en.m.wikipedia.org/wiki/Apache_Tomcat
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 6/20/20 8:41 AM, Mark Thomas wrote: 7.0.105 hasn't been released yet. You can use catalina.sh from 7.0 103 or the latest version from source control. Where would I find "the latest version from source control"? -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On June 19, 2020 10:49:54 PM UTC, "James H. H. Lampert" wrote: >On 6/19/20 3:20 PM, Mark Thomas wrote: >> https://bz.apache.org/bugzilla/show_bug.cgi?id=64501 > >Hmm. I'm now looking through the entire catalina.sh script in both >versions. (First, I looked through the startup.sh script; that appears >to be identical in both versions.) > >First thing I noticed was that a few new environment variables were >listed in the documentation section at the top. > >Second thing I noticed was the section beginning >> # Ensure that neither CATALINA_HOME nor CATALINA_BASE contains a >colon > >Third thing I noticed was in the secetion marked "Bugzilla 37848 . . ." >old: >> if [ "`tty`" != "not a tty" ]; then > >new: >> if [ -t 0 ]; then > >Fourth thing I noticed was the section marked >> # Check for the deprecated LOGGING_CONFIG > >This looks an awful lot like what's in the Bugzilla page. And I see >that >it is "Fixed in . . . 7.0.105 onwards." > >But the download page for 7 is still at 7.0.104. 7.0.105 hasn't been released yet. You can use catalina.sh from 7.0 103 or the latest version from source control. Either should be fine. Mark > >-- >JHHL > >- >To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 6/19/20 18:49, James H. H. Lampert wrote: > On 6/19/20 3:20 PM, Mark Thomas wrote: >> https://bz.apache.org/bugzilla/show_bug.cgi?id=64501 > > Hmm. I'm now looking through the entire catalina.sh script in both > versions. (First, I looked through the startup.sh script; that > appears to be identical in both versions.) > > First thing I noticed was that a few new environment variables > were listed in the documentation section at the top. > > Second thing I noticed was the section beginning >> # Ensure that neither CATALINA_HOME nor CATALINA_BASE contains a >> colon > > Third thing I noticed was in the secetion marked "Bugzilla 37848 . > . ." old: >> if [ "`tty`" != "not a tty" ]; then > > new: >> if [ -t 0 ]; then > > Fourth thing I noticed was the section marked >> # Check for the deprecated LOGGING_CONFIG > > This looks an awful lot like what's in the Bugzilla page. And I see > that it is "Fixed in . . . 7.0.105 onwards." > > But the download page for 7 is still at 7.0.104. Right. The release process hasn't yet started for .105 but you could probably look at the patches and adapt them locally. - -chris -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7uKmgACgkQHPApP6U8 pFj/jg//dwwJdqMeMRpLdMbpwfehLtHMzrO5QIocQJaGeEBWukqZZSq7JSOdFnvL op5rZcm0fqFW5ICQVTM/df3QC1VcwKCa5xuWkjtra50s16Lv8qxWifQ86CFab8k9 pjEyBI0ER1nw4ofIKqGFssG0rEXBDJqIX4jUnoeCHEp90LkdNUQcuA4lL0HgEYDH 7tHSQLZFa5//6ydxtZ/8dMf9wgJFpY4Qr5WDJRRpR3utpgJ2yNEFEdz/i35jvu3Y j1oj9x/MJIj12jQjO7q+NuS0McCVPSeppOJT9tH5D2jBFwlIZjhh+Q9UIlNUiExY 0F6zBKR2WqOY14UEetdgysRVQ1vgx/elw4iqK95qd4LQ1jcSDRR84GXwpdhdZQIk +3pnIXIVnm0gXqhrqyVeM5l/rGc3ebeYkFvkZKGKGEq+vkXJUaQ/JzlCwxyYjVQ4 7viL0iCsjWIuvROes4cLD9FBqiZe9lbfIP8fr+bNqrrHe+rxj8DjXYQiGvMRn8Js YXcien6M5sokhEBMBSqZVXmVGiv4fPfgVIDsPg+iIrpm/IAJCblXy47x6Y8w4Lk8 yKAF/qg8cVusuAG5m6UEhlgWmRiS4ZpaLy43OP/oHQXeimr7sbau/95zDvlhnDrm iGCpLKxFiuj+1fHSE0RH+nEETXqrl/qtHoSuxRe4thvyc5Chd14= =XpUI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 6/19/20 3:20 PM, Mark Thomas wrote: https://bz.apache.org/bugzilla/show_bug.cgi?id=64501 Hmm. I'm now looking through the entire catalina.sh script in both versions. (First, I looked through the startup.sh script; that appears to be identical in both versions.) First thing I noticed was that a few new environment variables were listed in the documentation section at the top. Second thing I noticed was the section beginning # Ensure that neither CATALINA_HOME nor CATALINA_BASE contains a colon Third thing I noticed was in the secetion marked "Bugzilla 37848 . . ." old: if [ "`tty`" != "not a tty" ]; then new: if [ -t 0 ]; then Fourth thing I noticed was the section marked # Check for the deprecated LOGGING_CONFIG This looks an awful lot like what's in the Bugzilla page. And I see that it is "Fixed in . . . 7.0.105 onwards." But the download page for 7 is still at 7.0.104. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 19/06/2020 21:14, James H. H. Lampert wrote: > Ladies and Gentlemen: > > In preparation for updating a customer box, I installed Tomcat 7.0.104 > on our own AS/400 (64-bit Java 6 JVM). > > 7.0.93 works just fine on our box, but 7.0.104 seems to crash on > takeoff, producing no log files, just a spool file consisting of the > single line > > *-D > > Any idea what could be going wrong? https://bz.apache.org/bugzilla/show_bug.cgi?id=64501 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 6/19/20 2:27 PM, calder wrote: a) it's worth asking the obvious ... are the file permissions correct for the new TCp installation, i.e , such as read/write in "logs" subdir and execute permissions for the TC scripts? Unless something weird is going on with the apache-tomcat-7.0.104.zip file, it appears that all the authorities match between old and new versions. b) are you using the same Java instance for both TC's ? Normally, for native-command-line launches, or launches from native CL programs (like shell scripts, only compiled), we have a CL program ("STRTOMCAT") that does a fair amount of advance setup, selects the first available JVM from a preference list, and then QShell's out startup.sh as a batch job. This CL program expects Tomcat to be in a particular place in the file system, in a directory called "tomcat." So to switch to a new Tomcat server, I shut the current one down, rename the current "tomcat" directory to something else (e.g., "tomcat93"), and rename the "apache-tomcat-7.0.104" directory to "tomcat" before starting it with STRTOMCAT. So it would *have* to be the same JVM, because that's explicitly selected by the STRTOMCAT CL program. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On Fri, Jun 19, 2020, 15:33 James H. H. Lampert wrote: > On 6/19/20 1:26 PM, calder wrote: > > a) are both Tomcat instances installed on that same server? > > Yes > > > b) if yes, is the 7.0.93 instance running when you launch the 7.0.104 > > instance? > > No. > > We've done this procedure before: installing a new version, doing the > setup in the new version, then shutting down the old version, renaming > both the old and the new versions (so things are where they're expected > to be), and starting up. Thanks. a) it's worth asking the obvious ... are the file permissions correct for the new TCp installation, i.e , such as read/write in "logs" subdir and execute permissions for the TC scripts? b) are you using the same Java instance for both TC's ?
Re: Strange crash-on-takeoff, Tomcat 7.0.104 (Trying again)
On 6/19/20 1:24 PM, Christopher Schultz wrote: My guess is that the system-property-setting part of catalina.sh (or some other script) is getting fouled-up. What script(s) are you running to start Tomcat? Remember, we're talking about IBM Midrange systems, not *nix. So bash is entirely unknown to the OS; instead, startup.sh calls catalina.sh, with everything running under "QShell," a Linux-like front-end that was provided with Java. If it's just catalina.sh, try running it like this: $ bash -x $CATALINA_HOME/bin/catalina.sh This will echo every command run to the console before running it, including all expanded arguments and all that stuff. Most likely, the last command run will (a) be the one which is interesting and (b) will be clear from the command what went wrong. Unfortunately, QShell doesn't appear to have anyplace to put "-x" as a parameter. But it does appear to support "set -x" at the QShell command line. If I do that, then I get: |$ | > set -x |+ set -x |$ | > catalina.sh |+ catalina.sh |*-D |$ PS You really are a magnet for weird problems with Tomcat, aren't you? Well, it comes with the territory of running Tomcat on AS/400s, I suppose. I'm thinking I should bring in the Java list over at Midrange.com as well. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 6/19/20 1:24 PM, Christopher Schultz wrote: My guess is that the system-property-setting part of catalina.sh (or some other script) is getting fouled-up. What script(s) are you running to start Tomcat? Remember, we're talking about IBM Midrange systems, not *nix. So bash is entirely unknown to the OS; instead, startup.sh calls catalina.sh, with everything running under "QShell," a Linux-like front-end that was provided with Java. If it's just catalina.sh, try running it like this: $ bash -x $CATALINA_HOME/bin/catalina.sh This will echo every command run to the console before running it, including all expanded arguments and all that stuff. Most likely, the last command run will (a) be the one which is interesting and (b) will be clear from the command what went wrong. Unfortunately, QShell doesn't appear to have anyplace to put "-x" as a parameter. But it does appear to support "set -x" at the QShell command line. If I do that, then I get: $ > set -x + set -x $ > catalina.sh + catalina.sh *-D $ PS You really are a magnet for weird problems with Tomcat, aren't you? Well, it comes with the territory of running Tomcat on AS/400s, I suppose. I'm thinking I should bring in the Java list over at Midrange.com as well. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On 6/19/20 1:26 PM, calder wrote: a) are both Tomcat instances installed on that same server? Yes b) if yes, is the 7.0.93 instance running when you launch the 7.0.104 instance? No. We've done this procedure before: installing a new version, doing the setup in the new version, then shutting down the old version, renaming both the old and the new versions (so things are where they're expected to be), and starting up. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Strange crash-on-takeoff, Tomcat 7.0.104
On Fri, Jun 19, 2020, 15:15 James H. H. Lampert wrote: > Ladies and Gentlemen: > > In preparation for updating a customer box, I installed Tomcat 7.0.104 > on our own AS/400 (64-bit Java 6 JVM). > > 7.0.93 works just fine on our box, but 7.0.104 seems to crash on > takeoff, producing no log files, just a spool file consisting of the > single line > a) are both Tomcat instances installed on that same server? . b) if yes, is the 7.0.93 instance running when you launch the 7.0.104 instance?
Re: Strange crash-on-takeoff, Tomcat 7.0.104
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 6/19/20 16:14, James H. H. Lampert wrote: > Ladies and Gentlemen: > > In preparation for updating a customer box, I installed Tomcat > 7.0.104 on our own AS/400 (64-bit Java 6 JVM). > > 7.0.93 works just fine on our box, but 7.0.104 seems to crash on > takeoff, producing no log files, just a spool file consisting of > the single line > > *-D > > Any idea what could be going wrong? What's the name of the file My guess is that the system-property-setting part of catalina.sh (or some other script) is getting fouled-up. What script(s) are you running to start Tomcat? If it's just catalina.sh, try running it like this: $ bash -x $CATALINA_HOME/bin/catalina.sh This will echo every command run to the console before running it, including all expanded arguments and all that stuff. Most likely, the last command run will (a) be the one which is interesting and (b) will be clear from the command what went wrong. - -chris PS You really are a magnet for weird problems with Tomcat, aren't you? -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl7tHuIACgkQHPApP6U8 pFjFNxAAqd4rCgDlMiNNJrECnCpMrX8+sormBO6UBEyE+eAGSpU1AYzyMR2YYzBe gE+dZAjWynoy4lMMBW0t6fiRflCYzJRXNRj7pqn6oA/+vMFLn19raIDSdvGgwkuw L9lDf9uXc7rXPH4ULL2ttkjXfqYjCvWi+06S5CJJemfhXplVaa+VDLVbLlsERDSH KBy/H63q4cmYdj1t0elCQWpLFNa/XoUC84o/TpYAQecgz9lNzi3obN3xXFOXtYBM jZb7SNlcZdCfKMRV/gvkMpdEism4O87kdHCyFyWT6syBiMOhaV9aR88HVTIpUMCX IyC5E7wggyu2SX9Ckit0sJOcET5hjE7EUvwl/EDptCR85sNHXq+wgGaNT/WP3F8J diMe0mh1Al5T5EIK+Nk4Ysac2An7tEVIxob1eWSY59n9FeBu4Jocx2upcZt+VF1T mn0+xMrhFkYiUfdi9IELBcIIAvhlVNyIsZTBmfBXrhtmPXxajGXlNW14KgBinpyi ZmD3G46TWv8H86E/3EsqURGaf2GU2oOuBCjx6VBQca727oE85yBxSE90YgJL/mUe qGEL2BlE9rczv59YVajNl4cBg32Z5VdcRvm6prb/PrViqtnUgKFFUqi2Ki6w41ag YWvvzLtZND1rtqPOMGGdXpJbuoPDJ0xjLVSjs1bnKQj983b/j2M= =x4cd -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org