------- Forwarded MessageHi Mark,>To: Unidata Support <address@hidden>
>From: Mark Tucker <address@hidden>
>Subject: LDM questions
>Organization: UCAR/Unidata
>Keywords: 200008041346.e74DjxT11375I've got a couple of problems with our ldm setup. LDM 5.0.10, solaris 8
X86.All of the error messages go to the console rather than being appendedto
the ldmd.log. Here is my /etc/syslog.conf:-------------- SNIP -------------------------------------------------
*.err;kern.notice;auth.notice;user.none;local0.none /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit;user.none;local0.none
/var/adm/messages*.alert;kern.err;daemon.err operator
*.alert root*.emerg *
# if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice ifdef(`LOGHOST', /var/log/authlog,
@loghost)mail.debug ifdef(`LOGHOST', /var/log/syslog,
@loghost)#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err /dev/sysmsg
user.err /var/adm/messages
user.alert `root, operator'
user.emerg *
)
local0.debug /usr/local/ldm/logs/ldmd.log
In order to not log the messages to the console, try adding something like the following line to syslog.conf:
local0.none /dev/console
Afterwards, be sure to remember to HUP the syslog daemon - maybe that's why these messages aren't also making it into ldmd.log even though you've told it to do so in syslog.conf.
(See the section called "Configuring the Operating System as root" in http://www.unidata.ucar.edu/packages/ldm/ldmPreInstallList.html#s8)
--------- CUT ---------------------------------------------------Also, since moving our ldm to the new version and OS I've not been able to
feed from sunset.meteor.wisc.edu. All of my other feeds have no problems.
I have tried requesting other products from sunset and gotten the
same problem. When I go back to other sources (navier.meteo.psu.edu
or redwood.atmos.albany.edu) for the same feeds I have no problems
at all. Ldmd.log shows the following:-------------- CUT --------------------------------------------------
Aug 04 13:21:29 cirrus sunset[22862]: run_requester: Starting Up:
sunset.meteor.wisc.edu
Aug 04 13:21:29 cirrus pqsurf[22859]: Starting Up (22849)
Aug 04 13:21:29 cirrus pqact[22866]: Starting Up
Aug 04 13:21:29 cirrus redwood[22860]: run_requester: Starting Up:
redwood.atmos.albany.edu
Aug 04 13:21:29 cirrus redwood[22860]: run_requester: 20000804131945.840
TS_ENDT {{HDS, "(
^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
Aug 04 13:21:29 cirrus navier[22861]: run_requester: 20000804132032.412
TS_ENDT {{IDS|DDPLU
S, "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
Aug 04 13:21:29 cirrus striker[22864]: run_requester: Starting Up:
striker.atmos.albany.edu
Aug 04 13:21:29 cirrus sunset[22862]: run_requester: 20000804131701.474
TS_ENDT {{MCIDAS,
"^(GUNRV2.*|LWTOA3.*)"},{SPARE, "^meso"}}
Aug 04 13:21:29 cirrus striker[22864]: run_requester: 20000804131837.336
TS_ENDT {{NLDN, "
.*"}}
Aug 04 13:21:29 cirrus navier[22861]: FEEDME(navier.meteo.psu.edu): OK
Aug 04 13:21:29 cirrus redwood[22860]: FEEDME(redwood.atmos.albany.edu):
OK
Aug 04 13:21:29 cirrus striker[22864]: FEEDME(striker.atmos.albany.edu):
OK
Aug 04 13:21:29 cirrus sunset[22862]: FEEDME(sunset.meteor.wisc.edu):
reclass: 200008041317
01.474 TS_ENDT {{MCIDAS, "^(GUNRV2.*|LWTO
Aug 04 13:21:29 cirrus sunset[22862]: FEEDME(sunset.meteor.wisc.edu): OK
Aug 04 13:21:29 cirrus lightning[22863]: run_requester: 20000804125933.742
TS_ENDT {{DIFAX,
".*"}}
Aug 04 13:21:30 cirrus sunset[22862]: RECLASS: 20000804122130.044 TS_ENDT
{{MCIDAS, "^(GUN
RV2.*|LWTOA3.*)"}}
Aug 04 13:21:30 cirrus pqexpire[22850]: > Recycled 17269.618 kb/hr (
9237.506 prods per h
our)
Aug 04 13:21:30 cirrus sunset[22862]: Connection reset by peer
Aug 04 13:21:30 cirrus sunset[22862]: Disconnect----------------- CUT ------------------------------------------
Here is the request line from my ldmd.conf:
Hmmm, we're not sure what's going on with sunset. I just tried a ldmping - there is no ldm running there currently, although there clearly was at the time this log was produced... Those log entries could be due to a flakey network connection.
----------------- CUT ------------------------------------------
request MCIDAS
"^(GUNRV2.*|LWTOA3.*)"
sunset.meteor.wisc.edu
request SPARE
"^meso"
sunset.meteor.wisc.edu
----------------- CUT ------------------------------------------Before the upgrade I had few problems with this feed. Is there
something I have done to cause this and, if not, is there another
source I can get our MCIDAS & SPARE from?
I suggest you send them some email and ask them what's up. You can get their information from our page: http://www.unidata.ucar.edu/projects/idd/sitelist.html
Related to this, how would I change this request line to pull just the pngGee, timely! Within the past half hour Tom Yoksas sent out a relevant message - did you see it? Here's the important part:
compressed images?
>the ldmd.conf MCIDAS request line for non-leaf node IDD (i.e., relay)
>sites should look like:
>request MCIDAS ".*" upstream_feed_machine_name
>This enables all images to be sent to the relay.
>The request line for IDD leaf nodes can be refined to request only
>PNG compressed imagery:
>request MCIDAS "^pnga2area Q[01]" upstream_feed_machine_name
>Leaf nodes should only change their MCIDAS request lines if they have
>installed and configured their pqact.conf files for pnga2area.
Last question (for now). I noticed that the stats for our server,Great! Thank you!
cirrus.lsc.vsc.edu, are not showing up on the Unidata IDD pages. I've
added the cronjob to run the statistics:35 * * * * bin/ldmadmin dostats
Happy to be of service,
Thanks.Mark Tucker
Information Technology
Lyndon State College
address@hidden
http://apollo.lsc.vsc.edu------- End of Forwarded Message
Anne
-- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************