ZoneMinder Forums

Hi

I had ZoneMinder working fine in feisty. I installed the .deb package, and did the arrangements noted in the wiki.

Now, I have installed Gutsy and theres no way I can get it to work. So this is what I did:

I installed ZoneMinder from the Ubuntu repositories. I modified the buffer max size so it could handle 640x480. I did the ln to link the files. Changed ZM_PATH_ZMS to zms (as I had problems with nph-zms in feisty).

I have a network camera, and it refused to work. The ip address was red. I tried different paths, video and jpg. And they didnt work. Tried the same paths in Firefox and they were working. I changed the netcam-regexps, no difference. Finally (and dont know why) I got the ip adress in green, but theres no image showing yet.

I checked the logs and it said something about needing openssl for hashed conections, but I have openssl package installed allredy. So, in Zoneminder I changed from hash to plain. Still doesnt show image, and now the syslog sais "segmentation fault" everytime I try to watch the live feed from the camera.

I just dont know what else to try.

Hugo

UPDATE: Ok, so magically is working now. After giving up trying, I just came to write here. Without changing anything went back to zoneminder, and it worked. I really dont understand how magically it can start working, so if anyone has some idea, some explanation would be very apreciated.

im guessing one of the new libs has issues in gutsy.. is it still beta?

me and ubuntu dont get on well with zm lol

Ok. So its definitively the hashed/plain isue. In hashed no image. With plain I get image. If someone can explain me exactly what is that changing and why with plain works, Ill apreciate it

Guess something is not compiled to support openssl or something like that.

Jameswilson thanks for the quick reply. Gutsy is Release Candidate now, and its coming out oficially in 3 days, so it should be almost working by now.

Hugo

PD: Also, if I click regexps I get a log warning saying: Oct 15 20:35:34 server zmc_m1[9840]: WAR [Unable to use netcam regexps as not compiled with libpcre]. Still working, but it may interest the .deb manteiner.

This authentication issue has been around a lot longer than that. I first saw it on Edgy, and others before that. It is odd, inconsistent, and not a high priority to fix, so I just deal with it... Sorry.

Might have Peter check and make sure that in the log for configure, that openssl was properly detected (openssl dev package required) and built into the package.

But I first found the "fix" in other posts from users of other distributions. This problem is older than Peter's .debs.

Yes it is and in most all cases have been OpenSSL, this issue has been around for two plus years since we added hashed authentication, If you don't get all the dependencies met, things that require them will not work. Deb has been an issue a majority of the time, but I have only ever been able to duplicate it by leaving out openssl, hence he needs to check the logs and let us know if it was detected or not.
The start of these are here , here, and here for example.
I did a deb install using source two years ago and had no problem getting hashed auth to work but not really sure what I had done differently. Either way, we need to track it down.
If you search the forum for OpenSSL you will find plenty of history on this issue.

Hmmm... Could you tell with ssh to a system with Peters deb on it? If so, I can give you a box in the morning.

The details would be in the configure.log from the build. The way I over came the issue in RPM is using BUIlDREQUIRES macro in the spec file to make sure that OpenSSL Dev package is available for the build assuming this to be the issue and it may not be, but at least it's a good starting point. Rule out the simple things first since OpenSSL is also linked to in Apache and MySQL, possibly PHP Builds as well but I'd have to check. The problem is we might have to dig pretty deep and before, others would be easily um detured I guess is the correct word or if they found the fix, didn't report back and we assume an issue still exists. I would love to put this one to bed once and for all.