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.
On Thu, 16 Sep 1999, Paul Hamer wrote: > Robb, > > >From your man pages on notifyme. > > > > NAME > > notifyme - ldm NOTIFYME example client > > UNIX SYNOPSIS > > notifyme [-x -v] [-l logfile] [-h remote] [-p pattern] [-f > feedtype] [-o offset] [-t timeout] [-T TotalTimeo] > > DESCRIPTION > > This program receives notification messages from the Unidata > Local Data Management system (ldm) and optionally prints the > notification information with timestamps. It calls up with > the LDM server at remote and requests notification of the > arrival data whose identifier matches pattern. As data > arrives at the server, notification is sent to this pro- > gram. > > > The guys here that took you course assured me that we could use this > utility to receive confirmation from the remote host that it had received > the product we had just sent. It does connect to the remote LDM, we > couldn't run this at first because the remote sites firewall wouldn't > accept the host from which we were running notifyme. In the description > above it refers to the "LDM server at remote" what does that mean if > it is not the remote host we were checking? It also says "notification of > the arrival data" not sent, but arrival. I know it was sent by looking > at my end. Paul, I misunderstood what you were saying. Yes if you use the -h flag then you can determine that a particular product was received at a remote host. > > There were no messages in the ldmd.log indicating that the execute > permission was the problem. > For the script problem, I tried it on our LDM and here are the messages: Sep 17 18:44:25 zero.unidata.ucar.edu pqact[17410]: child 25688 exited with status 127 Sep 17 18:44:29 zero.unidata.ucar.edu pqact[17410]: child 25690 exited with status 127 Robb... > And yes, whilst I agree that had the person on the remote site checked > his configuration more carefully we would not have had the problem I still > think that notifyme did not behave as advertised and ldmd.log or pqact.log > should contain a meaningful error message. > > Paul. > > > Robb Kambic wrote: > > > > On Wed, 15 Sep 1999, Unidata Support wrote: > > > > > > > > ------- Forwarded Message > > > > > > >From: Paul Hamer <address@hidden> > > > >Subject: LDM Bug? > > > >Organization: NOAA/FSL > > > >Keywords: 199909152236.QAA19761 LDM > > > > > > > > > I would like to report a possible LDM bug. > > > > > > The configuration used pqact to execute a perl script upon receipt > > > of a certain product. The sending ldm server host was running a > > > notifyme for receipt confirmation. > > > > > Paul, > > > > The notifyme did exactly what it was designed too. Notified you that the > > product was sent. There is no connection to the receiving LDM. > > > > > When the perl script does not have execute permission at the receiving > > > end no confirmation of receipt iss received even though the product > > > is in the target hosts product queue. Further, no indication of > > > a failure to execute the script was found at either end. > > > > There probaby was a message in the ldmd.log file, but not the kind you > > where expecting. If you look at the log file, there would be a line > > stating pqact subprocess exiting with some type of signal. Because the LDM > > forks the processes the name of the subprocess and the text of the error > > messages are lost. The common process of testing pqact entries is to run > > the entry as stated in pqact.conf from the command line as user LDM from > > LDM home. This would of caught the error immediately. > > > > Robb... > > > > > > Obviously having found the problem in this instance we have fixed > > > that config but it would seem that LDM should: > > > > > > 1. Be able to satisfy the notifyme query (if not perhaps give > > > some clue as to why); and > > > > > > 2. pqact should log the failure of a non-executable target script > > > or binary. > > > > > > Thanks, > > > > > > Paul. > > > > > > -- > > > Paul Hamer > > > Email: address@hidden > > > Phone: 303.497.6342 > > > > > > > > > ------- End of Forwarded Message > > > > > > > =============================================================================== > > Robb Kambic Unidata Program Center > > Software Engineer III Univ. Corp for Atmospheric > > Research > > address@hidden WWW: http://www.unidata.ucar.edu/ > > =============================================================================== > > -- > Paul Hamer > Email: address@hidden > Phone: 303.497.6342 > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================