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

20000926: upgrading to the ldm-mcidas pnga2area decoder (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: 20000926: upgrading to the ldm-mcidas pnga2area decoder (cont.)
  • Date: Tue, 26 Sep 2000 12:38:02 -0600
>From: Erick Lorenz <address@hidden>
>Organization: UC Davis
>Keywords: 200009220039.e8M0dBb07890 McIDAS-X 7.60 Linux

Erick,

>Something is wrong with my ldm now.  ATM20 froze up when I tried to mount a
>remote disk.  After I restarted it I found that I cannot completely stop
>the ldm:
>
>[ldm@ATM20 ~]$ ldmadmin stop
>stopping the LDM server...
>LDM server stopped
>
>[ldm@ATM20 ~]$ ldmadmin ps
>    1   794   794   794 ?           -1 S      802   0:00 rpc.ldmd -q
>/usr/local/
>  794   795   794   794 ?           -1 S      802   0:00 pqexpire
>  794   797   794   794 ?           -1 R      802  16:47 pqact
>  794   798   794   794 ?           -1 R      802  16:46 pqbinstats
>  794   800   794   794 ?           -1 R      802  16:45 rpc.ldmd -q
>/usr/local/
>  794   801   794   794 ?           -1 R      802  16:46 rpc.ldmd -q
>/usr/local/
> 1115  1123  1115   989 pts/1     1115 S      802   0:00 sh -c ps ajx |
>grep 794
> 1123  1125  1115   989 pts/1     1115 S      802   0:00 grep 794

rpc.ldmd can take a long time to stop on a Linux system especially when
it is receiving large products (like the images from the Unidata-Wisconsin
datastream).  This has been the topic of discussion on our ldm-users
email list recently.

>[ldm@ATM20 ~]$ ldmadmin start
>starting the LDM server...
>Sep 26 17:50:46 UTC ATM20.ucdavis.edu : start_ldm: There is another server
>running, start aborted
>
>and so on.

You have to wait until all LDM processes have exited before you can start
a new invocation of the LDM.  This means that your 'ps -u ldm' can not
contain reference to any LDM processes.

>I have disabled the init.d/ldm script so that I could start ldm
>by hand but it makes no difference.  I also tried 
>
>       ldmadmin clean
>
>right after a reboot but this behavior does not change.

After a reboot, you should not have _any_ LDM processes running IF
you correctly changed the ldm entry in init.d.  Are you saying that
this is not true?

>When I do get a fresh version running after a reboot I cannot see any
>incoming when I do ldmadmin watch.

This may be due to your clock's time being off.

>In fact ldmadmin watch does not even
>print the usual message about stopping with ^c or ^d.

>Thank you
>Erick Lorenz, UCDavis

Tom