[Bug 1224515] New: default for tomcat temp folder should be multiple instances should be ${catalina.base}/temp
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1224515
Bug ID: 1224515
Summary: default for tomcat temp folder should be multiple
instances should be ${catalina.base}/temp
Product: Fedora
Version: 21
Component: tomcat
Severity: low
Assignee: ivan.afonichev(a)gmail.com
Reporter: edwardquick(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, me(a)coolsvap.net
Description of problem:
When a user configures multiple instances of tomcat, the CATALINA_TMPDIR
setting is not updated to match the instance's temp folder.
Version-Release number of selected component (if applicable):
tomcat-7.0.59-1.fc21.noarch
How reproducible:
The default setting in /etc/tomcat/tomcat.conf is
# System-wide tmp
CATALINA_TMPDIR="/var/cache/tomcat/temp"
Steps to Reproduce:
1. systemctl enable tomcat(a)instance1.service
2. Create catalina base folders (and contents), conf, work, temp, webapps under
/var/lib/tomcats/instance1
3. systemctl start tomcat(a)instance1.service
Actual results:
In the tomcat instance1 process, the temp folder is specified as:
-Djava.io.tmpdir=/var/cache/tomcat/temp
Expected results:
The tomcat instance temp folder should be:
-Djava.io.tmpdir=/var/lib/tomcats/instance1/temp
Additional info:
Note we did nothing to configure LOGGING_PROPERTIES, yet the process correctly
specifies it as we expect
-Djava.util.logging.config.file=/var/lib/tomcats/instance1/conf/logging.properties
This issue is easily fixed with the followiing patch to
/usr/libexec/tomcat/preamble
# diff -u /usr/libexec/tomcat/preamble.orig /usr/libexec/tomcat/preamble
--- /usr/libexec/tomcat/preamble.orig 2015-05-23 23:10:14.979921192 +0100
+++ /usr/libexec/tomcat/preamble 2015-05-23 23:14:07.636951751 +0100
@@ -42,3 +42,11 @@
LOGGING_PROPERTIES="${CATALINA_HOME}/conf/logging.properties"
fi
fi
+
+if [ -z "$CATALINA_TMPDIR" ] ; then
+ CATALINA_TMPDIR="${CATALINA_BASE}/temp"
+ if [ ! -d "${CATALINA_TMPDIR}" ] ; then
+ CATALINA_TMPDIR="${CATALINA_HOME}/temp"
+ fi
+fi
+
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=niFb9Utlz4&a=cc_unsubscribe
8 years, 3 months
[Bug 1223569] New: Logs in catalina.out are lost with each RPM update
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1223569
Bug ID: 1223569
Summary: Logs in catalina.out are lost with each RPM update
Product: Fedora
Version: 21
Component: tomcat
Severity: medium
Assignee: ivan.afonichev(a)gmail.com
Reporter: doug.knight(a)karmix.org
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, me(a)coolsvap.net
Description of problem:
The rpm for tomcat contains /var/log/tomcat/catalina.out in its manifest. Each
time the tomcat package is updated, rpm replaces the catalina.out log with the
mostly-empty file from the package. All logs in catalina.out are lost in the
process.
Version-Release number of selected component (if applicable):
All versions since commit 3cb34c71 (tomcat-6.0.32-1)
How reproducible:
Always
Steps to Reproduce:
1. Install an old version of tomcat
2. Create logs in /var/log/tomcat/catalina.out
3. yum upgrade tomcat
Actual results:
catalina.out is clobbered, and the logs are lost.
Expected results:
Not this.
Additional info:
I recommend dropping catalina.out from the manifest. Since it is a log file,
and should initially be empty, we don't want rpm to manage its contents.
Likewise, we don't care about tracking its metadata since we are using the
/var/log/tomcat directory to control access to the tomcat log files.
I am not sure why we are putting the "tomcat-X.Y.Z RPM installed" message in
catalina.out; it seems like something that belongs in a system log, not an
application log. If we really need to keep that message around, we should add
it with something like
runuser -s /bin/bash -c '/bin/echo
"%{name}-%{major_version}.%{minor_version}.%{micro_version} RPM installed" >>
%{logdir}/catalina.out'
from the %post script.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ME0qtjP2n5&a=cc_unsubscribe
8 years, 3 months
[Bug 1222576] New: CVE-2014-7810 tomcat: Tomcat/JbossWeb: security manager bypass via EL expressions [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1222576
Bug ID: 1222576
Summary: CVE-2014-7810 tomcat: Tomcat/JbossWeb: security
manager bypass via EL expressions [fedora-all]
Product: Fedora
Version: 21
Component: tomcat
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: ivan.afonichev(a)gmail.com
Reporter: mprpic(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com, me(a)coolsvap.net
Blocks: 1222573 (CVE-2014-7810)
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time. If you need to fix the versions independent of each other,
you may clone this bug as appropriate.
[bug automatically created by: add-tracking-bugs]
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1222573
[Bug 1222573] CVE-2014-7810 Tomcat/JbossWeb: security manager bypass via EL
expressions
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bqqGMkX9c1&a=cc_unsubscribe
8 years, 3 months
[Bug 1147963] New: JENKINS script for showing failed jobs is not working
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1147963
Bug ID: 1147963
Summary: JENKINS script for showing failed jobs is not working
Product: Fedora
Version: 21
Component: jenkins
Severity: medium
Assignee: msrb(a)redhat.com
Reporter: amsharma(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
msrb(a)redhat.com
Description of problem:
JENKINS script for showing failed jobs is not working
Version-Release number of selected component (if applicable):
[root@dhcp201-185 ~]# rpm -qa | grep jenkins
jenkins-icon-shim-1.0.3-1.fc21.noarch
js-yui2-jenkins-2.9.0-6.fc21.noarch
jenkins-task-reactor-1.4-2.fc21.noarch
jenkins-external-monitor-job-plugin-1.2-1.fc21.noarch
jenkins-javadoc-plugin-1.2-1.fc21.noarch
jenkins-commons-jelly-1.1.20120928-6.fc21.noarch
jenkins-instance-identity-1.3-4.fc21.noarch
jenkins-sshd-1.6-4.fc21.noarch
jenkins-1.581-2.fc21.noarch
jenkins-ant-plugin-1.2-1.fc21.noarch
jenkins-executable-war-1.29-3.fc21.noarch
jenkins-xstream-1.4.7-3.jenkins1.fc21.noarch
trilead-ssh2-217-4.jenkins4.fc21.noarch
jenkins-ssh-cli-auth-1.2-4.fc21.noarch
jenkins-core-1.581-2.fc21.noarch
jenkins-remoting-2.43-1.fc21.noarch
jenkins-json-lib-2.4-7.fc21.noarch
jenkins-junit-plugin-1.1-1.fc21.noarch
jenkins-mailer-plugin-1.11-1.fc21.noarch
jenkins-extras-memory-monitor-1.8-1.fc21.noarch
jenkins-crypto-util-1.4-2.fc21.noarch
jenkins-version-number-1.1-4.fc21.noarch
jenkins-webapp-1.581-2.fc21.noarch
jenkins-winstone-2.3-1.fc21.noarch
jenkins-jexl-1.1-3.20111212.fc21.noarch
jenkins-cli-1.581-2.fc21.noarch
How reproducible:
Always
Steps to Reproduce:
1.go to https://wiki.jenkins-ci.org/display/JENKINS/Failed+Jobs
2. copy script and paste in localhost:8080/script
Actual results:
It does not display anything in output.
Result
Result: []
Expected results:
It should display all failed jobs
Additional info:
I had failed jobs in my jenkins
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=63mWa2HTjL&a=cc_unsubscribe
8 years, 4 months