[Support #APQ-450630]: Re: EDEX server

Hi Eric.

The log excerpt you sent shows only INFO messages (which are normal and 
expected) and no ERROR or WARN messages.

-Michael




 
> I was hoping you might be able to assist me. I have reinstalled the Fedex 
> server with the most recent release and while everything is running, I 
> believe I have a networking issue. Do you happen to recognize the error below 
> under  edex log which just repeats.
> 
> much thanks,
> Eric
> 
> 
> edex status:
> 
> [edex status]
> postgres    :: running :: pid 11087
> pypies      :: running :: pid 11166
> qpid        :: running :: pid 11201
> EDEXingest  :: running :: pid 11446 11650 25320 31485
> EDEXgrib    :: running :: pid 11450 11580 31495
> EDEXrequest :: running :: pid 11448 11731 31503
> ldmadmin    :: running :: pid 12282
> 
> 
> edex log:
> 
> INFO  2016-05-04 03:52:00,003 [DefaultQuartzScheduler_Worker-7] 
> JmsPooledConnection: EDEX - Creating connection: 
> com.raytheon.uf.common.jms.JmsPooledConnection@64f797e6
> INFO  2016-05-04 03:52:00,012 [IoReceiver - 
> localhost.localdomain/127.0.0.1:5672] ClientDelegate: Heartbeat interval is 0 
> sec. Heartbeats are disabled .
> INFO  2016-05-04 03:52:00,013 [DefaultQuartzScheduler_Worker-7] 
> AMQConnection: Connection 3304 now connected from /127.0.0.1:41125 to 
> localhost.localdomain/127.0.0.1:5672
> INFO  2016-05-04 03:52:00,015 [DefaultQuartzScheduler_Worker-7] 
> JmsPooledProducer: EDEX - Creating AMQ producer scheduledQCScanWork
> INFO  2016-05-04 03:52:45,505 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledConnection: EDEX - Closing 
> connection: com.raytheon.uf.common.jms.JmsPooledConnection@2bc9d1fa
> INFO  2016-05-04 03:52:45,509 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledSession: EDEX - Closing session: 
> com.raytheon.uf.common.jms.JmsPooledSession@3777b23c
> INFO  2016-05-04 03:52:45,509 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledProducer: EDEX - Closing AMQ 
> producer scheduledSoundingWork
> INFO  2016-05-04 03:52:45,517 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledConnectionFactory: EDEX - Closed 
> unused jms pooled resources: connections closed: 1, other resources closed: 
> 0, total time 12
> INFO  2016-05-04 03:53:45,551 [Camel (edexStats-camel) thread #14 - 
> timer://scanStats] AggregateManager: EDEX - Aggregated 0 stat events in 9 ms
> INFO  2016-05-04 03:54:45,504 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledConnection: EDEX - Closing 
> connection: com.raytheon.uf.common.jms.JmsPooledConnection@64f797e6
> INFO  2016-05-04 03:54:45,508 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledSession: EDEX - Closing session: 
> com.raytheon.uf.common.jms.JmsPooledSession@1d32e626
> INFO  2016-05-04 03:54:45,508 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledProducer: EDEX - Closing AMQ 
> producer scheduledQCScanWork
> INFO  2016-05-04 03:54:45,517 [Camel (camel) thread #4 - 
> timer://jmsPooledResourceCheck] JmsPooledConnectionFactory: EDEX - Closed 
> unused jms pooled resources: connections closed: 1, other resources closed: 
> 0, total time 13
> INFO  2016-05-04 03:55:45,551 [Camel (edexStats-camel) thread #14 - 
> timer://scanStats] AggregateManager: EDEX - Aggregated 0 stat events in 9 ms
> INFO  2016-05-04 03:57:00,003 [DefaultQuartzScheduler_Worker-6] 
> CurrentTimeClusterLockHandler: EDEX - Overriding lock for cluster task 
> [ClusteredQuartz/clusteredquartz://qc/scanQC/?cron=0+2%2C7%2C12%2C17%2C22%2C27%2C32%2C37%2C42%2C47%2C52%2C57+*+*+*+%3F]
>  time out [149999] exceeded by 150002 ms.
> 
> 
> 
> > On Apr 27, 2016, at 1:36 PM, erc96672 <address@hidden> wrote:
> >
> > Thanks so much for the reply and I too am sorry for the delay in responding 
> > as I was at the AMS tropical conference last week. Turns out that when I 
> > was away, the IP address of our server was changed and so modifications 
> > were made. Unfortunately the modifications led to EDEXingest failing. I am 
> > going to do a fresh install with the latest release and if that works I 
> > will update the CAVE clients. If i have difficulties, I suspect you will be 
> > hearing from me again, and I will utilize your suggestions from the 
> > previous email.
> >
> > thanks,
> > Eric
> >
> >
> >> On Apr 14, 2016, at 10:00 AM, Unidata AWIPS Support <address@hidden> wrote:
> >>
> >>> To whom it may concern,
> >>>
> >>> Below is an email from out IT staff on our localization problems 
> >>> connecting CAVE clients to our EDEX server. We have installed the most 
> >>> recent version of EDEX, 15.1.3.
> >>>
> >>> Any help would be greatly appreciated,
> >>> Eric Rappin
> >>>
> >>>> On Mar 31, 2016, at 1:52 PM, Quilligan, Andrew <address@hidden> wrote:
> >>>>
> >>>> We are successfully downloading data via the ldm and data is being 
> >>>> stored properly in the /awips2/data_store. The data products are not 
> >>>> showing up in cave clients that connect to the EDEX server. The 
> >>>> edex_static/base/distribution/ XML files look right. The only errors we 
> >>>> have uncovered from log files (EDEX/LDM/PYPIES/CAMEL) was occasional 
> >>>> thread failures due to a lack of allocated ram (The machine had 50G+ of 
> >>>> free ram). Changes were made to several JAVA calls in startup scripts 
> >>>> and these issues went away.
> >>
> >> Hi Eric,
> >>
> >> First, let me apologize for not replying to you sooner, Unidata is having 
> >> some problems with our support system where I am not being notified of 
> >> some incoming messages, so I didn't see this until today.
> >>
> >> To answer your question, I would first check for "successfully ingested" 
> >> messages scrolling by in the edex logs (you can check with "edex log", 
> >> "edex log grib", "edex log radar", etc.).
> >>
> >> Secondly, do a listing of /awips2/edex/data/hdf5/ and you will see the 
> >> data directories which are available.  You should see directories such as 
> >> radar, grid, satellite, obs, etc.  If you do NOT see these directories, 
> >> then there is a problem with the decoding of the data from 
> >> /awips2/data_store/.  If this is the case, there will probably be a lot of 
> >> error messages in the /awips2/edex/log files, which can be investigated 
> >> for hints as to what is not working.  If these files are not too large, 
> >> please send them back so I can look at them.
> >>
> >>
> >>
> >>
> >> Ticket Details
> >> ===================
> >> Ticket ID: APQ-450630
> >> Department: Support AWIPS
> >> Priority: High
> >> Status: Open
> >>
> >
> 
> 

Ticket Details
===================
Ticket ID: APQ-450630
Department: Support AWIPS
Priority: Urgent
Status: Open