[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19991012: atm12 and atm23 in bad shape

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19991012: atm12 and atm23 in bad shape
  • Date: Tue, 12 Oct 1999 21:25:28 -0600
>From: Erick Lorenz (address@hidden) <address@hidden>
>Organization: UC Davis
>Keywords: 199910011836.MAA28054 McIDAS-X DEC OSF/1 4.0F Tcl

Sheri,

I dropped in to check on LDM processing on atm23 and atm12 today and
found two systems in bad shape:

o it appears that atm23 stopped ingesting/decoding imagery from the
  Unidata-Wisconsin datastream early on the 11th.  I can't even ping
  this machine right now.

o syslogd is not running on atm12 (and it should be).  When  I logged onto
  atm12 at the end of the day today, I found a couple hundred instances
  of the McIDAS-XCD routine ingetext.k running.  I was unable to kill
  these processes even though I was using 'kill -9'!

I stopped the LDM on atm12 since the number of wayward ingetext.k processes
appeared to be growing.

It seems likely that both atm12 and atm23 need to be rebooted to clear
up their problems.

Tom Yoksas