AlertVIZ was replaced by AlertView which I think is included with the
awips/cave folders now. (Might be wrong). Per connection issues, your edex grib
process is not started. Check edex logs.
Sent from my iPhone
> On Jan 5, 2017, at 9:45 AM, Brian Bernard <bbernard@xxxxxxxxxxxx> wrote:
>
> Good morning,
>
>
> I just looked at the the Qpid.log file and noticed hundreds of the following
> lines:
>
>
> "
>
> 2017-01-05 00:00:26,083 INFO [IoReceiver - /10.10.9.21:44292]
> (StatisticsCounter.java:113) - Resetting statistics for counter:
> messages-delivered-1962-7857
> 2017-01-05 00:00:26,084 INFO [IoReceiver - /10.10.9.21:44292]
> (StatisticsCounter.java:113) - Resetting statistics for counter:
> data-delivered-1962-7858
> 2017-01-05 00:00:26,084 INFO [IoReceiver - /10.10.9.21:44292]
> (StatisticsCounter.java:113) - Resetting statistics for counter:
> messages-received-1962-7859
> 2017-01-05 00:00:26,084 INFO [IoReceiver - /10.10.9.21:44292]
> (StatisticsCounter.java:113) - Resetting statistics for counter:
> data-received-1962-7860
> 2017-01-05 00:00:26,538 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:26,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:27,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:28,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:29,071 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:29,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:29,960 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:30,131 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:30,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:31,102 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:31,340 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:31,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:32,336 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:32,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:33,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:34,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:35,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:36,663 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:37,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:38,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:39,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:40,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:41,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:42,380 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:42,381 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:42,382 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:42,383 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:42,383 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:42,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:43,518 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:43,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:44,345 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:44,596 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:44,631 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:45,533 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:45,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:45,769 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:46,546 INFO [IoReceiver - /10.10.9.21:43630]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes.
> 2017-01-05 00:00:46,597 INFO [IoReceiver - /10.10.9.21:43820]
> (TopicExchange.java:248) - Message routing key: edex.alerts No routes.
> 2017-01-05 00:00:46,928 INFO [IoReceiver - /10.10.9.21:43462]
> (TopicExchange.java:248) - Message routing key: edex.alarms.msg No routes."
>
> Now, when I updated AWIPS to 16.2.2 from 16.1.1 Alertvis wouldn't install; I
> remember the error being "awips2/alertvis doesn't exist" or something similar.
>
> Typing "edex status displays the following:
>
> "[edex status]
> postgres :: running :: pid 3682
> pypies :: running :: pid 2980
> qpid :: running :: pid 3034
> EDEXingest :: running :: pid 3353 3533 19163
> EDEXgrib :: not running
> EDEXrequest :: running :: pid 3351 3585 19177
> ldmadmin :: running :: pid 12928 "
>
> Thank you,
>
> Brian Bernard
>
>
> From: Michael James <mjames@xxxxxxxx>
> Sent: January 4, 2017 4:13:21 PM
> To: Keith Latteri
> Cc: Brian Bernard; awips2-users@xxxxxxxxxxxxxxxx
> Subject: Re: [awips2-users] Unable to connect to broker error: In AWIPS 16.2.2
>
> Be sure to check /awips2/qpid/logs/qpid.log for any error messages.
>
> Michael James
> Unidata Program Center
> Boulder, CO
>
>> On Wed, Jan 4, 2017 at 3:03 PM, Keith Latteri <keith@xxxxxxxxxxxxxxxxx>
>> wrote:
>> Brian,
>>
>> Can you make sure the QPID server is running, if not you can do “service
>> qpidd start”. This is a common error for me when qpid isn’t running.
>>
>>
>>> On Jan 4, 2017, at 4:02 PM, Brian Bernard <bbernard@xxxxxxxxxxxx> wrote:
>>>
>>> Hello,
>>>
>>> I recently installed AWIPS II 16.2.2, and in the IngestGrib log file, I'm
>>> getting a number of 'Unable to connect to broker errors'
>>>
>>> The log shows:
>>>
>>> "[Ingest.GribDecode-2] AMQConnection:
>>>
>>> Unable to connect to broker at
>>> tcp://awips2-1-testing:5672?connectdelay='5000'&connecttimeout='5000'&heartbeat='0'&retries='9999'
>>>
>>> ....
>>> Error connecting to broker.
>>> ....
>>> Connection refused... "
>>>
>>> I've enclosed a screen-capture of the /etc/sysconfig/iptables file in case
>>> that is where the problem lays...
>>>
>>> Thank you,
>>>
>>> Brian Bernard
>>> <iptables.png>_______________________________________________
>>> NOTE: All exchanges posted to Unidata maintained email lists are
>>> recorded in the Unidata inquiry tracking system and made publicly
>>> available through the web. Users who post to any of the lists we
>>> maintain are reminded to remove any personal information that they
>>> do not want to be made public.
>>>
>>>
>>> awips2-users mailing list
>>> awips2-users@xxxxxxxxxxxxxxxx
>>> For list information, to unsubscribe, or change your membership options,
>>> visit: http://www.unidata.ucar.edu/mailing_lists/
>>
>>
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> awips2-users mailing list
>> awips2-users@xxxxxxxxxxxxxxxx
>> For list information, to unsubscribe, or change your membership options,
>> visit: http://www.unidata.ucar.edu/mailing_lists/
>>
>
