Bug#764711: jenkins: Fails on Unable to read /var/lib/jenkins/config.xml
Source: jenkins Version: 1.565.3-1 Severity: important Dear Maintainer, After a recent upgrade, I can no longer access Jenkins, which displays : Error hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:912) at jenkins.model.Jenkins.init(Jenkins.java:811) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at jenkins.model.Jenkins$17.run(Jenkins.java:2561) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:901) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.thoughtworks.xstream.converters.ConversionException: hudson.security.GlobalMatrixAuthorizationStrategy : hudson.security.GlobalMatrixAuthorizationStrategy Debugging information message : hudson.security.GlobalMatrixAuthorizationStrategy cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : hudson.security.GlobalMatrixAuthorizationStrategy class : hudson.model.Hudson required-type : hudson.model.Hudson converter-type : hudson.util.RobustReflectionConverter path: /hudson/authorizationStrategy line number : 10 version : not available --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:112) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at hudson.XmlFile.unmarshal(XmlFile.java:163) ... 9 more Thanks in advance. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#764711: jenkins: Fails on Unable to read /var/lib/jenkins/config.xml
Hi. (Responding to myself) Olivier Berger olivier.ber...@telecom-sudparis.eu writes: After a recent upgrade, I can no longer access Jenkins, which displays : Error hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml FWIW, it seems 2 plugins (so far) have been missing for Jenkins to operate on my installation : - matrix-auth : this one seems to solve the config file parsing issue - matrix-project : solves a later issue my users have noticed (like https://issues.jenkins-ci.org/browse/JENKINS-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel) I manually fetched latest versions of these from http://updates.jenkins-ci.org/download/plugins/ and placed them in /var/lib/jenkins/plugins (chowned as jenkins:jenkins) and restarted. So far so good. My guess is that the build of latest upload misses quite a few plugins... Thanks in advance. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#739067: jenkins: multiple security vulnerabilities
On Fri, Feb 21, 2014 at 06:52:17AM +0100, Salvatore Bonaccorso wrote: Hi, On Sun, Feb 16, 2014 at 01:45:49AM +0900, Nobuhiro Ban wrote: Package: jenkins Version: 1.509.2+dfsg-2 Severity: grave Tags: security Dear Maintainer, The upstream vendor announced a security advisory. In this advisory, some vulnerabilities are rated high severity. https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14 SECURITY-105 affected by CVE-2013-7285 reported against XStream SECURITY-76 SECURITY-88 / CVE-2013-5573 SECURITY-109 SECURITY-108 SECURITY-106 SECURITY-93 SECURITY-89 SECURITY-80 SECURITY-79 SECURITY-77 SECURITY-75 SECURITY-74 SECURITY-73 See http://www.openwall.com/lists/oss-security/2014/02/21/2, where some CVEs were assigned to identify the issues. Please include the CVE identifier in the changelog when fixing the corresponding issues. FWIW, these are referenced in https://security-tracker.debian.org/tracker/source-package/jenkins Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#660688: [jenkins] Please enable maven-plugin
On Sat, Apr 06, 2013 at 10:51:31PM +0200, Guido Günther wrote: On Sat, Apr 06, 2013 at 09:29:52PM +0100, James Page wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/04/13 18:36, Guido Günther wrote: Re: James Page 2012-07-30 50167644.2040...@ubuntu.com Please note that it is possible to use the maven-plugin as distributed by upstream - so you should still be able to use this plugin. I tried to, but I couldn't find it listed in the Available tab. I guess that's because they assume it is included in core. I grabbed http://pkg.jenkins-ci.org/debian/binary/jenkins_1.480_all.deb and moved the maven-plugin.hpi and javadoc.hpi to /var/lib/jenkins/plugins. Created directories there without the hpi and unzipped the files into it. This seems to serve as a workaround. You should be able to install the maven plugin from the Jenkins Web UI - - I think its titled 'Maven 2 Plugin'. Tried that but it doesn't seem to werk for plugins already shipped with upstream Jenkins. It didn't show up for me. FWIW, http://updates.jenkins-ci.org/download/plugins/maven-plugin/ may offer the right version to be picked, i.e. currently for unstable's version, http://updates.jenkins-ci.org/download/plugins/maven-plugin/1.509.2/maven-plugin.hpi Btw, don't update it, once installed, or you'll get Java exceptions, if I'm not mistaken. Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#726489: jenkins: Provide directions on how to make it available on non-local IPs
Package: jenkins Version: 1.509.2+dfsg-2 Severity: wishlist Hi. It is not exactly explicit how Jenkins can be accessed, once installed, i.e. localhost:8080, from reading the README.Debian. However, this shouldn't be very hard to guess if one examines the running processes... nothing a casual admin should be blocked by. Still, making it explicit may be better, IMHO. But besides this minor point, I think it would be quite useful to provide directions on how to configure it (or what must be added, like apache + mod_proxy) to make it available on a non-local IP. Of course https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache may be useful, but there may be a better Debian way of doing things, which would be worth documenting in README.Debian. Many thanks in advance. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: i386 (i686) Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#675233: jenkins: Please secure access to jenkins or provide instructions to do so
Package: jenkins Severity: normal Hi. By default, AFAICT, Jenkins will be installed running on port 8080, accessible from anywhere, and fully configurable by anyone. I believed this is dangerous, security wise. Please either provide a default setup which limits its openness for instance allowing only local clients to connect on localhost:8080, or at minimum an important message when it gets installed via APT debconf templates, referring to a README providing instructions on how to configure its security. https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup seems a good start for such instructions, I guess, but I'm no Jenkins guru. Best regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (300, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#675234: jenkins: Should depend on libjs-yui instead of shipping a copy
Package: jenkins Severity: normal Hi. I've not checked in detail, but I can see lots of YUI JS files in the .war, which I believe should instead be used from the system ones packaged in libjs-yui. Hope this helps. Best regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (300, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#460398: bugs libapache2-mod-jk on lenny 32 bits with filer 8To
submitter 590075 maheus mleh...@cvf.fr found 590075 found 590075 1:1.2.26-2+lenny1 thanks On Thu, May 06, 2010 at 02:55:35PM +0200, maheus wrote: On lenny 32 bits with remote nfs 8To if workers.properties located on filer with value inode very high (probably 2^31) then workers.properties is not found by apache I recompile the libapache2-mod-jk sources with CFLAGS=$CFLAGS -D_FILE_OFFSET_BITS=64 and it solves the problem. I guess this relates to a totally different problem, so I've cloned it to #590075, hoping it will be treated there separately. Hope this helps. Best regards, __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#590078: libapache2-mod-jk: Conf file should refer to tomcat 6 now
Package: libapache2-mod-jk Version: 1:1.2.28-2 Severity: minor Hi. /etc/libapache2-mod-jk/workers.properties refers to : workers.tomcat_home=/usr/share/tomcat5 However, tomcat6 is now the defaults in squeeze. It would be great to adjust this, IMHO. Hope this helps. Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#590085: tomcat6: small typo about users file name in README.Debian
Package: tomcat6 Version: 6.0.26-5 Severity: minor Hi. In /usr/share/doc/tomcat6/README.Debian.gz on can read : ...then you need to edit /etc/tomcat6/tomcat6-users.xml... However, the file is currently named : /etc/tomcat6/tomcat-users.xml Hope this helps. Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomcat6 depends on: ii adduser 3.112 add and remove users and groups ii tomcat6-common6.0.26-5 Servlet and JSP engine -- common f Versions of packages tomcat6 recommends: ii authbind 1.2.0 Allows non-root programs to bind() Versions of packages tomcat6 suggests: ii tomcat6-admin 6.0.26-5 Servlet and JSP engine -- admin we ii tomcat6-docs 6.0.26-5 Servlet and JSP engine -- document ii tomcat6-examples 6.0.26-5 Servlet and JSP engine -- example pn tomcat6-user none (no description available) -- Configuration Files: /etc/tomcat6/policy.d/50local.policy changed [not included] /etc/tomcat6/tomcat-users.xml [Errno 13] Permission non accordée: u'/etc/tomcat6/tomcat-users.xml' -- debconf-show failed __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#590085: tomcat6: small typo about users file name in README.Debian
Hi. Also, while at it, one may fix the URL to be : http://localhost:8080/manager/html instead of http://localhost:8080/manager/ in the README.Debian.gz Hope this helps. Best regards, -- Olivier BERGER olivier.ber...@it-sudparis.eu http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#460398: Another victim
On Wed, Jul 23, 2008 at 01:22:37PM +0100, Matthew Exley wrote: Just wanted to say that I'm having the same problem with my own just-installed mod_jk installation. The connector is ignoring all JkMount directives in a global (in my case /etc/apache2/conf.d/mod_jk.conf) configuration, and instead these must be applied within each VirtualHosts definition. Indeed, the docs says : file:///usr/share/doc/libapache-mod-jk-doc/reference/apache.html ... You can use the JkMount directive at the top level or inside VirtualHost sections of your httpd.conf file. ... My 2 cents, Best regards, __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#552480: closed by Debian Orbital Alignment Team pkg-java-maintainers@lists.alioth.debian.org (Bug#552480: fixed in eclipse 3.5.2-1)
Hi. On Thu, Mar 18, 2010 at 10:36:58PM +, Debian Bug Tracking System wrote: #552480: eclipse: GTK dialog stopped working It has been closed by Debian Orbital Alignment Team pkg-java-maintainers@lists.alioth.debian.org. * Added workaround for gtk problems. (Closes: #552480) Am I wrong in saying that this has been fixed upstream in 3.5.2 and no workaround is needed anymore ? More details in https://bugs.eclipse.org/bugs/show_bug.cgi?id=290395#c38 Hope this helps. Best regards, __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#563937: Provide minimal info in /usr/share/doc/tomcat6/ for users
Package: tomcat6 Version: 6.0.20-9 Severity: wishlist Hi. I'd suggest to add some README.Debian file in /usr/share/doc/tomcat6/ in order to instruct, at least, the user, that more information may be found in /usr/share/doc/tomcat6-common/ and that the server should be accessible at http://localhost:8080/ once installed. Hope this helps, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomcat6 depends on: ii adduser 3.112add and remove users and groups ii jsvc1.0.2~svn20061127-10 wrapper to launch Java application ii tomcat6-common 6.0.20-9 Servlet and JSP engine -- common f tomcat6 recommends no packages. Versions of packages tomcat6 suggests: ii tomcat6-admin 6.0.20-9 Servlet and JSP engine -- admin we ii tomcat6-docs 6.0.20-9 Servlet and JSP engine -- document ii tomcat6-examples 6.0.20-9 Servlet and JSP engine -- example -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#563939: tomcat6-admin: Missing instructions on setting up admin user for manager webapp
Package: tomcat6-admin Version: 6.0.20-9 Severity: minor Hi. Once installed, http://localhost:8080/*manager/ ask for basic auth. However, there's nothing in /usr/share/doc/tomcat6-admin to instruct the Debian user what to do to get access. It seems to me that no user is configured by default and one has to to it by editing /etc/tomcat6/tomcat-users.xml, but it's not really obvious. Thanks in advance to add a README.Debian to mention this. Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomcat6-admin depends on: ii tomcat6 6.0.20-9 Servlet and JSP engine tomcat6-admin recommends no packages. tomcat6-admin suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#563948: tomcat6-admin: wrong french character encoding in manager app
Package: tomcat6-admin Version: 6.0.20-9 Severity: minor Hi. http://localhost:8080/manager/html contains strange encoding for french words, like D�marrer instead of Démarrer. Even though it's rendered as : Content-Type: text/html;charset=utf-8 That doesn't appear to be UTF-8 to me. Hope this helps. Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tomcat6-admin depends on: ii tomcat6 6.0.20-9 Servlet and JSP engine tomcat6-admin recommends no packages. tomcat6-admin suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
