-
Notifications
You must be signed in to change notification settings - Fork 1
/
scheduler_cron.sh
179 lines (155 loc) · 5.34 KB
/
scheduler_cron.sh
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
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
#!/bin/bash
# Generate an error if any variable doesn't exist
set -o nounset
delete_lock() {
LOCKDIR=$1
rm -rf "${LOCKDIR}"
if [ $? -ne 0 ]; then
echo "Could not remove lock dir '${LOCKDIR}'. (Check permissions...)"; >&2
exit 1;
fi
}
# @see http://wiki.bash-hackers.org/howto/mutex
acquire_lock () {
LOCKDIR=$1
PIDFILE="${LOCKDIR}/PID"
#echo "Trying to acquire lock '${LOCKDIR}'."
if mkdir "${LOCKDIR}" &>/dev/null; then
#echo "Successfully created '${LOCKDIR}'. Lock acquired"
# lock succeeded
trap 'delete_lock "${LOCKDIR}"; exit $?' INT TERM EXIT
echo "$$" >"${PIDFILE}"
else
#echo "Failed creating ${LOCKDIR}."
if [ ! -f "${PIDFILE}" ]; then
# no PID file found. This could be
# a) because you just updated from a previous version that didn't write a PID file, but a process is legitimetly running
# b) because you just updated from a previous version that didn't write a PID file and there's an abandoned lock
# c) because you hit the exact time between another process creating the dir and writing the PID file
# let's wait for a while to acount for c) and see if the file shows up
# and this also solves the problem of any old abandoned lock in b)
# only problem here is that there's a minimal chance of having two concurrent processes right after updating in case
# a new process expecting a PID file overlaps with an old process that didn't write a PID file
sleep 5
# if there's still no PID file we grab the process
if [ ! -f "${PIDFILE}" ]; then
#echo "No PID file found. Claiming lock now"
delete_lock "${LOCKDIR}"
# now try acquire new lock recursively...
#echo "Now acquiring new lock"
acquire_lock $LOCKDIR;
return
fi
fi
# lock failed, check if the other PID is alive
OTHERPID="$(cat "${PIDFILE}")"
# if cat isn't able to read the file, another instance is probably about to remove the lock -- exit, we're *still* locked
if [ $? != 0 ]; then
#echo "lock failed, PID ${OTHERPID} is active" >&2
exit 1;
fi
# check is the other process is still alive
if ! kill -0 $OTHERPID &>/dev/null; then
# lock is stale, remove it and restart
#echo "removing stale lock of nonexistant PID ${OTHERPID}" >&2
delete_lock "${LOCKDIR}"
# now try acquire new lock recursively...
acquire_lock $LOCKDIR;
else
# lock is valid and OTHERPID is active - exit, we're locked!
#echo "Other process is alive. Still locked"
exit 1
fi
fi
}
# Location of the php binary
PHP_BIN=$(which php || true)
if [ -z "${PHP_BIN}" ]; then
echo "Could not find a binary for php" 1>&2
exit 1
fi
# Location of the md5sum binary
MD5SUM_BIN=$(which md5sum || true)
if [ -z "${MD5SUM_BIN}" ]; then
echo "Could not find a binary for md5sum" 1>&2
exit 1
fi
# Absolute path to Magento installation shell scripts
DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")/shell" && pwd)
if [[ -z "${DIR}" || ! -d "${DIR}" ]]; then
echo "Could not resolve base shell directory" 1>&2
exit 1
fi
# The scheduler.php script
SCHEDULER="scheduler.php"
if [[ ! -e "${DIR}/${SCHEDULER}" || ! -r "${DIR}/${SCHEDULER}" ]]; then
echo "Could not find scheduler.php script" 1>&2
exit 1
fi
# Defaults
MODE="default"
INCLUDE_GROUPS=""
EXCLUDE_GROUPS=""
INCLUDE_JOBS=""
EXCLUDE_JOBS=""
# Parse command line args (very simplistic)
while [ $# -gt 0 ]; do
case "$1" in
--mode)
MODE=$2
shift 2
;;
--includeGroups)
INCLUDE_GROUPS=$2
shift 2
;;
--excludeGroups)
EXCLUDE_GROUPS=$2
shift 2
;;
--includeJobs)
INCLUDE_JOBS=$2
shift 2
;;
--excludeJobs)
EXCLUDE_JOBS=$2
shift 2
;;
--)
shift
break
;;
*)
echo "Invalid arguments." >&2
exit 1
;;
esac
done
# Verify we have a MODE parameter
if [ -z "${MODE}" ]; then
echo "Cron run mode MUST be defined." 1>&2
exit 1
fi
# Lock process to one run per set of options
# This is to prevent multiple processes for the same cron parameters (And the only reason we don't call PHP directly)
# Unique identifier for this cron job run
IDENTIFIER=$(echo -n "${DIR}|${MODE}|${INCLUDE_GROUPS}|${EXCLUDE_GROUPS}|${INCLUDE_JOBS}|${EXCLUDE_JOBS}" | "${MD5SUM_BIN}" - | cut -f1 -d' ')
acquire_lock "/tmp/magento.aoe_scheduler.${IDENTIFIER}.lock";
# Needed because PHP resolves symlinks before setting __FILE__
cd "${DIR}"
# Build the options
OPTIONS=""
if [ -n "${INCLUDE_GROUPS}" ]; then
OPTIONS="${OPTIONS} --includeGroups ${INCLUDE_GROUPS}"
fi
if [ -n "${EXCLUDE_GROUPS}" ]; then
OPTIONS="${OPTIONS} --excludeGroups ${EXCLUDE_GROUPS}"
fi
if [ -n "${INCLUDE_JOBS}" ]; then
OPTIONS="${OPTIONS} --includeJobs ${INCLUDE_JOBS}"
fi
if [ -n "${EXCLUDE_JOBS}" ]; then
OPTIONS="${OPTIONS} --excludeJobs ${EXCLUDE_JOBS}"
fi
# Run the job in the foreground
"${PHP_BIN}" "${SCHEDULER}" --action cron --mode ${MODE} ${OPTIONS}