Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: figured I hit the update button before I forget!

...

No change :-/


More research....


...


Try #? — Import using the SQL tab?


Let's drop the DB first--

Image Added


Image Added


Interesting:

Image Added


The details didn't help... running the pasted SQL—this is with the hope that if it errors out, we have a detailed (which line in the script it failed on error) info:

Image Added


Yea... no dice:

Image Added


Looking at the SQL file, we know that the import always fails on cache_menu after inserting 7 records and so what's the 8th record? Check this out:

Image Added


Image Added


Yea... I am sure that is above the max setting... getting rid of that insert and trying the import again:

Image Added

Note: removing that one query alone dropped the file size by a good chunk... Also note, we are not too worried about that one record — because it's a cache record anyways... so the system should be able to rebuild it.


AND..... .SUCCESSSSSS! We have the DB imported:

Image Added


Now, comes the code....

rsync -av PREP rjb03001admin@phptst1.its.uconn.edu:/apps

Image Added


Nice! The code has been moved off of RHEL6 and onto RHEL7—

Image Added


Change the settings file, same as with other portals:

vim /apps/PREP/sites/default/settings.php

→ Change $update_free_access to TRUE

→ Add (for troubleshooting purposes)---

error_reporting(E_ALL);
ini_set('display_errors', TRUE);
ini_set('display_startup_errors', TRUE);
$conf['error_level'] = 2;


Save and quit; let's navigate to the portal and see what's up:

Image Added


Nice! we are not going to login... instead, we will do the Drupal update process:

Image Added


And we get:

Image Added


Something is wrong........... must be the conf file....

So prior to making any changes to the conf file, let's back it up:

Image Added


Let's open-up the prep conf file...

Image Added


Sure enough... the AuthType is there and it shouldn't...

Here's how it should be:

Image Added


Save and quit and then give Apache a boot...

Image Added


Let's access the Drupal's update process—

Image Added


Much better:

Image Added


Let's create a user using phpMyAdmin---

Image Added


Image Added


Look at the settings file for the needed info—

Image Added


Image Added


Let's refresh Firefox and see what we get...

Image Added

MUCH BETTER! Before following-through with the update process, let's update CAS and LDAP related modules and then re-load the Drupal's update process...

Image Added


Image Added


Image Added


Okay...

Image Added


We have encountered rules module related error before... so before we move onto the Front page, let's update the rules module and then re-run the Drupal's update process...

Image Added


Image Added


Let's update the rules_conditional module too... On the live site, go to Available updates and download from the provided link:

Image Added


Upload the tar.gz file directly onto the server

Image Added


Remove the rules_conditional folder (do it either via FileZilla GUI or command line) and then extract the archive

Image Added


Remove the archive... and let's re-run the Drupal's update process...

Image Added

Awesome! Let's hit the Front page — we should be greeted with a CAS login page!

Image Added


AWESOME!!! After logging in... ... ...

Image Added


Huh!? Let's try a completely fresh browser session...

Image Added


After logging-in, same:

Image Added


Hmmm.... onto Research!


The following Q/A helped resolve this problem:

https://drupal.stackexchange.com/q/166358/72255


Visiting PREP2 now greets with a CAS login instead!

Image Added


Upon authenticating, we get to the landing page of the PREP tool!

Image Added


We do have a module that seems to be out of date: admin_menu — let's update it!

Image Added


Get the downloaded tar.gz file onto RHEL7 and extract and then run the Drupal's update process as before...

Image Added


Image Added


Image Added


Image Added

Voila! Error Free Landing Page!