I'll delete AWIPS II and reinstall. That'll be easier than trying to fix
these issues.
Brian Bernard
On Mon, Oct 20, 2014 at 10:02 AM, Magnuson.Erik <Magnuson.Erik@xxxxxxxxx>
wrote:
> Brian,
>
> Could the problem be reflected by these messages?
>
> INFO|14-10-17 17:27:48|Exception during startup: java.sql.SQLException:
> Failed to create database '/awips2/qpid/messageStore/edex', see the next
> exception for details.
> INFO|14-10-17 17:27:48|java.sql.SQLException: Failed to create database
> '/awips2/qpid/messageStore/edex', see the next exception for details.
> Is your /awips2/qpid/messageStore & messageStore/edex owned & writable by
> awips:fxalpha?
>
> As to no LDM messages: do ldm messages appear in /var/log/messages instead
> (i.e. check the local0.* line in rsyslog.conf.) Also check that the file on
> that line exists and is owned by ldm. It might be safest to blow away
> /awips2 and re-install from scratch with SELINUX disabled rather than chase
> down each potential error.
>
> --
> Erik
>
> ________________________________
> From: awips2-users-bounces@xxxxxxxxxxxxxxxx [
> awips2-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Brian Bernard [
> brian.brianbernard@xxxxxxxxx]
> Sent: Friday, October 17, 2014 5:32 PM
> To: Michael James
> Cc: awips2-users@xxxxxxxxxxxxxxxx
> Subject: Re: [awips2-users] EDEX LDM ingest problem
>
> I changed SELINUX from enforcing to disabled and restarted the system.
> However, after a few minutes QPID stops. I'm enclosing the QPID log files.
>
> On Fri, Oct 17, 2014 at 3:40 PM, Michael James <mjames@xxxxxxxx<mailto:
> mjames@xxxxxxxx>> wrote:
> 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<mailto: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<mailto: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<mailto:awips2-users@xxxxxxxxxxxxxxxx>
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
>
>
>
> ________________________________
> The information contained in this email message is intended only for the
> use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the intended
> recipient, or otherwise have received this communication in error, please
> notify the sender immediately by email at the above referenced address and
> note that any further dissemination, distribution or copying of this
> communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the electronic
> transmission of information and software to foreign countries and to
> certain foreign nationals. Recipient agrees to abide by these laws and
> their regulations -- including the U.S. Department of Commerce Export
> Administration Regulations and the U.S. Department of State International
> Traffic in Arms Regulations -- and not to transfer, by electronic
> transmission or otherwise, any content derived from this email to either a
> foreign national or a foreign destination in violation of such laws.
>
