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.
Stonie, > We have an old box, for legacy reasons, that is still running 6.3.0. > We recently rebooted the box, and when it came back up, LDM would not > come up. > > This same system had been running flawless for about two years. Yes, > I know a person normally reboots more often, but . . . . > > Anyway, the logs are filled with the following snipet. I have never > seen this before (and it's not in the logs prior to the reboot) - so > I'm wondering if you have any ideas. It isn't to say that some file > didn't get changed over the course of two years . . . we did try: > > ldmadmin stop > > ldmadmin delqueue > > ldmadmin mkqueue > > ldmadmin start > > Here is what the logs say - any ideas?: > > May 22 20:00:44 noaaportr ldmping[21924]: SVC_UNAVAIL 0.000788 > 0 localhost RPC: Program not registered > May 22 20:00:44 noaaportr pqcheck[21928]: Starting Up (21702) > May 22 20:00:44 noaaportr pqcheck[21928]: The writer-counter of the > product-queue is 0 > May 22 20:00:44 noaaportr pqcheck[21928]: Exiting > May 22 20:01:05 noaaportr ldmping[22122]: SVC_UNAVAIL 0.000649 > 0 localhost RPC: Program not registered > May 22 20:01:05 noaaportr pqcheck[22126]: Starting Up (22014) > May 22 20:01:05 noaaportr pqcheck[22126]: The writer-counter of the > product-queue is 0 > May 22 20:01:05 noaaportr pqcheck[22126]: Exiting > May 22 20:04:17 noaaportr ldmping[7950]: SVC_UNAVAIL 0.000575 > 0 localhost RPC: Program not registered > May 22 20:04:17 noaaportr pqcheck[7954]: Starting Up (6324) > May 22 20:04:17 noaaportr pqcheck[7954]: The writer-counter of the > product-queue is 0 > May 22 20:04:17 noaaportr pqcheck[7954]: Exiting > May 22 20:06:33 noaaportr ldmping[8490]: SVC_UNAVAIL 0.000570 > 0 localhost RPC: Program not registered > May 22 20:06:44 noaaportr ldmping[8496]: SVC_UNAVAIL 0.000569 > 0 localhost RPC: Program not registered > May 22 20:12:42 noaaportr ldmping[8571]: SVC_UNAVAIL 0.000573 > 0 localhost RPC: Program not registered > May 22 20:12:52 noaaportr ldmping[8579]: SVC_UNAVAIL 0.000554 > 0 localhost RPC: Program not registered > May 22 20:13:03 noaaportr ldmping[8594]: SVC_UNAVAIL 0.000659 > 0 localhost RPC: Program not registered > May 22 20:13:05 noaaportr pqcheck[8598]: Starting Up (8589) > May 22 20:13:05 noaaportr pqcheck[8598]: The writer-counter of the > product-queue is 0 > May 22 20:13:05 noaaportr pqcheck[8598]: Exiting > May 22 20:13:18 noaaportr ldmping[8607]: SVC_UNAVAIL 0.000562 > 0 localhost RPC: Program not registered > May 22 20:19:18 noaaportr ldmping[8670]: SVC_UNAVAIL 0.000549 > 0 localhost RPC: Program not registered > May 22 20:19:18 noaaportr pqcheck[8674]: Starting Up (8665) > May 22 20:19:18 noaaportr pqcheck[8674]: The writer-counter of the > product-queue is 0 > May 22 20:19:18 noaaportr pqcheck[8674]: Exiting > May 22 20:19:54 noaaportr ldmping[8688]: SVC_UNAVAIL 0.000571 > 0 localhost RPC: Program not registered The "ldmadmin start" command is checking to see if the LDM started and deciding that it didn't. If there are no relevant error messages in the LDM log file, then I suggest executing the LDM server manually and using the option "-vl-" to have log messages written to the standard error stream in verbose mode. Regards, Steve Emmerson Ticket Details =================== Ticket ID: JHE-806526 Department: Support LDM Priority: Normal Status: Closed