1 The executables are in /moira/bin/ on the moira server, with sources
2 in /mit/moiradev/src/afssync/. Most of the commands are run on the
5 #### Set up a workspace ####
10 #### This is preparation for the resync, to save non-Moira users. ####
11 First, get a recent copy of the prdb, and extract non-Moira entries:
13 /moira/bin/udebug prill -port 7002
14 rcp -px root@prill:/usr/afs/db/prdb.DB0 prdb.old
15 /moira/bin/udebug prill -port 7002
16 If the two udebugs show that the version changed, lather-rinse-repeat.
17 (udebug can be found in /usr/athena/bin; "prill" here and below is some
19 (Also check for "0 of them for write" at the end. It might matter.)
21 /moira/bin/pt_util -x -m -u -g -d prdb.extra -p prdb.old
22 perl /moira/bin/pt_util.pl < prdb.extra > prdb.extra.sort
23 to extract and prepare the personal groups and special user entries in
24 the old prdb for being reincorporated into the new prdb.
26 awk -F\| '$9 == 3 {print $1}' /backup/backup_1/users > /tmp/deactivated
28 and the following perl script:
30 #!/usr/athena/bin/perl -w
32 open(OUT, ">prdb.extra.trimmed");
34 for ( `cat /tmp/deactivated` ) {
41 foreach $L ( `cat prdb.extra.sort` ) {
45 @x = split(/:/,$w[0]);
52 # If we got here, we're either a user, a prefixless
53 # group, or a group member.
56 print OUT $L unless $punt == 1;
62 to remove the personal groups for users who are deactivated
64 awk '/^[^ ][^:]*@/ {printf "KERBEROS:%s\n",$1}' prdb.extra.trimmed \
66 blanche afs-foreign-users -f foreign
67 Get a list of all the @andrew.cmu.edu type (non- athena.mit.edu cell)
68 users, and sync the Moira list afs-foreign-users to this list.
69 Moira then adds those entries to the group system:afs-foreign-users,
70 thus keeping them from being lost in the prdb resync.
71 Sanity checking the diffs before running the blanche command is recommended.
73 awk '/^[^ 0-9][^:@]*$/ {printf "KERBEROS:%s@ATHENA.MIT.EDU\n",$1}' \
74 prdb.extra.trimmed > oddities
75 awk '/^[^ ][0-9.]* .*$/ {printf "KERBEROS:%s\n",$1}' prdb.extra.trimmed\
77 echo "LIST:afs-foreign-users" >> oddities
78 blanche afs-odd-entities -f oddities
79 Do the equivalent of afs-foreign-users for domestic users. We make
80 the afs-foreign-users list a member of the more general afs-odd-entities.
81 Sanity checking the diffs before running the blanche command is recommended.
83 WAIT for the incremental updates from the `blanche` changes to complete.
85 #### Now the actual resync begins. Incremental updates must stop. ####
87 touch /moira/afs/noafs
88 to disable AFS incremental updates during the synchronization. The
89 afs.incr (?) will wait 30 minutes on an incremental update before
90 timing out, so the resync should complete in that time, or list
91 changes in Moira might need to be propagated by hand.
93 /moira/bin/afssync prdb.moira
94 to dump the prdb data that is in Moira (users, groups, and group
95 memberships). This step takes about ten minutes, but can be done
96 concurrently with the next few steps.
98 REPEAT the above commands, thus regenerating prdb.trimmed from a now
99 completely-up-to-date prdb.
101 *** Make sure the "afssync" command has completed ***
103 cp prdb.moira prdb.new
104 /moira/bin/pt_util -w -d prdb.extra.trimmed -p prdb.new \
106 This use of pt_util will presumably log errors about failed user
107 creations and list additions. (To start over, do both the `cp` and
108 `pt_util` again.) You can filter out the "User or group doesn't exist"
109 type of lines that were caused by a user deactivation with something
111 awk -F\| '$9 == 3 {print $1}' /backup/backup_1/users > /tmp/deactivated
112 perl -e 'for(`cat /tmp/deactivated`){ chop; $ex{$_}=1;} \
113 foreach $L (`cat prdb.extra.err`){ $f=0; \
114 @w=split(/[ :]/,$L); for(@w){ $f=1 if $ex{$_}; } \
115 next if $f; print $L; }'
116 Now, back to the resync.
118 The only remaining errors should be errors creating system:foo groups,
119 be cause they already exist. These generally mean that that group has
120 an odd user on it (root instance, IP acl, etc.) and can safely be
124 Error while creating dcctdw:foo: Badly formed name (group prefix doesn't match owner?)
125 are probably an indication that a user with personal groups had a
126 username change (in the past they have also meant that a user with
127 personal groups was deactivated and the uid was re-used (this was
128 becasue we didn't trim the prdb.extra.sort file in the past.))
129 Assuming htese errors are due to a username change, the groups should
130 be renamed, and you should regenerate prdb.extra.trimmed starting with
131 a fresh prdb from prill. (You may want to abort and
132 rm /moira/afs/noafs and try again later.)
134 pts listmax > prdb.listmax
135 foreach i ( <db servers> )
136 rsh $i -l root -x /bin/athena/detach -a # detach packs
137 rsh $i -l root -x rm -f /usr/afs/db/{prdb.new,pre-resync-prdb}
138 rcp -px prdb.new root@${i}:/usr/afs/db/prdb.new
140 foreach i ( <db servers> )
141 bos shutdown $i ptserver -wait
142 bos exec $i "mv /usr/afs/db/prdb.DB0 /usr/afs/db/pre-resync-prdb; rm /usr/afs/db/prdb.DB*; mv /usr/afs/db/prdb.new /usr/afs/db/prdb.DB0"
144 foreach i ( <db servers> )
145 bos restart $i ptserver
148 /moira/bin/udebug prill -port 7002
149 to watch the status of the servers to make sure things are going well,
150 where "prill" is preferred db server (the sync site).
152 Make sure the beacons are working, and that once quorum is established
153 (~90 seconds) that the servers are resynchronizing their notions of
154 the databases and that the "dbcurrent" and "up" fields all become set
155 and the state goes to "1f". Also, if "sdi" isn't running, watch out
156 for large rx packet queues on port 7002 using rxdebug, as the
157 fileservers may get excessively backlogged, and restart servers, if
158 necessary, if the congestion remains excessive.
162 and if the id maxima are lower than the saved ones, reset them
163 appropriately to the saved ones using `pts setmax`.
165 pts ex system:administrators
166 as a good spot check, especially since it has special people.
167 (also spot check one of the personal groups and perhaps, something like
168 the membership of rcmd.reynelda)
171 to remove the lock file and let Moira's afs incrementals continue.
173 The afssync program doesn't deal with null instance KERBEROS
174 members of lists which are groups (example: if LIST zacheiss contains
175 KERBEROS zacheiss@ATHENA.MIT.EDU). To get around this, run:
179 Which will create /var/tmp/sync.out, which contains the pts commands
180 needed to add all the null instance KERBEROS members back to the pts
181 groups they belong in. If it looks sane, run:
185 Any failed additions are probably from lists that contain both USER
186 username and KERBEROS username@ATHENA.MIT.EDU.
190 1. Don't do this when you're tired... There may be no cleanup procedure
191 available, with certain mistakes.
193 2. /moira/afs/noafs is only good for 30 minutes. Keep track of the
194 critical log, and you may have to do some operations by hand when the
195 operation is complete. Also, if requests depend on other requests, they
196 may be processed out of order, and fail, and may need to be done by hand.