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

20030529: Problems with LDM 6.0.12: connecting to LDM 5

Christian,

> To: address@hidden
> From: =?ISO-8859-1?Q?Christian_Pag=E9?= <address@hidden>
> Subject: Problems with LDM 6.0.12
> Organization: UQAM

The above message contained the following:

> I get this forever with the new release of LDM 6.0.12. It was ok with 
> 6.0.11. I had to switch back this morning since I didn't receive any 
> GEM data at 00Z.
> 
> LDM 6.0.12:
> May 28 18:15:55 5Q:io dns2[60285671]: Desired product class: 
> 20030528170123.062 TS_ENDT {{GEM,  ".*"}}
> May 28 18:16:20 5Q:io dns2[60285671]: NOTICE: requester6.c:416; 
> ldm_clnt.c:265: nullproc_6 failure to dns2.cmc.ec.gc.ca; 
> ldm_clnt.c:141: Timed out

It appears from the above that host dns2.cmc.ec.gc.ca isn't running an
LDM-5 because the RPC call timed-out rather than indicating a program
version mismatch.

> LDM 6.0.11:
> May 29 13:47:10 5Q:io dns2[61372836]: Desired product class: 
> 20030529124705.031 TS_ENDT {{GEM,  ".*"}}
> May 29 13:47:35 5Q:io dns2[61372836]: acl.c:703: nullproc_6() failure: 
> Timed out
> May 29 13:47:35 5Q:io dns2[61372836]: Connecting to upstream LDM using 
> protocol version 5...
> May 29 13:47:35 5Q:io dns2[61372836]: FEEDME(dns2.cmc.ec.gc.ca): OK

It appears from the above that host dns2.cmc.ec.gc.ca is running an
LDM-5.

This conflicting evidence can be reconciled if the RPC layer on
dns2.cmc.ec.gc.ca is failing to return a program-version mismatch
indication when it should.  I tested the RPC implementations of 8
different operating systems for just this behavior and found no
problems.

Do you know what operating system dns2.cmc.ec.gc.ca is running?  If not,
can you find out?

> Christian Pagé
> address@hidden
> http://meteocentre.com/    http://meteoalerte.com/
> 
> Etudiant au Doctorat en Sciences de l'environnement UQAM
> +1 514 987 3000 ext. 2376

Regards,
Steve Emmerson