Bug#821391: AGAIN all tomcat server crashed due to this bug !

2016-06-27 Thread David_dev Dev
Correction for first mail of this morning : Resolution : sudo chown tomcat7 /var/lib/tomcat7/conf/jmxremote.password sudo chmod 600 /var/lib/tomcat7/conf/jmxremote.password sudo service tomcat7 restart (sorry bad copy/paste) 2016-06-27 11:34 GMT+02:00 David_dev Dev : > Hi, > > I'd prefer no

Bug#821391: AGAIN all tomcat server crashed due to this bug !

2016-06-27 Thread David_dev Dev
Hi, I'd prefer not change default config and current install (will need to change template, deploy scripts and internal docs to :-( ), and in precedent answers someone onawer that's this chown is not recommanded and should have been change : "So in my opinion we should stop chowning /etc/tomcat7

Bug#821391: AGAIN all tomcat server crashed due to this bug !

2016-06-27 Thread Emmanuel Bourg
Hi David, Did you consider moving the jmxremote.password file out of /etc/tomcat7? This would prevent future updates from messing with your files. Emmanuel Bourg

Bug#821391: AGAIN all tomcat server crashed due to this bug !

2016-06-27 Thread David_dev Dev
Hi, This morning we apply the security patch on our debian 7 servers, and ALL our tomcat7 crash ! Exactly the same problem, the patch overwrite the owner of ALL /etc/tomcat7 file, includind jmxremote.password to root:tomcat7. I see in the bug that you should have change this configuration. Here