The script needs to be undated to reflect the changes made in PIFR 2.x.

The INSTALL.txt has been updated and the script should be able to lose a few items. For instance there is no longer any need to download and patch SimpleTest D6 module as it is no longer required.

CommentFileSizeAuthor
#1 455744-upgrade.patch7.13 KBboombatower

Comments

boombatower’s picture

Status: Active » Needs review
StatusFileSize
new7.13 KB

Here is initial patch to remove SimpleTest components from install script.

The database needs to be updated.

boombatower’s picture

Looks like we will want to update the script to use Drupal 6.11 (which will also change the database.sql).

Please make sure the check the INSTALL.txt file, but one detail that for sure will need to be addressed is the requirements for settings.php.

$db_url = array();
$db_url['default'] = 'mysqli://user:password@localhost/drupal';
$db_url['pifr_checkout'] = 'mysqli://user:password@localhost/drupal_checkout';
boombatower’s picture

Not sure, but I think the script needs to update the CLI php.ini if it exists.

boombatower’s picture

Assigned: Unassigned » boombatower
  • Removed all SimpleTest dependencies and related code
  • Updated database for new versions
  • Update PIFR and Drupal tags
  • Removed gawk dependency

I see if I can get the CLI php.ini script set, and correct settings.php setup.

boombatower’s picture

Assigned: boombatower » Unassigned

The script now generates a settings.php file like #2. Only issue is they will always have mysql:// and use mysql helpers to generate the _checkout database. That will need to be updated, but that is beyond what I want to work on right now.

Swampcritter’s picture

Category: task » bug
Status: Needs review » Active

Okay, I ran the testing_server_install.sh but I keep seeing the following ‘error’ to appear…

[root@testing local]# ./testing_server_install.sh
Updating the testing server setup files from the Drupal contributions repository.
All prerequisites passed
Updating SSH pubkey for boombatower
Updating SSH pubkey for hunmonk
ERROR 1146 (42S02) at line 1: Table 'drupal.pifr_server' doesn't exist
Adding http://www.imedia2go.com/ to {pifr_server} table.
ERROR 1146 (42S02) at line 1: Table 'drupal.pifr_server' doesn't exist
ERROR 1146 (42S02) at line 1: Table 'drupal.pifr_server' doesn't exist
Ensuring webroot
Updating Drupal core tag DRUPAL-6-11
? ajax_authcache.php
? cache
? modules/authcache
? modules/boost
? modules/cacherouter
? sites/all/modules
? sites/default/files
? sites/default/settings.php
Updating Project issue file review tag HEAD
Changing ownership of drupal files for admins and web server
Setup complete!

Is there something else I need to be setting up or configuring for the test client? I also noticed that I need a client key and server URL to point to under the PIFR management tab and there is no reference to this anywhere in the script.

boombatower’s picture

The script it still attempting to setup a PIFR 1.x style test slave. It needs to be updated to the PIFR 2.x style test client.

Please install PIFR manually (just the Drupal side of things) and then take a look at the database, although I do not believe the script will need to insert any records anymore.

Amazon’s picture

I am going to add a message that Swampcritter reported on list:

As found in my server's watchdog log: "When requesting next test, server responded: Invalid server"

We might need this message to be more explicit.

boombatower’s picture

Perhaps that, or supply documentation of message somewhere. That means that the master server doesn't recognize the test client...which means it probably hasn't been added to the list or the key is not set on the client correctly.

That is something the script cannot do.

gordon’s picture

Version: » 6.x-2.x-dev

subscribing

boombatower’s picture

Assigned: Unassigned » boombatower
Status: Active » Fixed

This should be complete. Not a 100% pretty, but it should work.

boombatower’s picture

Status: Fixed » Active
boombatower’s picture

Status: Active » Fixed

Believe we should be back in business.

Lets just open up new issues when this occurs as the major update has been completed by this issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.