Closed satkunas closed 6 years ago
I may be going with the obvious thing, but just to make sure, did you follow the 8.0 upgrade instructions in the upgrade guide that is in devel ?
@julsemaan I was applying the upgrade-* scripts to a non-used database (pf
). My config is currently using an alternative mysql database name (pf_test74
).
I've since renamed to databases and updated mysql directives in pf.conf
and pfconfig.conf
.
I'm currently using 7.3.9. Upgrading with /usr/local/pf/db/upgrade-7.3.0-7.4.0.sql
produces a SUBVERSION_MINOR
mismatch. What should I do in the case of upgrading from 7.3.9
to 7.4.0
?
Should I assume that I'm running 7.4.0
and update upgrade-X.X.X-X.Y.Z.sql
to read?:
SET @PREV_MAJOR_VERSION = 7;
SET @PREV_MINOR_VERSION = 3;
SET @PREV_SUBMINOR_VERSION = 9;
in order to force 7.3.9
to 7.4.9
?
When you're testing, I would suggest you only upgrade stable to devel, never devel to devel
You're going to shoot yourself in the foot doing so
If you want to test the upgrade, install 7.4 then upgrade it to 8.0 (7.4.9)
Upgrade Summary
I'm attempting to upgrade from 7.3.9 -> 7.4.0 -> 7.4.9
I'm following the upgrade guide at: https://github.com/inverse-inc/packetfence/blob/devel/UPGRADE.asciidoc#upgrading-from-a-version-prior-to-7-4-0
7.3.9 -> 7.4.0:
No issues
7.4.0 to 7.4.9:
Upon upgrade completion I'm getting a failed service start, with the following error:
Upgrade Process