[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai commented on JENKINS-20630 Jenkins fails to start I used git bisect to determine that 7d2a3b3f9c96f3ab950d84781da5cf903ca4c4be was the first commit that had this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai commented on JENKINS-20630 Jenkins fails to start Jenkins 1.541 also fails to start in the same way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai created JENKINS-20630 Jenkins fails to start Issue Type: Bug Assignee: Unassigned Attachments: jenkins 1.539.err.log, jenkins 1.540.err.log Components: core Created: 18/Nov/13 5:59 PM Description: When I try to start Jenkins 1.540, it attempts to do so and eventually fails. When it fails, it tries to start again, which then fails. This repeats indefinitely. I've attached a log file from one such iteration. I am able to start 1.539 successfully. I've attached the log file from this as well. Environment: Microsoft Windows Server 2003 R2 Project: Jenkins Priority: Major Reporter: Matt Kraai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Matt Kraai updated JENKINS-20630 Jenkins fails to start Change By: Matt Kraai (18/Nov/13 6:07 PM) Attachment: hs_err_pid1788.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-18275) http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php
Matt Kraai reopened JENKINS-18275 http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 124. I see the same error again when I visit http://jenkins-ci.org/. Change By: Matt Kraai (29/Jul/13 3:45 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18387) Jenkins sometimes fails to restart successfully
Matt Kraai commented on JENKINS-18387 Jenkins sometimes fails to restart successfully This problem also appears to have happened when I restarted Jenkins after downloading the .war file for 1.524. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18387) Jenkins sometimes fails to restart successfully
Matt Kraai commented on JENKINS-18387 Jenkins sometimes fails to restart successfully This problem appears to have happened again when I restarted Jenkins after downloading the .war file for 1.522. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Matt Kraai commented on JENKINS-15355 AdjunctManager: exception upon startup I see the same exception when starting Jenkins 1.522 if and only if the Maven Integration plugin is disabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repository] (JENKINS-18288) Link to latest send to version 1.518 on the mirror page
Matt Kraai commented on JENKINS-18288 Link to latest send to version 1.518 on the mirror page It now redirects to http://fallback.jenkins-ci.org/war/1.518/jenkins.war, which does not work. I suspect this occurs because 1.519 has been released. I've tried this from multiple systems, at least one of which I'm sure is not cached. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18387) Jenkins sometimes fails to restart successfully
Matt Kraai created JENKINS-18387 Jenkins sometimes fails to restart successfully Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: log Components: core Created: 18/Jun/13 3:54 PM Description: When I try to restart Jenkins by visiting its /restart URL, it sometimes fails to restart successfully. When this problem occurs, Process Explorer first shows the existing jenkins.exe and java.exe processes terminate. It then shows a new jenkins.exe as the parent of a new java.exe process and a DW20.exe process (a Microsoft Office error reporting tool). After some time, it shows the jenkins.exe process terminate and the java.exe and DW20.exe processes with no parent. It then shows another jenkins.exe and java.exe start, run briefly, then terminate. This repeats indefinitely. Eventually, DW20.exe terminates. The first java.exe process started runs until manually killed, at which point jenkins.exe and java.exe start and run successfully. I'll attach the contents of jenkins.err.log from one such occurrence. Environment: Microsoft Windows Server 2003 R2, Standard Edition, Service Pack 2 Project: Jenkins Priority: Major Reporter: Matt Kraai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-18275) http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php
Matt Kraai resolved JENKINS-18275 as Fixed http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 124. I no longer see this warning when I visit the Jenkins home page, so this issue appears to have been fixed. Change By: Matt Kraai (11/Jun/13 2:47 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-18275) http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php
Matt Kraai closed JENKINS-18275 as Fixed http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 124. Change By: Matt Kraai (11/Jun/13 2:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-18275) http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php
Matt Kraai created JENKINS-18275 http://jenkins-ci.org/ displays warning: unlink(/tmp/cache_lock) [function.unlink]: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 124. Issue Type: Bug Assignee: Unassigned Attachments: Jenkins home page.PNG Components: www Created: 10/Jun/13 4:02 PM Description: When I visit the Jenkins home page at http://jenkins-ci.org/ it displays the following message in a red box above the "Meet Jenkins" icon and description: warning: unlink(/tmp/cache_lock) function.unlink: No such file or directory in /etc/drupal/6/sites/default/modules/cacherouter/Cache.php on line 124. I do not see this warning when I visit https://jenkins-ci.org/ Project: Jenkins Priority: Major Reporter: Matt Kraai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17824) Error when upgrading from version 1.30: com4j.ComException:The server is not operational.
Matt Kraai resolved JENKINS-17824 as Duplicate Error when upgrading from version 1.30: com4j.ComException:The server is not operational. Change By: Matt Kraai (03/May/13 10:42 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15469) Fails to save hudson.plugins.ircbot.IrcPublisher.xml at startup
Matt Kraai created JENKINS-15469 Fails to save hudson.plugins.ircbot.IrcPublisher.xml at startup Issue Type: Bug Assignee: kutzi Components: ircbot Created: 10/Oct/12 10:24 PM Description: When I start Jenkins, the following message appears in the error log: Oct 10, 2012 3:14:51 PM hudson.model.Descriptor save WARNING: Failed to save C:\Program Files\Jenkins\hudson.plugins.ircbot.IrcPublisher.xml java.io.IOException: Unable to delete C:\Program Files\Jenkins\hudson.plugins.ircbot.IrcPublisher.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Descriptor.save(Descriptor.java:758) at hudson.plugins.ircbot.IrcPublisher$DescriptorImpl.readResolve(IrcPublisher.java:522) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:46) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:137) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at hudson.XmlFile.unmarshal(XmlFile.java:160) at hudson.model.Descriptor.load(Descriptor.java:779) at hudson.plugins.ircbot.IrcPublisher$DescriptorImpl.init(IrcPublisher.java:204) at hudson.plugins.ircbot.IrcPublisher.clinit(IrcPublisher.java:55) at sun.reflect.GeneratedSerializationConstructorAccessor27.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.thoughtworks.xstream.converters.reflection.Sun14ReflectionProvider.newInstance(Sun14ReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:375) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:220) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:263) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at
[JIRA] (JENKINS-13001) Use HTTP Proxy Configuration to check for new Jenkins versions
Matt Kraai created JENKINS-13001: Summary: Use HTTP Proxy Configuration to check for new Jenkins versions Key: JENKINS-13001 URL: https://issues.jenkins-ci.org/browse/JENKINS-13001 Project: Jenkins Issue Type: Improvement Components: core Reporter: Matt Kraai Priority: Minor If I configure Jenkins to use my company's HTTP proxy using the Plugin Manager HTTP Proxy Configuration section, Plugin Manager appears to be able to download plugin information, but Jenkins doesn't appear to detect when new versions of Jenkins are released. If I add the appropriate -Dhttp.proxyHost option in jenkins.xml, Jenkins does detect when new versions of Jenkins are released. It would be nice if the HTTP Proxy Configuration section was moved to the Jenkins configuration page and used to check for new versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
