Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    4
  • Views views
    567
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Storage Manager error: Times out while waiting for a database connection to become available in the connection pool.

afirizarry_uw

Engine running on OES2018sp3, Storage manager 5.3, Admin console 5.3.0.18.  Broke from one day to the next.  Does not manage home directories.

I checked the firewall on engine server and port 3009 is open.  Also tried shutting down the firewall and still same error.

Using nsmengine-config, I try to stop the service and it hangs and fails.  I am able to start the service and it shows as running but still get the errors.

Top shows the nsmengined process running at 100%Server has 16GB memory and 13GB free.  no space issues on the system partition.

Parents
  • 0  

    You mentioned memory is free but CPU is capped; are there multiple processor cores on this VM? (Presumably this is a VM?)

    Do you have a case open with technical support for this?

  • 0 in reply to   

    Yes to both.  Incident #02541637 .  VM has 4 CPU.  What I did last night as a work around:
    I edited the nsmengine.conf file. In the <ConnectionPool> section, I increased the value from 30 to 130 and restarted the engine. The Admin console then started fine and I was able to manage home directories again. I would still like to talk to someone from Condrey to discuss what happened and what an appropriate value is for the connection pool. Top is also reporting normal utilization and namengined thread is no longer running at 100%

Reply
  • 0 in reply to   

    Yes to both.  Incident #02541637 .  VM has 4 CPU.  What I did last night as a work around:
    I edited the nsmengine.conf file. In the <ConnectionPool> section, I increased the value from 30 to 130 and restarted the engine. The Admin console then started fine and I was able to manage home directories again. I would still like to talk to someone from Condrey to discuss what happened and what an appropriate value is for the connection pool. Top is also reporting normal utilization and namengined thread is no longer running at 100%

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.