Revision f0b1bafe man/ganeti.rst
b/man/ganeti.rst | ||
---|---|---|
179 | 179 |
|
180 | 180 |
All Ganeti daemons re-open the log file(s) when sent a SIGHUP signal. |
181 | 181 |
**logrotate**(8) can be used to rotate Ganeti's log files. |
182 |
|
|
183 |
Common field formatting |
|
184 |
----------------------- |
|
185 |
|
|
186 |
Multiple ganeti commands use the same framework for tabular listing of |
|
187 |
resources (e.g. **gnt-instance list**, **gnt-node list**, **gnt-group |
|
188 |
list**, **gnt-debug locks**, etc.). For these commands, special states |
|
189 |
are denoted via a special symbol (in terse mode) or a string (in |
|
190 |
verbose mode): |
|
191 |
|
|
192 |
*, (offline) |
|
193 |
The node in question is marked offline, and thus it cannot be |
|
194 |
queried for data. This result is persistent until the node is |
|
195 |
de-offlined. |
|
196 |
|
|
197 |
?, (nodata) |
|
198 |
Ganeti expected to receive an answer from this entity, but the |
|
199 |
cluster RPC call failed and/or we didn't receive a valid answer; |
|
200 |
usually more information is available in the node daemon log (if |
|
201 |
the node is alive) or the master daemon log. This result is |
|
202 |
transient, and re-running command might return a different result. |
|
203 |
|
|
204 |
-, (unavail) |
|
205 |
The respective field doesn't make sense for this entity; |
|
206 |
e.g. querying a down instance for its current memory 'live' usage, |
|
207 |
or querying a non-vm_capable node for disk/memory data. This |
|
208 |
result is persistent, and until the entity state is changed via |
|
209 |
ganeti commands, the result won't change. |
|
210 |
|
|
211 |
??, (unknown) |
|
212 |
This field is not known (note that this is different from entity |
|
213 |
being unknown). Either you have mis-typed the field name, or you |
|
214 |
are using a field that the running Ganeti master daemon doesn't |
|
215 |
know. This result is persistent, re-running the command won't |
|
216 |
change it. |
Also available in: Unified diff