Technical article 104896

"putc - Out of clists (NCLIST = xxxx exceeded); yyyy failures so far".

OpenServer 5.0.0OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

My system is running out of clists even when the NCLIST is set at very high values. Increasing the NCLIST kernel tunable parameter only allows the system to run longer between crashes. In some cases, the kernel seems to lose clists even when idle. For example, it will crash at night with no cron jobs running. The kernel message is:

putc - Out of clists (NCLIST = xxxx exceeded); yyyy failures so far

Solution

This may be caused by a faulty serial device, or cabling problems, resulting in spurious characters being handed to the serial driver.

One possible cause is a "chatty modem."  Chatting can occur if CD
is forced high on the modem, and/or both the non-modem control and
modem control ports of a given tty are enabled in /etc/inittab.

Chatting can be seen by viewing /etc/wtmp with the utility /usr/lib/acct/fwtmp. To do this, type:

# cat /etc/wtmp | /usr/lib/acct/fwtmp | pg

An eight minute duration of chatting looks like this:

LOGIN    Se2A tty2A        13799  8 0000 0001 778541143 Sep  2 14:25:43 1994
getty    Se2A tty2A        13920  5 0000 0000 778541143 Sep  2 14:25:43 1994
LOGIN    Se2A tty2A        13920  6 0000 0000 778541143 Sep  2 14:25:43 1994
LOGIN    Se2A tty2A        13920  8 0000 0001 778541213 Sep  2 14:26:53 1994
getty    Se2A tty2A        14050  5 0000 0000 778541213 Sep  2 14:26:53 1994
LOGIN    Se2A tty2A        14050  6 0000 0000 778541213 Sep  2 14:26:53 1994
LOGIN    Se2A tty2A        14050  8 0000 0001 778541282 Sep  2 14:28:02 1994
getty    Se2A tty2A        14182  5 0000 0000 778541282 Sep  2 14:28:02 1994
LOGIN    Se2A tty2A        14182  6 0000 0000 778541282 Sep  2 14:28:02 1994
LOGIN    Se2A tty2A        14182  8 0000 0001 778541352 Sep  2 14:29:12 1994
getty    Se2A tty2A        14314  5 0000 0000 778541352 Sep  2 14:29:12 1994
LOGIN    Se2A tty2A        14314  6 0000 0000 778541352 Sep  2 14:29:12 1994
LOGIN    Se2A tty2A        14314  8 0000 0001 778541422 Sep  2 14:30:22 1994
getty    Se2A tty2A        14445  5 0000 0000 778541422 Sep  2 14:30:22 1994
LOGIN    Se2A tty2A        14445  6 0000 0000 778541422 Sep  2 14:30:22 1994
LOGIN    Se2A tty2A        14445  8 0000 0001 778541491 Sep  2 14:31:31 1994
getty    Se2A tty2A        14575  5 0000 0000 778541491 Sep  2 14:31:31 1994
LOGIN    Se2A tty2A        14575  6 0000 0000 778541492 Sep  2 14:31:32 1994
LOGIN    Se2A tty2A        14575  8 0000 0001 778541561 Sep  2 14:32:41 1994
getty    Se2A tty2A        14705  5 0000 0000 778541561 Sep  2 14:32:41 1994
LOGIN    Se2A tty2A        14705  6 0000 0000 778541561 Sep  2 14:32:41 1994

Compare the timestamps from /etc/wtmp with the timestamps of the out-of-clists messages in /usr/adm/messages to see if they correlate.

Other possible culprits are:

Uninterruptible Power Supplies connected to serial ports have been implicated in some cases.

Static generated by paper passing through printers into ungrounded paper collectors, has apparently caused the system to use clists and display the putc() error.

Improper serial cabling can cause this problem.  Look for loose
or bent pins.  Try disabling ports that aren't in use.

From the Xinuos technical article database, record 104896. Reproduced with permission. The original is at www.sco.com/ta/104896, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.