XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    vm_fault: pager read error, pid 88715 (rrdtool)

    Scheduled Pinned Locked Moved Hardware
    3 Posts 2 Posters 56 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kevdog
      last edited by

      I'm running pfsense version 2.8.0 virtualized on xcp-ng 8.3.0.

      The host has 64 GB RAM (two 32 GB dual channel DDR4 modules) with a 1Tb Nvme drive and 1tb samsung SSD.

      I have 5 virtualized systems on the xcp-ng host consuming a total of 30Gb of the 64 GB.

      One of my virtualized hosts is pfSense 2.8.0. Recently the pfSense host is giving me consistent error messages such as the following:

      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      Aug 25 07:46:28	kernel		vm_fault: pager read error, pid 24443 (rrdtool)
      

      Doing some reading on the error (https://www.reddit.com/r/opnsense/comments/1jlfshn/vm_fault_pager_read_error_pid_76098_rrdtool/), it could indicate a bad RAM module?? I'm just not sure. Is RAM presented to the pfsense host as virtual memory? Other than doing a mem86+ test on the RAM modules of the xcp-ng host, is there any other way to debug this error? I don't see errors from any other of the virtualized linux operating systems, however is there something I should be checking on the other virtualized systems or the host that would confirm a possible memory error as error (assuming its a memory error)?

      Thanks for any input.

      D 1 Reply Last reply Reply Quote 0
      • D Offline
        DustinB @kevdog
        last edited by

        @kevdog a memtest is going to check the physical memory for any issues, if you're not seeing any other errors on other VMs I would lean more towards this VM having some kind of corruption issue.

        A memtest won't hurt and it would help to eliminate a possible issue, it would definitely take some time to complete, which may not be an option if you have any sort of uptime requirements.

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          kevdog @DustinB
          last edited by

          @DustinB I have time to run a ram check (luckily), and if not I'll just recreate VM. Luckily pfsense makes it pretty easy to reinstall from scratch by saving to a configuration file which can be imported to new version. I'll work on it later today or tomorrow and report back.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post