andrewatfornax

Hey @diego, I'd love to continue to help, but you are really not helping me (or the community) to help you. A link to a 13MB log file, with the expectation that I (or anyone else) has time to look through the log file for you, is pretty ungracious of you. If you'd like additional help, please try trimming the log file down to something relevant that we can work with - ideally, just the part of the log file that is produced at the time you see the issue. This is what you should be investigating yourself anyway!

If you have the same problem (namely, that you see mod security in your logs denying access), then you have not disabled mod security. If you have disabled mod security, then you will not have the same problem - you will have a different problem, which will need details on what the problem actually is, from the logs, if you would like help.

Use *x* zones!

Sure, it's open source, so you are free to modify the software in anyway that you want!

That sort of looks like a timeout issue, that you started the upgrade under PHP 5.6, and then took a while to install PHP 7, and then came back to the upgrade. Did you try the upgrade from the beginning after installing PHP 7?

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

No, there is no solution for Revive Adserver to allow for a distributed solution which periodically synchronises statistics back to a central service.

Do you have any zones of the same time and size set up?

Not a stupid question at all. The host name you pass in needs to be the one that the Revive Adserver system is running on - not where the ads are displayed. (Revive Adserver can show ads on any website; the place the ads are shown doesn't really matter.) The way you are calling scheduled maintenance looks good, now, so I am somewhat at a loss as to why this doesn't work. Possibly a missing extension from PHP that handles command line parameters? I am really not sure.. I have never seen this before. Nothing extra in the web or PHP logs that might help?

So, I can see you are using ModSecurity. We specifically mention this in the troubleshooting guide that I referred you to earlier, and which you indicated that you had followed. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

Hi @benwinton, Just in case you were not aware, please note that upgrading to 4.2.0 will not automatically clean a compromised system - if a system has been compromised, then the system will need to be cleaned (ideally, replaced with a new system), rather than just upgrading Revive Adserver.

And what do you see in the web server and Revive Adserver logs?

Hi @benwinton, Good question! I updated our FAQs for this one, as it seems like something that people might ask frequently: https://documentation.revive-adserver.com/display/DOCS/FAQs

Not sure what the -q option for PHP is there - might be affecting things? https://documentation.revive-adserver.com/display/DOCS/Running+Maintenance

Without more specific information, I cannot help any further. What did you adjust, how did you adjust it - exactly what did you specifically do, and do you still see the same specific error in your log files as before? If not, do you have any other error(s) in your log files?

Hi @Bono, Can you please check if your PHP installation supports the zip extension? Although this was needed in previous versions, we did not correctly test to ensure it was installed - the feature to test to ensure that the zip extension is installed during upgrade/install was added in 4.2.0.

I've created https://github.com/revive-adserver/revive-adserver/issues/1054 to capture this issue.

No, sorry, I cannot - I have never actually used the API myself! Hopefully someone else in the community may be able to assist though.

I would imagine that when you have an error telling you that the software can't write to a given directory, the solution is to assign the appropriate permissions to the directory to give the software the ability to write to that directory, yes? ?

I think that you could potentially use one of the https://documentation.revive-adserver.com/display/DOCS/Site+Delivery+Rules options - say Site - Variable - but unfortunately, you'd need to have something custom in place to pass in all of the relevant content that you wanted to check for the presence of the forbidden word(s) as the variable to Revive Adserver - and that would probably limit how much content you could pass in...

Bingo! Sounds like you have at least one error you can now fix, and see if that helps!

Hi @NjScoot, Yes, there is an (as yet undocumented) XML-RPC API, that allows for the management of (most) of the things you can do via the UI, and there is also at least one 3rd party REST API plugin for Revive Adserver as well that I'm aware of, if XML-RPC isn't your thing... HTH.

No, at this stage, I cannot. When you say "it does not go to the next step", what does it do? What does it show? Can you take a screenshot and show us?

Hi @chrisA, No worries, thanks for confirming. In that case, I would ask that you please double-check the upgrade instructions - it looks to me like you were maybe performing a clean install, but trying to do that into an existing database, instead of taking the required steps to get Revive Adserver to recognise that it's an upgrade, rather than a clean install. HTH!

You say, trying to install the update... Just to clarify, are you trying to perform a clean install, or are you trying to upgrade an existing installation?