[arm-allstar] I haven't seen this echolink error before...

[Mr. Possum (Bill)]

I have something that just started...  Sort of out of the blue...  When I sit in a terminal session, watching the Asterisk CLI I keep getting these messages scrolling across my screen...
[Feb  2 08:05:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org
    -- Received OK from Echolink server naeast.echolink.org
[Feb  2 08:05:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
[Feb  2 08:06:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org
    -- Received OK from Echolink server servers.echolink.org
[Feb  2 08:06:38] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on servers.echolink.org
  == Refreshing DNS lookups.
    -- Received OK from Echolink server naeast.echolink.org
[Feb  2 08:06:58] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on naeast.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
    -- Received OK from Echolink server nawest.echolink.org
[Feb  2 08:07:18] ERROR[475]: chan_echolink.c:2290 do_el_directory: Error in parsing header on nawest.echolink.org
RP1*CLI>

I hadn't noticed this before the last update...  I don't know if it has anything to do with an update...  I just started noticing it because I had an occasion to watch it happening while connected to the node in a terminal session - for hours.

Anyone else see this recently or have this problem?  Or is it just a recent problem with echolink.org?
Thanks,
Bill - N5MBM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20180202/83f7778a/attachment.html>