Upgrading issues 4.2.1 > 5.0.0

[manuel]

We are not able to upgrade our Revive Adserver to 5.0.0. After the update the delivery rule sets are completely broken and can't be fixed by the maintenance/repair function either. Else, the DB seems to stay always at 4.2.1 version. 

 

More in Detail: 

Running the upgrade process the "Recompile_Acls" task and it seems to stall for a couple minutes, eventually throwing "Error occurred when running installation task "Recompile_Acls": Request timed out" while apparently finishing the upgrade successfully.

 

After logging in to the upgraded Revive Adserber, product updates show that it's running Revive v5.0.0 but adding "warning: database is stamped as v4.2.1" suggesting that the DB upgrade didn't complete.

 

PHP/nginx timeouts and memory limits have already been adjusted as to not cause any timeouts: memory_limit = 4096M, max_execution_time = 18000
After that no errors show up in the PHP error log (512M memory was apparently to little to process our ~17 GB data + ~17 GB index = 34 GB total DB)

 

According to the install.log everything seems to finish successfully though:

 

[...]

attempting to include file

/var/www/html/revive-adserver-5.0.0/etc/changes/tasks/openads_upgrade_task_Recompile_Acls.php

Recompiling Acls

OK

Starting Acls Recompilation

Acls Recompilation: Complete

executed file

/var/www/html/revive-adserver-5.0.0/etc/changes/tasks/openads_upgrade_task_Recompile_Acls.php

Starting file-check for plugins...

Finished file-check for plugins

Starting file-check for plugins...

Finished file-check for plugins

(END)

 

Between every attempted update we did a complete filesystem rollback to make sure the DB is back to its "known-good" 4.2.1 state.

 

Same result every time - DB seems to stay at 4.2.1 and after the update the delivery rule sets are completely broken and can't be fixed by the maintenance/repair function either.

 

[andrewatfornax]

Related?

https://github.com/revive-adserver/revive-adserver/issues/1103