Re: Unable to access Manager App, Host Manager and Server Status urls
Thank you so much ! Issue resolved. So why it was not asking for username and password before ?? Also the standard documentation doesn't talk about removing that tag from context.xml. One last thing though, I can access "Server Status" and "Manager app" but not "Host Manager" ? I do have admin-gui role defined so not sure why I cannot access it. Cheers On Monday, 15 August 2016, 3:50, Mark Olsson wrote: Tried that but no charm as of yet. If I add comments like the one I have bold, I am unable to access tomcat manager.So I have to uncomment it. After uncomment. It says access denied... Take just this out of context.xml and restart Tomcat and your browser. ** Actually I don't know if restarting is necessary on either, but it can't hurt.
Re: Unable to access Manager App, Host Manager and Server Status urls
Tried that but no charm as of yet. [root@docker1 META-INF]# cat /opt/tomcat/webapps/manager/META-INF/context.xml If I add comments like the one I have bold, I am unable to access tomcat manager.So I have to uncomment it. After uncomment. It says access denied... On Sunday, 14 August 2016, 23:14, Mark Thomas wrote: On 14 August 2016 12:37:37 BST, Andrew M wrote: >I have clear the history, tried different browsers, restarted tomcat >several times. I'm not sure what you want me to comment/uncomment. My >context.xml file is below: That is the global context.xml. Check the web application specific context.xml at $CATALINA_BASE/webapps/manager/META-INF/context.xml Mark >root@docker1 conf]# cat context.xml encoding="UTF-8"?> > >WEB-INF/web.xml >${catalina.base}/conf/web.xml > [root@docker1 conf]# >Spent lot of investigating but I'm still not sure what is the >problem. > >On Sunday, 14 August 2016, 19:55, Mark Olsson >wrote: > > >On Sun, Aug 14, 2016 at 1:43 AM, Andrew M > >wrote: > >> I tried disabling SE Linux but no charm :( >> What is interesting is I have enabled finest level of debugging but I >> cannot see anything in log files as ALL or finest level of logging. >> > >Make sure if you have an address filter in >webapps/manager/META-INF/context.xml that it's correct, and try >removing or >commenting it out temporarily even if it does look correct just in >case. > >Since your first message was 18 hours ago, I'm assuming at some point >you >have closed and reopened your browser? On my systems, if I enter the >wrong >user or password to get into the management console I get the 403 and I >can't get back to the login prompt without completely closing and >restarting the browser. I don't know if that's intentional or just a >side >effect of Firefox and the various privacy extensions I use, never >bothered >to look for the cause. So, depending on your browser, try >closing/restarting, clearing caches and active logins, even try from a >different browser. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Unable to access Manager App, Host Manager and Server Status urls
I have clear the history, tried different browsers, restarted tomcat several times. I'm not sure what you want me to comment/uncomment. My context.xml file is below: root@docker1 conf]# cat context.xml WEB-INF/web.xml ${catalina.base}/conf/web.xml [root@docker1 conf]# Spent lot of investigating but I'm still not sure what is the problem. On Sunday, 14 August 2016, 19:55, Mark Olsson wrote: On Sun, Aug 14, 2016 at 1:43 AM, Andrew M wrote: > I tried disabling SE Linux but no charm :( > What is interesting is I have enabled finest level of debugging but I > cannot see anything in log files as ALL or finest level of logging. > Make sure if you have an address filter in webapps/manager/META-INF/context.xml that it's correct, and try removing or commenting it out temporarily even if it does look correct just in case. Since your first message was 18 hours ago, I'm assuming at some point you have closed and reopened your browser? On my systems, if I enter the wrong user or password to get into the management console I get the 403 and I can't get back to the login prompt without completely closing and restarting the browser. I don't know if that's intentional or just a side effect of Firefox and the various privacy extensions I use, never bothered to look for the cause. So, depending on your browser, try closing/restarting, clearing caches and active logins, even try from a different browser.
Re: Unable to access Manager App, Host Manager and Server Status urls
I tried disabling SE Linux but no charm :( What is interesting is I have enabled finest level of debugging but I cannot see anything in log files as ALL or finest level of logging. logging.properties file.[CODE][root@docker1 logs]# cat ../conf/logging.properties # Licensed to the Apache Software Foundation (ASF) under one or more# contributor license agreements. See the NOTICE file distributed with# this work for additional information regarding copyright ownership.# The ASF licenses this file to You under the Apache License, Version 2.0# (the "License"); you may not use this file except in compliance with# the License. You may obtain a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing, software# distributed under the License is distributed on an "AS IS" BASIS,# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.# See the License for the specific language governing permissions and# limitations under the License. handlers = 1catalina.org.apache.juli.AsyncFileHandler, 2localhost.org.apache.juli.AsyncFileHandler, 3manager.org.apache.juli.AsyncFileHandler, 4host-manager.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler .handlers = 1catalina.org.apache.juli.AsyncFileHandler, java.util.logging.ConsoleHandler # Handler specific properties.# Describes specific configuration info for Handlers. 1catalina.org.apache.juli.AsyncFileHandler.level = ALL1catalina.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs1catalina.org.apache.juli.AsyncFileHandler.prefix = catalina. 2localhost.org.apache.juli.AsyncFileHandler.level = ALL2localhost.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs2localhost.org.apache.juli.AsyncFileHandler.prefix = localhost. 3manager.org.apache.juli.AsyncFileHandler.level = ALL3manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs3manager.org.apache.juli.AsyncFileHandler.prefix = manager. 4host-manager.org.apache.juli.AsyncFileHandler.level = ALL4host-manager.org.apache.juli.AsyncFileHandler.directory = ${catalina.base}/logs4host-manager.org.apache.juli.AsyncFileHandler.prefix = host-manager. java.util.logging.ConsoleHandler.level = ALLjava.util.logging.ConsoleHandler.formatter = org.apache.juli.OneLineFormatter # Facility specific properties.# Provides extra control for each logger. org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = ALLorg.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.AsyncFileHandler org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = ALLorg.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers = 3manager.org.apache.juli.AsyncFileHandler org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = ALLorg.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers = 4host-manager.org.apache.juli.AsyncFileHandler # For example, set the org.apache.catalina.util.LifecycleBase logger to log# each component that extends LifecycleBase changing state:org.apache.catalina.util.LifecycleBase.level = ALL # To see debug messages in TldLocationsCache, uncomment the following line:org.apache.jasper.compiler.TldLocationsCache.level = ALL # To see debug messages for HTTP/2 handling, uncomment the following line:org.apache.coyote.http2.level = ALL # To see debug messages for WebSocket handling, uncomment the following line:org.apache.tomcat.websocket.level = ALLorg.apache.catalina.session.level=ALLjava.util.logging.ConsoleHandler.level=ALL[root@docker1 logs]# [/CODE] output of catalina.out [CODE]13-Aug-2016 23:14:26.763 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /opt/apache-tomcat-8.5.4/webapps/ROOT13-Aug-2016 23:16:20.064 INFO [localhost-startStop-1] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRan...skipping...14-Aug-2016 18:38:29.084 FINE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.session.ManagerBase.processExpires Start expire sessions StandardManager at 1471163909084 sessioncount 0[/CODE] output of manager.log file[CODE]14-Aug-2016 18:34:35.878 FINE [http-nio-8080-exec-10] org.apache.catalina.core.ApplicationDispatcher.doForward Disabling the response for further output[/CODE] On Sunday, 14 August 2016, 10:26, Andrew M wrote: I'm not sure if this is related in any way but I just exported variable JAVA_HOME in setclasspath.sh export JAVA_HOME=/usr/java/default Still n
Re: Unable to access Manager App, Host Manager and Server Status urls
I'm not sure if this is related in any way but I just exported variable JAVA_HOME in setclasspath.sh export JAVA_HOME=/usr/java/default Still not challenge to input the credentials On Sunday, 14 August 2016, 8:35, Andrew M wrote: Yes, absolutely. I restarted after adding snippet several times but still not charm. What I observed is it doesn't even ask me for username and password but just says directly Access denied (403). On Sunday, 14 August 2016, 2:57, "Caldarale, Charles R" wrote: > From: Andrew M [mailto:bluemind2...@yahoo.com.INVALID] > Subject: Unable to access Manager App, Host Manager and Server Status urls > I have added these three lines in my tomcat-users.xml file: > > And did you remove the comment markers that bracket that area of the file? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Unable to access Manager App, Host Manager and Server Status urls
Yes, absolutely. I restarted after adding snippet several times but still not charm. What I observed is it doesn't even ask me for username and password but just says directly Access denied (403). On Sunday, 14 August 2016, 2:57, "Caldarale, Charles R" wrote: > From: Andrew M [mailto:bluemind2...@yahoo.com.INVALID] > Subject: Unable to access Manager App, Host Manager and Server Status urls > I have added these three lines in my tomcat-users.xml file: > > And did you remove the comment markers that bracket that area of the file? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Unable to access Manager App, Host Manager and Server Status urls
Good Day, Just another day in Paradise !My query is as mentioned in the subject.[Unable to access Manager App, Host Manager and Server Status urls], for each of these web applications, I am not challenged to input credentials rather gives directly access denied 403. Nothing interesting in catalina.out 14-Aug-2016 00:14:23.636 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/8.5.414-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: Jul 6 2016 08:43:30 UTC14-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number: 8.5.4.014-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Linux14-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 3.10.0-327.22.2.el7.x86_6414-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture: amd6414-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: /usr/java/jdk1.7.0_80/jre14-Aug-2016 00:14:23.637 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.7.0_80-b1514-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: Oracle Corporation14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: /opt/apache-tomcat-8.5.414-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: /opt/apache-tomcat-8.5.414-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=204814-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=/opt/tomcat14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=/opt/tomcat14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/tomcat/temp14-Aug-2016 00:14:23.638 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib14-Aug-2016 00:14:23.807 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]14-Aug-2016 00:14:23.837 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read14-Aug-2016 00:14:23.845 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]14-Aug-2016 00:14:23.846 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read14-Aug-2016 00:14:23.847 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 928 ms14-Aug-2016 00:14:23.879 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina14-Aug-2016 00:14:23.879 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.414-Aug-2016 00:14:23.896 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /opt/apache-tomcat-8.5.4/webapps/ROOT14-Aug-2016 00:14:55.791 INFO [localhost-startStop-1] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [31,061] milliseconds.14-Aug-2016 00:14:55.862 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /opt/apache-tomcat-8.5.4/webapps/ROOT has finished in 31,966 ms14-Aug-2016 00:14:55.862 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /opt/apache-tomcat-8.5.4/webapps/docs14-Aug-2016 00:14:55.913 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /opt/apache-tomcat-8.5.4/webapps/docs has finished in 51 ms14-Aug-2016 00:14:55.914 INFO [localhos
Unable to get the jmx information for tomcat 8 from command line(curl command)
Hi Guys, Any idea why it is saying "401 Unauthorized" I execute the following command: curl -1 --max-time 10 -s -k -u tomcat_jmx:'eyFW$&$FvSIp#FUk' --url https://pentagon505:8443/deploy/jmxproxy? I have added the user to tomcat-users.xml configuration file as well Where are the things going wrong? Please note that I am executing the command from a remote server: Complete output is as follows:http://www.w3.org/TR/html4/strict.dtd";> 401 Unauthorized 401 Unauthorized You are not authorized to view this page. If you have not changed any configuration files, please examine the file conf/tomcat-users.xml in your installation. That file must contain the credentials to let you use this webapp. For example, to add the manager-gui role to a user named tomcat with a password of s3cret, add the following to the config file listed above. Note that for Tomcat 7 onwards, the roles required to use the manager application were changed from the single manager role to the following four roles. You will need to assign the role(s) required for the functionality you wish to access. manager-gui - allows access to the HTML GUI and the status pages manager-script - allows access to the text interface and the status pages manager-jmx - allows access to the JMX proxy and the status pages manager-status - allows access to the status pages only The HTML interface is protected against CSRF but the text and JMX interfaces are not. To maintain the CSRF protection: Users with the manager-gui role should not be granted either the manager-script or manager-jmx roles. If the text or jmx interfaces are accessed through a browser (e.g. for testing since these interfaces are intended for tools not humans) then the browser must be closed afterwards to terminate the session. For more information - please see the Manager App HOW-TO. Would greatly appreciate your help. Thanks ! Andrew