[CRTech] Christian Radio Tech [MSG 81383]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
RE: CAP Server IPAWS is DOWN
To: 'CRTech' <crtech@crtech.org>
Subject: RE: CAP Server IPAWS is DOWN
From: nathaniel.steele@icloud.com
Date: Tue, 21 Nov 2017 16:23:04 -0600
Content-language: en-us
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1511302988; bh=wWqSU8jI7UdbBzouWypbJ9PO0hSIOgPwYLUuzRAMk7w=; h=From:To:Subject:Date:Message-id:MIME-version:Content-type; b=SeZEe72Wv/yehzxYbRZ0XWy/NEiXUOMn1q3o9HKe7SdvSaM0xI7J40SdgqR0MhF4V 3FEpohFoi72C4otNMMhNJ444UcpHRElFXJEKSfgm6t0XvmpkHZvwcM02hoEq5z+3dy 8hvJ1goUxAGEkO+YpcQcWDKhQwtPCtiTDLysyBCiFSPrjd36xU6xwqtX3o84ost8CQ 9n5HN8RXdEzc+3Bxjr2tO1pQWH8T2VigZAlj9LFymyEJMCE/I4BmKjBJZa4usRC4ju GEqEkeRpuXzBNTF8cSSyX1H6SBTzLMDtIzODBPP/ncsgeWdj8iRlnBkBKd03aefu+v eRAIyhuvdhLPw==
In-reply-to: <4156CF88-128C-469A-9CD0-081D512C23D8@mchambersradio.com>
References: <au037pt0oy21t5wv13vqt3cm.1511268163805@email.android.com> <25426E1C-7D27-4D76-894C-2718D3923311@wrbs.com> <001701d362cc$01665350$0432f9f0$@Faithradio.us> <2dd777c8-0982-459b-ab96-00b2865e82fc@am91.org> <CAC0sCoHAHqLaf-JvhNjE0dkNBwnE781shbjOxECv4=PRHusC2w@mail.gmail.com> <39BDB4B5A083864B9802AFB66985BC07C07683@KSGN-DC.KSGNNET.local> <014101d36301$84ccfca0$8e66f5e0$@Faithradio.us> <39BDB4B5A083864B9802AFB66985BC07C0885E@KSGN-DC.KSGNNET.local> <CAPQBvqr0x2WD0N1=zhyhFP0Z59m-4LhQABhyrJ-of-an0nRGgg@mail.gmail.com> <4156CF88-128C-469A-9CD0-081D512C23D8@mchambersradio.com>
Thread-index: AQIEfbG5XzmdkUT11axMF1Ns57dEYwHwa4wgAcYLGHwCNbxc6gGTaZN2ARSV0jQCYg3W9QLZz6bnAXySXO4B5miUt6Izmqrw

That sounds like an interesting story.

 

You should be able to block senders via your email client.

 

From: Matthew Chambers [mailto:sales@mchambersradio.com]
Sent: Tuesday, November 21, 2017 4:05 PM
To: CRTech <crtech@crtech.org>
Subject: Re: [CRTech] CAP Server IPAWS is DOWN

 

I got a string of those messages from all the ENDECs at my former employer. 

 

Changing the topic only slightly, is there a way to block getting those emails for cases like mine where I really don’t want to know if and when they get their RWTs, RMTs and CAP alerts any longer since I’m no longer employed by them. I would simply call someone at the my former employer’s company and ask about it but I’m only allowed to communicate with their attorney now. 

 

 

Matthew Chambers - Owner

PO BOX 111, Macon, MO 63552

mchambers@mchambersradio.com
sales@mchambersradio.com

www.mchambersradio.com



On Nov 21, 2017, at 3:50 PM, Mark Croom <markc@newmail.kinshipradio.org> wrote:

 

Jon,

 

I saw something similar at one of my stations yesterday. The message said CAP is OK but it was full of those errors.

Looked like a server issue so I didn't fixate on it. My guess is they might have been working on the issue what was generating all these errors and took the server down completely.

 

I did get the IPAWS down message from a few of my sites.

 

Mark

MN

 

On Tue, Nov 21, 2017 at 3:43 PM, Jon Foreman <Jon@ksgn.com> wrote:

Yes. The CAP Status OK is there. I did find this log (below) under Tools-IPAWS

 

Jon Foreman
Chief Engineer/IT Manager
jon@ksgn.com
909-583-2136

Office: 909-583-2150
Fax: 909-583-2170

 

Internal log for the IPAWS poller, times are in UTC

File was last modified 1 hour, 9 minutes ago.

Nov 21 11:52:52 PollForUpdate: wget exited with error 1

Nov 21 11:52:52   11:52:51 ERROR 504: Gateway Time-out.

Nov 21 11:53:32 PollForUpdate: wget exited with error 1

Nov 21 11:53:32   11:53:32 ERROR 500: Internal Server Error.

Nov 21 11:54:12 PollForUpdate: wget exited with error 1

Nov 21 11:54:12   11:54:12 ERROR 500: Internal Server Error.

Nov 21 11:55:00 PollForUpdate: wget exited with error 1

Nov 21 11:55:00   11:55:00 ERROR 504: Gateway Time-out.

Nov 21 11:55:48 PollForUpdate: wget exited with error 1

Nov 21 11:55:48   11:55:48 ERROR 500: Internal Server Error.

Nov 21 11:56:28 PollForUpdate: wget exited with error 1

Nov 21 11:56:28   11:56:28 ERROR 500: Internal Server Error.

Nov 21 11:57:09 PollForUpdate: wget exited with error 1

Nov 21 11:57:09   11:57:09 ERROR 500: Internal Server Error.

Nov 21 11:57:52 PollForUpdate: wget exited with error 1

Nov 21 11:57:52   11:57:52 ERROR 500: Internal Server Error.

Nov 21 11:58:50 PollForUpdate: wget exited with error 1

Nov 21 11:58:50   11:58:50 ERROR 504: Gateway Time-out.

Nov 21 11:59:31 PollForUpdate: wget exited with error 1

Nov 21 11:59:31   11:59:31 ERROR 500: Internal Server Error.

Nov 21 12:00:06 PollForUpdate: wget exited with error 1

Nov 21 12:00:06   12:00:06 ERROR 500: Internal Server Error.

Nov 21 12:01:04 PollForUpdate: wget exited with error 1

Nov 21 12:01:04   12:01:04 ERROR 504: Gateway Time-out.

Nov 21 12:02:01 PollForUpdate: wget exited with error 1

Nov 21 12:02:01   12:02:01 ERROR 504: Gateway Time-out.

Nov 21 12:02:42 PollForUpdate: wget exited with error 1

Nov 21 12:02:42   12:02:42 ERROR 500: Internal Server Error.

Nov 21 12:03:14 PollForUpdate: wget exited with error 1

Nov 21 12:03:14   12:03:14 ERROR 500: Internal Server Error.

Nov 21 12:03:49 PollForUpdate: wget exited with error 1

Nov 21 12:03:49   12:03:49 ERROR 500: Internal Server Error.

Nov 21 12:04:40 PollForUpdate: wget exited with error 1

Nov 21 12:04:40   12:04:40 ERROR 504: Gateway Time-out.

Nov 21 12:05:38 PollForUpdate: wget exited with error 1

Nov 21 12:05:38   12:05:38 ERROR 504: Gateway Time-out.

Nov 21 12:06:35 PollForUpdate: wget exited with error 1

Nov 21 12:06:35   12:06:35 ERROR 504: Gateway Time-out.

Nov 21 12:07:39 PollForUpdate: wget exited with error 1

Nov 21 12:07:39   12:07:39 ERROR 504: Gateway Time-out.

 

 

 

Follow-Ups: Re: CAP Server IPAWS is DOWN
(Matthew Chambers <sales@mchambersradio.com>, 21 Nov 2017 22:26:11 -0000)
Re: CAP Server IPAWS is DOWN
(Tom Bosscher <tom@bosscher.org>, 21 Nov 2017 22:53:02 -0000)
References: Re: CAP Server IPAWS is DOWN
(Mark <mbohnett43@bevcomm.net>, 21 Nov 2017 12:42:57 -0000)
Re: CAP Server IPAWS is DOWN
(Pete Allen <pallen@wrbs.com>, 21 Nov 2017 12:58:46 -0000)
RE: CAP Server IPAWS is DOWN
("Thomas Cottle" <Tom@Faithradio.us>, 21 Nov 2017 13:24:12 -0000)
RE: CAP Server IPAWS is DOWN
(Dan Harder <dan@am91.org>, 21 Nov 2017 13:33:55 -0000)
Re: CAP Server IPAWS is DOWN
(David Benson <wn8mup@gmail.com>, 21 Nov 2017 16:47:36 -0000)
RE: CAP Server IPAWS is DOWN
(Jon Foreman <Jon@ksgn.com>, 21 Nov 2017 17:03:20 -0000)
RE: CAP Server IPAWS is DOWN
("Thomas Cottle" <Tom@Faithradio.us>, 21 Nov 2017 19:47:22 -0000)
RE: CAP Server IPAWS is DOWN
(Jon Foreman <Jon@ksgn.com>, 21 Nov 2017 21:44:07 -0000)
Re: CAP Server IPAWS is DOWN
(Mark Croom <markc@newmail.kinshipradio.org>, 21 Nov 2017 21:50:24 -0000)
Re: CAP Server IPAWS is DOWN
(Matthew Chambers <sales@mchambersradio.com>, 21 Nov 2017 22:05:45 -0000)
Prev by date: Re: CAP Server IPAWS is DOWN
(Matthew Chambers, 21 Nov 2017 22:05:45 -0000)
Next by date: Re: CAP Server IPAWS is DOWN
(Matthew Chambers, 21 Nov 2017 22:26:11 -0000)
Prev by thread: Re: CAP Server IPAWS is DOWN
(Matthew Chambers, 21 Nov 2017 22:05:45 -0000)
Next by thread: Re: CAP Server IPAWS is DOWN
(Matthew Chambers, 21 Nov 2017 22:26:11 -0000)
CRTech.org