HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- proc table full
Operating System - HP-UX
1827458
Members
5305
Online
109965
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
09-24-2000 11:39 PM
09-24-2000 11:39 PM
Hi,
Im getting this message from dmesg;
proc: table is full
But if I do a sar -v 1 1 it says proc-sz is only 214/664. What is happening ?
Im getting this message from dmesg;
proc: table is full
But if I do a sar -v 1 1 it says proc-sz is only 214/664. What is happening ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2000 11:48 PM
09-24-2000 11:48 PM
Re: proc table full
Check what time these messages ocurred to see if theyre recent;
grep full /var/adm/syslog/syslog.log
Now you get a date+timestamp on them. If theyre recent then at the time stated your proc table was full, ie it went over your 664 limit. Now you need to find out why. What jobs are running at that time ? its usually an overnight backup or batch job which causes it. If you need to then run a job at regular intervals doing a sar -v 1 1 command and a ps -elf so list all processes running so if it happens again you can check thru this output to see what all the extra processes were that were running.
If you have Measureware installed and PerfView you could backtrack thru their performance logs and do a drill down by process to see what the processes were that were running.
Im from Palmerston North, New Zealand, but somehow ended up in London...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2000 11:50 PM
09-24-2000 11:50 PM
SolutionYou proc table did fill up at some point.
To fix it increase nproc and rebuild the kernel and reboot.
To see when it last produced this error do an ll /var/adm/msgbuf, the date+timestamp on this file gives you the last time an entry about the proc table being full was added, ie. when your proc table was full.
The whole world is a simple perl script
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP