Randomly not recording

Forum for questions and support relating to the 1.24.x releases only.
Post Reply
joako
Posts: 30
Joined: Mon Nov 01, 2010 7:10 am

Randomly not recording

Post by joako » Sat Jun 25, 2011 9:46 pm

I have an issue where randomly some camera will stop recording. I can still view it live!

I've looked at the logs and there's nothing relevant.

How can I ensure my cameras are always recording? There's plenty of free disk space.

Code: Select all

[   15.190257] type=1505 audit(1308872556.188:11): operation="profile_load" pid=907 name=/usr/sbin/traceroute
[   17.029323] tg3 0000:04:04.0: firmware: requesting tigon/tg3_tso5.bin
[   17.111655] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.260806] tg3 0000:04:04.0: eth0: Link is up at 1000 Mbps, full duplex
[   20.260812] tg3 0000:04:04.0: eth0: Flow control is on for TX and on for RX
[   20.261007] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   33.459788] bttv1: PLL can sleep, using XTAL (28636363).
[   35.044408] bttv3: PLL can sleep, using XTAL (28636363).
[  277.602688] NET: Registered protocol family 17
[  726.304866] 3w-9xxx: scsi2: AEN: INFO (0x04:0x0029): Verify started:unit=0.
[ 1251.259485] 3w-9xxx: scsi2: AEN: INFO (0x04:0x003D): Verify paused:unit=0.
[ 1491.242161] 3w-9xxx: scsi2: AEN: INFO (0x04:0x0029): Verify started:unit=0.
[46764.290987] 3w-9xxx: scsi2: AEN: INFO (0x04:0x002B): Verify completed:unit=0.
[47132.515565] 3w-9xxx: scsi2: AEN: INFO (0x04:0x0029): Verify started:unit=0.
[79668.756547] tg3 0000:04:04.0: eth0: Link is down
[79671.679674] tg3 0000:04:04.0: eth0: Link is up at 1000 Mbps, full duplex
[79671.679680] tg3 0000:04:04.0: eth0: Flow control is on for TX and on for RX
[87689.237384] 3w-9xxx: scsi2: AEN: INFO (0x04:0x003D): Verify paused:unit=0.
[87699.435012] 3w-9xxx: scsi2: AEN: INFO (0x04:0x0029): Verify started:unit=0.
[89564.539568] 3w-9xxx: scsi2: AEN: INFO (0x04:0x002B): Verify completed:unit=0.
[89969.019903] 3w-9xxx: scsi2: AEN: INFO (0x04:0x0029): Verify started:unit=0.
[104242.396032] bttv1: timeout: drop=212 irq=7904826/7904826, risc=36ba403c, bits: HSYNC OFLOW
[135992.577078] 3w-9xxx: scsi2: AEN: INFO (0x04:0x002B): Verify completed:unit=0.

Code: Select all

==> /var/log/zm/zmdc.log <==
06/25/11 17:57:06.051920 zmdc[1807].INF ['zma -m 1' starting at 11/06/25 17:57:06, pid = 4856]

==> /var/log/zm/zmwatch.log <==
06/25/11 17:57:05.172619 zmwatch[1876].INF [Restarting analysis daemon for Monitor-1, time since last analysis 9 seconds (1309039025-1309039016)]
06/25/11 17:57:06.085892 zmwatch[1876].INF ['zma -m 1' starting at 11/06/25 17:57:06, pid = 4856]
06/25/11 17:57:06.088930 zmwatch[1876].INF [Restarting analysis daemon for Monitor-2, time since last analysis 8 seconds (1309039025-1309039017)]

==> /var/log/zm/zmdc.log <==
06/25/11 17:57:06.799844 zmdc[1807].INF ['zma -m 2' starting at 11/06/25 17:57:06, pid = 4860]

==> /var/log/zm/zmwatch.log <==
06/25/11 17:57:06.832262 zmwatch[1876].INF ['zma -m 2' starting at 11/06/25 17:57:06, pid = 4860]

==> /var/log/zm/zmdc.log <==
06/25/11 17:57:08.639240 zmdc[1807].ERR ['zma -m 1' exited abnormally, exit status 145]
06/25/11 17:57:09.319385 zmdc[1807].ERR ['zma -m 2' exited abnormally, exit status 145]

==> /var/log/zm/zmwatch.log <==
06/25/11 17:57:16.836582 zmwatch[1876].INF [Restarting analysis daemon for Monitor-1, time since last analysis 8 seconds (1309039036-1309039028)]

==> /var/log/zm/zmdc.log <==
06/25/11 17:57:17.485872 zmdc[1807].INF ['zma -m 1' starting at 11/06/25 17:57:17, pid = 4865]
06/25/11 17:57:18.235202 zmdc[1807].INF ['zma -m 2' starting at 11/06/25 17:57:18, pid = 4869]

==> /var/log/zm/zmwatch.log <==
06/25/11 17:57:17.524560 zmwatch[1876].INF ['zma -m 1' starting at 11/06/25 17:57:17, pid = 4865]
06/25/11 17:57:17.527613 zmwatch[1876].INF [Restarting analysis daemon for Monitor-2, time since last analysis 7 seconds (1309039036-1309039029)]
06/25/11 17:57:18.272526 zmwatch[1876].INF ['zma -m 2' starting at 11/06/25 17:57:18, pid = 4869]

==> /var/log/zm/zmdc.log <==
06/25/11 17:57:20.076670 zmdc[1807].ERR ['zma -m 1' exited abnormally, exit status 145]
06/25/11 17:57:20.748997 zmdc[1807].ERR ['zma -m 2' exited abnormally, exit status 145]
Once I restart the server or even just zm service it starts recoding again, for a while.
Attachments
zmfail01.JPG
zmfail01.JPG (83.91 KiB) Viewed 1909 times

mastertheknife
Posts: 678
Joined: Wed Dec 16, 2009 4:32 pm
Location: Israel

Re: Randomly not recording

Post by mastertheknife » Sat Jun 25, 2011 11:11 pm

Hi,

Seems zma is lagging behind and can not keep up with the rate of zmc. Try slowing down the capture or speeding up the analysis.

mastertheknife
Kfir Itzhak.

joako
Posts: 30
Joined: Mon Nov 01, 2010 7:10 am

Re: Randomly not recording

Post by joako » Sun Jun 26, 2011 8:07 pm

I am using mode: "record" w/o any analysis. So even to record w/o motion I need faster hardware?

mastertheknife
Posts: 678
Joined: Wed Dec 16, 2009 4:32 pm
Location: Israel

Re: Randomly not recording

Post by mastertheknife » Mon Jun 27, 2011 5:26 am

Ok, seems like something else is the issue then.

Please enable debugging level 9 and post a debugging log for zma.

mastertheknife.
Kfir Itzhak.

joako
Posts: 30
Joined: Mon Nov 01, 2010 7:10 am

Re: Randomly not recording

Post by joako » Mon Jul 11, 2011 11:37 pm

I fix the issue by deleting all the events and starting over.

But now my 2nd system does the same?

How can I ensure recording continues without deleting everything? It sort of defeats the purpose of recoding.

joako
Posts: 30
Joined: Mon Nov 01, 2010 7:10 am

Re: Randomly not recording

Post by joako » Sat Jul 30, 2011 7:19 pm

no matter what i do on this system it always goes back to not recordidng.

how can i ensure it records at all hours without fail?

TucsonDirect
Posts: 23
Joined: Tue Feb 08, 2011 3:10 am

Re: Randomly not recording

Post by TucsonDirect » Sun Jul 31, 2011 9:49 am

Try the zmlarch Live Cd.
Just remember to edit the hosts file so the server will start

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests