Apache Setup After 1.26.3 Upgrade

[kbocek]

I just upgraded from 1.24.2 to 1.26.3. My camera images are in grayscale. From searching around the forum it looks like I still have my old 1.24.3 Apache setup in place. Can anyone point me in the right direction for fixing this? I ran configure for /var/www/html and /var/www/cgi-bin. I see nph-zms and zms in cgi-bin but nothing other than defaults in /var/www/html.

Are there some files I can manually copy to get the 1.26.3 html files up and running?

[knight-of-ni]

Open the source tab on each of your monitors and verify the target colorspace has not defaulted back to 8bit grayscale.
Part of the upgrade adds a new 32-bit colorspace option to this field. You should set all your color cameras to 32bit colorspace to get SSE performance improvements. They are significant.

[kbocek]

Thanks knnniggett, it was definitely my old 1.24.2 files. Yes, I only had 8-bit gray and 24 bit color available.

I was able to manually copy the new web file from source. I had forgotten that I had move my web location so I had specified the wrong install destination. After copying the files (and figuring out the mootools symlinks) I got the new interface up and now see the 8/24/32 bit options. My cameras are not in color.

Yes indeed, the performance increase is impressive. Now I have two of my six cameras down at the moment but it does look better.

However I lost my live camera feed. Clicking on a camera gives me a static image. Any suggestions?

[knight-of-ni]

However I lost my live camera feed. Clicking on a camera gives me a static image. Any suggestions?

You need to check your log files to see what the issue is.

BTW, I read your other post and see you are running CentOS 5.
I have working CentOS 6 rpms here: http://www.zoneminder.com/forums/viewto ... =9&t=19119

I don't have any plans to rebuild them for CentOS 5, but you are welcome to try.

[knight-of-ni]

Oh, note that zoneminder 1.25 introduced access to your log file from the web portal. You've upgraded from such an old version that you may not have noticed the new link labelled "Log" in the top right corner of your screen. Makes it easy to quickly see what is going on.

[kbocek]

Okay, I'm seeing a large number of 'capturing' and 'processing' message from my cameras along with FPS measurements in the log screen. So something is going on. However the main web page isn't showing any events and clicking on a camera shows a static image but no FPS or live image. So I've screwed something up.

[knight-of-ni]

Okay, I'm seeing a large number of 'capturing' and 'processing' message from my cameras along with FPS measurements in the log screen. So something is going on. However the main web page isn't showing any events and clicking on a camera shows a static image but no FPS or live image. So I've screwed something up.

The capturing and processing events are good.

With the log window open, do you see any errors or warnings pop up when you open a monitor?

If the image you see when you open a monitor does indeed refresh just very, very slowly then that mean it didn't detect a browser that supports native streaming, and then it also didn't detect cambozola on your system. The third fallback option is to send single jpeg's albeit very, very slowly. Let me know if this is what is going on and I'll show you how to fix it.

[kbocek]

then that mean it didn't detect a browser that supports native streaming,

Okay, I just tried IE and got a live feed. Back to Chrome, no live feed. Does that tell you anything? Do I need to enable something in Chrome?

1.24.2 used to require Java. I assume we've gotten away from that.

[knight-of-ni]

then that mean it didn't detect a browser that supports native streaming,

Okay, I just tried IE and got a live feed. Back to Chrome, no live feed. Does that tell you anything? Do I need to enable something in Chrome?

1.24.2 used to require Java. I assume we've gotten away from that.

Native streaming in Chrome was intentionally disabled due to a bug in chrome. I only recently learned of this, found that the Chrome bug was fixed, and then re-enabled native streaming support for Chrome in zoneminder. This change, however, won't appear until 1.26.4.

For the time being, your workaround for this is to navigate to Options -> High B/W -> WEB_H_CAN_STREAM. Change that from "Auto" to "Yes". You can make a similar change to Medium B/w & Low B/W if you need to. This bypasses zoneminder's browser detection.

[kbocek]

Options -> High B/W -> WEB_H_CAN_STREAM. Change that from "Auto" to "Yes".

Yes indeed, that does allow streaming in Chrome. Thanks.

But I take back my performance statement. I'm on a pretty low-end dual-core atom box. Dedicated, but low-end. So I'm sure a lot of the performance enhancements won't apply. Now that I've got all my cameras up, I'm seeing about the same CPU usage I did before.

[knight-of-ni]

The Atom cpu has the same SSE support as other modern cpu's. As long as you have compiled zoneminder against libjpeg-turbo and have your colorspace set to 32bit then you should see noticeable improvement. My cpu load dropped by nearly a full point.

[kbocek]

As long as you have compiled zoneminder against libjpeg-turbo

Nope. No libjpeg-turbo for CentOS 5. Only the older libjpeg. I searched around and it doesn't seem to be available. When I select 32-bit color, my cameras don't work so I assume that's tied to libjpeg-turbo, correct?

[mastertheknife]

As long as you have compiled zoneminder against libjpeg-turbo

Nope. No libjpeg-turbo for CentOS 5. Only the older libjpeg. I searched around and it doesn't seem to be available. When I select 32-bit color, my cameras don't work so I assume that's tied to libjpeg-turbo, correct?

Correct.

[knight-of-ni]

Yes, 32bit colorspace needs libjpeg-turbo.

RPM's can be downloaded here:
http://sourceforge.net/projects/libjpeg ... les/1.3.0/

I used older versions of these back when I was running CentOS 5.x.

If, for some reason, there is an issue with the rpm, then your next step would be to download the source rpm from that same link and rebuild it like so:

Code: Select all

rpmbuild --rebuild libjpeg-turbo-official-1.3.0.src.rpm

[kbocek]

RPM's can be downloaded here:
http://sourceforge.net/projects/libjpeg ... les/1.3.0/

Well go ahead, make a liar out of me I searched all over for this. Nerdcred--.

Do you know if a -devel package is required for compilation? I don't see one there. The x86_64 RPM installed fine.

Edit:
Answering my own question, it appears yes, you need a -devel package. I recompiled and reinstalled 1.26.3 after installing libjpeg-turbo.x86_64 to try and fix some other web related issues I was having. 32-bit color is still not working.

However, attempting to rebuild the source RPM yields:

Code: Select all

...
checking whether the assembler (nasm -felf64 -DELF -D__x86_64__) works... no
configure: error: installation or configuration problem: assembler cannot create object files.

nasm *is* installed.