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

20021115: ldm having issues starting up related to McIDAS-XCD (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: 20021115: ldm having issues starting up related to McIDAS-XCD (cont.)
  • Date: Fri, 15 Nov 2002 14:13:10 -0700
>From: William C Klein <address@hidden>
>Organization: Valparaiso
>Keywords: 200211131551.gADFpqL24688 LDM ldmd.conf xcd_run McIDAS-XCD

Bill,

>From address@hidden Fri Nov 15 13: 21:38 2002

>What is the good word on the rebuild?

re: The build is proceeding normally now.  After it finishes, we'll see if
the newly compiled code works.

After the McIDAS build was done:

<login as 'mcidas'>
cd mcidas2002/src
make clobber
make all

I reinstalled the distribution:

make install.all

and then tested the new executables to see if they still had the shared
memory read problem.  They don't have the problem anymore.

Since the McIDAS executables appear to be OK, I restarted your LDM:

<login as 'ldm'>
cd ~ldm
[ 1 ] > ps -u ldm
   PID TTY      TIME CMD
 25769 pts/2    0:00 tcsh

[ 2 ] > ipcs
IPC status from <running system> as of Fri Nov 15 15:06:52 CST 2002
T         ID      KEY        MODE        OWNER    GROUP
Message Queues:
Shared Memory:
m          0   0x50000d2f --rw-r--r--     root     root
m        101   0          --rw-------      ldm vumcidas
Semaphores:

I deleted the lone ipc:

[ aeolus : ldm : ~ ]                                                            
[ 3 ] > ipcrm -m 101

and then removed the associated .mctmp subdirectory:

[ aeolus : ldm : ~ ]                                                            
[ 4 ] > ls .mctmp
101

[ aeolus : ldm : ~ ]                                                            
[ 5 ] > cd .mctmp
                                                                                
[ aeolus : ldm : ~/.mctmp ]                                                     
[ 6 ] > rm -rf 101


After this cleanup, I restarted your LDM:

[ aeolus : ldm : ~/.mctmp ]                                                     
[ 7 ] > cd
                                                                                
[ aeolus : ldm : ~ ]                                                            
[ 8 ] > ldmadmin start
starting the LDM server...
the LDM server has been started


Your LDM is apparently now working as it was before the reboot a couple
of days ago.

Tom