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

19990929: ADDE performance on Debian Linux (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: 19990929: ADDE performance on Debian Linux (cont.)
  • Date: Wed, 29 Sep 1999 14:35:03 -0600
>From: Mark Tucker <address@hidden>
>Organization: Lyndon State
>Keywords: 199909271950.NAA15960 McIDAS ADDE performance

Mark and mugsters,

Mark Tucker wrote:

>Tom,
>I found another piece to the puzzle on the mcserv performance.  I noticed
>that there are many failures from inetd for starting mcserv.  Here's a
>short sample of the log entries:
>
>Sep 29 13:11:35 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>Sep 29 13:22:01 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>Sep 29 13:32:26 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>Sep 29 13:42:51 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>Sep 29 13:53:12 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>Sep 29 14:03:36 cirrus inetd[1369]: mcserv/tcp server failing (looping),
>service terminated 
>
>Occasionally, I've found performance to be exceptionally slow with only a
>single user in the lab without any unusual load on the network/server.

This is starting to sound like a Linux configuration problem, not a
McIDAS mcserv problem.  Is there a process limit on your machine that
could be causing this?

Tom

>From address@hidden  Thu Oct  7 14:45:29 1999

Hi Tom-

I forgot to talk with you about this while you were here.  I forwarded Mark's 
emails on to Dave Santek and John Benson, and they also feel that this sounds 
like a problem with inetd.  I'll log the email correspondence in the inquiry 
and close it.  If something changes, and Mark's problem looks to be related 
to mcserv, let us know and I'll reopen the inquiry.

Thanks, 
Jay Heinzelman
McIDAS Help Desk
address@hidden