2015-02-26 19:26 GMT+03:00 Mark Shifman <mark.shif...@yale.edu>: > This is truly embarrassing since I have the manager running fine on tomcat > 7. > > http://localhost:8080/manager/status > returns > 127.0.0.1 - - [26/Feb/2015:10:47:11 -0500] "GET /manager/status HTTP/1.1" > 404 1022 > > http://localhost:8080/manager/html > returns > 127.0.0.1 - - [26/Feb/2015:11:00:40 -0500] "GET /manager/html HTTP/1.1" 404 > 1018 > > I am starting tomcat 8.0.20 with jsvc and running tomcat as "mas" > > catalina.out shows > > Feb 26, 2015 10:37:23 AM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deployment of web application directory > /home/apache-tomcat-8.0.20/webapps/manager has finished in 326 ms > > so it looks like the manager is started.
No. The above message just displays timing (some people were interested in how long the deployment takes). The same text is used regardless of success or failure. 404 usually means that the web application is not running. In that situation the request is served by the ROOT webapp, not by manager webapp. (It is visible if either the ROOT webapp or the manager webapp has its own configuration of AccessLogValve). Do you have the files in /home/apache-tomcat-8.0.20/webapps/manager ? Any chance that you are starting with Java Security Manager being enabled? In this case you should see error messages in the logs. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
