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

[LDM #NJD-255826]: ldmadmin problem on startup

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 #NJD-255826]: ldmadmin problem on startup
  • Date: Fri, 09 Aug 2013 10:31:13 -0600
Dan,

> Full Name: Dan Fredette
> Email Address: address@hidden
> Organization: WSI
> Package Version: 6.10.1
> Operating System: Centos 6
> Hardware:
> Description of problem: Hi,
> 
> I came across something today about ldmadmin on startup.  I search in
> the archives and couldn't find anything on it, so I thought I would post
> what I saw.  We run a multi-queue setup and one of my queues ran into
> a problem when it tried to startup.  Here is my log from when it tried:
> 
> 20:15:33  [INFO] ldm_start_and_monitor: Starting LDM, command = ldmadmin 
> start -v
> 20:15:45  The product-queue is OK.
> 20:15:45  Checking pqact(1) configuration-file(s)...
> 20:15:46  ulog: Couldn't connect(2) to UNIX socket "/dev/log": No such file 
> or directory
> 20:15:46  ulog: Couldn't connect(2) to UNIX socket "/dev/log": No such file 
> or directory
> 20:15:46  Checking LDM configuration-file (/home/ldm_sat_raw/etc/ldmd.conf)...
> 20:15:46  Starting the LDM server...
> 20:17:52  start(): Server not started.
> 20:18:08  start(): Server not started.
> 20:18:26  start(): Server not started.
> 20:18:44  start(): Server not started.
> 20:19:03  start(): Server not started.
> 20:19:23  start(): Server not started.
> 20:19:44  start(): Server not started.
> 20:20:06  start(): Server not started.
> 20:20:29  start(): Server not started.
> 20:20:53  start(): Server not started.
> 20:21:18  start(): Server not started.
> 20:21:44  start(): Server not started.
> 20:22:11  start(): Server not started.
> 20:22:39  start(): Server not started.
> 20:23:08  start(): Server not started.
> 20:23:38  start(): Server not started.
> 20:24:09  start(): Server not started.
> 20:24:41  start(): Server not started.
> 20:25:14  start(): Server not started.
> 20:25:48  start(): Server not started.
> 20:26:23  start(): Server not started.
> 20:26:59  start(): Server not started.
> 20:27:36  start(): Server not started.
> 20:28:14  start(): Server not started.
> 20:28:53  start(): Server not started.
> 20:29:33  start(): Server not started.
> 20:30:14  start(): Server not started.
> 
> This "Server not started" continues on until this morning, when I finally
> killed the processes.  Once I did that it restarted fine.  I looked in
> the ldmadmin script and saw that it should break out after 15 tries,
> but it did not appear that's what it did.
> 
> print "Starting the LDM server...\n";
> system("$cmd_line $ldmd_conf > $pid_file");
> if ($?) {
> unlink($pid_file);
> errmsg("start(): Could not start LDM server");
> $status = 1;
> }
> else {
> # Check to make sure the LDM is running
> my($loopcount) = 1;
> while(!isRunning($pid_file, $ip_addr)) {
> if($loopcount > 15) {
> errmsg("start(): ".
> "Server not started.");
> $status = 1;        # failure
> break;
> }
> sleep($loopcount);
> $loopcount++;
> }
> }
> 
> I don't see any other loops that it might be stuck in, in the ldmadmin
> script.  Have you seen anything like this before?

I've never seen this before. Given the code, I don't see how it could happen.

If you start it manually via the command "ldmadmin start", does it work?

I'm very concerned about the error-messages from ulog(3). It appears that 
you're not running the LDM on the system on which it was built. If so, then you 
might encounter other problems.

> Thanks
> Dan

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NJD-255826
Department: Support LDM
Priority: Normal
Status: Closed