Page 2 of 2
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Fri Sep 20, 2013 9:49 pm
by iitywygms
Magic919 wrote:Great. After than just run zmupdate.pl with no arguments.
Magic919. You obviously know more about zoneminder than I.
But from this thread,
http://www.zoneminder.com/forums/viewto ... .pl#p80904
it says you must run certain arguments.
I am not saying which way is right, or create confusion for the op and I apologize if I do. I just want to pass on info that I come across.
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Sat Sep 21, 2013 6:17 am
by topromotion
Magic919 wrote:Great. After than just run zmupdate.pl with no arguments.
I have an error after zmupdate.pl command. See picture.
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Sat Sep 21, 2013 7:47 am
by Magic919
Running from that location overrides your config - as the message says.
Leave that directory, then run it somewhere that doesn't contain a zm.conf.
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Sat Sep 21, 2013 12:56 pm
by knight-of-ni
Magic919 wrote:Great. After than just run zmupdate.pl with no arguments.
Negative.
If your previous version of zoneminder is older than 1.26.0 than you have to call zmupdate.pl like so or the upgrade will leave your system with missing columns in the Monitors dB table:
Code: Select all
sudo zmudpate.pl --user=root --pass={mysql_root_pwd}
When in doubt, always run zmupdate.pl like that.
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Sat Sep 21, 2013 1:50 pm
by Magic919
I've never run mine that way, but my database has the newer columns, Deinterlacing and Colours. It'll come down to how you've set the privileges of your ZM user for the database at the end of the day, surely. I don't mind it being the recommended way, just I can't see we 'have' to.
Re: How update ZM from 1.25.0 to 1.26.3
Posted: Sat Sep 21, 2013 2:07 pm
by knight-of-ni
Magic919 wrote:I've never run mine that way, but my database has the newer columns, Deinterlacing and Colours. It'll come down to how you've set the privileges of your ZM user for the database at the end of the day, surely. I don't mind it being the recommended way, just I can't see we 'have' to.
From the zoneminder wiki:
Code: Select all
mysql> grant select,insert,update,delete on zm.* to '<database user>'@localhost identified by '<database password>';
The lines of Perl script that updates an older dB to 1.26.0 looks like this:
Code: Select all
$dbh->do(q{alter table Monitors add column `Colours` tinyint(3) unsigned NOT NULL default '1' after `Height`;});
$dbh->do(q{alter table Monitors add column `Deinterlacing` INT unsigned NOT NULL default '0' after
This step will fail for anyone following the zoneminder documentation. That's why I said something.
While you might have upgraded the permissions of the zmuser account on your system, a new person following the instructions would not know to do this. That person would end up with a database missing the mentioned columns. Running zmupdate.pl a second time is not an option because the script would have written a 1.26.x to the config table. Catch-22. Yuck.
This is an issue we are currently working on, but in the meantime you have to run zmupdate.pl the way that was previously mentioned if you are upgrading to/past 1.26.0.