Revision 4e3c9f2d
b/man/ganeti-watcher.rst | ||
---|---|---|
68 | 68 |
FILES |
69 | 69 |
----- |
70 | 70 |
|
71 |
The command has a state file located at |
|
72 |
``@LOCALSTATEDIR@/lib/ganeti/watcher.data`` (only used on the master) |
|
73 |
and a log file at ``@LOCALSTATEDIR@/log/ganeti/watcher.log``. Removal |
|
74 |
of either file will not affect correct operation; the removal of the |
|
75 |
state file will just cause the restart counters for the instances to |
|
76 |
reset to zero. |
|
71 |
The command has a set of state files (one per group) located at |
|
72 |
``@LOCALSTATEDIR@/lib/ganeti/watcher.GROUP-UUID.data`` (only used on the |
|
73 |
master) and a log file at |
|
74 |
``@LOCALSTATEDIR@/log/ganeti/watcher.log``. Removal of either file(s) |
|
75 |
will not affect correct operation; the removal of the state file will |
|
76 |
just cause the restart counters for the instances to reset to zero, and |
|
77 |
mark nodes as freshly rebooted (so for example DRBD minors will be |
|
78 |
re-activated). |
|
79 |
|
|
80 |
In some cases, it's even desirable to reset the watcher state, for |
|
81 |
example after maintenance actions, or when you want to simulate the |
|
82 |
reboot of all nodes, so in this case, you can remove all state files:: |
|
83 |
|
|
84 |
rm -f @LOCALSTATEDIR@/lib/ganeti/watcher.*.data |
|
85 |
rm -f @LOCALSTATEDIR@/lib/ganeti/watcher.*.instance-status |
|
86 |
rm -f @LOCALSTATEDIR@/lib/ganeti/instance-status |
|
87 |
|
|
88 |
And then re-run the watcher. |
|
77 | 89 |
|
78 | 90 |
.. vim: set textwidth=72 : |
79 | 91 |
.. Local Variables: |
Also available in: Unified diff