Hi Brian,
The LDM not writing log files tells me that selinux is "enforced", and
would explain qpid not starting correctly. If this is the case, you'll
need to set selinux to permissive or disabled and restart your system.
Michael James
Unidata Program Center
Boulder, CO
On Fri, Oct 17, 2014 at 1:08 PM, Brian Bernard <brian.brianbernard@xxxxxxxxx
> wrote:
> Just an update to my post. I rebooted my system and then checked the
> status with 'edex status' and all was running. But, after a few minutes I
> checked 'edex status' and it shows that QPID is not running.
>
> Brian Bernard
>
> On Fri, Oct 17, 2014 at 2:45 PM, Brian Bernard <
> brian.brianbernard@xxxxxxxxx> wrote:
>
>> Hi all,
>>
>> I seem to have the EDEX server running, though when I typed 'edex
>> status', QPID wasn't running. I then typed 'service qpidd start' and got
>> the message "Starting QPID", then the line below that said "QPID is not
>> running", but when I type 'edex status' I get the following:
>>
>>
>> [edex status]
>> postgres :: running :: pid 3210
>> pypies :: running :: pid 2731
>> qpid :: running :: pid 7137
>> EDEXingest :: running :: pid 3050 3525 7337
>> EDEXgrib :: running :: pid 3115 3527 7347
>> EDEXrequest :: running :: pid 2910 3554 7355
>>
>> So, it appears that EDEX is running but I get no ingest from LDM. I
>> checked the ldmd.log for any errors but it is empty. Does anyone know the
>> names of any other log files I should check for errors? Thanks it would
>> really help.
>>
>> Brian Bernard
>>
>>
>>
>>
>
> _______________________________________________
> 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/
>
>
