-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.346.3
CloudBees Disk Usage Simple Plugin Version178.v1a_4d2f6359a_8
disk-usage plugin Version 0.28
WARNING com.cloudbees.simplediskusage.QuickDiskUsagePlugin$2 run Unable to run disk usage check
{{ java.io.IOException: Failed to set the timestamp of /var/lib/jenkins to 1678353573659}}
{{ at hudson.FilePath$Touch.invoke(FilePath.java:1804)}}
{{ at hudson.FilePath$Touch.invoke(FilePath.java:1789)}}
{{ at hudson.FilePath.act(FilePath.java:1200)}}
{{ at hudson.FilePath.act(FilePath.java:1183)}}
{{ at hudson.FilePath.touch(FilePath.java:1786)}}
{{ at com.cloudbees.simplediskusage.UsageComputation$1.preVisitDirectory(UsageComputation.java:109)}}
{{ at com.cloudbees.simplediskusage.UsageComputation$1.preVisitDirectory(UsageComputation.java:97)}}
{{ at java.base/java.nio.file.Files.walkFileTree(Files.java:2732)}}
{{ at java.base/java.nio.file.Files.walkFileTree(Files.java:2797)}}
{{ at com.cloudbees.simplediskusage.UsageComputation.computeUsage(UsageComputation.java:97)}}
{{ at com.cloudbees.simplediskusage.UsageComputation.compute(UsageComputation.java:52)}}
{{ at com.cloudbees.simplediskusage.QuickDiskUsagePlugin$2.run(QuickDiskUsagePlugin.java:286)}}
{{ at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)}}
{{ at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)}}
{{ at java.base/java.lang.Thread.run(Thread.java:829)}}
[JENKINS-70763] disk usage plugin seems to fail on timestamp updating with /var/lib/jenkins folder
Alexander
added a comment - still getting such lines after a day despite measures on the build nodes.
not sure whats up - it might be a master related subject - but why?
Alexander
added a comment - still getting such lines after a day despite measures on the build nodes.
not sure whats up - it might be a master related subject - but why? Can you try with https://github.com/jenkinsci/cloudbees-disk-usage-simple-plugin/releases/tag/203.v3f46a_7462b_1a_ that contains a fix for a similar issue?
i am not that sure about (but i am doing some testing now)
that the mentioned subdir might be meant to be for the static build node (or one of my nodes)
in my current jenkins setup - thus there is no such subdir at all and the user trying to access it just fails for that reason. (also it has no such rights, unless issuing commands via 'sudo' which i don't want to use during build times.)
so i went to console and created such a resource now - lets find out if that will diminish such messages for me.
rationale for the module builders:
first check for the directory - and if its missing at all, then please issue a more hinting message that includes that "missing" state and also the node name that it was happening for.