HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- error messages in syslog.log
Operating System - HP-UX
1831043
Members
3391
Online
110019
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
02-09-2004 07:22 PM
02-09-2004 07:22 PM
hello!
os : hpux 10.20 (2000)
hardware : k250
i was using cobol application server.
suddenly, this system was hung.
the command such as bdf , ls didn't work.
so i rebooted it.
it works well.
but i don't know why.
i think this is not hardware problem.
i just have the following messages.
there is no clue about this problem.
help me please!!!
Feb 8 02:07:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 1 times (see termio(7)).
Feb 8 02:07:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 249 times (see termio(7)).
Feb 8 02:09:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 426 times (see termio(7)).
Feb 8 02:11:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 688 times (see termio(7)).
Feb 8 02:11:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 950 times (see termio(7)).
Feb 8 02:13:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 1212 times (see termio(7)).
Feb 8 03:03:34 sahruga vmunix: WARNING: cblock exhaustion has occurred 1246 times (see termio(7)).
Feb 8 03:35:34 sahruga vmunix: WARNING: cblock exhaustion has occurred 1249 times (see termio(7)).
Feb 8 09:39:35 sahruga vmunix: WARNING: cblock exhaustion has occurred 1254 times (see termio(7)).
Feb 8 10:01:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1260 times (see termio(7)).
Feb 8 10:39:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1264 times (see termio(7)).
Feb 8 12:33:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1268 times (see termio(7)).
Feb 8 13:03:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1286 times (see termio(7)).
Feb 8 13:27:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1287 times (see termio(7)).
Feb 8 13:37:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1288 times (see termio(7)).
Feb 8 13:59:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1289 times (see termio(7)).
Feb 8 14:11:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1290 times (see termio(7)).
Feb 8 14:13:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1293 times (see termio(7)).
Feb 8 14:19:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1296 times (see termio(7)).
Feb 9 09:29:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1524 times (see termio(7)).
Feb 9 10:01:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1525 times (see termio(7)).
Feb 9 10:09:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1783 times (see termio(7)).
Feb 9 18:47:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1784 times (see termio(7)).
Feb 9 20:51:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1786 times (see termio(7)).
Feb 9 21:01:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1788 times (see termio(7)).
Feb 9 21:05:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1854 times (see termio(7)).
Feb 10 00:27:47 sahruga vmunix: WARNING: cblock exhaustion has occurred 1889 times (see termio(7)).
Feb 10 03:41:48 sahruga vmunix: WARNING: cblock exhaustion has occurred 1890 times (see termio(7)).
Feb 10 07:55:49 sahruga vmunix: WARNING: cblock exhaustion has occurred 1892 times (see termio(7)).
Feb 10 08:21:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1896 times (see termio(7)).
Feb 10 08:21:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1909 times (see termio(7)).
Feb 10 08:23:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1957 times (see termio(7)).
Feb 10 08:25:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1958 times (see termio(7)).
Feb 10 08:27:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1972 times (see termio(7)).
Feb 10 08:27:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 2001 times (see termio(7)).
Feb 10 08:31:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 2006 times (see termio(7)).
Feb 10 13:51:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2009 times (see termio(7)).
Feb 10 13:51:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2248 times (see termio(7)).
Feb 10 13:53:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2440 times (see termio(7)).
Feb 10 13:53:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2931 times (see termio(7)).
Feb 10 13:55:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3380 times (see termio(7)).
Feb 10 13:57:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3381 times (see termio(7)).
Feb 10 13:59:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3531 times (see termio(7)).
Feb 10 14:01:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3777 times (see termio(7)).
Feb 10 14:01:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4052 times (see termio(7)).
Feb 10 14:09:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4217 times (see termio(7)).
Feb 10 14:29:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4377 times (see termio(7)).
Feb 10 14:31:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4456 times (see termio(7)).
Feb 10 14:31:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4468 times (see termio(7)).
Feb 10 14:33:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4480 times (see termio(7)).
Feb 10 14:35:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4504 times (see termio(7)).
Feb 10 14:37:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4524 times (see termio(7)).
Feb 10 14:39:19 sahruga vmunix: WARNING: cblock exhaustion has occurred 4530 times (see termio(7)).
Feb 10 14:39:19 sahruga vmunix: WARNING: cblock exhaustion has occurred 4542 times (see termio(7)).
os : hpux 10.20 (2000)
hardware : k250
i was using cobol application server.
suddenly, this system was hung.
the command such as bdf , ls didn't work.
so i rebooted it.
it works well.
but i don't know why.
i think this is not hardware problem.
i just have the following messages.
there is no clue about this problem.
help me please!!!
Feb 8 02:07:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 1 times (see termio(7)).
Feb 8 02:07:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 249 times (see termio(7)).
Feb 8 02:09:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 426 times (see termio(7)).
Feb 8 02:11:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 688 times (see termio(7)).
Feb 8 02:11:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 950 times (see termio(7)).
Feb 8 02:13:33 sahruga vmunix: WARNING: cblock exhaustion has occurred 1212 times (see termio(7)).
Feb 8 03:03:34 sahruga vmunix: WARNING: cblock exhaustion has occurred 1246 times (see termio(7)).
Feb 8 03:35:34 sahruga vmunix: WARNING: cblock exhaustion has occurred 1249 times (see termio(7)).
Feb 8 09:39:35 sahruga vmunix: WARNING: cblock exhaustion has occurred 1254 times (see termio(7)).
Feb 8 10:01:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1260 times (see termio(7)).
Feb 8 10:39:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1264 times (see termio(7)).
Feb 8 12:33:36 sahruga vmunix: WARNING: cblock exhaustion has occurred 1268 times (see termio(7)).
Feb 8 13:03:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1286 times (see termio(7)).
Feb 8 13:27:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1287 times (see termio(7)).
Feb 8 13:37:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1288 times (see termio(7)).
Feb 8 13:59:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1289 times (see termio(7)).
Feb 8 14:11:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1290 times (see termio(7)).
Feb 8 14:13:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1293 times (see termio(7)).
Feb 8 14:19:37 sahruga vmunix: WARNING: cblock exhaustion has occurred 1296 times (see termio(7)).
Feb 9 09:29:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1524 times (see termio(7)).
Feb 9 10:01:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1525 times (see termio(7)).
Feb 9 10:09:43 sahruga vmunix: WARNING: cblock exhaustion has occurred 1783 times (see termio(7)).
Feb 9 18:47:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1784 times (see termio(7)).
Feb 9 20:51:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1786 times (see termio(7)).
Feb 9 21:01:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1788 times (see termio(7)).
Feb 9 21:05:46 sahruga vmunix: WARNING: cblock exhaustion has occurred 1854 times (see termio(7)).
Feb 10 00:27:47 sahruga vmunix: WARNING: cblock exhaustion has occurred 1889 times (see termio(7)).
Feb 10 03:41:48 sahruga vmunix: WARNING: cblock exhaustion has occurred 1890 times (see termio(7)).
Feb 10 07:55:49 sahruga vmunix: WARNING: cblock exhaustion has occurred 1892 times (see termio(7)).
Feb 10 08:21:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1896 times (see termio(7)).
Feb 10 08:21:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1909 times (see termio(7)).
Feb 10 08:23:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1957 times (see termio(7)).
Feb 10 08:25:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1958 times (see termio(7)).
Feb 10 08:27:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 1972 times (see termio(7)).
Feb 10 08:27:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 2001 times (see termio(7)).
Feb 10 08:31:50 sahruga vmunix: WARNING: cblock exhaustion has occurred 2006 times (see termio(7)).
Feb 10 13:51:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2009 times (see termio(7)).
Feb 10 13:51:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2248 times (see termio(7)).
Feb 10 13:53:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2440 times (see termio(7)).
Feb 10 13:53:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 2931 times (see termio(7)).
Feb 10 13:55:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3380 times (see termio(7)).
Feb 10 13:57:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3381 times (see termio(7)).
Feb 10 13:59:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3531 times (see termio(7)).
Feb 10 14:01:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 3777 times (see termio(7)).
Feb 10 14:01:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4052 times (see termio(7)).
Feb 10 14:09:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4217 times (see termio(7)).
Feb 10 14:29:51 sahruga vmunix: WARNING: cblock exhaustion has occurred 4377 times (see termio(7)).
Feb 10 14:31:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4456 times (see termio(7)).
Feb 10 14:31:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4468 times (see termio(7)).
Feb 10 14:33:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4480 times (see termio(7)).
Feb 10 14:35:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4504 times (see termio(7)).
Feb 10 14:37:52 sahruga vmunix: WARNING: cblock exhaustion has occurred 4524 times (see termio(7)).
Feb 10 14:39:19 sahruga vmunix: WARNING: cblock exhaustion has occurred 4530 times (see termio(7)).
Feb 10 14:39:19 sahruga vmunix: WARNING: cblock exhaustion has occurred 4542 times (see termio(7)).
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2004 07:29 PM
02-09-2004 07:29 PM
Solution
This error occurs when the kernel tunable "nclist" is not big enough. When nclist is exhausted, data going throuigh the terminal can be lost. This might be why things appear to have hung.
Increase "nclist" in your kernel.
Increase "nclist" in your kernel.
Never preceed any demonstration with anything more predictive than "watch this"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2004 07:31 PM
02-09-2004 07:31 PM
Re: error messages in syslog.log
Increase nclist
That should resolve teh problem
http://docs.hp.com/hpux/onlinedocs/939/KCParms/KCparam.Nclist.html
That should resolve teh problem
http://docs.hp.com/hpux/onlinedocs/939/KCParms/KCparam.Nclist.html
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