Hi folks:
I've got a problem with a list that I'm tech advisor on. It !seems! to boil
down to the outgoing list being trashed...i.e. file is still there, but
suddenly the file is blank. Symptoms include: sudden innability to get a who
list, inability to unsubscribe bad addresses (or it breaks the list), sudden
cessation of list activity (people send in messages & they go nowhere).
Our majordomo site has been up for 11 months now, and we only recently began
seeing this problem (last 3 weeks).. We've had it happen 3 times now. We
haven't changed config variable on this list since August. Our ISP did have
some T1 & DNS problems around the start of the problem, but unsure how that
would be related. We are running Majordomo 1.92.
Anyhow, I've enclosed the sequence that I used to get the error to occur,
and what my ISP contact discovered that majordomo did on reviewing the logs.
Has anyone seen this before? I noticed sporadic references to what looked
like a similar problem back in Feb-Mar '95, but no description of a fix was
included.
Any help appreciated,
Robin
------------------------------------
What caused problem
-------------------------------------
At the start of this sequence, list was up & functioning. I was attempting to
confirm that unsubscribe worked.
>Here is the sequence of stuff I did:
>
>1) Pulled a who list. That worked.
>dtooley was gone (you removed), I was there, pam was there twice, etc.
>
>2)Added a new name (so I had somebody to unsubscribe), peterson@state.or.us ,
>which is not a real address, but is at a real site (should have used a real
address, but typed it in wrong).
>
>3)Got a who list. Address was added. Also got the subscribe, pam got
notification of subscribe, and welcome message went out (I know 'cause it
bounced back to Pam).
>
>4)Unsubscribed peterson@state.or.us. using the approve password. Got the
succeeded message, and Pam got the notification of unsubscribe, but no
notification went out to subscriber (which I believe should occur). This is
the behavior or similiar to the behavior we were seeing when the unsubscribe
was broken. So at this point unsure whether peterson@state.or.us still on
list or not.... so:
>
>5)Went to pull the who list to see if it was still there. No can do. I get
the message back saying: pednet is a private list, and you have to be a
member of the list to get the who list. (All this time peterson@europa.com
has been subscribed.)
>
>6)So, I figure, maybe having two copies of the same name, even with
different servers doesn't work. Never mind that Pam has constintley done
this with pjudd@europa.com and pjudd@atheria.europa.com. So I go and login
as Pam and attempt to pull a who list as her, knowing that it worked on
Friday and that she probably did it yesterday. No can do. She's not allowed
to get the who list either.
>
>The upshot of it all:
>
>At this point: 1)The who is 'broken' again. 2)It's unconfirmed as to
whether unsubscribe worked or not. You should be able to tell by inspecting
the file directly; peterson@state.or.us would be the last entry if the
unsubscribe failed.
>
------------------------------------
ISP's analysis of log files
------------------------------------
>Here's what I get out of your tests (adding what I see on this end):
> 1. You got a who list. No problem.
> 2. You added someone and got another who list. No problem.
> 3. You unsubscribed the person.
>*4. The pednet subscriber list is blanked. The file is still there, so it
> hasn't been deleted. But, in effect, everyone is unsubscribed. This
> happened at exactly 6:59pm Sunday night. About a half an hour before
> you sent me the note about your tests.
> 5. You try to get a who list, noone belongs to the mailing list. Request
fails.
> 6. Same thing when coming in as Pam.
>
>I'm extracting the pednet subscriber list from backup as I write this, it
>should be in place shortly (I'll send you mail, when it's in place).
Follow-Ups:
|
|
