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

Re: 20051012: LDM 6-4-1 instalation problem

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: Re: 20051012: LDM 6-4-1 instalation problem
  • Date: Wed, 12 Oct 2005 13:52:00 -0600
Donna,

> To: <address@hidden>
> cc: "Kliche, Donna V." <address@hidden>
> From: "Kliche, Donna V." <address@hidden>
> Subject: LDM 6-4-1 instalation problem
> Organization: SDSMT
> Keywords: 200510121619.j9CGJ1eX010042 LDM-6.4.1 build

The above message contained the following:

> I installed the new version LDM-6.4.1 on a new linux machine (SUSE). I
> tried starting it following the instructions on the web abd I got this
> output:
> 
> ldm@squall:/> ldmadmin delqueue
> ldm@squall:/> ldmadmin mkqueue
> ldm@squall:/> ldmadmin start
> The product-queue is OK.
> /usr/local/ldm/etc/pqact.conf is syntactically correct
> sh: /etc/killall: No such file or directory
> hupsyslog: system("/etc/killall -HUP syslogd") returns 32512
> (E.G. It didn't work. Check that this program is setuid)
> Starting the LDM server...
> ldm@squall:/> ldmadmin watch
> sh: /usr/local/ldm/bin/pqutil: No such file or directory
> ldm@squall:/>
> 
> Any thoughts on how to fix this problem is appreciated.
> Best regards,
> Donna Kliche

Interesting.  The above occurs because the the configure(1) script
couldn't find the file that contains the process-ID of the syslog(8)
daemon (hence, it configures the LDM system to use the killall(1)
utility, instead).

Do any of the following files exist on your system:

    /etc/syslog.pid
    /var/run/syslog.pid
    /var/run/syslogd.pid
    /var/run/syslogd.pid

If so, what's the output of the command "ls -l" on the file?

If not, then what's the output of the command

    ps -ef | grep syslog

In any case, what's the output of the command

    uname -a

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.