ZoneMinder Forums

Because the pids in question were httpd-prefork I looked in the apache error log and that is where I saw reference to a Bot.

Sorry, should have thought to provide that information. I am running ZM 1.30.2 on OpenSuse Leapwith Foscam FI8918W and FI8904W cameras. I always compile ZM from source. On looking a little more at the errors I find that the pids are pointing at an httpd-prefork process and the apache error log is sh...

I've just found a bunch of errors in the log which come from web_php which read 'No row for Frame'. They seem to be transient and not causing any obvious issue. I was wondering what causes them.

Shouldn't the watchdog somehow spot that this process isn't running correctly and kill it?

I've just started getting the same type of problem. System running perfectly OK and then I can no longer see one, or maybe two cameras. In my case the two that just did are both wired and have fixed IP addresses which are not in a DHCP range. If I kill the zmc process the camera recovers. The zm log...

I can see from the new website that you are discouraging downloading the source however for those of us who wish to do that is it not possible to have a link which does just that rather than having to go to GitHub?

I've just hit the same problem and I got the message about shared data not being initialized, but I had already read elsewhere that that error was a bit of red herring. Initially I couldn't see what was happening with the images directory but then I found that it was in the wrong place, probably my ...

Zoneminder 1.26.4 introduced cmake as the build tool and there is a note in the INSTALL file that this will become the default so I guess that's why 1.27 doesn't have a configure script. The cmake route works fine. As far as a package for OpenSuse is concerned, there is work going on to produce work...

Guess you have either found a way around this or have given up. I had a problem with one of the database updates and I had to break down the zmupdate.pl into manual lumps and run them through by hand to find out which one was broken and then sort out the specific error.

I wonder if anyone can offer a simple solution to a problem which shows up when you have zm configured as a service that systmed can control and you then use zmpkg.pl to stop/start zm. The problem seems to be that if you use systemd's service control then the console and zmpkg.pl will tell you that ...

Not sure what the problem was back in 2011 but presets work fine these days

Can't say for sure if this is the same problem I had with OpenSuse but maybe. The problem I had was the later releases of OpenSuse use systemd and that has introduced the concept of private /tmp space and the default for ZM is to use /tmp. So the web console is looking and the private /tmp and zmpkg...

I just had the same problem and discovered that the cause was because MySql had strict mode turned on. If you get rid of strict mode then the problem goes away. Obviously, in the longer term it would be preferable that ZM code didn't need this but in the short term this is a way out. Look in your my...

I'm not entirely sure if this is the answer but I too had a similar problem with OpenSuse and I think the change I made which stopped this happening was to set short_open_tag = On in /etc/php5/apache2/php.ini. Be careful when you are editing the file as you will find two references to short_open_tag...

I have been setting up a new install of zm on OpenSuse 13.1, which has mariadb as the default replacement for mysql. The installation appears to default to using strict mode, which then causes zm problems in more than one area but the place I found it was trying yo add a monitor, when it gave an SQL...