Revision 3a4e3bac
b/README.admin | ||
---|---|---|
37 | 37 |
Obviously the lower the interval value and the higher the setting of |
38 | 38 |
RECONCILIATION_MIN, the less load is going to be put on Ganeti. |
39 | 39 |
|
40 |
Logging |
|
41 |
======= |
|
42 |
|
|
43 |
Logging in Synnefo is using Python's logging module. The module is configured |
|
44 |
using a configuration file, whose format is described here: |
|
45 |
|
|
46 |
http://docs.python.org/library/logging.config.html |
|
47 |
|
|
48 |
By default, the log initialization code will look for the logging.conf file |
|
49 |
in the following locations in order: |
|
50 |
|
|
51 |
1. /etc/synnefo/logging.conf |
|
52 |
2. os.getcwd()/logging.conf |
|
53 |
3. synnefo.logic.__path__[0]/logging.conf (<-- this is the default) |
|
54 |
|
|
55 |
The default configuration is using Linux conventions: it logs to /dev/log for |
|
56 |
all loggers. The default configuration can be changed by copying the default |
|
57 |
file to any of the above mentioned locations and changing it appropriately. |
|
58 |
|
|
59 |
* Logging and demonization: If the logging is configured to print to the console |
|
60 |
(using the consoleHandler handler) then daemon processes (notably, the |
|
61 |
dispatcher) will not work as it should. This only happens after the daemon |
|
62 |
has lost its controlling terminal (e.g. because the terminal was closed); |
|
63 |
in this case the dispatcher does not know where to log to and depending on |
|
64 |
the system it either crashes or stalls. This can be avoided if the logging |
|
65 |
module is not configured to output to the console. |
Also available in: Unified diff