Suspension during recording

[bader77uk]

NextPVR Version: 5.0.6.200614

i had a scheduled recording last night started at (2020-08-02 1:29 AM)
Recording is due to be stopped at 8/2/2020 3:35 AM. But its keep saying "RECORDING" in NPVR WEB under Schedule Section until 10:13 AM then stopped
at Recording event time no HTTP errors occured
actual Recording TS File Stopped at 3:02:57 AM

its a first time this issue, i am not sure what cause this, i have attached the logs for you to investigate

FFprobe recording info:

Duration: 01:34:21.95, start: 32467.411333, bitrate: 2392 kb/s

[mvallevand]

When you posted "But its keep saying "RECORDING" in NPVR WEB under Schedule Section until 10:13 AM then stopped" how did you determine that. Did you edit the logs? I don't see any browser requests for seven hour. Is it possible your time or timezone was changed?

The system logs are probably going to be most helpful.

Martin

[bader77uk]

No, i didn't edited the logs and i didn't changed timezone during this process. and Yes the RECORDING status was showing under Schedule until the stop time which showing in log:

logs-20200802-1025\nrecord.log

2020-08-02 10:13:51.455 [DEBUG][8] Stopping recording (868 on 21). Past end time of recording. 2

As its stopped at the above time, of course that means it was on RECORDING since Started time 1:29 AM

EDIT: can you guide me how to provide system log for this issue?

[mvallevand]

The status was recording but the last system request logged that would have shown you this was

2020-08-02 03:11:57.726 [DEBUG][21] method=recording.recurring.list

and the next one was

2020-08-02 10:24:28.617 [DEBUG][34] method=recording.recurring.list

Since you didn't (according to the logs) refresh the browser you wouldn't have visually have had indication that it was recording or not during that period.

Recording status also do not mean the the file is growing or streaming was working. It just means it hasn't stopped. There are many instances of zero byte recordings for various reasons.

Martin

[bader77uk]

maybe I didnt refresh page. but the major issue why the recording file suspended while no streaming errors or actual stopping occured in NPVR also why stopping recording event was too late (out of recording time)

[mvallevand]

Since you don't have sudo you may need to get the system logs from the admin typically I would suggest

sudo dmesg > dmesg.txt
sudo journalctl > journal.txt

There is not always an error if 0 bytes are being read.

Martin

[bader77uk]

looks like the issue was caused by network connection reset, i found this log related to recording suspension time:

Aug 02 03:02:52 mazeinc systemd-networkd[677]: enp0s3: Lost carrier
Aug 02 03:02:52 mazeinc kernel: e1000: enp0s3 NIC Link is Down
Aug 02 03:02:52 mazeinc sshd[31723]: Failed password for root from 10.0.2.2 port 10923 ssh2
Aug 02 03:02:52 mazeinc systemd-networkd[677]: enp0s3: DHCP lease lost
Aug 02 03:02:56 mazeinc systemd-networkd[677]: enp0s3: Gained carrier
Aug 02 03:02:56 mazeinc systemd-timesyncd[517]: Network configuration changed, trying to establish connection.
Aug 02 03:02:56 mazeinc kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Aug 02 03:02:56 mazeinc systemd-networkd[677]: enp0s3: DHCPv4 address 10.0.2.15/24 via 10.0.2.2
Aug 02 03:02:56 mazeinc systemd-networkd[677]: enp0s3: Configured
Aug 02 03:02:58 mazeinc sshd[31723]: Connection reset by authenticating user root 10.0.2.2 port 10923 [preauth]
Aug 02 03:02:58 mazeinc sshd[31723]: PAM 2 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=10.0.2.2  user=root

i have attached dmesg output

Note: currently hosting in Linux VM Via VirtualBox