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

20040525: Questions about MPS300-based NOAAPORT ingest system (cont.)

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: 20040525: Questions about MPS300-based NOAAPORT ingest system (cont.)
  • Date: Tue, 25 May 2004 14:53:03 -0600
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200405251609.i4PG9AtK010175 NOAAPORT IDD

Bob,

I dug up the login information for datoo and have begun looking at the
situation with the MPS300.  I see from repeatedly running:

commstats -s mps300 -S mps

that the fail numbers are, in fact, climbing steadily.  I also see that
the load average on datoo is low, so the problem is most likely not one
of CPU starvation on the ingest side.  I will be getting together with
our system administrator, Mike Schmidt, tomorrow (hopefully) to discuss
the possible causes of the ever increasing fail numbers that commstats
is reporting.

One quick question:  have you reset (power cycled) the MPS300 as part of
your troubleshooting?  If not, it may be a good idea to try shutting
it off for a bit and then turning it back on.

More to come...

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.