On February 11, 2021 11:01:27 PM UTC, Jim Weill <moon...@icsi.berkeley.edu> wrote: >Yes, the file is there and readable. The NTFS permissions have only >the >built-in SYSTEM, CREATOR OWNER, and domain administrators group as >having >any kind of access to the folder. This was working before I started >upgrading. The last modified date is 2017 on that file.
Check the user the Tomcat service is running as. This changed from Local System (essentially an admin account) to the less privileged Local Service. Mark > >jim > >On Thu, Feb 11, 2021 at 2:17 PM Rémy Maucherat <r...@apache.org> wrote: > >> On Thu, Feb 11, 2021 at 10:33 PM Jim Weill ><moon...@icsi.berkeley.edu> >> wrote: >> >> > Sorry, I should have posted it yesterday. This was the only thing >I >> could >> > find that had anything like an error in the stderr log: >> > >> > 10-Feb-2021 17:34:09.930 SEVERE [main] >> > org.apache.catalina.core.StandardService.initInternal Failed to >> initialize >> > connector [Connector[HTTP/1.1-8443]] >> > org.apache.catalina.LifecycleException: Protocol handler >initialization >> > failed >> > at >> > >org.apache.catalina.connector.Connector.initInternal(Connector.java:1077) >> > at >org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) >> > at >> > >> > >> >org.apache.catalina.core.StandardService.initInternal(StandardService.java:552) >> > at >org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) >> > at >> > >> > >> >org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:846) >> > at >org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) >> > at org.apache.catalina.startup.Catalina.load(Catalina.java:639) >> > at org.apache.catalina.startup.Catalina.load(Catalina.java:662) >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) >> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) >> > at java.lang.reflect.Method.invoke(Unknown Source) >> > at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302) >> > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:472) >> > Caused by: java.lang.IllegalArgumentException: Illegal character in >> opaque >> > part at index 2: D:\_ssh\_.ICSI.Berkeley.EDU.key >> > at >> > org.apache.tomcat.util.net >> > >.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:100) >> > at >> > org.apache.tomcat.util.net >> > .AbstractJsseEndpoint.initialiseSsl(AbstractJsseEndpoint.java:72) >> > at >org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:247) >> > at >> > org.apache.tomcat.util.net >> > .AbstractEndpoint.init(AbstractEndpoint.java:1143) >> > at >> > org.apache.tomcat.util.net >> > .AbstractJsseEndpoint.init(AbstractJsseEndpoint.java:222) >> > at >org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:599) >> > at >> > >> > >> >org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:80) >> > at >> > >org.apache.catalina.connector.Connector.initInternal(Connector.java:1075) >> > ... 13 more >> > Caused by: java.lang.IllegalArgumentException: Illegal character in >> opaque >> > part at index 2: D:\_ssh\_.ICSI.Berkeley.EDU.key >> > at java.net.URI.create(Unknown Source) >> > at java.net.URI.resolve(Unknown Source) >> > at >> > >> > >> >org.apache.tomcat.util.file.ConfigFileLoader.getURI(ConfigFileLoader.java:105) >> > at >> > >> > >> >org.apache.tomcat.util.file.ConfigFileLoader.getInputStream(ConfigFileLoader.java:88) >> > at org.apache.tomcat.util.net.jsse.PEMFile.<init>(PEMFile.java:98) >> > at org.apache.tomcat.util.net.jsse.PEMFile.<init>(PEMFile.java:90) >> > at >> > org.apache.tomcat.util.net >> > .SSLUtilBase.getKeyManagers(SSLUtilBase.java:313) >> > at >> > org.apache.tomcat.util.net >> > .SSLUtilBase.createSSLContext(SSLUtilBase.java:245) >> > at >> > org.apache.tomcat.util.net >> > >.AbstractJsseEndpoint.createSSLContext(AbstractJsseEndpoint.java:98) >> > ... 20 more >> > Caused by: java.net.URISyntaxException: Illegal character in opaque >part >> at >> > index 2: D:\_ssh\_.ICSI.Berkeley.EDU.key >> > at java.net.URI$Parser.fail(Unknown Source) >> > at java.net.URI$Parser.checkChars(Unknown Source) >> > at java.net.URI$Parser.parse(Unknown Source) >> > at java.net.URI.<init>(Unknown Source) >> > ... 29 more >> > 10-Feb-2021 17:34:09.930 INFO [main] >> > org.apache.coyote.AbstractProtocol.init Initializing >ProtocolHandler >> > ["ajp-nio-127.0.0.1-8009"] >> > 10-Feb-2021 17:34:09.930 INFO [main] >> > org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using >a >> > shared >> > selector for servlet write/read >> > 10-Feb-2021 17:34:09.930 INFO [main] >> > org.apache.catalina.startup.Catalina.load Initialization processed >in >> 1522 >> > ms >> > >> >> This happens when D:\_ssh\_.ICSI.Berkeley.EDU.key is not a file (or >not >> there) and it then tries as a URL. Is your keystore still there after >your >> update ? >> There were recent changes, but there's no difference that I can see >with >> that location as input. >> >> Rémy >> >> >> > >> > On Thu, Feb 11, 2021 at 12:17 AM Mark Thomas <ma...@apache.org> >wrote: >> > >> > > On 11/02/2021 02:06, Jim Weill wrote: >> > > > I had 8.5.41 working and decided to do the upgrade to 8.5.63 >today on >> > > > Windows Server 2012r2. I've had success with stopping the >service, >> > > > renaming the tomcat directory, putting the unzipped files of >the new >> > > > version in its place, and dropping in the server.xml, and >web.xml >> files >> > > to >> > > > replace the default files. As well, I copy over the webapps >folder >> for >> > > the >> > > > site, then restart the service. This process has worked many >times >> > > before. >> > > > >> > > > When I did this today, the service would not start for some >reason. >> > So I >> > > > renamed the folders back to their original names, and then ran >the >> > > > uninstall from the add/remove programs. I ran the install >executable >> > on >> > > > 8.5.63, dropped in the webapps folder, and the server.xml and >web.xml >> > > files >> > > > and the service started, but the site never loads, even on >localhost. >> > > >> > > What do you see in the logs? Ideally you want to clear the logs, >start >> > > Tomcat, make a single request, stop Tomcat and then look at the >logs. >> > > >> > > If you see an error, the safest approach is to fix that error and >then >> > > repeat the process as subsequent errors are often side-effects of >the >> > > first error. >> > > >> > > Mark >> > > >> > > >--------------------------------------------------------------------- >> > > 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
