[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #BWV-519399]: New Install: LDM tries to start, then dies.

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #BWV-519399]: New Install: LDM tries to start, then dies.
  • Date: Thu, 22 Jan 2015 13:35:05 -0700
Lucas,

> Full Name: Lucas E.
> Email Address: address@hidden
> Organization: Home
> Package Version: 6.12.6
> Operating System: Debian
> Hardware:
> Description of problem:
> 
> I just installed LDM version 6.12.6 on a Debian machine. Actually, I
> already have it running on another similar machine, but this one will
> not work.
> 
> The install went smoothly, and I edited all the configuration files to
> match the other machines (except I had to change 10.0.0.1 to 10.0.0.3).
> I have confirmed data is streaming in on eth1 as well.
> 
> However, here is the log when I start:
> 
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: Starting Up (version: 6.12.6; 
> built: Jan 19 2015 20:51:00)
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: Using local address 0.0.0.0:388
> Jan 19 21:48:07 Machine pqact[23363] NOTE: Starting Up
> Jan 19 21:48:07 Machine pqact[23363] NOTE: Configuration-file 
> "/home/ldm/etc/pqact.conf" has no entries. You should probably not start this 
> program instead.
> Jan 19 21:48:07 Machine pqact[23363] WARN: No such file or directory
> Jan 19 21:48:07 Machine pqact[23363] WARN: stateRead(): Couldn't open 
> "/home/ldm/etc/pqact.conf.state"
> Jan 19 21:48:07 Machine pqact[23363] WARN: Previous-state information doesn't 
> exist.  Continuing...
> Jan 19 21:48:07 Machine rtstats[23364] NOTE: Starting Up (23361)
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23367 terminated by signal 
> 11: noaaportIngester -m 224.0.1.3 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: Killing (SIGTERM) process group
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: Exiting
> Jan 19 21:48:07 Machine pqact[23363] NOTE: Exiting
> Jan 19 21:48:07 Machine rtstats[23364] NOTE: Exiting
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: Terminating process group
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23365 terminated by signal 
> 15: noaaportIngester -m 224.0.1.1 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23366 terminated by signal 
> 15: noaaportIngester -m 224.0.1.2 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23368 terminated by signal 
> 15: noaaportIngester -m 224.0.1.4 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23369 terminated by signal 
> 15: noaaportIngester -m 224.0.1.5 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23370 terminated by signal 
> 15: noaaportIngester -m 224.0.1.6 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23371 terminated by signal 
> 15: noaaportIngester -m 224.0.1.7 -I 10.0.0.3
> Jan 19 21:48:07 Machine ldmd[23361] NOTE: child 23372 terminated by signal 
> 15: pqact etc/pqact.gempak

> You may cancel the ticket, we actually found the problem.  We did not have
> eth1 configured correctly.  Had 10.0.0.1 instead of 10.0.0.3 in this case.
> But I guess it's good to know what that error looks like.

Excellent! Well done!

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: BWV-519399
Department: Support LDM
Priority: Normal
Status: Closed