[Slackbuilds-users] Problems upgrading ZoneMinder
Geno Bob
geno.bob at gmail.com
Tue May 8 02:24:26 UTC 2018
No problem. Thank you for testing. I will test on my VM and see if I can
replicate.
Thank you,
GenoBob
On Mon, May 7, 2018 at 7:08 PM, Daniel Prosser <dpross1100 at msn.com> wrote:
> Bob,
>
> Thank you for helping me try to sort this out. I was able to use the
> upgrade dbs in /usr/share/zoneminder/db to incrementally upgrade my
> database to 1.31.1. At least, the commands completed without reporting
> any errors. Before I could do that, I did have to grant alter permission
> to zmuser, which wasn't mentioned in README.SLACKWARE, FYI. However,
> after upgrading I'm getting a bunch of errors in the logs about not
> having proper permissions on directories, sockets not existing, etc.
> Those logs recommend running zmupdate.pl -f, which I am still unable to
> do. So I'm not really sure if the database was actually upgraded
> correctly. These errors may be fixable with some hand editing of the
> paths through the web interface, but I need to do more research to find
> out.
>
> B Watson, aka Urchlay, ank youthay orfay explainingay erewhay ethay
> ourcesay amecay omfray. (Pardon my poor pig latin.)
>
> Dan
>
> On Sun, May 06, 2018 at 09:25:21PM -0700, Geno Bob wrote:
> > I apologize, no. Anytime you upgrade Zoneminder from any version to
> > another newer version, you have to upgrade the database incrementally.
> > My easiest method is no not use the zmupdate tool (it works great if
> > you are working with incremental versions, but anything more and I
> like
> > to do it the old fashioned way), but instead to access mysql directly.
> > In this case run:
> > mysql -u zmuser -p databasename <
> > /usr/share/zoneminder/db/zm_update-1.31.0.sql
> > and
> > mysql -u zmuser -p databasename <
> > /usr/share/zoneminder/db/zm_update-1.31.1.sql
> > replacing zmuser with your database username and databasename with
> your
> > db name (probably just zm ?)
> > This will also give us some more info as to what issue you are having
> > with the db files, and which file it is having the issue with.
> > Let me know if this works for you or not.
> > Thank you,
> > GenoBob
> >
> > On Sun, May 6, 2018 at 8:47 PM, Daniel Prosser <[1]dpross1100 at msn.com
> >
> > wrote:
> >
> > If I get time, I will give that a try. But seeing as how upstream
> > still
> > has 1.30.4 as the latest source, I'm not exactly sure where I'm
> > supposed
> > to get 1.31.0. I'm guessing the same urchlay site, but just adjust
> > the
> > download URL?
> > I guess I'm just ignorant, but I have been active on the Slackware
> > forum
> > on Linuxquestions.org for a couple years and never remember coming
> > across someone named Urchlay. But that aside, I'm not sure why being
> > a
> > well-known Slackware user makes him the correct upstream for
> > ZoneMinder.
> > Is he a ZoneMinder dev also? Why does the official upstream still
> > have
> > 1.30.4 as the latest stable release? I need a better reason for the
> > upgrade than what you have provided, and I'm sure the rest of the
> > ZoneMinder users on SBo would appreciate one too. (Please don't get
> > me
> > wrong -- I'm very appreciative of your maintainership efforts.)
> > Regards,
> > Dan
> > On Sun, May 06, 2018 at 12:11:37AM -0700, Geno Bob wrote:
> > > If you get a few minutes, you might try updating the database
> > one step
> > > at a time. You are going from 1.30.4 right to 1.31.1, however
> > there is
> > > a decent amount of updates in the 1.31.0 db file. Try updating
> > the db
> > > to 1.31.0 and then to 1.31.1 and see if it makes a difference.
> > When I
> > > get a chance I will spin up a VM with 1.30.4 and see if I cant
> > > replicate your issue.
> > > Also, Urchlay is THE urchlay. If you ever go onto a slackware
> > forum or
> > > IRC, he will be there.
> > > Thank you,
> > > GenoBob
> > >
> > > On Sat, May 5, 2018 at 8:12 PM, Daniel Prosser
> > <[1][2]dpross1100 at msn.com>
> > > wrote:
> > >
> > > I failed to reply all in my previous message, but anyway it
> > wasn't
> > > very
> > > important. The long and short of it was that I changed the
> > password
> > > for
> > > the "zmuser" DB user, but I think I needed to regrant
> > permission to
> > > the
> > > zm database after that. However, after taking care of that
> > and
> > > ensuring
> > > I can log in to mysql as zmuser, I am right back to the
> > original
> > > error
> > > when I try to run [2][3]zmupdate.pl.
> > > But anyway, as far as I'm concerned, I'm not going to upgrade
> > to a
> > > new
> > > version until it's actually released by upstream. Hopefully
> > the
> > > zmupdate
> > > script will work when that happens.
> > > Dan
> > > On Sat, May 05, 2018 at 03:51:08PM -0700, Geno Bob wrote:
> > > > Daniel,
> > > > According to your error, your credentials are incorrect
> > for
> > > your SQL
> > > > database. Try signing into your database using mysql -u
> > zmuser
> > > -p
> > > > when it asks for a password put in your password (the
> > same
> > > credentials
> > > > you used in the '[1][3][4]zmupdate.pl' command above).
> > > > Thank you,
> > > >
> > > > On Sat, May 5, 2018 at 6:35 AM, Daniel Prosser
> > > <[2][4][5]dpross1100 at msn.com>
> > > > wrote:
> > > >
> > > > Hi,
> > > > ZoneMinder was upgraded to version 1.31.1 in the last
> > update.
> > > The
> > > > new
> > > > version builds fine, but I am having trouble running
> > the
> > > > [3][5][6]zmupdate.pl
> > > > script to update my database. Using this command:
> > > > /usr/bin/[4][6][7]zmupdate.pl --version=1.30.4
> > --user={dbuser}
> >
> > >
> > > > --pass={dbpass}
> > > > I get this result:
> > > > ----------
> > > > Initiating database upgrade to version 1.31.1 from version
> > > 1.30.4
> > > > Please ensure that ZoneMinder is stopped on your system
> > prior to
> > > > upgrading the database.
> > > > Press enter to continue or ctrl-C to stop :
> > > > Do you wish to take a backup of your database prior to
> > > upgrading?
> > > > This may result in a large file in /var/tmp/zm if you have
> > a lot
> > > of
> > > > events.
> > > > Press 'y' for a backup or 'n' to continue : n
> > > > Upgrading database to version 1.31.1
> > > > Loading config from DBNo option 'ZM_DIR_EVENTS' found,
> > removing.
> > > > No option 'ZM_DIR_IMAGES' found, removing.
> > > > No option 'ZM_DIR_SOUNDS' found, removing.
> > > > No option 'ZM_FRAME_SOCKET_SIZE' found, removing.
> > > > No option 'ZM_OPT_FRAME_SERVER' found, removing.
> > > > No option 'ZM_PATH_ARP' found, removing.
> > > > No option 'ZM_PATH_LOGS' found, removing.
> > > > No option 'ZM_PATH_MAP' found, removing.
> > > > No option 'ZM_PATH_SOCKS' found, removing.
> > > > No option 'ZM_PATH_SWAP' found, removing.
> > > > No option 'ZM_PATH_ZMS' found, removing.
> > > > 207 entries
> > > > Saving config to DB 207 entries
> > > > DBD::mysql::db do failed: Access denied for user
> > > > 'zmuser'@'localhost' to
> > > > database 'zm' at /usr/share/perl5/vendor_perl/
> > > ZoneMinder/Config.pm
> > > > line
> > > > 214, <STDIN> line 2.
> > > > Can't lock Config table: Access denied for user
> > > 'zmuser'@'localhost'
> > > > to
> > >
> >
> > > > database 'zm' at /usr/bin/[5][7][8]zmupdate.pl line
> > 464.
> > > > ----------
> > > > I have also tried without specifying --user and
> > --pass, but I
> > > get
> > > > the
> > > > same error. For now I have gone back to my old version
> > and
> > > restored
> > > > the
> > > > backup database. I can also ask on the ZoneMinder
> > forums, but
> > > I'm
> > > > not
> > > > sure if the issue lies with [6][8][9]zmupdate.pl or
> > with the way
> > > > ZoneMinder is
> > > > configured by the SBo package. Seems like pretty much
> > > everyone over
> > > > there uses Ubuntu, CentOS, or Debian.
> > > > Dan
> > > >
> > >
> > > > References
> > > >
> > > > 1. [9][10]http://zmupdate.pl/
> > > > 2. mailto:[10][11]dpross1100 at msn.com
> > > > 3. [11][12]http://zmupdate.pl/
> > > > 4. [12][13]http://zmupdate.pl/
> > > > 5. [13][14]http://zmupdate.pl/
> > > > 6. [14][15]http://zmupdate.pl/
> > >
> > > References
> > >
> > > 1. mailto:[16]dpross1100 at msn.com
> > > 2. [17]http://zmupdate.pl/
> > > 3. [18]http://zmupdate.pl/
> > > 4. mailto:[19]dpross1100 at msn.com
> > > 5. [20]http://zmupdate.pl/
> > > 6. [21]http://zmupdate.pl/
> > > 7. [22]http://zmupdate.pl/
> > > 8. [23]http://zmupdate.pl/
> > > 9. [24]http://zmupdate.pl/
> > > 10. mailto:[25]dpross1100 at msn.com
> > > 11. [26]http://zmupdate.pl/
> > > 12. [27]http://zmupdate.pl/
> > > 13. [28]http://zmupdate.pl/
> > > 14. [29]http://zmupdate.pl/
> >
> > References
> >
> > 1. mailto:dpross1100 at msn.com
> > 2. mailto:dpross1100 at msn.com
> > 3. http://zmupdate.pl/
> > 4. http://zmupdate.pl/
> > 5. mailto:dpross1100 at msn.com
> > 6. http://zmupdate.pl/
> > 7. http://zmupdate.pl/
> > 8. http://zmupdate.pl/
> > 9. http://zmupdate.pl/
> > 10. http://zmupdate.pl/
> > 11. mailto:dpross1100 at msn.com
> > 12. http://zmupdate.pl/
> > 13. http://zmupdate.pl/
> > 14. http://zmupdate.pl/
> > 15. http://zmupdate.pl/
> > 16. mailto:dpross1100 at msn.com
> > 17. http://zmupdate.pl/
> > 18. http://zmupdate.pl/
> > 19. mailto:dpross1100 at msn.com
> > 20. http://zmupdate.pl/
> > 21. http://zmupdate.pl/
> > 22. http://zmupdate.pl/
> > 23. http://zmupdate.pl/
> > 24. http://zmupdate.pl/
> > 25. mailto:dpross1100 at msn.com
> > 26. http://zmupdate.pl/
> > 27. http://zmupdate.pl/
> > 28. http://zmupdate.pl/
> > 29. http://zmupdate.pl/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180507/9cac15f5/attachment-0001.html>
More information about the SlackBuilds-users
mailing list