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

[LDM #TBZ-761980]: memory leak?

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: [LDM #TBZ-761980]: memory leak?
  • Date: Mon, 06 Jun 2011 16:52:41 -0600
Bruce,

> See below for the output you requested:
> 
> [ldm@s15399185 logs]$ ldmadmin config
> 
> hostname:              s15399185.onlinehome-server.com
> os:                    Linux
> release:               2.6.9-023stab052.4-smp

Wow! That's an old version of the operating-system.

> ldmhome:               /usr/local/ldm
> LDM version:           6.9.7
> PATH:
> /usr/local/ldm/bin:/usr/local/ldm/decoders:/usr/local/ldm/util:/usr/local/ldm/bin:/usr/gnu/bin:/usr/bin:/bin
> LDM conf file:         /usr/local/ldm/etc/ldmd.conf
> pqact(1) conf file:    /usr/local/ldm/etc/pqact.conf
> scour(1) conf file:    /usr/local/ldm/etc/scour.conf
> product queue:         /usr/local/ldm/var/queues/ldm.pq
> queue size:            750M bytes
> queue slots:           default
> reconcilliation mode:  increase queue
> pqsurf(1) path:        /usr/local/ldm/var/queues/pqsurf.pq
> pqsurf(1) size:        2M
> IP address:            0.0.0.0
> port:                  388
> PID file:              /usr/local/ldm/ldmd.pid
> Lock file:             /usr/local/ldm/.ldmadmin.lck
> maximum clients:       256
> maximum latency:       3600
> time offset:           3600
> log file:              /usr/local/ldm/var/logs/ldmd.log
> numlogs:               7
> log_rotate:            1
> netstat:               /bin/netstat -A inet -t -n
> top:                   /usr/bin/top -b -n 1
> metrics file:          /usr/local/ldm/var/logs/metrics.txt
> metrics files:         /usr/local/ldm/var/logs/metrics.txt*
> num_metrics:           4
> check time:            1
> delete info files:     0
> ntpdate(1):            /usr/sbin/ntpdate
> ntpdate(1) timeout:    5
> time servers:          ntp.ucsd.edu ntp1.cs.wisc.edu ntppub.tamu.edu
> otc1.psu.edu timeserver.unidata.ucar.edu
> time-offset limit:     10

The rest looks OK.

The memory-usage metric that's accumulated by the "ldmadmin addmetrics" command 
is for total system usage. Can you verify that one or more of the LDM processes 
is actually increasing its memory usage (via the ps(1) command, for example)?

> Bruce

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TBZ-761980
Department: Support LDM
Priority: Normal
Status: Closed