-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate / clear up exceptions in jenkins system log #3514
Comments
I've deleted job 493 from bullet 3 - if anyone wants to look into it, here is a tarball with the job directory from it, plus the two at either side: |
Azure cloud definition has been removed |
Adding these which are also occurring:
(Final three are fairly common but potentially related to the new Debian container that was done for #3043 which seems to have been producing some exceptions - the others less common) |
Running this again today, we have 18 occurences of lines like this, all on different build jobs: Other than that we have the following that are in double figures from yesterday's log:
Significantly fewer than before, and most of the remaining ones seem to be relating to the orka plugin |
A quick search on the recent ones (today and yesterday) can be done with
grep -h '^[^\ ]*Exception' /var/log/jenkins/jenkins.log /var/log/jenkins/jenkins.log.1 | sort | uniq -c
The two largest culprits at the moment are
SEVERE c.m.a.v.r.AzureVMAgentSSHLauncher#launch: Got exception on agent azurebuildagentxxxxxx
WARNING hudson.slaves.NodeProvisioner#update: Unexpected exception encountered while provisioning agent azurebuildagent
so both are with the deprecated Azure pluginWARNING o.j.p.w.cps.CpsStepContext$2#onFailure: Failed to proceed after CpsStepContext[287:build]:Owner[build-scripts/jobs/jdk8u/jdk8u-windows-x64-temurin/493:build-scripts/jobs/jdk8u/jdk8u-windows-x64-temurin #493]
INFO o.j.p.cloudstats.CloudStatistics#getIdFor: No support for cloud-stats-plugin by class io.jenkins.plugins.orka.OrkaProvisionedAgent
No node in
READYstate is available to deploy to
with a mention of orka. The others generally haveWARNING h.i.i.InstallUncaughtExceptionHandler#handleException
as the preceding lineBased on this clearing up things from the Azure and Orka provisioning would help with bullets 1, 2, 4 with 3 being one specific job that I can delete and the final one is partially with orka (Noting that as of 1142 today 100% of those were orka)
The text was updated successfully, but these errors were encountered: