[IDD #ZAJ-969398]: IDD Data is too old

Hi Elliott,

re:
> This host is directly on that IP: 156.110.246.56:
> 
> [ldm@irads-ingest0 ~]$ ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:50:56:01:01:38
> inet addr:156.110.246.56  Bcast:156.110.247.255  Mask:255.255.254.0
> inet6 addr: fe80::250:56ff:fe01:138/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> RX packets:34818145231 errors:0 dropped:0 overruns:0 frame:0
> TX packets:77245529689 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:45228913153206 (41.1 TiB)  TX bytes:100127864519981 (91.0 TiB)
> 
> lo        Link encap:Local Loopback
> inet addr:127.0.0.1  Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING  MTU:65536  Metric:1
> RX packets:814433 errors:0 dropped:0 overruns:0 frame:0
> TX packets:814433 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3203806806 (2.9 GiB)  TX bytes:3203806806 (2.9 GiB)

OK, thanks.

Follow-up question:

- what is 'hostname' defined as in your LDM registry, ~ldm/etc/registry.xml

re:
> I have switched to idd.meteo.psu.edu, deleted/recreated queues, and am 
> monitoring. It
> appears to be behind from the start.

OK.  Deleting and remaking the LDM queue will result in the most recent hour
of data being sent on all REQUESTs, so indicated latencies being large is no
unexpected.  Let's see what happens when things go to a steadier state.

re:
> I have checked change requests and there were no changes to the campus 
> networks over the
> weekend. My belief is that if this were a network issue (at least local to 
> our campus),
> we would be seeing the same on our L2 feed, but it has looked good the whole 
> time:
> http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD2+irads-ingest0.net.ou.edu

What we didn't know until you sent us the output from 'ifconfig' is if your
machine had multiple interfaces and the routing to/from other upstream feed
sites was different than it is to/from us.  We now know that this is not
the case.

Again "for the files": other sites being fed from the same idd.unidata.ucar.edu
real server backend machine are not experiencing high latencies for the
same feeds as your machine.  This tells us that there is nothing fundamentally
wrong with the particular backend machine or its connection to the network.

Last question:

Is it possible that OU turned on an intrusion detection package like Palo
Alto?  These kinds of packages can be setup to inspect things on a per
connection basis.

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: ZAJ-969398
Department: Support IDD
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.