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

20040816: ADDE server log file (cont.)

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: 20040816: ADDE server log file (cont.)
  • Date: Mon, 16 Aug 2004 11:55:01 -0600
>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200408161556.i7GFu9aW028940 McIDAS ADDE SERVER.LOG

Gilbert,

re: The best way to check this is:

>> <login as 'mcidas'>
>> cd workdata
>> dmap.k SERVER.LOG
>
>It comes back with:
>
>/home/mcidas/workdata/SERVER.LOG
>
>Last written in 2002!

OK.  I would move this to the ~ldm/logs directory.

>As user "mcidas", I was able to do a "touch MCIDAS.LOG" in /home/ldm/logs
>with no errors, so I dunno why it is still doing this. The message doesn't 
>show what directory or the file it is trying to write to. That would 
>help for a future release (hint hint :-) ).

The procedure I sent above allows you as the user 'mcidas' to find out
which file is to be written.

I moved ~mcidas/workdata/SERVER.LOG to /home/ldm/logs.  I then "taught"
McIDAS to look for all files named SERVER.* in the LDM logs directory:

<as 'mcidas'>
cd workdata
redirect.k ADD SERVER.\* \"/home/ldm/logs

Now, the ADDE server log file is in the ~ldm/logs directory; is being
updated when remote ADDE transactions occur; and can be interrogated
by the McIDAS command ADDEINFO:

<still as 'mcidas'>
cd workdata
addeinfo.k

The last setup step is to have this log file rotated on a regular
basis.  This is done through a crontab entry of the user 'ldm':

# McIDAS ADDE Remote Server Logging
1 0 * * 6 bin/newlog logs/SERVER.LOG 3; chmod 666 logs/SERVER.LOG

Since this crontab entry was already setup, I am at a loss to understand
how/when the McIDAS pointing (REDIRECTion) was either not setup or
was lost.

All is well now.

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.

>From address@hidden  Mon Aug 16 12:39:48 2004

Hi Tom,

re: I am at a loss to understand how/when the McIDAS pointing (REDIRECTion)
was either not setup or

>Yes, I don't understand how it was lost, either. It was working. Hmmm.

re: All is well now.

>As always, Tom...thanks again big time for your help! Take care.

*******************************************************************************
Gilbert Sebenste                                                     ********
(My opinions only!)                                                  ******
Staff Meteorologist, Northern Illinois University                      ****
E-mail: address@hidden                                               ***
web: http://weather.admin.niu.edu                                      **
Work phone: 815-753-5492                                                *
*******************************************************************************