Jump to content
audioguy234

Avigilon NVR/Camera Issue

Recommended Posts

Hey there, just seeing if any other Avigilon installers are also seeing the same problem that we are seeing in their installations.

Logs showing failed pings to cameras (with packet captures not showing any dropped packets), cameras doing their "sentinel reboot" after supposed lost connection to server (network is proven solid)

 

This rare enough where most won't catch it (out of 300 cameras maybe 1 or 2 will drop for 3-5 minutes per day).

 

Not looking for the odd advice or guesses, only input from anyone who has seen this first hand. Thanks

 

Here are some Camera logs

 

 

W(t102:CameraApp:2.6.0.92:13177) [711639(33) 2011-01-01T00:00:26.710Z] Arch/a5/Sys/src/Sys/StreamManagerVideoCam.cpp:272 "Probable dropped frame detected, incrementing Rtp time by 3000"

W(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:42.238Z] Sys/src/Sys/LogManager.cpp:459 "Device-initiated shutdown"

W(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:41.906Z] Arch/a5/Sys/src/Sys/StreamManagerVideoCam.cpp:272 "Probable dropped frame detected, incrementing Rtp time by 24000"

F(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:41.018Z] Sys/src/Sys/WatchdogManager.cpp:306 "Sentinel time has expired. Rebooting device!"

 

here are some server logs

2015-10-21 16:49:45 WARN : ? : Device 1.0018850adbd7: Sending retry ping (timeout 1.000s - payload size 32 bytes)

2015-10-21 16:49:46 WARN : ? : Device 1.0018850adbd7: Ping failed (failure count ! (RTT 1.030s - error NoResponse - boostErr 0: The operation completed successfully)

2015-10-21 16:49:46 WARN : ? : Device 1.0018850adbd7: Not Present (consecutive ping failure limit exceeded)!

2015-10-21 16:49:46 INFO : Rules::RulesManager::ProcessTriggeredRules_ : The rule "Notify users (default)" has been triggered

2015-10-21 16:49:46 INFO : ? : Device 1.0018850adbd7 at 192.168.52.106:80: Error (ping-err: CommunicationTimeout) occurred during accessibility check (i.e. PING).

2015-10-21 16:49:46 ERROR : ? : Onvif SOAP call (tev__PullMessages to 192.168.52.106:80) failed at HTTP level (NotConnected)!

Share this post


Link to post
Share on other sites

Hey there, just seeing if any other Avigilon installers are also seeing the same problem that we are seeing in their installations.

Logs showing failed pings to cameras (with packet captures not showing any dropped packets), cameras doing their "sentinel reboot" after supposed lost connection to server (network is proven solid)

 

This rare enough where most won't catch it (out of 300 cameras maybe 1 or 2 will drop for 3-5 minutes per day).

 

Not looking for the odd advice or guesses, only input from anyone who has seen this first hand. Thanks

 

Here are some Camera logs

 

 

W(t102:CameraApp:2.6.0.92:13177) [711639(33) 2011-01-01T00:00:26.710Z] Arch/a5/Sys/src/Sys/StreamManagerVideoCam.cpp:272 "Probable dropped frame detected, incrementing Rtp time by 3000"

W(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:42.238Z] Sys/src/Sys/LogManager.cpp:459 "Device-initiated shutdown"

W(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:41.906Z] Arch/a5/Sys/src/Sys/StreamManagerVideoCam.cpp:272 "Probable dropped frame detected, incrementing Rtp time by 24000"

F(t102:CameraApp:2.6.0.92:13177) [711639(32) 2015-10-21T23:52:41.018Z] Sys/src/Sys/WatchdogManager.cpp:306 "Sentinel time has expired. Rebooting device!"

 

here are some server logs

2015-10-21 16:49:45 WARN : ? : Device 1.0018850adbd7: Sending retry ping (timeout 1.000s - payload size 32 bytes)

2015-10-21 16:49:46 WARN : ? : Device 1.0018850adbd7: Ping failed (failure count ! (RTT 1.030s - error NoResponse - boostErr 0: The operation completed successfully)

2015-10-21 16:49:46 WARN : ? : Device 1.0018850adbd7: Not Present (consecutive ping failure limit exceeded)!

2015-10-21 16:49:46 INFO : Rules::RulesManager::ProcessTriggeredRules_ : The rule "Notify users (default)" has been triggered

2015-10-21 16:49:46 INFO : ? : Device 1.0018850adbd7 at 192.168.52.106:80: Error (ping-err: CommunicationTimeout) occurred during accessibility check (i.e. PING).

2015-10-21 16:49:46 ERROR : ? : Onvif SOAP call (tev__PullMessages to 192.168.52.106:80) failed at HTTP level (NotConnected)!

 

Camera brand?

Network Sw?

What is Avigilon support opinion ?

Share this post


Link to post
Share on other sites

Hi dears,

I am also facing the same issue with Avigilon cameras. can anyone help me out to solve this issue.

 

some camera logs FYR:

E(t102:CameraApp:2.6.0.150:15529) [1612125(32) 2011-01-01T00:00:37.460Z] Onvif/src/Onvif/PtzEventHandlerOnvif.cpp:100 "Event send request for profile that no longer exists (vidSrcIndex: 0, proto: 0)! Dropping it!"

F(t102:CameraApp:2.6.0.150:15529) [1612125(31) 2017-07-18T06:02:51.168Z] Sys/src/Sys/WatchdogManager.cpp:302 "Sentinel time has expired. Rebooting device!"

E(t102:CameraApp:2.6.0.150:15529) [1612125(31) 2011-01-01T00:00:37.949Z] Onvif/src/Onvif/PtzEventHandlerOnvif.cpp:100 "Event send request for profile that no longer exists (vidSrcIndex: 0, proto: 0)! Dropping it!"

F(t102:CameraApp:2.6.0.150:15529) [1612125(30) 2017-07-18T05:53:34.770Z] Sys/src/Sys/WatchdogManager.cpp:302 "Sentinel time has expired. Rebooting device!"

E(t102:CameraApp:2.6.0.150:15529) [1612125(30) 2011-01-01T00:00:37.629Z] Onvif/src/Onvif/PtzEventHandlerOnvif.cpp:100 "Event send request for profile that no longer exists (vidSrcIndex: 0, proto: 0)! Dropping it!"

F(t102:CameraApp:2.6.0.150:15529) [1612125(29) 2011-01-01T00:02:46.472Z] Sys/src/Sys/WatchdogManager.cpp:302 "Sentinel time has expired. Rebooting device!"

 

Model: AVIGILON 2.0MP Day/Night 20x HD PTZ Dome Camera

FW Ver: Current Firmware Version: 2.6.0.150

Share this post


Link to post
Share on other sites

Thanks for the support guys,

 

Avigilon Server : 21.0TB-HD-NVR2

ACC version : 5.6.2.22

Camera model - Avigilon 2.0W-H3PTZ-DP20

Firmware version - 2.6.0.150

Network Topology - Star

Share this post


Link to post
Share on other sites
Thanks for the support guys,

 

Avigilon Server : 21.0TB-HD-NVR2

ACC version : 5.6.2.22

Camera model - Avigilon 2.0W-H3PTZ-DP20

Firmware version - 2.6.0.150

Network Topology - Star

 

You're running an old version of ACC5. Update that to the latest 5.10.14.2 This will also update the firmware on your cameras to the latest version then report back if the issue is still there.

Share this post


Link to post
Share on other sites

Or if you bought your ACC5 licenses after July 2016 you can upgrade to 6.4 at no charge

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×