Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65302

Nodes monitoring temporary broken due to inodes-monitor

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • inodes-monitor-plugin
    • None
    • inodes-monitor-plugin 0.5.1
      Jenkins 2.263.1

      The Nodes monitoring didn't refresh for some time (showed N/A for values) and I found this in the logs:
      ```

      2021-04-07 08:39:02.655+0000 [id=2406340] WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: m.data(c) in /computer/. Reason: java.lang.IllegalStateException: WTF? Can't parse - as integer percentage2021-04-07 08:39:02.655+0000 [id=2406340] WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: m.data(c) in /computer/. Reason: java.lang.IllegalStateException: WTF? Can't parse - as integer percentagejava.text.ParseException: - at org.jenkinsci.plugins.inodesnodemonitor.InodesMonitor.parse(InodesMonitor.java:59) at org.jenkinsci.plugins.inodesnodemonitor.InodesMonitor.data(InodesMonitor.java:71)Caused: java.lang.IllegalStateException: WTF? Can't parse - as integer percentage at org.jenkinsci.plugins.inodesnodemonitor.InodesMonitor.data(InodesMonitor.java:94) at sun.reflect.GeneratedMethodAccessor2914.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:100) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
      ```

       

      I suspect that it happened because one node was offline

          [JENKINS-65302] Nodes monitoring temporary broken due to inodes-monitor

          kutzi added a comment -

          This seems to happen whenever only a single agent is down.
          Then also e.g. the REST API for any other agent is broken

          kutzi added a comment - This seems to happen whenever only a single agent is down. Then also e.g. the REST API for any other agent is broken

          kutzi added a comment -

          See https://github.com/jenkinsci/inodes-monitor-plugin/pull/4 which should IMO fix it.
          Not sure though which value I should return in that case

          kutzi added a comment - See https://github.com/jenkinsci/inodes-monitor-plugin/pull/4  which should IMO fix it. Not sure though which value I should return in that case

          Jana added a comment -

          Hi kutzi
          can you please help me to reproduce this issue?

          Jana added a comment - Hi kutzi can you please help me to reproduce this issue?

          kutzi added a comment -

          Hi there,

          it's pretty long ago.
          I think it was quite easy to reproduce, when one of the build agents is being restarted.
          During that time you will get with some probability this error

          kutzi added a comment - Hi there, it's pretty long ago. I think it was quite easy to reproduce, when one of the build agents is being restarted. During that time you will get with some probability this error

            Unassigned Unassigned
            kutzi kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: