File: outdate-peer.sh

package info (click to toggle)
drbd-utils 9.15.0-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 6,464 kB
  • sloc: ansic: 47,782; xml: 11,374; cpp: 9,765; sh: 4,398; makefile: 1,020; perl: 353
file content (124 lines) | stat: -rwxr-xr-x 3,015 bytes parent folder | download | duplicates (13)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
#!/bin/bash
#
#  outdate-peer.sh
#  This file is part of DRBD by Philipp Reisner and Lars Ellenberg.
#

#
# It is expected that your clustermanager of choice brings its own
# implementation of this ... E.g. Heartbeat's variant should be able
# to use all of Heartbeat's communication pathes, including the
# serial connections.
#

# This script requires, that there is a password less ssh-key for
# root. You should not use such keys on a bigger scale. Only use
# it with the "from" option!
#
# How to setup SSH:
#
# 1. ssh-keygen -t dsa   (as root, on the first machine)
#    no passphrase!
#
# 2. go to the second machine, edit the file .ssh/authorized_keys2
#    Start a line with from="10.9.9.181,10.99.99.1" [content of id_dsa.pub]
#      Put the IPs of you first machine here, also the id_dsa.pub
#      is from the first machine All needs to be in a single line.
#
# 3. ssh from the first machine to the second one, do this for all
#    IP addresses of the second machine. When doing this the first
#    time it asks you if it should ad the fingerprint to the list
#    of known hosts: Say yes here.
#
# 4. Do this a second time for each IP address, now it should not ask
#    any questions...
#
# Repeate this 4 steps for the other direction, BTW, you can not
# copy the file over, since you have two distrinct keys.. and also
# the IP addresses in the from="" part are different.
#

#
# The caller (drbdadm) sets DRBD_RESOURCE and DRBD_PEER for us.
#

TIMEOUT=6

for P in "$@"; do
    if [ "$P" = "on" ]; then
	EXP_HOST_NAME=1
	EXP_PEER_IP=0
	EXP_OWN_IP=0
    else
	if [ "$EXP_PEER_IP" = "1" ]; then
	    PEER_IP="$PEER_IP $P"
	fi;
	if [ "$EXP_OWN_IP" = "1" ]; then
	    OWN_IP="$OWN_IP $P"
	fi;
	if [ "$EXP_HOST_NAME" = "1" ]; then
	    if [ "$P" != `uname -n` ]; then
		EXP_PEER_IP=1
	    else
		EXP_OWN_IP=1
	    fi
	    EXP_HOST_NAME=0
	fi
    fi
done

if [ -z "$PEER_IP" -o -z "$OWN_IP" ]; then
    echo "USAGE: outdate-peer.sh on host1 IP IP ... on host2 IP IP ..."
    exit 10
fi

for IP in $PEER_IP; do
    ssh $IP drbdadm outdate ${DRBD_RESOURCE:-r0} &
    SSH_PID="$SSH_PID $!"
done


SSH_CMDS_RUNNING=1
while [ "$SSH_CMDS_RUNNING" = "1" ] && [ $TIMEOUT -gt 0 ]; do
    sleep 1
    SSH_CMDS_RUNNING=0
    for P in $SSH_PID; do
	if [ -d /proc/$P ]; then SSH_CMDS_RUNNING=1; fi
    done
    TIMEOUT=$(( $TIMEOUT - 1 ))
done

RV=5
for P in $SSH_PID; do
    if [ -d /proc/$P ]; then
	kill $P
	wait $P
    else
	wait $P
	EXIT_CODE=$?

	# exit codes of drbdmeata outdate:
	# 5  -> is inconsistent
	# 0  -> is outdated
	# 17 -> outdate failed because peer is primary.
	# Unfortunately 20 can have other reasons too....

	if [ $EXIT_CODE -eq 5 ]; then RV=3; else
	    if [ $EXIT_CODE -eq 17 ]; then RV=6; else
		if [ $EXIT_CODE -eq 0 ]; then RV=4; else
		    echo "do not know about this exit code"
		fi
	    fi
	fi
    fi
done

# We return to DRBD - kernel driver:
#
# 6 -> peer is primary (and UpToDate)
# 5 -> peer is down / unreachable.
# 4 -> peer is outdated
# 3 -> peer is inconsistent

exit $RV