PDQ Inventory 16.2.0.0 Memory Issue

Comments

7 comments

  • Eric Jacobs

    Rolling back to the previous release of PDQ Inventory resolved this issue, as it's been online for an hour and the PDQ Inventory Service is using less than 150MB of memory.

    0
    Comment actions Permalink
  • Timothy Bryant

    I'm having two different issues, but even with the database updates rolling back did not cause problems with your install? If I could get it back up, I might be able to fix the other issue which is a timeout for localhost:7337. I've created rules to make sure PDQ Inventory and port 7337 are not blocked by the firewall.

     

    Thanks,

    Tim

     

    0
    Comment actions Permalink
  • sean johnson

    I'm getting the time out error after updating as well (I'll upgrade again to see if there were any memory problems). Rolling back to the previous version has fixed this both times that I've tested updating. Created a ticket last Thursday, not sure what all changed on the backend to be causing this much trouble for us. 

    0
    Comment actions Permalink
  • Eric Jacobs

    When you install an older version the database gets rolled back to the older version as well. I was worried about the database also, but luckily it's designed to roll back with a downgrade. I tried re-installing and uninstalling and installing from scratch. Either way I have the issue with memory usage, and with time I timeout when trying to connect as well. Going back to the old version is the way to resolve the issue until they release a fix.

    0
    Comment actions Permalink
  • Novinger, Shawn

    I have the same issue as well.  Massive memory usage causing client connections to the server as well as local connections to the console to time out.  I suppose I will roll back the version until this is straightened out.

    0
    Comment actions Permalink
  • Jason Hanks

    Have you contacted Support@pdq.com with these issues?  I believe there are some newer customer builds that might help and if the error persists after those are applied, any information you provide will help us narrow down the problem.

    0
    Comment actions Permalink
  • Novinger, Shawn

    Hi Jason,

    I contacted Support and resolved the issue with one of their later builds (16 Release 2 Build 5 to be exact.)  Thanks for the follow up. 

     

    0
    Comment actions Permalink

Please sign in to leave a comment.