[Qa-jenkins-scm] Jenkins OOM -> log-parser disabled

[Holger Levsen]

Hi Helmut,

(not sure if you are subscribed...)

On Freitag, 17. Juli 2015, Helmut Grohne wrote:
> Holger rebooted jenkins today to try to fix the OOM exceptions observed
> in the morning. Shortly thereafter, it was throwing OOM exceptions
> again. Using jstack -F $jenkins_pid (-> /root/jstack.out) I observed
> that 242/325 threads were doing log-parser stuff and concluded that
> "somehow" log-parser was the culprit. My attempts at getting a heap
> profile using jmap were less successful (/root/jenkins.hprof, killed
> after 10 minutes of stalling jenkins).
> 
> Thus I disabled the log-parser plugin by touching
> /var/lib/jenkins/plugins/log-parser.jpi.disabled and restarted the
> jenkins service (I had to kill -9 it).
> 
> It seems to be running stable now, but we want to figure out whether/why
> log-parser is the culprit. Any ideas?

no, except that sometimes java needs to be kicked + restarted, which is what I 
have done, after enabling the plugin again. Now everything seems to be fine 
again, til the next hick-up :/


cheers,
	Holger


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/qa-jenkins-scm/attachments/20150719/b2e9f7b9/attachment.sig>