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

[IDD #RUB-260067]: ldm cluster at A&M is doing some odd things (or perhaps my new client is?)



Hi Gerry,

re:
> I've got a new VM set up for some limited LDM data collection on a VM
> cluster associated with boomer.oscer.ou.edu.

Interesting.

re:
> I'm not seeing anything come
> back from the server when I start LDM on the local VM host and do a
> subsequent 'tail'.

Do you mean 'ldmadmin tail'?

re:
> When I try 'notifyme' I see the following
> 
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/etc/ldmd.conf
> gcreager  8694  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8695  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8696  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8697  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8698  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8699  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8700  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m
> 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> root      8705  1704  0 09:08 ?        00:00:00 sshd: gcreager [priv]
> gcreager  8707  8705  0 09:08 ?        00:00:00 sshd: gcreager@pts/3
> gcreager  8708  8707  0 09:08 pts/3    00:00:00 -bash
> gcreager  9017  8708  2 09:54 pts/3    00:00:00 ps -efw
> gcreager  9018  8708  0 09:54 pts/3    00:00:00 grep gcreager
> root     13117  1704  0 Dec10 ?        00:00:00 sshd: gcreager [priv]
> gcreager 13119 13117  0 Dec10 ?        00:00:00 sshd: gcreager@pts/2
> gcreager 13120 13119  0 Dec10 pts/2    00:00:00 -bash
> gcreager 13676 13120  0 Dec10 pts/2    00:00:00 ssh boomer
> root     13847  1704  0 Dec10 ?        00:00:00 sshd: gcreager [priv]
> gcreager 13849 13847  0 Dec10 ?        00:00:00 sshd: gcreager@pts/1
> gcreager 13850 13849  0 Dec10 pts/1    00:00:00 -bash

This is like no 'notifyme' output that I have ever seen!?  It looks like
the output of 'ps -eaf'. 


re:
> [gcreager@ldm /]$ ps -efw|grep gcreager
> gcreager  8685     1  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8687  8685  0 09:06 ?        00:00:00 pqact -v
> gcreager  8688  8685  0 09:06 ?        00:00:00 rtstats -h
> rtstats.unidata.ucar.edu
> gcreager  8689  8685  0 09:06 ?        00:00:04 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8690  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8691  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8692  8685  0 09:06 ?        00:00:04 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8693  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8694  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8695  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8696  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8697  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8698  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8699  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> gcreager  8700  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq /home/gcreager/et
> c/ldmd.conf
> root      8705  1704  0 09:08 ?        00:00:00 sshd: gcreager [priv]
> gcreager  8707  8705  0 09:08 ?        00:00:00 sshd: gcreager@pts/3
> gcreager  8708  8707  0 09:08 pts/3    00:00:00 -bash
> gcreager  9019  8708  0 09:54 pts/3    00:00:00 ps -efw
> gcreager  9020  8708  0 09:54 pts/3    00:00:00 grep gcreager
> root     13117  1704  0 Dec10 ?        00:00:00 sshd: gcreager [priv]
> gcreager 13119 13117  0 Dec10 ?        00:00:00 sshd: gcreager@pts/2
> gcreager 13120 13119  0 Dec10 pts/2    00:00:00 -bash
> gcreager 13676 13120  0 Dec10 pts/2    00:00:00 ssh boomer
> root     13847  1704  0 Dec10 ?        00:00:00 sshd: gcreager [priv]
> gcreager 13849 13847  0 Dec10 ?        00:00:00 sshd: gcreager@pts/1
> gcreager 13850 13849  0 Dec10 pts/1    00:00:00 -bash
> [gcreager@ldm /]$ ps -efw|grep ldmd
> gcreager  8685     1  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8689  8685  0 09:06 ?        00:00:04 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8690  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8691  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8692  8685  0 09:06 ?        00:00:04 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8693  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8694  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8695  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8696  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8697  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8698  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8699  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  8700  8685  0 09:06 ?        00:00:00 ldmd -I 0.0.0.0 -P 388 -M
> 256 -m 3600 -o 3600 -q /home/gcreager/var/queues/ldm.pq
> /home/gcreager/etc/ldmd.conf
> gcreager  9022  8708  0 09:54 pts/3    00:00:00 grep ldmd

OK, this does look like 'ps -eaf' output.

re:
> [gcreager@ldm /]$ ldmadmin restart ; ldmadmin tail
> Stopping the LDM server...
> Waiting for the LDM server to terminate...
> The product-queue is OK.
> Checking pqact(1) configuration-file(s)...
> /home/gcreager/etc/pqact.conf: syntactically correct
> Checking LDM configuration-file (/home/gcreager/etc/ldmd.conf)...
> Starting the LDM server...
> ^C

OK.

re:
> [gcreager@ldm /]$ cd var/
> [gcreager@ldm var]$ ls
> account  cache  crash  cvs  db  empty  games  lib  local  lock  log
> lost+found  mail  nis  opt  preserve  run  spool  tmp  yp

This looks like a list of /var, not ~ldm/var.

re:
> [gcreager@ldm var]$ cd log
> [gcreager@ldm log]$ ls
> anaconda.ifcfg.log    anaconda.yum.log  conman.old     dmesg
> maillog-20121209   prelink         secure            tallylog
> yum.log
> anaconda.log          audit             ConsoleKit     dmesg.old   mcelog
> rhncfg-actions  secure-20121209   tuned
> anaconda.program.log  boot.log          cron           dracut.log  messages
> rhsm            spooler           up2date
> anaconda.storage.log  btmp              cron-20121209  lastlog
> messages-20121209  sa              spooler-20121209  up2date-20121209
> anaconda.syslog       conman            cups           maillog     ntpstats
> samba           sssd              wtmp

Where were you when these were run?

re:
> [gcreager@ldm log]$ cd
> [gcreager@ldm ~]$ cd var/log
> -bash: cd: var/log: No such file or directory
> [gcreager@ldm ~]$ cd var/logs/
> [gcreager@ldm logs]$ ls
> ldmd.log  netcheck.log

This looks better...

re:
> [gcreager@ldm logs]$ ls -al
> total 16
> drwxr-xr-x. 2 gcreager tamuear 4096 Dec 10 20:47 .
> drwxr-xr-x. 5 gcreager tamuear 4096 Dec 10 19:27 ..
> -rw-r--r--. 1 gcreager tamuear    0 Dec 10 20:47 ldmd.log
> -rw-r--r--. 1 gcreager tamuear 4721 Dec 10 19:46 netcheck.log

Is LDM logging working correctly?  You can answer this by running the
following:

<as the user running the LDM>

cd
ls -alt var/logs/ldmd.log
logger -p local0.debug 'test of LDM logging ...'
ls -alt var/logs/ldmd.log

Did the size of the LDM log file change (is no longer zero)?  If
not, then LDM logging is not setup/working, and the questions are:

- is syslogd being run, or is the system logger daemon something like
  syslog-ng?

- if syslogd is being used, is it correctly configured to log LDM
  stuff?

- if yes, is SELINUX configured to allow LDM logging.  The file
  to check is:

  /etc/selinux/config

  The setting that is needed is:

SELINUX=disabled


> [gcreager@ldm logs]$ less netcheck.log
> [gcreager@ldm logs]$ grep ldmi netcheck.log
> Dec 11 01:46:55 UTC: ldmingest01.nwc.ou.edu
> ping -c 10 -s 64 ldmingest01.nwc.ou.edu:
> --- ldmingest01.nwc.ou.edu ping statistics ---
> traceroute ldmingest01.nwc.ou.edu:
> traceroute to ldmingest01.nwc.ou.edu (129.15.109.251), 30 hops max, 60 byte
> packets
> [gcreager@ldm logs]$ ldmping ldmingest01.nwc.ou.edu
> Dec 11 15:58:41 INFO:      State    Elapsed Port   Remote_Host
> rpc_stat
> Dec 11 15:58:41 INFO: Resolving ldmingest01.nwc.ou.edu to 129.15.109.251
> took 0.001133 seconds
> ^C

What does 'ldmping' return?

re:
> [gcreager@ldm logs]$ notifyme -xvl - -h ldmingest.nwc.ou.edu
> Dec 11 15:59:12 notifyme[9144] NOTE: Starting Up: ldmingest.nwc.ou.edu:
> 20121211155912.449 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:12 notifyme[9144] NOTE: LDM-5 desired product-class:
> 20121211155912.449 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:12 notifyme[9144] INFO: Couldn't resolve "ldmingest.nwc.ou.edu"
> to an Internet address in 0.002721 seconds

NOTE that ldmingest.nwc.ou.edu is not being resolved into an Internet
address!

re:
> Dec 11 15:59:12 notifyme[9144] ERROR: NOTIFYME(ldmingest.nwc.ou.edu): 13:
> ldm_clnt_addr(ldmingest.nwc.ou.edu): no such host is known
> ^CDec 11 15:59:18 notifyme[9144] NOTE: exiting

re:
> [gcreager@ldm logs]$ notifyme -xvl - -h ldmingest01.nwc.ou.edu
> Dec 11 15:59:24 notifyme[9145] NOTE: Starting Up: ldmingest01.nwc.ou.edu:
> 20121211155924.785 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:24 notifyme[9145] NOTE: LDM-5 desired product-class:
> 20121211155924.785 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:24 notifyme[9145] INFO: Resolving ldmingest01.nwc.ou.edu to
> 129.15.109.251 took 0.001344 seconds
> Dec 11 15:59:24 notifyme[9145] ERROR: NOTIFYME(ldmingest01.nwc.ou.edu): 7:
> Access denied by remote server
> ^CDec 11 15:59:30 notifyme[9145] NOTE: exiting

Note that the request is being denied.

re:
> [gcreager@ldm logs]$ notifyme -xvl - -h ldm.tamu.edu
> Dec 11 15:59:42 notifyme[9146] NOTE: Starting Up: ldm.tamu.edu:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:42 notifyme[9146] NOTE: LDM-5 desired product-class:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:42 notifyme[9146] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.001111 seconds
> Dec 11 15:59:42 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 15:59:42 notifyme[9146] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 15:59:42 notifyme[9146] ERROR: Request denied by upstream LDM:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 15:59:42 notifyme[9146] ERROR: Does it overlap with another?
> Dec 11 16:00:07 notifyme[9146] NOTE: LDM-5 desired product-class:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:07 notifyme[9146] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000845 seconds
> Dec 11 16:00:07 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:00:07 notifyme[9146] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:00:07 notifyme[9146] ERROR: Request denied by upstream LDM:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:07 notifyme[9146] ERROR: Does it overlap with another?
> Dec 11 16:00:32 notifyme[9146] NOTE: LDM-5 desired product-class:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:32 notifyme[9146] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000832 seconds
> Dec 11 16:00:32 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:00:32 notifyme[9146] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:00:32 notifyme[9146] ERROR: Request denied by upstream LDM:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:32 notifyme[9146] ERROR: Does it overlap with another?
> Dec 11 16:00:57 notifyme[9146] NOTE: LDM-5 desired product-class:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:57 notifyme[9146] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000697 seconds
> Dec 11 16:00:57 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:00:57 notifyme[9146] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:00:57 notifyme[9146] ERROR: Request denied by upstream LDM:
> 20121211155942.440 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:00:57 notifyme[9146] ERROR: Does it overlap with another?
> ^CDec 11 16:01:05 notifyme[9146] NOTE: exiting

I saw the same sort of thing when trying to REQUEST data from idd.tamu.edu
when setting up a new LDM installation on shu.calu.edu.  To me this is
something weird with the LDM-6.11.x installation on the TAMU cluster
nodes.  A good test would be to roll back the LDM on the TAMU cluster
real server nodes (e.g., to v6.10.1).  I made a comment to Donna that
Steve really needs to get involved in troubleshooting the feed REQUEST
denials by the TAMU cluster.  He just had surgery on his left arm
(elbow area), and his ability to type is not back to normal yet.

re:
> [gcreager@ldm logs]$ ldmadmin stop
> Stopping the LDM server...
> Waiting for the LDM server to terminate...
> [gcreager@ldm logs]$ notifyme -xvl - -h ldm.tamu.edu
> Dec 11 16:01:11 notifyme[9223] NOTE: Starting Up: ldm.tamu.edu:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:01:11 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:01:11 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.001451 seconds
> Dec 11 16:01:11 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:01:11 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:01:11 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:01:11 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:01:36 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:01:36 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000829 seconds
> Dec 11 16:01:36 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:01:36 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:01:36 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:01:36 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:02:01 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:01 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000659 seconds
> Dec 11 16:02:01 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:02:01 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:02:01 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:01 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:02:26 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:26 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000993 seconds
> Dec 11 16:02:26 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:02:26 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:02:26 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:26 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:02:51 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:51 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000801 seconds
> Dec 11 16:02:52 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:02:52 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:02:52 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:02:52 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:03:17 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:03:17 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000785 seconds
> Dec 11 16:03:17 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:03:17 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:03:17 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:03:17 notifyme[9223] ERROR: Does it overlap with another?
> Dec 11 16:03:42 notifyme[9223] NOTE: LDM-5 desired product-class:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:03:42 notifyme[9223] INFO: Resolving ldm.tamu.edu to
> 128.194.76.175 took 0.000777 seconds
> Dec 11 16:03:42 DEBUG: NOTIFYME(ldm.tamu.edu) returns RECLASS
> Dec 11 16:03:42 notifyme[9223] NOTE: NOTIFYME(ldm.tamu.edu): reclass:
> TS_ZERO TS_ZERO {}
> Dec 11 16:03:42 notifyme[9223] ERROR: Request denied by upstream LDM:
> 20121211160111.804 TS_ENDT {{ANY,  ".*"}}
> Dec 11 16:03:42 notifyme[9223] ERROR: Does it overlap with another?

Same sort of thing I saw on shu.calu.edu when I was trying to setup some
non-overlapping feeds from idd.tamu.edu.

re:
> Could we schedule some time to look at its config and operation, please?

We need to get Steve involved.  The short term "solution" is to roll back
to a previous version of the LDM on the idd.tamu.edu cluster real servers.

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: RUB-260067
Department: Support LDM
Priority: Normal
Status: Open