Difference between revisions of "Server crashes"
From Finninday
(New page: * July 30, 2008 7:38:26am -- Crash while processing cron.daily. Cron.daily started at 7:35:01. When successful, cron.daily usually finishes around 7:45, depending on how much has changed...) |
|||
| Line 1: | Line 1: | ||
* July 30, 2008 7:38:26am -- Crash while processing cron.daily. Cron.daily started at 7:35:01. When successful, cron.daily usually finishes around 7:45, depending on how much has changed on the filesystem that needs to be backed up. | * July 30, 2008 7:38:26am -- Crash while processing cron.daily. Cron.daily started at 7:35:01. When successful, cron.daily usually finishes around 7:45, depending on how much has changed on the filesystem that needs to be backed up. | ||
| + | |||
| + | ====Turned on lvm logging==== | ||
| + | Made some edits to /etc/lvm/lvm.conf. Changed these lines: | ||
| + | |||
| + | verbose = 2 | ||
| + | file = "/var/log/lvm2.log" | ||
| + | level = 5 | ||
| + | |||
| + | The file was commented out, the verbosity and level were set to 0. Verbosity goes from 0-3. Level goes from 0-7. | ||
| + | |||
| + | The man page for lvm.conf said that executing an lvm command would cause the configuration to be reloaded, so I just issued a pvdisplay to get the logging settings activated. | ||
Latest revision as of 16:37, 30 July 2008
- July 30, 2008 7:38:26am -- Crash while processing cron.daily. Cron.daily started at 7:35:01. When successful, cron.daily usually finishes around 7:45, depending on how much has changed on the filesystem that needs to be backed up.
Turned on lvm logging
Made some edits to /etc/lvm/lvm.conf. Changed these lines:
verbose = 2 file = "/var/log/lvm2.log" level = 5
The file was commented out, the verbosity and level were set to 0. Verbosity goes from 0-3. Level goes from 0-7.
The man page for lvm.conf said that executing an lvm command would cause the configuration to be reloaded, so I just issued a pvdisplay to get the logging settings activated.
