Error and failure when clicking the next or previous event button

[kd4pbs]

Forgive me if this isn't the place for this... I am generally a moron about such things.
I have a fresh install of Ubuntu 20.04 LTS server. Followed the "How to Install ZoneMinder-Master ,v 1.35.4 on UBUNTU 20.04 LTS ( Focal Fossa)" guide at https://wiki.zoneminder.com/How_to_Inst ... l_Fossa%29 and adjusted for the revision which was downloaded from iconnor's repository when I installed, v1.35.14 (thanks, bud!)
Things went rather smoothly with the installation and I was able to get monitors and events happening from a couple of IP cameras in the "lab" (I actually prefer to call it a "shop" as it seems far less pretentious). Only problem was that as I would attempt to change from one event to the other with the |< Prev or >| next buttons from the event view window, ZM will consistently puke at me with "Event was not found." and no next or previous event, when I know darned well one exists.

Checking the log, I see that when I open up an event to view, I get these log errors from the same PID:

SQL-ERR 'SQLSTATE[HY000]: General error: 1525 Incorrect DATETIME value: ''', statement was 'SELECT E.Id AS Id, E.StartDateTime AS StartDateTime FROM Events AS E INNER JOIN Monitors AS M ON E.MonitorId = M.Id WHERE E.StartDateTime
from /usr/share/zoneminder/www/includes/database.php, line 161

followed immediately by:
Failed to load previous event using SELECT E.Id AS Id, E.StartDateTime AS StartDateTime FROM Events AS E INNER JOIN Monitors AS M ON E.MonitorId = M.Id WHERE E.StartDateTime
from /usr/share/zoneminder/www/ajax/status.php, line 439

Then, when I get the "Event was not found." error on the web page after clicking the next or previous button, I get these log errors from a different PID:

Socket /run/zm/zms-788541s.sock [this number changes every time I get a set of these errors] does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/lat ... window-etc for more information.
from /usr/share/zoneminder/www/includes/functions.php, line 1913

followed immediately by:
getCmdResponse stream error: Socket /run/zm/zms-788541s.sock [this number changes every time I get a set of these errors] does not exist. This file is created by zms, and since it does not exist, either zms did not run, or zms exited early. Please check your zms logs and ensure that CGI is enabled in apache and check that the PATH_ZMS is set correctly. Make sure that ZM is actually recording. If you are trying to view a live stream and the capture process (zmc) is not running then zms will exit. Please go to http://zoneminder.readthedocs.io/en/lat ... window-etc for more information. - checkStreamForErrors()
from ?view=event

Now, I'm not the sharpest knife in the butcher block, but it seems to me that something's wrong here... an old Zoneminder box I have had running for the past few years with v1.30.4 doesn't do this, it happily goes to the next event for that monitor. It also stands to reason that most of those errors I see when I get the "Event was not found." message would indicate that lots of other stuff would not be working if they were more valid than not.

Checking the web_js.log and the web_php.log shows the same errors. These errors also propagate to the syslog. No other logging reveals anything else.

I also discovered an issue that had me chasing my tail a while... if one re-assigns the "Default" storage location by just changing the path to the new place one wants things written, say, /mount/footage in the Options\Storage setting, everything looks fine and happy. Problem is, if one already created a monitor, it will keep trying to write to the old original path, and will do so until that old path isn't available and things go sideways because the directories no longer exist, or that file system gets filled, or what have you. But if one goes back into the monitor settings and clicks on the Storage settings page, eventually one might notice that there are now two "Default" options now with no indication of which is the correct one. If one then creates a new storage location, with a name of, say, "Bubba", then deletes the "Default" location, and then goes back into the monitor storage settings, "Default" is still an option, and it will still write to the old original as-built "Default" location. I think I saw someone else with a similar issue as a bug request on the github, but it was a bit unclear of what that user was referring to, so forgive me if this is a known issue.

What is even more interesting is that a total wipe of everything, a clean reinstallation of Ubuntu from scratch,and a clean reinstallation of ZoneMinder duplicates the issue... it is still there.

Any ideas? Perhaps I am merely not holding my mouth right when I install Zoneminder?

Regards-

[dougmccrary]

I haven't seen that lately, but it might be a good idea to go with the release version, get that working, then change the repo to get back to 1.35...but I'm only using one storage area, so that might be related.
OTOH, are you really on 1.35.4? Current is 1.35.14 1.35.14~20201111174357-focal
These 1.35 versions get broken a * lot *...

[kd4pbs]

No, I installed 1.35.14 but used that guide for 1.35.4 that I found.

I'll see what I can do about getting it back to 1.35 .

It will be a while before they start screaming at me to replace the older server I have running, so if you all need me to test anything new on this, let me know.

Kind regards-

[kd4pbs]

I just noticed that another release was available, and I updated to it; 1.35.14~20201111141728-focal . I was on 1.35.14~20201110123829-focal . It does not appear to have fixed the problem I am seeing with the Next / Prev event. Off to figure out how to install an older version...

[kd4pbs]

I gave up on figuring out how to get an early 1.35 version on the machine and installed.
Since it isn't a HUGE error to deal with, I'll just let it roll and deal with not being able to click the next and precious buttons until that gets fixed and updated.
Thanks, y'all!

[dougmccrary]

I haven't seen that lately, but it might be a good idea to go with the release version, get that working, then change the repo to get back to 1.35...but I'm only using one storage area, so that might be related.

I'm sorry I wasn't clear - a release version would be a 1.34.x.
If you're running a production machine, best stick with that until this 1.35.x development version is released.

[iconnor]

I can confirm the presence of this issue. I will have it fixed today.

[kd4pbs]

Thanks bunches, Isaac.
Regards-
Matt