You are correct, it DOES work now. THANKS!
I am not getting the same error you are though... wierd
[all info inside] Having trouble monitoring...
-
- Posts: 678
- Joined: Wed Dec 16, 2009 4:32 pm
- Location: Israel
-
- Posts: 678
- Joined: Wed Dec 16, 2009 4:32 pm
- Location: Israel
I don't believe thats a problem caused by the format because here i let it run for 5 minutes and it worked just fine.
check the system log for more errors such as not being able to initalize shared memory.
By the way your shmall is too high. keep in mind its not in kilobytes but pages and the default value is 8 GB:
http://www.linuxquestions.org/questions ... le-607991/
check the system log for more errors such as not being able to initalize shared memory.
By the way your shmall is too high. keep in mind its not in kilobytes but pages and the default value is 8 GB:
http://www.linuxquestions.org/questions ... le-607991/
-
- Posts: 678
- Joined: Wed Dec 16, 2009 4:32 pm
- Location: Israel
I checked a little and it seems this error doesn't orginate from ZM, but rather from libjpeg, which zoneminder uses for decoding jpeg images.
Your camera probably streams slightly corrupt\broken images, but as long as they work in ZM, i think its OK to ignore that warning.
If you want you can recompile libjpeg to remove that warning, or even easier, set up a syslog filter against this warning.
Your camera probably streams slightly corrupt\broken images, but as long as they work in ZM, i think its OK to ignore that warning.
If you want you can recompile libjpeg to remove that warning, or even easier, set up a syslog filter against this warning.
Last edited by mastertheknife on Sun Feb 21, 2010 7:29 pm, edited 1 time in total.
-
- Posts: 678
- Joined: Wed Dec 16, 2009 4:32 pm
- Location: Israel
Hi.
After some searching in this forum it appears this error seems like a known problem with no fix, not really related to shared memory.
Few things you might want to try that worked for others:
1) Reduce fps (try 5?)
2) Increase HTTP timeout in Network->Options to 5000
3) Try switching between HTTP/1.1 and HTTP/1.0 in Network->Options.
I can't reproduce it, it happily works here (tested 15 minutes)
After some searching in this forum it appears this error seems like a known problem with no fix, not really related to shared memory.
Few things you might want to try that worked for others:
1) Reduce fps (try 5?)
2) Increase HTTP timeout in Network->Options to 5000
3) Try switching between HTTP/1.1 and HTTP/1.0 in Network->Options.
I can't reproduce it, it happily works here (tested 15 minutes)