X-Envelope-to: BANYAN-L@VM1.CC.UAKRON.EDU
Newsgroups: bit.listserv.banyan-l
Date:         Tue, 15 Sep 1992 10:18:58 AES
From:         Ian=Brabham%CC%Monash@BANYAN.CC.MONASH.EDU.AU
Subject:      re: StreetTalk woes

Greg Martin,

What was the problem and solution with your comms?

>Early in his testing, he created a group on server 1 which was the same
>as that on server 2.  He never deleted it.  A month later after he got the
>servers talking.  I noticed the ST information from the group on server2
>wasn't available to the rest of the network.  While snooping, I found the
>duplicate group.  I went to server 1 and deleted the duplicate group,
>rebooted server 2 to force an ST broadcast, but still the ST entries for
>server 2 aren't available from anywhere on the network (except server 2),

You have a mild form of the 96 hour StreetTalk flu.  It is exactly
the same as you get when changing server keys or renaming servers ONLY
it is not effecting the ServerName@Servers group (so it's only flu and
not pneumonia, if the group were only a test group then it would only
be a cold;-).

Every server maintains a database of all the StreetTalk groups (including
duplicates) in the network WITH the server key number of the server that
owns that group, a 96 hour timer (reset by a ST blast containing that group)
and other serial and sequence number data.  A ST coldstart blows all this
info away and builds it a fresh (great stuff).

>What must we do to get server 2's St information out to the rest of
>the world?

Simple answer "Wait 96 hours".  Less simple answer "Coldstart all the
other StreetTalks in the network".  Complex answer "Play move ST group
between server 1 and server 2".

>Did I screw up by deleting the duplicate group?

Not very much.  Move ST group does a delete also, but does it offline
so the effect of the change seems to be slightly more assertive.  I
think there must be a subtly different "operator deleted group" message
as opposed to the "administrator deleted group" message between ST's.

>Should I have "moved" the group to tape vs deleting it?

It depends on how desperate you were to make the group active instead of
a duplicate.  There are no guaranntees.

I might have tried the following (no guaranntees this would work).  Given
group2 on server2 is the one you want as the active group with the minimum
unavailabilty and ALL servers except server2 believe server1 is active and
server2 is the duplicate.  If different servers believe different things
then a stack of ST coldstarts is the only fast solution to this problem.

1. Operator down server2.
2. Move group2 to tape.
3. Reboot server2. The "duplicate" group2 on server2 now starts ageing.
4. Operator down server1.
5. Move group1 to tape on server1. (Just to get rid of it offline)
6. Move group2 from tape on server1.  This is cheating, server1 should
   now only report a null change in it's StreetTalk to the network.
7. Reboot server1, the group2 data on server1 should now be the active
   group on all servers in the network including server2.
8. Wait 96 hours for the old duplicate "group2 on server2" to age out of
   all the other ST's.  Mean while run with the live group on server1.
9. Do a normal move group from server1 to server2 to get everything
   where it is wanted at your leisure.

Ian Brabham                 email: ian@banyan.cc.monash.edu.au
Micro Support Group         phone: +61 3 565 4742
Monash University           fax:   +61 3 565 4746
Melbourne Australia

PS I just read Russels answer and it might work also but I think it will
only fix server1 and server2 NOT all the other servers as they each
maintain there own timers and duplicate ST group data.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU