HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Cluster error
Operating System - HP-UX
1837253
Members
2255
Online
110115
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 02:39 AM
07-09-2008 02:39 AM
Hi one of the node in a two node cluster got rebooted. In syslog we found following messages.
Jul 8 16:49:27 hp07 vmunix: proc: table is full
Jul 8 16:49:27 hp07 above message repeats 2388 times
Jul 8 16:49:01 hp07 prngd[2180]: Could not fork: Resource temporarily unavailable
Jul 8 16:49:27 hp07 above message repeats 23 times
output of who -b is
reboot system boot Tue Jul 8 16:56
Can any one give the possible reasons and solution to fix this issue.
regards
Sujith
Jul 8 16:49:27 hp07 vmunix: proc: table is full
Jul 8 16:49:27 hp07 above message repeats 2388 times
Jul 8 16:49:01 hp07 prngd[2180]: Could not fork: Resource temporarily unavailable
Jul 8 16:49:27 hp07 above message repeats 23 times
output of who -b is
reboot system boot Tue Jul 8 16:56
Can any one give the possible reasons and solution to fix this issue.
regards
Sujith
"The most wasted day is that in which we have not laughed."
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 02:43 AM
07-09-2008 02:43 AM
Re: Cluster error
Hi Sujith,
It is discussed many times in the forum. It is normally because of the nproc kernel value.
Please see the thread:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1215600049708+28353475&threadId=686615
There ia another one just today:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1247779
Regards.
It is discussed many times in the forum. It is normally because of the nproc kernel value.
Please see the thread:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1215600049708+28353475&threadId=686615
There ia another one just today:
http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1247779
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2008 03:05 AM
07-09-2008 03:05 AM
Solution
It means you could not run or fork another process. You need to increase your nproc parameter.
A good way to monitor for this parm would be using the 'sar' command. Example to check every 3 seconds for the next 20 times:
sar -v 3 20
The output will show proc-sz; inod-sz; file-sz
The first value is what is being used, the second in each column shows what the current parm is set at. You might monitor throughout day and maybe write a short script and cron it to run around the time your box showed the issue. You may find by watching you can determine what the best parm value should be.
Remember - increasing a parm is not always giving you more. You may find it best to increase one, while reducing another will best tune your box. It takes a good bit of research on the parms, and a good bit of watching and tuning.
Rgrds,
Rita
A good way to monitor for this parm would be using the 'sar' command. Example to check every 3 seconds for the next 20 times:
sar -v 3 20
The output will show proc-sz; inod-sz; file-sz
The first value is what is being used, the second in each column shows what the current parm is set at. You might monitor throughout day and maybe write a short script and cron it to run around the time your box showed the issue. You may find by watching you can determine what the best parm value should be.
Remember - increasing a parm is not always giving you more. You may find it best to increase one, while reducing another will best tune your box. It takes a good bit of research on the parms, and a good bit of watching and tuning.
Rgrds,
Rita
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2008 11:50 PM
08-25-2008 11:50 PM
Re: Cluster error
Thank U
"The most wasted day is that in which we have not laughed."
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP