Http Error 500

[kkrofft]

Updated from 1.30.0 to 1.30.1. Had to run zmupdate.pl to get Zoneminder to run. Now when I click on the hour/day/week/month event count to view and delete new events I get a http error 500. I think it is likely a permissions issue resulting from running zmupdate as root. Anyone got a suggestion on the right way to correct it? Or suggestions of an alternative cause?

Thanks!

Kory

[knight-of-ni]

HTTP 500 means a problem with your web server configuration. Look in your web server log for clues.

1.30.1 has not been released. Where did you install zoneminder from?

[kkrofft]

The error appears to be in the ssl_error_log. It reads:
PHP Fatal error: Class 'Event' not found in /usr/share/zoneminder/www/skins/classic/views/events.php on line 98...

The update was listed in the software updates list in CentOS 6.8 software updater. being a ..1 point release I thought is was minor and therefore likely safe.

Is there an elegant way to fix it or recover it?

[knight-of-ni]

Thanks for reporting that. Looks like you ran into this:
https://github.com/ZoneMinder/ZoneMinder/pull/1729

You could manually make the changes to the php files shown there and fix it, but I'm not sure what you want to do at this point.

At some point you enabled the testing repo on your system. As the name implies these packages are only for testing the latest software.
Is that what you want? You are welcome to try it, but understand the packages in the testing reop have received little to no testing.
Errors can and will happen.

If that isn't what you want, then you should disable the repo and then perform "yum downgrade zoneminder" to roll back to the 1.30.0 release.

[kkrofft]

Not sure why I enabled the testing repo. Probably several versions ago. If I do the downgrade, what must be done to reconcile the database schema which is now 1.30.1?

Thank you,

Kory

[jrf]

My installation was updated to 1.30.1 today, using apt-get. No issues so far, but only running for an hour now. Using iconnor ppa.

[kkrofft]

The downgrade worked perfectly. Back to a fully functioning 1.30.0. I did not know that zmupdate.pl worked for up and down rev.

Thank you for the advice.

Kory

[knight-of-ni]

Hey, I forgot about zmupdate. What I've always done is gone into the Config table and manually set the version string, which I forgot to tell you about.
But if the web console is not showing the version in red and refusing to start then no harm no foul. If you don't see any errors then don't worry about it. There is little difference between the two dB schemas so you don't have to worry about that causing a problem.

[kkrofft]

After the yum downgrade, ZM would not start as before due to the version mismatch. So I tried zmupdate and it revised the database version back to 1.30.0. At this point all the everything is working as before the update.