Gentlepeople;
In an attempt to get some discussion going, and getting to the bottom of
this (and since the electronic fingers are pointing at us), I have attempted
to summarize the complaints:
1. UBVM users are not receiving list mail from lists at sites like
AUVM (ALLMUSIC), IUBVM (MLA-L), and USCVM (GAY-LIBN).
2. Users at Marist are not receiving mail for lists not hosted at UBVM,
but for which UBVM is in the distribute path. In addition, those
not using UBVM are OK (according to Harry Williams).
3. LIST mail coming from lists hosted at UBVM are delievering OK (from
Keith Trimmer), like [log in to unmask]
4. An ONONDAGA user reported not receiving mail from the GARDENS list
at UKCC, which does NOT have UBVM in it's distribute path.
In all of the cases above, non-list mail has been reported as working fine.
...and the reported problems that have occured:
1. On 1/19/94, UBVM had a NYNEX circuit problem, and CUNYVMV2 was forced
to dump about 8000 files to tape. I assume these files were reloaded,
and would account for some of the "out-of-order" delivery reports.
2. ALBNYVM1 had a head crash, according to Ben Chi, but I can't remember
the exact date (too quick with PF9 ;-) ).
4. POLYVM-CUNYVMV2 link down since 1/10/94 (according to Glenn Malling),
and has approx. 290 files queued on CUNYVMV2 (I thought I saw 900-
something there last week, during CUNYVMV2-UBVM's problem?).
Here are the paths for nodes that have reported problems. Note that in all
cases, except for UKCC-ONONDAGA, the RSCS paths are identical. In the UKCC-
ONONDAGA path, LISTSERV goes UKCC-UGA-CUNYVMV2-SUNYBING-..., and RSCS goes
UKCC-UGA-CRNLBIT-SUNYBING-... :
tell listserv show path auvm ubvm
tkssteve; T=0.01/0.01 14:08:20
* AUVM -9.6k-> VTBIT -9.6k-> CUNYVMV2 -9.6k-> UBVM (=3.2k)
tell listserv show path iubvm ubvm
tkssteve; T=0.01/0.01 14:10:06
* IUBVM -9.6k-> UICVM -9.6k-> CUNYVMV2 -9.6k-> UBVM (=3.2k)
tell listserv show path arizvm1 ubvm
tkssteve; T=0.01/0.01 14:11:58
* ARIZVM1 -9.6k-> CUNYVMV2 -9.6k-> UBVM (=4.8k)
tell listserv show path polyvm ubvm
tkssteve; T=0.01/0.01 14:12:05
* POLYVM -9.6k-> CUNYVMV2 -9.6k-> UBVM (=4.8k)
tell listserv show path ukcc ubvm
tkssteve; T=0.01/0.02 14:12:21
* UKCC -64k-> UGA -9.6k-> CUNYVMV2 -9.6k-> UBVM (=4.5k)
tell listserv show path ukcc onondaga
tkssteve; T=0.01/0.01 14:12:37
* UKCC -64k-> UGA -9.6k-> CRNLBIT -9.6k-> SUNYBING -64k-> SNYCENVM -9.6k-> SED
* -9.6k-> ONONDAGA (=2.2k)
tell listserv show path uscvm ubvm
tkssteve; T=0.01/0.01 14:13:08
* USCVM -9.6k-> ARIZVM1 -9.6k-> CUNYVMV2 -9.6k-> UBVM (=3.2k)
tell listserv show path uwavm ubvm
tkssteve; T=0.01/0.01 14:13:22
* UWAVM -9.6k-> UCBCMSA -9.6k-> CUNYVMV2 -9.6k-> UBVM (=3.2k)
tell listserv show path marist ubvm
tkssteve; T=0.01/0.01 14:09:45
* MARIST -9.6k-> YALEVM -9.6k-> CUNYVMV2 -9.6k-> UBVM (=3.2k)
I'm not trying to deflect this problem to another site, but the only
common node in all of the above is CUNYVMV2 ;-), and it is directly connected
to a backbone distribute node that has been down for 15 days. And, during
the composition if this mail piece, the queue for POLYVM on CUNYVMV2 has
grown to 526. What is happening to the mail being queued here? If it isn't
isn't going to POLYVM, does CUNYVMV2 have these files on tape? Are they
being purged by some auto-process for being to old? That's a growth rate of
about 200 files in the past hour! If this link has been down as Glenn says,
then files have been lost, or re-routed somehow.
In summary, if anyone can glean any thoughtful insights from the data
above, Jim Gerland and I would love to hear from you (as would a lot of
other interested parties).
Thanks, and please reply to the list, so everyone can keep abreast of the
progress in resolving these problems (that is, assuming you are all getting
this mail).
Steve
([log in to unmask] | [log in to unmask] | (716)645-3564)
|
