# Echolink issues suddenly appeared...error parsing header?

**URL:** <https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797>\
**Category:** AllStarLink\
**Created:** [August 9, 2021, 12:27am UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797 "2021-08-09T00:27:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![wb0yle](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/ce73a5/32.png) [@wb0yle](https://community.allstarlink.org/u/wb0yle)\
**Post date:** [August 9, 2021, 12:27am UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/1 "2021-08-09T00:27:11Z")

</div>

Well…been working for a while…and then tonight, I got notified that my node was not there…haven’t touched the config in over 6 months, been working ok all along…and then now I get:

[Aug 8 20:21:01] ERROR[32348] chan\_echolink.c: Error in parsing header on [naeast.echolink.org](http://naeast.echolink.org)  
[Aug 8 20:21:21] ERROR[32348] chan\_echolink.c: Error in parsing header on [server3.echolink.org](http://server3.echolink.org)  
[Aug 8 20:21:41] ERROR[32348] chan\_echolink.c: Error in parsing header on [nasouth.echolink.org](http://nasouth.echolink.org)  
[Aug 8 20:22:01] ERROR[32348] chan\_echolink.c: Error in parsing header on [naeast.echolink.org](http://naeast.echolink.org)  
[Aug 8 20:22:21] ERROR[32348] chan\_echolink.c: Error in parsing header on [server3.echolink.org](http://server3.echolink.org)  
[Aug 8 20:22:41] ERROR[32348] chan\_echolink.c: Error in parsing header on [nasouth.echolink.org](http://nasouth.echolink.org)  
[Aug 8 20:23:01] ERROR[32348] chan\_echolink.c: Error in parsing header on [naeast.echolink.org](http://naeast.echolink.org)

Anyone have any insight? The system has been (up to this point…) ok…used every week by a number of folks around the country for a net on Sunday nights…like I said…been working till now, and haven’t touched it since the beginning of the year.

Thoughts? Thanks in advance…

73 de Bryan wb0yle

---

<div class="post-metadata">

**Author:** ![Bob\_Pyke](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bob_pyke/32/1396_2.png) [@Bob\_Pyke](https://community.allstarlink.org/u/Bob_Pyke)\
**Post date:** [August 9, 2021, 4:03pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/2 "2021-08-09T16:03:04Z")

</div>

I don’t see an EchoLink node registered with your call sign. Have you tried rebooting your node?

Thanks,  
Bob  
K6ECM

---

<div class="post-metadata">

**Author:** ![wb0yle](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/ce73a5/32.png) [@wb0yle](https://community.allstarlink.org/u/wb0yle)\
**Post date:** [August 9, 2021, 4:10pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/3 "2021-08-09T16:10:42Z")

</div>

Yup. Tried restarting asterisk…then rebooting node…checked with the cloud provider (Linode) to see if they were blocking any ports suddenly…

---

<div class="post-metadata">

**Author:** ![Bob\_Pyke](https://community.allstarlink.org/user_avatar/community.allstarlink.org/bob_pyke/32/1396_2.png) [@Bob\_Pyke](https://community.allstarlink.org/u/Bob_Pyke)\
**Post date:** [August 9, 2021, 8:39pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/4 "2021-08-09T20:39:32Z")

</div>

Submit a ticket to Echolink. They can tell you what they see in their end.

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [August 9, 2021, 9:08pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/5 "2021-08-09T21:08:41Z")

</div>

Hi Brian… been a while…

I would try to flush out dns on your nat router & isp router/modem  
Then reboot.

---

<div class="post-metadata">

**Author:** ![wb0yle](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/ce73a5/32.png) [@wb0yle](https://community.allstarlink.org/u/wb0yle)\
**Post date:** [August 10, 2021, 7:48pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/6 "2021-08-10T19:48:26Z")

</div>

It’s in a cloud, so, that’s not going to happen. It sees the echo servers (get an OK from \*.echolink.org), but it’s claiming an error parsing headers.

Is the database kept in memory or on disk? If the latter, maybe the local db got hosed? Just spitballing…

Will look deeper, but to be honest, echolink is a tertiary service (if that) on my network.

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [August 11, 2021, 12:45am UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/7 "2021-08-11T00:45:51Z")

</div>

I think you have the right idea about local db corrupt, but I know not where it is.

But, it just looks like a network error. …delete temp files etc.

Why not first start trying to get it to log-in.

---

<div class="post-metadata">

**Author:** ![Keith\_Mitchell](https://community.allstarlink.org/user_avatar/community.allstarlink.org/keith_mitchell/32/2137_2.png) [@Keith\_Mitchell](https://community.allstarlink.org/u/Keith_Mitchell)\
**Post date:** [November 1, 2022, 9:27pm UTC](https://community.allstarlink.org/t/echolink-issues-suddenly-appeared-error-parsing-header/18797/8 "2022-11-01T21:27:23Z")

</div>

I cleared my log files var/log/asterisk/  
it worked
