ZoneMinder Forums

Seems like the same question as the other thread.

You either run zmupdate as a more powerful DB user, or turn off binary logging. (As it states in the text you posted)

Mostly the OP, and as an FYI for you, so you can see what works.

As I said before, I can reach the API from here, which says it's working. I could also see the default Apache page.

The fact the dynamic DNS hostname I used is in the logs, says that bit works too.

Yes, clearly.

The API responds when I test it (albeit not authenticated). Don't know why Python requests is having trouble with it. Have you tested this from the machine that runs ZMES? I'm wondering about DNS, for example.

You can get their attention here https://www.bountysource.com/teams/zoneminder

Usual fix is to toggle UDP/TCP.

No risk for most people. Cameras will point to the local DNS by default.

Try the logging settings in the web interface. See if you can turn them up a bit.

The right direction is Bountysource.

It just shows ZM is running.

Apache is another matter. Check the service is running. Run a netstat to see the ports it is using. make sure you've anabled the ZM site.

Stop fiddling. Make sure you enable the zoneminder site. Put the other stuff back.

Zoneminder looks ok.

What did you do with Apache? Not sure I understand what you did with ports.

It may run the service, I don’t know your set up. It clearly isn’t starting it at boot, which is what you need to tell it to do.