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

[LDM #YVO-673787]: LDM Problem

Geboy,

> Thanks for looking into this.

No worries.

> Here is the output.
> 
> /usr/local/ldm/var/data

Ah ha!

The value of the "pqact/datadir-path" in the LDM registry determines the 
current working directory of the pqact(1) process (i.e., the pqact(1) process 
will set it's current working directory to that pathname). Consequently, the 
pqact process executes in the /usr/local/ldm/var/data directory and you've told 
it to file under data/flightexplorer. That's why the directory 
/usr/local/ldm/var/data/data exists.

Possible solutions include 1) setting the value of that parameter to 
"/usr/local/ldm/var"; or 2) removing the "data/" prefix from all the FILE 
actions in the pqact(1) configuration-file. Just don't do both!

> One quick question
> Can we use telnet like below to make sure the remote LDM is accessible.
> 
> telnet host 388

Yes, indeed. Execute that command on any host you think should be able to reach 
the LDM server. You can hit control-C to exit will no ill effects.

> Is there any other tool that will help us track network issues?

Depends on the network issue. Among the utilities we've used are telnet(1), 
ping(1), traceroute(1), mtr(8), netstat(1).

Most frequently, however, we use the notifyme(1) utility of the LDM package. It 
not only tells you if you can connect, but whether you're allowed, and what 
products you can receive.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YVO-673787
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.