On 24/07/17 11:57, Mark Thomas wrote:
> On 24/07/17 11:12, Flynn, Peter wrote:
I must apologise first for unintentionally misleading you: the upgrade
was from Tomcat 7.0.54-2 to 7.0.69-11, not from 6 to 7. I inherited this
along with what was clearly bad information.
> Running from a package tends to limit the members of this that are
> available to help to those that understand the packaging on the
> platform in question.
I'm afraid so. But I hope this is not about packaging, but about
modifying the configuration.
> Tomcat needs allowLinking to be correctly set if that path to a web
> application (or the web application itself) uses symlinks. I don't think
> that has changed between 6.0.x and 7.0.x.
There seem to be two, but I have never used or touched examples.
# find /var/lib/tomcat/webapps -type l -ls
536929726 0 lrwxrwxrwx 1 tomcat tomcat 40 Aug 11 2016
/var/lib/tomcat/webapps/examples/WEB-INF/lib/jstl.jar ->
/usr/share/java/jakarta-taglibs-core.jar
536929727 0 lrwxrwxrwx 1 tomcat tomcat 44 Aug 11 2016
/var/lib/tomcat/webapps/examples/WEB-INF/lib/standard.jar ->
/usr/share/java/jakarta-taglibs-standard.jar
>> # In new-style instances, if CATALINA_BASE isn't specified, it will
>> # be constructed by joining TOMCATS_BASE and NAME.
>
> Those last two variables are package specific.
What is a 'package' in this context? A Tomcat application?
> The Tomcat logs should at least tell you what - if anything - Tomcat is
> deploying.
If I can make sense of them...
> There is no one 'right' way to install Tomcat. Pick the one that works
> best for you (and be prepared to try an alternative if you hit problems).
:-) I'd rather compile from scratch, but that's just the way I was
brought up.
On 24/07/17 14:50, Coty Sutherland wrote:
[...]
> In my experience, a 404 after an update (with no other application
> changes) suggests that the application failed deployment. Can you
> verify that you don't see any exceptions in your log?
I would if I knew what to look for :-) In /var/log/tomcat there are:
• a catalina.out but it's empty
• hundreds of host-manager.yyyy-mm-yy.log, all empty
• hundreds of localhost.yyyy-mm-yy.log, all empty
• hundreds of localhost_access_log.yyyy-mm-dd.txt, between 10–20MB each
• dozens of catalina.out-yyyymmdd.gz, 20 or so bytes each
• dozens of catalina.yyyy-mm-dd.log, 30-100KB each
• one catalina.out, empty
I realise this is probably CentOS's or RedHat's doing :-)
A typical catalina.yyyy-mm-dd.log starts with
> Jul 25, 2017 7:55:01 AM org.apache.catalina.core.StandardServer await
> INFO: A valid shutdown command was received via the shutdown port. Stopping
> the Server ins
> tance.
> Jul 25, 2017 7:55:01 AM org.apache.coyote.AbstractProtocol pause
> INFO: Pausing ProtocolHandler ["http-bio-8080"]
> Jul 25, 2017 7:55:05 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in produ
> ction environments was not found on the java.library.path:
> /usr/java/packages/lib/amd64:/u
> sr/lib64:/lib64:/lib:/usr/lib
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlValidation'
> to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlNamespaceAwa
> re' to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlValidation'
> to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlNamespaceAwa
> re' to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlValidation'
> to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.tomcat.util.digester.SetPropertiesRule
> begin
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
> 'xmlNamespaceAwa
> re' to 'false' did not find a matching property.
> Jul 25, 2017 7:55:05 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["http-bio-8080"]
> Jul 25, 2017 7:55:05 AM org.apache.coyote.AbstractProtocol init
> INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
> Jul 25, 2017 7:55:05 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 586 ms
> Jul 25, 2017 7:55:05 AM org.apache.catalina.core.StandardService startInternal
> INFO: Starting service Catalina
and eventually gets round to
> Jul 25, 2017 7:55:30 AM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 25398 ms
and it includes
> INFO: Deployment of web application directory
> /var/lib/tomcat/webapps/examples has finished in 1,019 ms
> INFO: Deployment of web application directory /var/lib/tomcat/webapps/sample
> has finished in 299 ms
> INFO: Deployment of web application directory
> /var/lib/tomcat/webapps/host-manager has finished in 259 ms
> INFO: Deployment of web application directory /var/lib/tomcat/webapps/manager
> has finished in 244 ms
> INFO: Deployment of web application directory /var/lib/tomcat/webapps/ROOT
> has finished in 9,396 ms
So it appears to have found ROOT (which contains my Cocoon stuff) and
deployed it. But all the URIs come back with a Tomcat 404, which is why
I think that this version of Tomcat is interpreting the config
differently (or missing some expected attribute), as the config was
untouched between before and after.
///Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
