[JIRA] [core] (JENKINS-32932) How to set jenkins log level from maven?
Title: Message Title code fx9 updated an issue Jenkins / JENKINS-32932 How to set jenkins log level from maven? Change By: code fx9 I am running Jenkins 1.646 from source using mvn jenkins-dev:run. It seems to be logging at the DEBUG level making page load very slow. How do I change the log level of Jenkins. I have tried the usual util.logging properties file, but I can't get it working.01:58:52.542 [Handling POST /ajaxBuildQueue from 0:0:0:0:0:0:0:1 : RequestHandlerThread[#5]] DEBUG o.apache.commons.jelly.JellyContext - Registering tag library to: jelly:swt taglib: org.apache.commons.jelly.tags.swt.SwtTagLibrary 01:58:52.542 [Handling POST /ajaxBuildQueue from 0:0:0:0:0:0:0:1 : RequestHandlerThread[#5]] DEBUG o.apache.commons.jelly.JellyContext - Registering tag library to: jelly:swt taglib: org.apache.commons.jelly.tags.swt.SwtTagLibraryI followed the various ideas from http://stackoverflow.com/questions/35218415/how-to-set-jenkins-log-level-from-maven . But those did not help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [core] (JENKINS-32932) How to set jenkins log level from maven?
Title: Message Title code fx9 created an issue Jenkins / JENKINS-32932 How to set jenkins log level from maven? Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Feb/16 8:03 AM Priority: Major Reporter: code fx9 I am running Jenkins from source using mvn jenkins-dev:run. It seems to be logging at the DEBUG level making page load very slow. How do I change the log level of Jenkins. I have tried the usual util.logging properties file, but I can't get it working. 01:58:52.542 [Handling POST /ajaxBuildQueue from 0:0:0:0:0:0:0:1 : RequestHandlerThread5] DEBUG o.apache.commons.jelly.JellyContext - Registering tag library to: jelly:swt taglib: org.apache.commons.jelly.tags.swt.SwtTagLibrary 01:58:52.542 [Handling POST /ajaxBuildQueue from 0:0:0:0:0:0:0:1 : RequestHandlerThread5] DEBUG o.apache.commons.jelly.JellyContext - Registering tag library to: jelly:swt taglib: org.apache.commons.jelly.tags.swt.SwtTagLibrary I followed the various ideas from http://stackoverflow.com/questions/35218415/how-to-set-jenkins-log-level-from-maven . But those did not help.
[JIRA] [core] (JENKINS-32932) How to set jenkins log level from maven?
Title: Message Title code fx9 updated an issue Jenkins / JENKINS-32932 How to set jenkins log level from maven? Change By: code fx9 Labels: jelly logging Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException in global-build-stats plug-in at startup
Kevin Calman assigned JENKINS-17248 to Frédéric Camblor java.lang.NullPointerException in global-build-stats plug-in at startup Change By: Kevin Calman (19/Jul/13 5:29 PM) Assignee: FrédéricCamblor 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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Kevin Calman commented on JENKINS-17248 java.lang.NullPointerException by start I am experiencing this issue too. I have Hudson 2.2.1 installed on CentOS 5.4 typically and it has been working fine for months, since the last version upgrade. I have not added or updated any plugins in the last several weeks, and have restarted the service and rebooted the machine since any configuration changes and all was working. Today, I restarted the service and experienced this issue. I manually removed the global-build-stats plug-in and restart, and it worked. From the Hudson web interface, I re-installed the global-build-stats v1.3 and set the service to restart when no jobs were running, and the issue reappeared. I have to again manually remove the global-build-stats plug-in and run without until this issue is resolved. Status? Can I provide any more info that would be useful? 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] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException in global-build-stats plug-in at startup
Kevin Calman updated JENKINS-17248 java.lang.NullPointerException in global-build-stats plug-in at startup Change By: Kevin Calman (19/Jul/13 5:02 PM) Summary: java.lang.NullPointerException bystart inglobal-build-statsplug-inatstartup 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-8801) When using the init scripts in the Redhat RPM package, the PID file is not updated when restarted from web interface
[ https://issues.jenkins-ci.org/browse/JENKINS-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159489#comment-159489 ] Kevin Calman commented on JENKINS-8801: --- Additional detail added to corresponding [Hudson issue HUDSON-8669|http://issues.hudson-ci.org/browse/HUDSON-8669], not reproduced on Jenkins. When using the init scripts in the Redhat RPM package, the PID file is not updated when restarted from web interface Key: JENKINS-8801 URL: https://issues.jenkins-ci.org/browse/JENKINS-8801 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: CentOS 5 x86, OpenJDK Reporter: Edward Rudd The init script stored the PID of the java process start in /var/run/jenkins.pid. This is used when the init script stops or restarts the jenkins proces. It is also used when rotating log files via the logrotate script. However, if I install a plugin, or update a plugin and restart jenkins from the web interface the PID is incorrect (it's the PID when jenkins first started, NOT after it was restarted via the web interface). This causes the log rotation script to not work and the init scripts to not shut down/restart jenkins. The logrotation is what really brought this to my attention as the logs were rotated, but since the PID was incorrect jenkins was not sent the SIGALARM so that it would reopen the log files.. And as such kept logging to the now deleted log file and consequently filled up that partition. Ideally jenkins should manage the PID itself, and just have an extra argument passed on startup.. i.e. --pidfile /var/run/jenkins.pid -- 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
