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

[LDM #WIG-568967]: data size/timestamp differences

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: [LDM #WIG-568967]: data size/timestamp differences
  • Date: Thu, 18 Jul 2013 14:57:27 -0600
Steve,

It could be that the two NOAA computers generate slightly different 
data-products. Unfortunately, I can't view the image you attached. Can you tell 
if the files are semanticaly different (rather than simply different sizes)?

> I have parallel linux servers running RHEL5; one at a primary location
> and one at a back-up location.  The 2 machines are set up the same.
> However, I'm seeing a problem in that sometimes the same files do not have
> matching sizes or timestamps.  For example, I am using LDM to download
> the 12km NAM. When I look at today's 12Z run, look at the primary (left)
> vs back-up (right) shown below.  I have 8 other servers and I'm seeing
> other issues like this, but only on the back-up machines.
> 
> So I'm trying to figure out why I am getting incomplete data files on
> the backup machine (right side) I have made sure that the clocks are
> synched between the noaaport server and the weather server.  When I
> check the /var/log/messages files on both machines, I am seeing a lot of
> primary/alternate switches between noaasvrp1 and noaasvrc1, but only on
> the back-up machine.    There are none on the primary machine.  So I'm
> thinking that all of the switching is the root cause of the problem, but
> I'm not sure how to determine that and what to do about it.  Our noaaport
> contact at Planetary Data suggested that it could be network "fluttering"
> at the back-up site or a firewall issue.
> 
> Any thoughts?
> 
> [cid:image003.jpg@01CE83CE.ADCE8EA0]
> 
> 
> Jul 18 17:59:20 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: Switching 
> data-product transfer-mode to primary
> Jul 18 17:59:20 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: LDM-6 
> desired product-class: 20130718165920.360 TS_ENDT {{ANY,  ".*"},{NONE,  
> "SIG=210d2bfb76df77c48ba22cc97c4f92ec"}}
> Jul 18 17:59:25 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: Upstream 
> LDM-6 on noaasvrp1.duke-energy.com is willing to be a primary feeder
> Jul 18 18:00:29 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: Switching 
> data-product transfer-mode to alternate
> Jul 18 18:00:29 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: LDM-6 
> desired product-class: 20130718170029.660 TS_ENDT {{ANY,  ".*"},{NONE,  
> "SIG=bc690d46d7d0f74d7c34cb3d61aee148"}}
> Jul 18 18:00:29 clttvwxp4 noaasvrp1.duke-energy.com[32481] NOTE: Upstream 
> LDM-6 on noaasvrp1.duke-energy.com is willing to be an alternate feeder
> 
> Steve Leyton, CCM | Sr. Meteorologist
> Duke Energy Corporation
> 526 S. Church Street/PO Box 1006 | Charlotte, NC 28201-1006
> Office 704-382-4316 | Cell 704-609-6154 | Fax 704-382-4014
> Email address@hidden<mailto:address@hidden>


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: WIG-568967
Department: Support LDM
Priority: Normal
Status: Closed