Bug #956
1-second events and avlib errors when recordings cannot be written
| Status: | Resolved | Start date: | 09/12/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  John Brooks |
% Done: | 100% |
|
| Category: | Server | Spent time: | - | |
| Target version: | 2.0.0-beta9.1 | |||
| Release Blocker: | No | Affected Release: | ||
| Operating System: |
Description
When the server fails to create the file for a recording, it enters a horrific loop of restarting the recording and failing every second, including lots of random and confusing avlib errors, CPU usage, and polluting the database with these useless 1-second-long events. This may also be a factor in causing video input corruption (#853).
This situation should be handled gracefully, without avlib errors, and without putting continuous events in the database that have no associated recording. Emitting an error event would be ideal, but that can be done under a separate bug if the log output can be improved. Retrying once per second is also non-ideal in the case of errors like these.
Reproduce:- Set at least one device to continuous recording
- chmod 000 /var/lib/bluecherry/recordings/
- restart bluecherry
- Observe 1-second events and the spew in bluecherry.log
Related issues
History
Updated by John Brooks 5 months ago
- Status changed from New to Assigned
- Assignee set to John Brooks
- Target version changed from 2.x (Staging) to 2.0.0-beta9.1
Updated by John Brooks 5 months ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100