Jump to content

damon18

Approved members
  • Posts

    4
  • Joined

  • Last visited

About damon18

damon18's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. Thanks, using quotations around the database credentials solved the problem for me too. The copy of the config file did not use quotes, was this a documented change or caused by some server configuration?
  2. When I start the update by navigating to the /adserver_new directory I get a blank page with error 500 and this is produced in the error_log file: [02-Feb-2021 21:38:06 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to RV\Container::__construct() must be of the type array, boolean given, called in /home/username/public_html/adserver_new/init.php on line 65 and defined in /home/username/public_html/adserver_new/lib/RV/Container.php:38 Stack trace: #0 /home/username/public_html/adserver_new/init.php(65): RV\Container->__construct(false) #1 /home/username/public_html/adserver_new/init.php(143): init() #2 /home/username/public_html/adserver_new/index.php(21): require_once('/home/username/p...') #3 {main} thrown in /home/username/public_html/adserver_new/lib/RV/Container.php on line 38
  3. Did you find an answer to this? I seem to have the same problem upgrading from 4.1.3 to 5.1.1 when I start the upgrade after carefully following the upgrade instructions. [02-Feb-2021 21:38:06 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to RV\Container::__construct() must be of the type array, boolean given, called in /home/username/public_html/adserver_new/init.php on line 65 and defined in /home/username/public_html/adserver_new/lib/RV/Container.php:38 Stack trace: #0 /home/username/public_html/adserver_new/init.php(65): RV\Container->__construct(false) #1 /home/username/public_html/adserver_new/init.php(143): init() #2 /home/username/public_html/adserver_new/index.php(21): require_once('/home/username/p...') #3 {main} thrown in /home/username/public_html/adserver_new/lib/RV/Container.php on line 38
  4. While I was doing an update from Revive 3.2.0 to 3.2.4 I noticed that there were over 25,000 files named maintenance.php.xxxx the xxxx is a sequential number and the files are empty. A new file was written twice per hour at :03 and :18 (like 5:03 and 5:18) for a long time and I hadn't noticed them because they were stored above the public_html web folder where Revive is installed. The installation is on a dedicated domain used only for Revive. Any idea why that happened? They are still being generated, haven't done the upgrade yet. Also, looking at the database, there are two tables with large amounts of records. data_intermediate_ad has 362,734 data_summary_ad_hourly has 362,728 I've obviously got something screwed up here, although in the control panel under Maintenance > Maintenance it shows "Scheduled maintenance is running correctly".
×
×
  • Create New...