Page 1 of 1
Add frameserver patch to latest source
Posted: Tue Oct 04, 2011 1:32 pm
by knight-of-ni
When using zm 1.24.2, some of us noticed many "incomplete read of frames" errors in our log files. This problem did not go away despite increasing buffer sizes as suggested by other topics found in the forum.
What did fix the problem is located here:
http://www.zoneminder.com/forums/viewto ... 55&p=72191
and was placed in the Wiki here:
http://www.zoneminder.com/wiki/index.php/1.24.2_Patches
Moving forward, I recently upgraded to 1.25.0 and was surprised to see these errors return. Applying the patch to the 1.25 source code and re-compiling fixes the problem.
Any chance we could get this patch incorporated into the latest source code?
Re: Add frameserver patch to latest source
Posted: Mon Oct 17, 2011 11:57 pm
by dogmeat206
I ran the patch and I see the same errors....
Re: Add frameserver patch to latest source
Posted: Tue Oct 18, 2011 1:28 am
by knight-of-ni
Post your logs.
If the patch was successful, then the errors change to warnings:
Code: Select all
2011-10-17 19:54:53.113820 zmf 31907 WAR Image read : Read rest of short read: 404 bytes read total of 32364 bytes zmf.cpp 250
2011-10-17 19:54:53.113491 zmf 31907 WAR Image read : continuing, read 16000 bytes (31960 so far) zmf.cpp 254
2011-10-17 19:54:53.112811 zmf 31907 WAR Image read : Short read 15960 bytes of 32364 expected bytes zmf.cpp 246
2011-10-17 19:54:48.707509 zmf 31907 WAR Image read : Read rest of short read: 283 bytes read total of 32243 bytes zmf.cpp 250
2011-10-17 19:54:48.707184 zmf 31907 WAR Image read : continuing, read 16000 bytes (31960 so far) zmf.cpp 254
This is simply saying that it had to re-read to get all the information (i.e. it's not an error).
If you see something else then there is another cause to the messages you see in your log.
Re: Add frameserver patch to latest source
Posted: Tue Oct 18, 2011 4:08 am
by dogmeat206
Ill post logs when I get into the office tomorrow morning.
Re: Add frameserver patch to latest source
Posted: Tue Oct 18, 2011 3:47 pm
by dogmeat206
Ahh, your correct,
2011-10-18 09:41:33.454106 zmf 1912 WAR Image read : Read rest of short read: 23116 bytes read total of 71076 bytes zmf.cpp 250
2011-10-18 09:41:33.453461 zmf 1912 WAR Image read : Short read 47960 bytes of 71076 expected bytes zmf.cpp 246
2011-10-18 09:41:30.457203 zmf 1912 WAR Image read : Read rest of short read: 39320 bytes read total of 71280 bytes zmf.cpp 250
2011-10-18 09:41:30.456290 zmf 1912 WAR Image read : Short read 31960 bytes of 71280 expected bytes zmf.cpp 246
2011-10-18 09:41:28.293312 zma_m1 1896 INF Monitor-1: 449000 - Processing at 17.24 fps zm_monitor.cpp 1055
2011-10-18 09:41:27.970139 zmf 1912 WAR Image read : Read rest of short read: 39160 bytes read total of 71120 bytes zmf.cpp 250
2011-10-18 09:41:27.969334 zmf 1912 WAR Image read : Short read 31960 bytes of 71120 expected bytes zmf.cpp 246
2011-10-18 09:41:24.614555 zmf 1912 WAR Image read : Read rest of short read: 23335 bytes read total of 71295 bytes zmf.cpp 250
2011-10-18 09:41:24.614196 zmf 1912 WAR Image read : Short read 47960 bytes of 71295 expected bytes zmf.cpp 246
Sadly tho, this comes up only when motion is detected. The event starts but never stops. Any idea why that is?