1. Home
  2. Docs
  3. MicroPVR
  4. Launch and use
  5. Logistics

Logistics

The main log file of the micropvr process

/var/log/micropvr/micropvr.log - the main log file. The messages are as follows:

%timestamp%log level%module%function%%PID%(%message code%)%message text%

Example:

Tue Mar 14 06:31:21 2017 DEBUG RECORDS MANAGER CheckWritingFilesSizes[18527]: file size check: ch_id-76_time-1489462267_task_id-962839 - 0 bytes

Possible message levels in order of increasing log detail (each level includes previous levels):

  • CRITICAL - critical errors that directly affect the operation of the micropvr process: copying errors, entries to the database, etc.
  • ERROR - significant errors: configuration reading errors, space shortage messages, etc.
  • Warnings: API call errors, task restart messages due to error, etc.
  • INFOs are informational messages.
  • DEBUG - minor messages, useful for debugging.
  • EXTENDED – access to the database.

Micropvr state log

If the parameter log-state-period more 0, then micropvr with a given frequency in minutes will keep the state log /var/log/micropvr/micropvr_state.log.

View of log records:

Log OK: 12/10 13:28:59
Mem used: 958868 KiB, mem free: 3099672 KiB
Swap used: 127652 KiB, swap free: 8257880 KiB
CPU LA1: 0.5
Content requests: 0 requests in 59 seconds, 0.0 per second
Successful requests: 0 requests in 59 seconds, 0.0 per second

_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
| CID | CHANNEL NAME | SOURCE | START TIME | STOP TIME | LOCK TIME | REPEAT | LOCATION | PRIOR | STATUS |
—---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 1 | channel1 | udp:// @239.1.2.3:1234 | 12/10 15:00:00 | 12/10 16:00:00 | 13/10 16:00:00 | 3600 secs | /tmp/pvr/ch_1 | 3 | NEW|
| 2 | channel2 | udp:// @239.1.2.3:1235 | 12/10 15:00:00 | 12/10 16:00:00 | 13/10 16:00:00 | 3600 secs | /tmp/pvr/ch_2 | 3 | NEW|
| 3 | channel3 | udp:// @239.1.2.3:1236 | 12/10 13:00:00 | 12/10 14:00:00 | 14/10 14:00:00 | 3600 secs | /tmp/pvr/ch_3 | 3 | STARTED |
| 3 | channel3-sd | udp:// @239.1.2.3:1236 | 12/10 13:00:00 | 12/10 14:00:00 | 14/10 14:00:00 | 3600 secs | /ssd/pvr/ch_3 | 5 | STARTED |
| 4 | channel4 | udp:// @239.1.2.3:1236 | 12/10 13:29:10 | 12/10 14:00:00 | 14/10 14:00:00 | 3600 secs | /ssd/pvr/ch_4 | 5 | POSTPONED |
| 5 | channel5 | udp:// @239.1.2.3:1240 | 12/10 14:20:00 | 12/10 17:20:00 | 15/10 17:20:00 | no repeat | /ssd/pvr/ch_5 | 5 | NEW|
________________________________________________________________________________________________________________________________________________________________________
| PATH | FREE SPACE | RESERVED | AVAILABLE |
—---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| / | 393849 MiB | 30000 MiB | 363849 MiB |
| /ssd | 128350 MiB | 30000 MiB | 98350 MiB |

Task table fields:

  • CID is the channel identifier specified when creating a task.
  • CHANNEL NAME is the name of the channel used to create the task.
  • SOURCE is the source of the recording.
  • START TIME is the actual recording start time (in the server time zone).
  • STOP TIME is the end time of the record (in the server time zone).
  • LOCK TIME is the time before which automatic deletion of a record is blocked (in the server time zone).
  • REPEAT, the repetition period of a task, may not coincide with the actual recording duration. If a new task has already been established, it is indicated repeatedif the task is non-periodic, it is indicated no, no. no, no. no. no. no. no. no. no.
  • Location is a recording directory.
  • PRIOR is a record priority. When you request offset and file will be given a record with high priority.
  • Status is the status of the task.

Possible statuses:

  • NEW – The task has not yet started and is on the waiting list.
  • POSTPONED is similar to NEW, but the task was restarted due to an error.
  • STARTING – The task is in the process of launching.
  • Failed is an error in completing a task.
  • STARTED – the task is in the process of execution, the recording is carried out.
  • UNKNOWN is a different status.

Log recorder

recorder Additional log file of recorder processes. Activated by option recorder in a micropvr configuration. The messages are as follows:

%timestamp%log level%function%[%PID%](%message code%)%message text%