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

[IDD #IFM-792517]: moving LDM to a new host server



Hi Svetlin,

re:
> thanks for you help. I checked the settings for the log files and
> I redid everything. I restarted the ldm but still no data.
> 
> >Can we get a login as 'ldm' to fiji and pleiades?
> 
> You asked to get a login on pleiades and fiji. Yes you can, the password for
> pleiades.coastal.edu is xxxxxxxx

Thanks.

> Pleiades can be accessed from you machine, but for fiji.coastal.edu you have
> to login from pleiades using same password.

OK.

> I hope you can help us on this problem.

I just logged in as 'ldm' and see your problem:

1) you setup /etc/syslog.conf to use local8 for LDM logging instead of the
   default local0.

2) you did _not_ change the build of the LDM to use local8 instead of local0.

3) your /etc/syslog.conf entry for local8 has spaces between local8.debug and
   /usr/local/ldm/logs/ldmd.log; local8.none and /dev/console and 
/var/adm/messages

I had hoped that 'ldm' might have sudo privileges, but it doesn't.  Because of 
this
I am unable to make the changes that are needed.

Question:

- do you need to use local8 for LDM logging instead of the default local0?

If the answer is no, then you should modify your /etc/syslog.conf file to use
local0 for LDM logging.  If the answer is yes, then you will need to perform
a special build every time you build the LDM.

Here is the procedure for building the LDM to use local8 for logging (and to not
build in support for large LDM queues like you did when building LDM-6.6.5):

<as 'ldm'>

cd ~ldm/ldm-6.6.5.src
make distclean
./configure --disable-max-size --enable-logging=local8
make
make install
sudo make install_setuids

<as 'root'>

-- edit /etc/syslog.conf to fix the problems with local8 entries:

   - make sure that the whitespace between local8.debug and 
     /usr/local/ldm/logs/ldmd.log is(are) a tab(are tabs)

   - remove ';local8.none' from the line that specifies logging
     to /dev/console (optional)

   - change the space just after local8.none to a tab in the last
     two lines of the file

<as 'ldm'>

-- test logging:

logger -p local8.debug 'test of LDM logging'

If ~ldm/logs/ldmd.log is still empty, you still have an error in either
/etc/syslog.conf or you did not build the LDM to use local8 for logging.

If logging worked, restart your LDM:

ldmadmin restart

After your LDM is running again, monitor the log file to see why you are
not receiving CONDUIT (aka NMC2) data.

I imagine that the problems on fiji are more or less the same as what I
found on pleiades.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: IFM-792517
Department: Support IDD
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.