[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, 5 months
[Bug 1256847] New: CVE-2015-3271 tika: Information disclosure vulnerability when running Apache Tika Server [fedora-all]
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1256847
Bug ID: 1256847
Summary: CVE-2015-3271 tika: Information disclosure
vulnerability when running Apache Tika Server
[fedora-all]
Product: Fedora
Version: 22
Component: tika
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: puntogil(a)libero.it
Reporter: amaris(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
puntogil(a)libero.it
Blocks: 1256846 (CVE-2015-3271)
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=1256846
[Bug 1256846] CVE-2015-3271 tika: Information disclosure vulnerability when
running Apache Tika Server
--
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=Sk7x8hG4e0&a=cc_unsubscribe
_______________________________________________
java-sig-commits mailing list
java-sig-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/java-sig-commits@lists.fedorapro...
8 years, 5 months
[Bug 1247793] New: /usr/bin/gradle-local missing in F22
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1247793
Bug ID: 1247793
Summary: /usr/bin/gradle-local missing in F22
Product: Fedora
Version: 22
Component: javapackages-tools
Assignee: mizdebsk(a)redhat.com
Reporter: orion(a)cora.nwra.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mat.booth(a)redhat.com, mizdebsk(a)redhat.com,
msimacek(a)redhat.com, msrb(a)redhat.com
Description of problem:
/usr/bin/gradle isn't shipped in the F22 version of gradle-local. Since gradle
is in F22, would be nice to have gradle-local as well.
Version-Release number of selected component (if applicable):
4.3.2-6.fc22
--
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=0bT4lTdKRV&a=cc_unsubscribe
8 years, 5 months
[Bug 1261458] New: Zookeeper service fails to start due to classpath errors, logging no error
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1261458
Bug ID: 1261458
Summary: Zookeeper service fails to start due to classpath
errors, logging no error
Product: Fedora
Version: 22
Component: zookeeper
Assignee: tstclair(a)redhat.com
Reporter: KevinFarshaw(a)mailinator.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ctubbsii-fedora(a)apache.org, ethan(a)ethantuttle.com,
java-sig-commits(a)lists.fedoraproject.org,
jeff(a)ocjtech.us, s(a)shk.io, tstclair(a)redhat.com
Created attachment 1071694
--> https://bugzilla.redhat.com/attachment.cgi?id=1071694&action=edit
Patched /usr/libexec/zkEnv.sh
I've reviewed the other zookeeper issues, they report other problems and
concern f21 rather the the current f22.
Description of problem:
After sudo cp /etc/zookeeper/zoo_sample.cfg /etc/zookeeper/zoo.cfg,
Starting the zookeeper service fails silently without logging any error
to console or journal.
Manually starting it in the foreground using:
sudo -u zookeeper /usr/bin/zkServer.sh start-foreground
Gives:
JMX enabled by default
Using config: /etc/zookeeper/zoo.cfg
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/usr/share/java/slf4j/slf4j-log4j12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/share/java/slf4j/slf4j-simple.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/share/java/slf4j/slf4j-nop.jar!/org/slf4j/impl/StaticLoggerBinder.class]
Version-Release number of selected component (if applicable):
zookeeper-3.4.6-4.fc22.x86_64
How reproducible:
always
Steps to Reproduce:
1. sudo cp /etc/zookeeper/zoo_sample.cfg /etc/zookeeper/zoo.cfg
2. systemctl start zookeeper (fails, nothing logged)
3. sudo -u zookeeper /usr/bin/zkServer.sh start-foreground (logs error to
stderr)
Additional info:
Tipped off by https://issues.apache.org/jira/browse/SOLR-2369, it appears
that:
1. The classpath used to launch zk contains multiple jars of
slog4j logging providers.
2. This is not allowed as documented by sl4fj at
http://www.slf4j.org/codes.html#multiple_bindings
3. Inspection of the classpath setup by /usr/libexec/zkEnv.sh shows much
duplication, including multiple bindings.
Attached modified zkEnv.sh in which I've:
1. Removed duplicates.
2. Commented out alternate bindings and allegedly redundant jars.
3. I did not intentionally remove any jars originally in the file (only
commented).
4. Added individual log4j jars from appropriate package.
After updating zkEnv.sh, starting the service with systemctl complains
about missing precondition of file at /var/lib/zookeeper/data/myid.
After creating the file (with a single line containing an id such as
the digit '1'), zookeeper starts.
I have not exercised zookeeper to see whether something else is broken
(or was broken by the changes), but it does start up properly now.
--
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=laEkcaD2Z1&a=cc_unsubscribe
_______________________________________________
java-sig-commits mailing list
java-sig-commits(a)lists.fedoraproject.org
http://lists.fedoraproject.org/postorius/java-sig-commits@lists.fedorapro...
8 years, 5 months