Ah, the file itself has nothing wrong with it, but here are my findings: In /var/lib/dpkg/info/tomcat7.postinst I noticed (as it should) that /etc/default/tomcat7 was included. In our JAVA_OPTS we just noticed that there are actual newlines inserted into the definition (as well as in CATALINA_OPTS).
It looked like: CATALINA_OPTS="-Xmx5588m -Xms5588m -XX:MaxPermSize=512m " Those were inserted by our config system and my guess is that previously the postinstall script it has accepted this configuration, or we simply have never applied a tomcat upgrade before on this setup and this is our first unlucky (but unrelated to the actual release content) encounter. I just corrected trimmed the whitespaces out of a server that did not have this update applied and then the upgrade proceeded without a problem (prompting me what to do with the file) and succesfully upgrade. I cannot make out which of the two issues above we're encountering, but Marc, could you verify something has changed with the handling of whitespace in the config files or verify for me the last time a security upgrade for tomcat was issued so I can verify this on my timeline? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599378 Title: Tomcat7 crashes after upgrade to 7.0.52-1ubuntu0.6 (over 7.0.52-1ubuntu0.3) on Ubuntu 14.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1599378/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
