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

[IDD #AIZ-345619]: LDM: pattern in ldmd.conf and pact.conf no longer works for CONDUIT??

Hi Christian,

re:
> So I rebooted the VM, and it did not fix the problem. I also installed the
> latest LDM 6.3.11, but with the same results...

Rats!

re:
> Do you think firewall configuration could be a cause? It is using iptables.
> Port 388 is open, but maybe other specific rules for fragmented packets or
> similar things could interfere?

If port 388 is open, then I can't imagine what local firewall setting could
be limiting/blocking the receipt of products on a specific LDM feed.

re:
> I also noticed that when doing:
> 
> ldmadmin watch -f CONDUIT
> it takes a few seconds before the ctrl-D message shows...
> while if I do it for HDS it is instantaneous.

I think that is because vkepler is receiving a lot of products
in the HDS feed, so no searching in the queue is needed.

Here is another idea of something to try:

Since autan.sca.uqam.ca is receiving the CONDUIT feed, try REQUESTing
it from vkepler.  I just tried a 'notifyme -vl- -f CONDUIT -h 
autan.sca.uqam.ca',
but it failed because there is no ALLOW in autan's LDM configuration file for
vkepler.

Other than that, I have no idea on how to proceed.  Steve and I will continue
to discuss this situation, so he may come up with some other test(s) to run.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: AIZ-345619
Department: Support IDD
Priority: Normal
Status: Open
===================
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.