Upgrade to RN 2.3 NukeSentinel Failed

jlajax · Posted: Sun Feb 08, 2009 8:54 am

Greetings folks,

I just finished upgrading a site to RavenNuke(tm) 2.3. The uograde appeared to go smoothly until I tried to update nuke sentinel. I got the following error message.

Your Sentinel configuration value was detected as
(This is the value that is in the "config_value" field of your nsnst_config table.)

This is not a legitimate configuration value for this update... please correct it or post the issue in our forums... execution is being terminated to avoid further issues.

The valid values for the configuration setting of Nukesentinel(tm) for this update are:
 2.4.2pl5
 2.4.2pl6
 2.4.2pl7
 2.4.2pl8
 2.4.2pl9
 2.5.00
 2.5.01
 2.5.02
 2.5.03
 2.5.04
 2.5.05
 2.5.06
 2.5.07
 2.5.08
 2.5.09
 2.5.10
 2.5.11
 2.5.12
 2.5.13
 2.5.14
 2.5.15
 2.5.16
 2.5.17
 2.5.18
 2.6.00
These are the only versions that we are able to upgrade from. If you have a much older version, it might be best to get the latest full install from NukeScripts Network and perform a re-installation of the tables and files.

If you have already upgraded to 2.6.01 then you do not need to run this.

If you are ABSOLUTELY SURE of your version number, you may correct it using PhPMyAdmin or another tool and rerun this script. Just BE SURE of yourself before you take this approach.

In checking PhPMyAdmin it says in the nuke_nsngr_config that the version is 1.7.1 I went to

Only registered users can see links on this board!
Get registered or login to the forums!

and did not see an update script. I have the data base backed up. How do I complete the conversion. If I do a complete DB over write will I be able to upload the old info? This site is live and it is down so I am wanting to get it fixed ASAP however I am unsure of the proper way to proceed.

This portal has been up for a number of years and in checking my records it seems that I have not upgraded it since I installed it. At least I have no notes on the upgrade and I keep notes on every upgrade I do. Comments? Suggestions? Guidance.

jlajax · Posted: Sun Feb 08, 2009 9:05 am

Interesting note. I removed the installation directory and the site is functional. I went to nuke sentinel and inside of the portal nuke sentinel tells me that I have version 2.6 installed. From PhPMyAdmin it says I have 1.7.1 installed. I am definately confused. The portal is functioning and the upgrade appears to have taken.

RavensScripts

fkelly · Posted: Sun Feb 08, 2009 9:18 am

The upgrade script that you are referencing in your first note does database updates for all the "legitimate versions" you listed in that note. Basically, we copied the database updates that were present in the upgrade packages on the Nukescripts site and consolidated them all in one script. However, we did not go back to NS 1.7.1.

Your NS version should be 2.6.01 when you are complete. It is possible that there might be some database updates between 1.7.1 and 2.4.2pl5 (which is the earliest version supported by the upgrade script) that you are missing. Because the upgrade script didn't think you had a legitimate version to start with, it didn't update your nsngr_config value to 2.6.01.

The only completely "safe" approach that will be sure to preserve your old NS table contents is to go out to Nukescripts and see how many upgrades there were between 1.7.1 and 2.4.2 and apply the database portions of them all. I don't know how many there were off the top. Then when you get to 2.4.2 you can run our upgrade script.

If you can live without your old data in NS tables you could just install 2.6.01 fresh.

Susann · Posted: Sun Feb 08, 2009 9:25 am

The table to find the NukeSentinel version number is:

nuke_nsnst_config

and you checked: nuke_nsngr_config ???

So these are tow different things.

Older versions of NukeSentinel can be found at:

Only registered users can see links on this board!
Get registered or login to the forums!

jlajax · Posted: Tue Sep 22, 2009 6:38 pm

I just had another failure updating Nuke Sentinel. phpMyAdmin says the version numer is rn2.40.00 in the nuke_config table. The nuke_nsnst_config is missing the config_name column completely the config_value column is there. When I ran the script it did not update. If I go to the Sentinel admin page for the site no version number is displayed. The rest of the upgrade seems to be working just fine. I am assuming I messed up somehow. Content Plus is there. Projects is there. NukeNav is working. Everything else seems to have installed just fine. Any ideas? Many thanks in advance.

RavensScripts

fkelly · Posted: Tue Sep 22, 2009 7:52 pm

Looking back through the thread I would recommend that you install Nuke Sentinel from scratch using the latest version 2.6.03.

jlajax · Posted: Wed Sep 23, 2009 8:15 pm

Question...

I just discovered a rn2.0.0 site that I have never upgraded. I just finished upgrading to 2.4 and all went very smoothly. If I extract the nuke_nsnst_config from the back up data base that I made before I upgraded and insert it into the site that Nuke Sentinel didn't upgrade and then try and run the upgrade script will that work? The version in the site that failed is the same as the version tht was in RN 2.0 I believe.

I am thinking that extracting the nuke_nsnst_config file from that DB and adding it to the one that is missing the config_name column will repair what I percieve to be wrong and enable the update script to do its thing.. I figured I would ask you folks who are so much more savvy than I if this is an idea that will work rather than trying it and making things worse..

RavensScripts

fkelly · Posted: Thu Sep 24, 2009 7:38 am

Just back up your current table first. Using Phpmyadmin you could rename it. Then try what you suggest. At first I was thinking you were just missing one "record" but the nsnst_config table is made up of config_name and config_value pairings so if you are missing the config_name field then your current table is fouled up beyond recognition. I'd just keep a renamed version on your system for reference purposes.

♠

jlajax · Posted: Sat Sep 26, 2009 2:25 am

Yeah Man that worked fine. All is well.!

RavensScripts