installSQL.php error

Regular Joined: Jan 16, 2009 Posts: 91

I chose to upgrade from 2.3 version to 2.4. I am actually doing a fresh install instead. I seem that Raven or someone else wrote a wrong code in installSQL.php. You may look at this.

I clicked on step 3b.

Error said

The exact error message that your MySQL server reported is:
MySQL Error # 4 at line 117 in file installSQL.php ==> Duplicate entry '1401432064-1401434111-ie' for key 1

Error in ns_ip2c3.sql.gz at line 1:
INSERT INTO `nuke_nsnst_ip2country` (`ip_lo`, `ip_hi`, `date`, `c2c`) VALUES (1401432064, 1401434111, 1217134800, 'ie');

registered · Posted: Mon Aug 23, 2010 3:52 pm

Are you using the latest version, 2.40.01?

Posted: Mon Aug 23, 2010 4:14 pm

Yes, that's correct.

Posted: Tue Aug 24, 2010 5:29 am

Reporting errors of this nature without including server info php and mysql versions especially make it very difficult to... well to do anything.

In my case I had a failed install due to the latest PHP Version 5.3.2 date issues.
PHP 5.3 problem: Warning: date() [function.date]: It is not safe ...
I was able to quickly find a dirty hack to fix it but it was specific to my php version.

Posted: Tue Aug 24, 2010 9:50 pm

If you get to this point, It means that the base system sql tables have been populated, so your system must be usable at the moment. But is still weird that error message being displayed.

I'll have to try a fresh install when possible and then report back....

Posted: Wed Aug 25, 2010 8:44 am

FWIW, I did two fresh installs with the same PHP version 5.3.2 and no errors whatsoever. I wonder if dropping the IP2C table and then using the installSQL once again this time only loading those tables will work. I've done just that in the past with success.

Posted: Wed Aug 25, 2010 1:16 pm

Also wondering if the gzip may be problematic for whatever reason. I'm thinking of my problems with 5.3.2 and apache mods.

Posted: Wed Aug 25, 2010 2:28 pm

jestrella wrote:

If you get to this point, It means that the base system sql tables have been populated, so your system must be usable at the moment. But is still weird that error message being displayed.

I'll have to try a fresh install when possible and then report back....

Everything include SQL is fresh.

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

tourniqu3t, just to clarify, did you drop the tables first or install to a new database? Knowing that will help us determine how to address this.

Posted: Wed Aug 25, 2010 3:31 pm

Find your PHP.INI file and then look for the timezone setting:

For your timezone, edit the line or uncomment it, such as:

Code:




date.timezone = "America/New_York"

That's just an example.

Cheers, let us know how it turns out.

BTW: On new installs of PHP 5.3.2, the date line is usually commented out.

Posted: Wed Aug 25, 2010 10:41 pm

kguske wrote:

tourniqu3t, just to clarify, did you drop the tables first or install to a new database? Knowing that will help us determine how to address this.

I dropped all tables first before I start to install.

Everything is fresh. That's all I did.

Posted: Thu Aug 26, 2010 6:24 am

Have you tried the PHP.INI edit?? I'm thinking that will do it.

Mine is set to:

Code:

date.timezone="US/Central"

Posted: Thu Aug 26, 2010 6:51 am

dad7732 wrote:

Have you tried the PHP.INI edit?? I'm thinking that will do it.

Mine is set to:

Code:

date.timezone="US/Central"

dad7732 what is the reason you are asking him to do that?

Posted: Thu Aug 26, 2010 7:28 am

Because I googled the error and one of the fixes was to configure the correct timezone entry in PHP.INI

I think it's worth a shot anyways ..

Nevermind, I'm looking at the wrong reply .. Sad

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

A duplicate entry error usually means you tried loading the tables without dropping them first.

Posted: Sat Aug 28, 2010 12:05 am

Raven wrote:

A duplicate entry error usually means you tried loading the tables without dropping them first.

Ok, I will try again tomorrow morning.

Posted: Sun Sep 05, 2010 8:57 am

Sorry to keep you waiting for an answer from me. I struggled with upload. It's solved. And installSQL.php is successful now. Smile

New Member Joined: Nov 10, 2012 Posts: 4

Even though I read this and nothing seemed to help I remembered reading another thread talking about an SQL query limit that was set for some people 50,000 and others 75,000. I Know I'm set to 75,000. So, during installation, I load my top two sets first. Core tables sit at 833 instructions and NukeSentinel sit at 950.

Add and Subtract 833+950= 1783

75k-1783 = some odd number. I just decided to wait an hour for the query limit to reset so I would start of with an empty counter.

3a-3g have 20k instructions each. So, obviously I can only load 3 sets without going over. THAT being said. I think that's where people are running into the Duplicate entry problem. For example if you have a SQL query limit and you've already loaded 60k instructions (eg: 3a,3b,3c), wait 1 hour for your query limit to reset then start again. Otherwise, say you try to load 3d immediately after 3a,b,and c. Some instructions will load and once you hit your 75k cap it'll kick back the error. Now, unless you know what you need to delete, everything needs to be wiped from your db and started all over. This time just keep an eye on the clock, your instructions loaded, and know your limit.

This all is just my theory but it worked for me and finally got my wheels turning after a standstill for 3days lol Laughing

Hope this helps someone out in the future! Cool

registered · Posted: Sat Nov 17, 2012 9:44 am

Thanks sssstrick.

Or, find a better host that doesn't have these limitations or see if it would be possible that they bump that up or remove the restriction just for initial installation purposes.