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

WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Environment:
      Customer updated to the latest Long-Term Support version, 2.107.1, and is experiencing this warning with our NonStop platform.
    • Similar Issues:

      Description

      This exception is thrown by Jenkins to indicate that memory monitor inside Jenkins is unable to find "/proc/meminfo" or "top" command on nonstop platform.

      INFO: Jenkins is fully up and running
      Mar 28, 2018 12:44:28 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor
      WARNING: Failed to monitor master for Free Swap Space
      java.util.concurrent.ExecutionException: java.io.IOException: No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32
      at java.util.concurrent.FutureTask.report(FutureTask.java:122)
      at java.util.concurrent.FutureTask.get(FutureTask.java:206)
      at hudson.remoting.LocalChannel$2.get(LocalChannel.java:81)
      at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96)
      at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)
      Caused by: java.io.IOException: No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32
      at org.jvnet.hudson.MemoryMonitor.obtain(MemoryMonitor.java:91)
      at org.jvnet.hudson.MemoryMonitor.get(MemoryMonitor.java:57)
      at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:118)
      at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:114)
      at hudson.remoting.LocalChannel$1.call(LocalChannel.java:52)
      at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:748)

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            It does not seem to be a regression in the Jenkins core. Last change in https://github.com/jenkinsci/extras-memory-monitor was 4 years ago (CC Jesse Glick just in case)

            What do you expect to see there? Do you actually have "/proc/meminfo" or "top" in your package? Or do you expect Jenkins to do custom handling for this platform?

            Show
            oleg_nenashev Oleg Nenashev added a comment - It does not seem to be a regression in the Jenkins core. Last change in https://github.com/jenkinsci/extras-memory-monitor was 4 years ago (CC Jesse Glick just in case) What do you expect to see there? Do you actually have "/proc/meminfo" or "top" in your package? Or do you expect Jenkins to do custom handling for this platform?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Apparently there is a User ML thread for this issue: https://groups.google.com/forum/#!topic/jenkinsci-users/rrt25fUJCWY (CC Mark Waite)

            Drew Ritter please cross-reference queries if you create multiple ones.

            Show
            oleg_nenashev Oleg Nenashev added a comment - Apparently there is a User ML thread for this issue: https://groups.google.com/forum/#!topic/jenkinsci-users/rrt25fUJCWY (CC Mark Waite ) Drew Ritter please cross-reference queries if you create multiple ones.
            Hide
            drewritter69 Drew Ritter added a comment -

            Oleg Nenashev, I appreciate you finding this google group for me.  I honestly did not know exactly what component to select for this issue.  I saw similar issues reported that had core as their component and followed suit.  I also have changed the issue from a bug to an improvement.  I understand your point that I cannot expect the package to cater to every platform out there.  I will make sure to cross reference my questions in the other group here.

            Show
            drewritter69 Drew Ritter added a comment - Oleg Nenashev , I appreciate you finding this google group for me.  I honestly did not know exactly what component to select for this issue.  I saw similar issues reported that had core as their component and followed suit.  I also have changed the issue from a bug to an improvement.  I understand your point that I cannot expect the package to cater to every platform out there.  I will make sure to cross reference my questions in the other group here.

              People

              • Assignee:
                Unassigned
                Reporter:
                drewritter69 Drew Ritter
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: