ZoneMinder Forums

I've noticed some previous postings on this topics but haven't found a definitive answer. I installed ZM 1.28.1 on CentOS 7 using an RPM. The web gui is showing the console as stopped. When checking in the CLI the console appears to be running. I also cannot view one of my camera feeds, which I'm assuming is because the gui thinks the console isn't running. Any help on how to resolve this?

This problem does not appear when installing zoneminder on a default, clean centos 7 system with a new zm database.
It has got something to do with how you installed zoneminder.

Since no details were provided, we need to ask a lot of questions to figure out where the problem is:

When you say you've installed a zoneminder RPM, do you mean you installed zoneminder from zmrepo and followed all the steps in the README?

The following questions assume you indeed have install zoneinder via zmrepo and have followed the README:

Other than the rpm's that get installed from zmrepo, do you or have you ever installed any additional RPM's not contained in the defaul CentOS rpm repository?

Did you at anytime, previsouly attempt to build zoneminder from source on this machine?

Was the database created from sratch using the currently install RPM, or did you create it previously?

Did you make any changes to any paths under Options?

We had the same thing happen to us when we first installed on CentOS 6. If I remember correctly we ended up disabling SELinux and rebooted to fix the issue. We haven't jumped to CentOS 7 yet so it may be different, but worth a try.

Kenny

I have the same problem. CentOs 7 with repo installation. not is Selinux problem because disable it and web continue in state "stopped"

are you getting socket errors in the logs for second monitor? if so it's very common and no fix to date.

cornbread wrote:are you getting socket errors in the logs for second monitor? if so it's very common and no fix to date.

socket errors mean you have a configuration issue with your system.

knnniggett wrote:

cornbread wrote:are you getting socket errors in the logs for second monitor? if so it's very common and no fix to date.

socket errors mean you have a configuration issue with your system.

Could you be more specific? I'm getting errors of this kind in my new Ubuntu14.04+ZM1.28 when there was no errors in Debian7.0+ZM1.25. What could be the source of the errors?

Thanks in advance,

PacoLM

Getting "socket sendto" errors are like getting "general protection fault" messages in older version of Windows.

There are many ways to generate these errors, and it generally means that something in your system is not configured correctly. It could be the camera config, it could be your ramdisk /dev/shm is set too small often, but not always, due to low memory (sounds like that was cornbread's issue from another thread), it could folder permissions, an incorrect apache config will cause this, but it could be something else entirely. I really can't be specific because a thorough description of the your system, including full log output, and what you are trying to do has not been given, but please don't do that in this tread since it doesn't apply to the OP. Please create a new topic.