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

Re: 20000614: LDM notifyme and ldmadmin

Unidata Support wrote:

> ------- Forwarded Message
>
> >From: Matthew Maschmann <address@hidden>
> >Subject: LDM notifyme and ldmadmin
> >Organization: University of Nevada/Las Vegas
> >Keywords: 200006141351.e5EDpaT15553 LDM ldmadmin hupsyslog
>
> Good morning,
>
> I have a question regarding the notifyme command in LDM.  I am still
> working on getting LDM up and running, and I thought I had everything
> about ready to go.  I ran ldmadmin, and it gave me an odd error.  I next
> tried notifyme to see if it was in good shape.  Now all it does is hang,
> whereas before it worked fine. The notifyme message is as follows:
>
> notifyme -vl - -h "ldmhost.dri.edu" (my input)
> Jun 14 15:40:12 notifyme[2065]: Starting Up: ldmhost.dri.edu: 
> 20000614154012.904 TS_ENDT {{ANY, ".*"}}
> Jun 14 15:40:13 notifyme[2065]: NOTIFYME(ldmhost.dri.edu): OK
>
> Also, here is the message I receive when I run ldmadmin start:
>
> starting the LDM server... hupsyslog: system("/etc/killall -HUP syslogd")
> returns 65280
> (E.G. It didn't work. Check that this program is setuid)
>
> Any information or possible leads would be greatly appreciated.
>
> Thank you,
> Matt Maschmann
>
> ------- End of Forwarded Message

Hi Matt,

There seems to be two separate problems here.  Something seems to be wrong with 
your upstream site.
We're checking that out now and have sent email to them.

The other problem is with your own ldm.  Apparently the signal sent to the 
syslog deamon didn't work.
The ldm's hupsyslog program must be setuid root.  That is, permissions for 
$LDMHOME/bin/hupsyslog should
look like this:
-rwsr-xr-x    1 root     ustaff      24001 Mar 28 15:34 hupsyslog*
This should have happened when you were installing the software and you issued 
the 'make install_setuids'
command.

If that's not the problem, here's something else to try: 'ldmadmin' is simply a 
script that invokes other
programs.  In order to get more information, you can run the command that 
ldmadmin would execute from the
command line.  You can add the -v (for verbose) flag to get more information.  
From your LDMHOME
directory try executing: "bin/rpc.ldmd -vl - etc/ldmd.conf"

You should be able to get your ldm up and running even though data may not be 
flowing to you.  Check
these things out and let us know the result.

Anne
--
***************************************************
Anne Wilson                     UCAR Unidata Program
address@hidden                  P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************