[Pdl] Realtime PDL Hub changes - reported problems

[Fee, Jeremy]

Hello,

This email is a follow up with information about problems reported by some
users after yesterday's DNS change.

These problems appear to only affect users who did not take the
precautionary steps recommended in the original announcement:
    https://geohazards.usgs.gov/pipermail/pdl/2017-January/000040.html


1) Users with an old version of Java 1.6, or who did not configure
https.protocols

The java command line arguments to enable TLSv1.2 support require Java 1.6
update 121 or newer.  All versions of Java 1.7 support the command line
arguments, and Java 1.8 does not require any command line arguments.

http://www.oracle.com/technetwork/java/javase/overview-156328.html#R160_121


2) File not found exceptions for URLs ending in ".xml".

The new PDL hubs use a more efficient "bin"ary format instead of the
original "xml" format.  Some clients that still connected using the
hostname "ehppdl1" received notifications for the "xml" format, and the
associated products could no longer be downloaded.

To fix this you can reset your receiver's trackingfile to reprocess any
products that were not already processed within the past 72 hours:
a) stop your PDL client
b) remove the receiver tracking file(s)
this is usually "data/receiver_pdl_tracking.dat",
and can be found in your receiver configuration as a "trackingfile"
property, usually within the [receiver_pdl] configuration section.
c) start your PDL client

After this change you may still see exceptions related to the previous
notifications, however, notifications from the new server will start being
received and processed.


Let us know if you have any problems or questions,


Thanks,

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/pdl/attachments/20170214/e8e60c68/attachment.html>