[arm-allstar] Echolink Cannot Find DB entry

Tim Sawyer tisawyer at gmail.com
Mon Mar 25 23:10:19 EDT 2019


Looks like the problem is different than I thought. I'm guessing the DB
lookup messages are normal. I'm thinking something else is wrong.
Troubleshooting that, whatever it is.

On Mon, Mar 25, 2019 at 7:51 PM Tim Sawyer <tisawyer at gmail.com> wrote:

> Anybody know why this is happing?
>
> There are a lot of stations in the DB, but new connects can't be looked
> up.
>
> [Mar 25 19:16:36] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: KD6OQV, IP: <F8><B1><90>v37.75.243. Requesting DB update.
> [Mar 25 19:16:38] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: KD6OQV, IP: . Requesting DB update.
> [Mar 25 19:16:40] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: KD6OQV, IP: 8f<91>v37.75.243. Requesting DB update.
> [Mar 25 19:16:42] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: KD6OQV, IP: <98>f<91>v37.75.243. Requesting DB update.
> [Mar 25 19:16:47] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: KD6OQV, IP: <F8>f<91>v37.75.243. Requesting DB update.
> [Mar 25 19:25:11] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: N6SLD, IP: Xg<91>v90.6.103. Requesting DB update.
> [Mar 25 19:28:35] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: K6GAT, IP: @. Requesting DB update.
> [Mar 25 19:45:22] NOTICE[367] chan_echolink.c: Cannot find DB entry for
> Callsign: WD6AWP, IP: @. Requesting DB update.
>
>
> --
> Tim WD6AWP
>


-- 
Tim WD6AWP


More information about the ARM-allstar mailing list