[OpenAFS] Odd ubik (?) synchronization problem
Russ Allbery
rra@stanford.edu
Mon, 26 Apr 2004 15:38:42 -0700
Russ Allbery <rra@stanford.edu> writes:
> Here's the tcpdump data from the slave around the point at which things
> went south.
Even with five kill -TSTP of the vlserver on the slave, I'm not seeing
anything particularly useful in those logs. The same sort of event looks
like:
Mon Apr 26 15:33:56 2004 recovery running in state 0
Mon Apr 26 15:33:56 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:00 2004 recovery running in state 0
Mon Apr 26 15:34:00 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:03 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:04 2004 recovery running in state 0
Mon Apr 26 15:34:04 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:08 2004 recovery running in state 0
Mon Apr 26 15:34:08 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:08 2004 Received beacon type 1 from host 171.64.7.222
Mon Apr 26 15:34:12 2004 recovery running in state 0
Mon Apr 26 15:34:12 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:13 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:15 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:15 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 recovery running in state 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:16 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:17 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:17 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:17 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:17 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:17 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:18 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:19 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:20 2004 recovery running in state 0
Mon Apr 26 15:34:20 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:20 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:21 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:21 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:21 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:22 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 recovery running in state 0
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 Received beacon type 1 from host 171.64.7.222
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:24 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:25 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:25 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:25 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:26 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:26 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:27 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:27 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:27 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:28 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:28 2004 recovery running in state 0
Mon Apr 26 15:34:28 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:28 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:28 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:29 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:29 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:30 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:30 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:30 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:31 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:31 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:31 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:32 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:32 2004 recovery running in state 0
Mon Apr 26 15:34:32 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:32 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:32 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:33 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:34 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:34 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:34 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:35 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:35 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:36 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:36 2004 recovery running in state 0
Mon Apr 26 15:34:36 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:36 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:36 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:37 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:37 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:38 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:38 2004 Received beacon type 1 from host 171.64.7.222
Mon Apr 26 15:34:40 2004 recovery running in state 0
Mon Apr 26 15:34:40 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:44 2004 recovery running in state 0
Mon Apr 26 15:34:44 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:48 2004 recovery running in state 0
Mon Apr 26 15:34:48 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:52 2004 recovery running in state 0
Mon Apr 26 15:34:52 2004 beacon: amSyncSite is 0
Mon Apr 26 15:34:56 2004 recovery running in state 0
Mon Apr 26 15:34:56 2004 beacon: amSyncSite is 0
Mon Apr 26 15:35:00 2004 recovery running in state 0
Mon Apr 26 15:35:00 2004 beacon: amSyncSite is 0
Mon Apr 26 15:35:01 2004 beacon: amSyncSite is 0
Mon Apr 26 15:35:04 2004 recovery running in state 0
Mon Apr 26 15:35:04 2004 beacon: amSyncSite is 0
Mon Apr 26 15:35:08 2004 recovery running in state 0
Mon Apr 26 15:35:08 2004 beacon: amSyncSite is 0
Mon Apr 26 15:35:08 2004 Received beacon type 1 from host 171.64.7.222
Mon Apr 26 15:35:08 2004 Ubik: Synchronize database with server 171.64.7.222
Mon Apr 26 15:35:10 2004 Ubik: Synchronize database completed
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>