ZoneMinder Forums

Hi, just upgraded to 1.28.1 and all seems ok so far except that when I ran I got the message "Database already at version 1.28.0, update aborted". On the web interface I had V1.28.1 in red and when I clicked on it I got message to run zmupdate.pl.
I fixed it by manually updating the database with as required for the upgrade and then So if you get the problem this may help but if this is a problem not just specific to me then it probably needs fixing in the install code.

What distro are you running and how did you install zoneminder?

That was quick !!

I am running Archlinux and I got the install from link in the announcement on this forum.

I edited the release, without making any changes, and re-saved the page, which triggered creation of a new tar.gz.
I have verified that the new tar.gz contains the proper references to 1.28.1. Go ahead and re-download the source files. It should be fixed.

Something very strange happened on github that I can't explain. When I created the release over the weekend, the first thing I noticed was that it said "10 days" ago when I just created the release seconds ago. Thanks to your post, I just now noticed that it did not create the .tar.gz correctly. I guess the .tar.gz was a repsentation of the release branch from 10 days ago as well.

I didn't noticed it earlier, because the rpms I build are based directly off a git-clone of the release branch, and did not exeprience the issue. Don't expect you to know any of this, I'm just baffled as to how this happened in the first place, which sucks because I don't know how to avoid it in the future.

Ok, thanks for the update.
Does this mean I do not have the latest build of 1.28.1 and should I download it again ?

If zoneminder is no longer displaying the version in red and/or refusing to start then you are good.
From what you posted, it looks like you discovered all the bits that were not correct and manually fixed them.

Ok, it all seems ok so I'll leave it alone, thanks again.

Thanks for letting us know. I had no idea the source tarball was not right.

Hello,

I just downloaded the tarball form the website, literally minutes ago, and it is still not working right:

The current tarball contents looks correct.
Make sure you are starting from a clean state before you (re)build. Make-uninstall the previous attempt.
When you expand the source files, open the file configure.ac. The second line, AC_INIT, should be at 1.28.1.
If that is not the case, then you somehow have a copy of the old tarball.

knnniggett wrote:The current tarball contents looks correct.
Make sure you are starting from a clean state before you (re)build. Make-uninstall the previous attempt.
When you expand the source files, open the file configure.ac. The second line, AC_INIT, should be at 1.28.1.
If that is not the case, then you somehow have a copy of the old tarball.

Thankfully - I run a VM so I just reverted back to pre-upgrade state. I'll try it once more.

Edit: just did a clean slate - yes, configure.ac does show 1.28.1 - but still, the update fails!

I don't know if it matter at all - but this is what the DB reports prior to compiling the update:

Here's another interesting tidbit - I tried to manually update the DB (run the commands in mysql cli) and while the UI now displays the 1.28.1 version in blue as opposed to red, ZM service fails to start, stating the following:


Now I am really confused - what's going on here? I've done upgrades many times... never have had this kind of an issue. I am even tried doing a clean install (but kept the DB) - it still complains!

This message: Looks like this in the source code: ZM_DYN_DB_VERSION is at 1.28.1, which means you've updated the database correctly, but ZM_VERSION is still 1.28.0.

So where does ZM_VERSION come from?
It gets set in the Perl script called "Base.pm". On my system, that file is here:
/usr/share/perl5/vendor_perl/ZoneMinder/Base.pm

Yours is probably under /usr/local if you are not building a package

On a compiled system, the value of ZM_VERSION in Base.pm is going to look like a static number: But if you look at the uncompiled source code, it is really tied to the make macro @VERSION@: The value @VERSION@ represents the value I mentioned previsouly, AC_INIT, at line 2 of configure.ac
So if ZM_VERSION is 1.28.0, then that can only mean you've got files on your system that were built with a configure.ac still at the old 1.28.0.

I can't see exactly what you are doing, but somehow or someway, you've either got stale files hanging around or you are building off of a configure.ac that has 1.28.0 in it and you don't realize it. That is the only thing it could be.

Must be a stale file, then. I double checked configure.ac several time and it points to 1.28.1:
Now - I just re-downloaded the tarball from the website and recompiled it. Here's what Base.pm shows now; I have not run make install yet:
So now I ran make install - all went through just fine; no errors. Try to run the update script - same exact issue; still complains that I am on 1.28.0.


Where is the .ZM_VERSION value written after compiling and installing?


And here's the most baffling thing:

This is what the UI shows while the service is offline:



Ok - so at this point I went into mysql cli and modified the Monitor table as well as update config to reflect 1.28.1; have not started the service yet but refreshed the UI:



At this point - all is well. Now I try to start the UI...:


Back to square one


The ONLY thing I can think of is that perhaps when compiling it is reading Base.pm from a previous version folder? I have some of the older source codes in /usr/src but in their own directories. I don't have anything pointing to those and it has never been a problem before. I suppose I can try and recompile everything after cleaning the old versions, though.


By the way - I also have Base.pm in /usr/local/share/perl5/ZoneMinder/Base.pm after compilation and it too shows 1.28.1...