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.
>From: William C Klein <address@hidden> >Organization: Valparaiso >Keywords: 200211131551.gADFpqL24688 LDM ldmd.conf xcd_run McIDAS-XCD Bill, >Here is part of the ldmd.log from this morning. I tried starting up ldm >and it's not very happy: > >Nov 13 15:40:39 aeolus pqact[8950]: pbuf_flush (4) write: Broken pipe >Nov 13 15:40:39 aeolus pqact[8950]: pipe_dbufput: xcd_runHRS write error >Nov 13 15:40:39 aeolus pqact[8950]: pipe_prodput: trying again >Nov 13 15:40:39 aeolus pqact[8950]: pbuf_flush (4) write: Broken pipe >Nov 13 15:40:39 aeolus pqact[8950]: pipe_dbufput: xcd_runHRS write error >Nov 13 15:40:39 aeolus pqact[8950]: child 9444 exited with status 1 >Nov 13 15:40:39 aeolus pqact[8950]: child 9442 exited with status 1 >Nov 13 15:40:40 aeolus pqact[8950]: child 9446 exited with status 1 >Nov 13 15:40:40 aeolus pqact[8950]: pbuf_flush (4) write: Broken pipe >Nov 13 15:40:40 aeolus pqact[8950]: pipe_dbufput: xcd_runDDS write error >Nov 13 15:40:40 aeolus pqact[8950]: pipe_prodput: trying again >Nov 13 15:40:40 aeolus pqact[8950]: pbuf_flush (4) write: Broken pipe >Nov 13 15:40:40 aeolus pqact[8950]: pipe_dbufput: xcd_runDDS write error >Nov 13 15:40:40 aeolus pqact[8950]: child 9450 exited with status 1 >Nov 13 15:40:40 aeolus pqact[8950]: child 9448 exited with status 1 >Nov 13 15:40:40 aeolus pqact[8950]: pbuf_flush (4) write: Broken pipe >Nov 13 15:40:40 aeolus pqact[8950]: pipe_dbufput: xcd_runHRS write error >Nov 13 15:40:40 aeolus pqact[8950]: pipe_prodput: trying again > >Please advise. All of this is telling us that the LDM is unable to run 'xcd_run' or that some process being to be run from 'xcd_run' is failing. This most likely indicates: o the PATH for the user running the LDM has changed so that the directory containing 'xcd_run' is missing o you tried starting the LDM as a user other than 'ldm' (this can be very bad if the user starting the LDM was 'root'!) o the permissions on 'xcd_run' was somehow changed so that the user running the LDM does not have execute permission o the setting of MCGUI in 'xcd_run' points to a directory that is supposed to contain McIDAS executables, but no longer does o the execute permissions on McIDAS executables got changed so that the user running the LDM can no longer execute run them o the permissions on the directories that XCD decoders want to write to have changes so that the user running the LDM no longer has write permission o there are no inter process communication handles left on the system. This can be tested by running 'ipcs' from the account running the LDM. If you end up with a _long_ list of ipc handles in use, it probably means that McIDAS processes run from the LDM startup have been exiting uncleanly and leaving those handles. If this is the case, you can either reboot, or clean up all of the handles using the 'ipcrm -m' function. Also, if this is the case, you should look in the .mctmp directory for the user running the LDM to see if there are lots of subdirectories there (their names will be ipc handle numbers). If you find these, you should remove all of them after removing the ipc handles and before attempting to restart the LDM Tom