Ravens PHP Scripts: Forums
 

 

View next topic
View previous topic
Post new topic   Reply to topic    Ravens PHP Scripts And Web Hosting Forum Index -> v2.4 RN Issues
Author Message
dad7732
RavenNuke(tm) Development Team



Joined: Mar 18, 2007
Posts: 1242

PostPosted: Sat Oct 09, 2010 8:36 am Reply with quote

First of all, I plead guilty for not capturing any error message(s) Sad

The problem centers around all tables nuke_seo_xxxxx and only those.

I backed up a DB (mysql 4) to a .dump file using the mysql command line:

Code:
mysqldump -uuser -ppassword database > database.dump


Works just fine, no errors.

Then, I dropped the database in question and then used bigdump to restore after renaming the dump file to .gz which does work btw.

Bigdump proceeded to restore but stopped at nuke_seo_dh and would not proceed any further. Neither would trying the restore using the mysql command line function, stopped in the same exact spot.

I then edited the dump file, removing nuke_seo_dh_master but the bigdump stopped on seo_dh_feed. So then I removed ALL of the nuke_seo_xxx lines and this worked.

To get the nuke_seo_xxxx tables back, I fortunately had another site with basically the same database but on a php5 and mysql5 server. I then exported just the nuke_seo_xxxx tables choosing mysql4 compatibility and then restored that. That worked.

Also note that re-loading the core tables work but then all the tables are default.

So, what is wrong with those particular tables, any ideas? This isn't the first time I've encountered probles with those tables.
 
View user's profile Send private message
hicuxunicorniobestbuildpc
The Mouse Is Extension Of Arm



Joined: Aug 13, 2009
Posts: 1123

PostPosted: Sat Oct 09, 2010 8:49 am Reply with quote

can you post that table to take a look? I do know Bigdump doesn't like some this kind of line. I don't remember right now but post it here.

ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
 
View user's profile Send private message
dad7732







PostPosted: Sat Oct 09, 2010 9:04 am Reply with quote

Ok, dumping the table "nuke_seo_dh_master"

Code:
#

# Table structure for table `nuke_seo_dh_master`
#

CREATE TABLE nuke_seo_dh_master (
  mid int(11) NOT NULL auto_increment,
  order int(5) NOT NULL default '0',
  type varchar(50) NOT NULL default '',
  name varchar(50) NOT NULL default '',
  default varchar(255) NOT NULL default '',
  active int(1) NOT NULL default '0',
  PRIMARY KEY  (mid),
  KEY order (order)
) TYPE=MyISAM;

#
# Dumping data for table `nuke_seo_dh_master`
#

INSERT INTO nuke_seo_dh_master VALUES (1, 0, 'title', 'title', '$slogan', 1);
INSERT INTO nuke_seo_dh_master VALUES (2, 100, 'http-equiv', 'refresh', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (3, 200, 'http-equiv', 'Content-Type', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (4, 300, 'http-equiv', 'Content-Language', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (5, 400, 'http-equiv', 'Content-Script-Type', 'text/javascript', 1);
INSERT INTO nuke_seo_dh_master VALUES (6, 500, 'http-equiv', 'Content-Style-Type', 'text/css', 1);
INSERT INTO nuke_seo_dh_master VALUES (7, 600, 'http-equiv', 'Pragma', 'no-cache', 1);
INSERT INTO nuke_seo_dh_master VALUES (8, 700, 'http-equiv', 'Expires', '0', 1);
INSERT INTO nuke_seo_dh_master VALUES (9, 800, 'http-equiv', 'Ext-cache', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (10, 900, 'http-equiv', 'set-cookie', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (11, 1000, 'http-equiv', 'window-target', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (12, 1100, 'http-equiv', 'PICS-Label', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (13, 1200, 'http-equiv', 'Cache-Control', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (14, 1300, 'http-equiv', 'Vary', '', 0);
INSERT INTO nuke_seo_dh_master VALUES (15, 1400, 'name', 'ROBOTS', 'NOARCHIVE', 0);
INSERT INTO nuke_seo_dh_master VALUES (16, 1500, 'name', 'RESOURCE-TYPE', 'DOCUMENT', 1);
INSERT INTO nuke_seo_dh_master VALUES (17, 1600, 'name', 'DISTRIBUTION', 'GLOBAL', 1);
INSERT INTO nuke_seo_dh_master VALUES (18, 1700, 'name', 'AUTHOR', '$sitename', 1);
INSERT INTO nuke_seo_dh_master VALUES (19, 1800, 'name', 'COPYRIGHT', 'Copyright (c) 2009-2010 by $sitename', 1);
INSERT INTO nuke_seo_dh_master VALUES (20, 1900, 'name', 'DESCRIPTION', '$slogan', 1);
INSERT INTO nuke_seo_dh_master VALUES (21, 2000, 'name', 'KEYWORDS', 'news, technology, headlines, nuke, phpnuke, php-nuke, geek, geeks, hacker, hackers', 1);
INSERT INTO nuke_seo_dh_master VALUES (22, 2100, 'name', 'ROBOTS', 'INDEX, FOLLOW', 1);
INSERT INTO nuke_seo_dh_master VALUES (23, 2200, 'name', 'REVISIT-AFTER', '1 DAY', 1);
INSERT INTO nuke_seo_dh_master VALUES (24, 2300, 'name', 'RATING', 'GENERAL', 1);
INSERT INTO nuke_seo_dh_master VALUES (25, 2400, 'name', 'GENERATOR', 'RavenNuke(tm) Copyright (c) 2002-2010 by Gaylen Fraley. This is free software, and you may redistribute it under the GPL (http://www.gnu.org/licenses/gpl-2.0.txt). RavenNuke(tm) is supported by the RavenNuke(tm) Team at http://www.ravenphpscripts.com .', 1);



Is that what you need?

Mysql restoring from the command line didn't like that one OR the next one I posted as well as nuke_seo_subscriptions. The ones that did load were _dh and _disabled modules.


Last edited by dad7732 on Sat Oct 09, 2010 9:10 am; edited 1 time in total 
dad7732







PostPosted: Sat Oct 09, 2010 9:07 am Reply with quote

And next, wouldn't load this one:

Code:
#

# Table structure for table `nuke_seo_feed`
#

CREATE TABLE nuke_seo_feed (
  fid int(6) NOT NULL auto_increment,
  content varchar(20) NOT NULL default '',
  name varchar(20) NOT NULL default '',
  level varchar(20) NOT NULL default '',
  lid int(6) NOT NULL default '0',
  title varchar(50) NOT NULL default '',
  desc text NOT NULL,
  order varchar(20) NOT NULL default '',
  howmany char(3) NOT NULL default '',
  active int(1) NOT NULL default '0',
  desclimit varchar(5) NOT NULL default '',
  securitycode varchar(50) NOT NULL default '',
  cachetime varchar(6) NOT NULL default '',
  feedburner_address varchar(100) NOT NULL default '',
  PRIMARY KEY  (fid),
  KEY content (content,title)
) TYPE=MyISAM;
 
hicuxunicorniobestbuildpc







PostPosted: Sat Oct 09, 2010 2:13 pm Reply with quote

I checked it out and I tested myself on my server. It went ok with me. I tested with IE 8 and with FF 3.6 last version. everything went ok.
 
dad7732







PostPosted: Sat Oct 09, 2010 2:31 pm Reply with quote

What DB language and versions of PHP and MySql are you running? I'm thinking I have a compatibility problem but thats really last on the list because I backed up and restored with 30 minutes of each operation. Same dump, same DB, same everything.
 
hicuxunicorniobestbuildpc







PostPosted: Sat Oct 09, 2010 3:38 pm Reply with quote

I am running php 5.3 and the last version of Mysql.
 
dad7732







PostPosted: Sat Oct 09, 2010 5:23 pm Reply with quote

The problematic scenario was on my other server with PHP 4 and MySQL 4 .. dunno, quite puzzling with backup/restore in less than 30 mins apart.

Cheers
 
hicuxunicorniobestbuildpc







PostPosted: Sat Oct 09, 2010 6:21 pm Reply with quote

That is the problem. Bigdump is not compatible with php 4. That was the real problem I guess. Now u know.
 
dad7732







PostPosted: Sat Oct 09, 2010 6:34 pm Reply with quote

Not really, when bigdump didn't work I tried the standard command line mysql to restore, same problem.
 
dad7732







PostPosted: Sat Oct 09, 2010 7:08 pm Reply with quote

Interesting you say that BD isn't compatible with PHP 4 but it worked just fine after removing those nuke_seo_xxx lines from the dump file. The MySQL command line dump didn't restore either until removing the lines ... dunno.
 
Guardian2003
Site Admin



Joined: Aug 28, 2003
Posts: 6799
Location: Ha Noi, Viet Nam

PostPosted: Sun Oct 10, 2010 4:31 am Reply with quote

I could be completely wrong but...
This might be mySQL version specific i.e. the more recent versions might hiccup.
In the tablenuke_seo_dh_master I think the field order could be a MySQL reserved word, in which case you would need to enclose that field with back ticks;
Code:


CREATE TABLE nuke_seo_dh_master (
  mid int(11) NOT NULL auto_increment,
  `order` int(5) NOT NULL default '0',
  type varchar(50) NOT NULL default '',
  name varchar(50) NOT NULL default '',
  default varchar(255) NOT NULL default '',
  active int(1) NOT NULL default '0',
  PRIMARY KEY  (mid),
  KEY order (order)
) TYPE=MyISAM;

It's actually good practice when creating backups to use the "enclose fields with back ticks" options (not sure of the command line syntax for that) to prevent this kind of problem.

Likewise, the table nuke_seo_feed has a field desc which I think is a reserved word, so that will also likely need backticks.
 
View user's profile Send private message Send e-mail
Guardian2003







PostPosted: Sun Oct 10, 2010 4:35 am Reply with quote

I just looked it up to be sure and it seems I'm correct.
Here is a list of reserved words;
http://dev.mysql.com/doc/mysqld-version-reference/en/mysqld-version-reference-reservedwords-5-1.html
 
dad7732







PostPosted: Sun Oct 10, 2010 6:59 am Reply with quote

Ok, but ... Why would it hiccup when making the backup and then restoring to the same PHP/MySQL versions. Wasn't like backing up from MySQL-4 and the restoring to 5. This is the puzzle as I see it. The original files were core dumped in a MySQL-4 environment to begin with and in fact I did a new core installation from the 2.4.01 distro that worked. Just the backup/restore that didn't work - hiccuped at the SEO tables. And to make matters even more interesting, I restored the SEO tables from a working MySQL-5 installation to the 4 installation, same 2.4.01 distro, go figure.
 
Palbin
Site Admin



Joined: Mar 30, 2006
Posts: 2583
Location: Pittsburgh, Pennsylvania

PostPosted: Sun Oct 10, 2010 8:26 am Reply with quote

Did you compare the sql?

_________________
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." — Brian W. Kernighan. 
View user's profile Send private message
dad7732







PostPosted: Sun Oct 10, 2010 8:39 am Reply with quote

Not yet but I can. My point is that if the backup was on a DB under MySQL 4 and the restore was back to the same DB under MySQL 4, same site, etc. then why did it fail on the SEO tables but the restore from an export on another site under MySQL 5 work?

The backup was on the same server, same PHP and MySQL versions 4.x and 4.x .. Now, what COULD have happened is that the upgrade from 2.4 to 2.4.01 was the eventual culprit and if I remember correctly, the SEO tables didn't install correctly then and I made a post about that and the backticks was mentioned and Gaylen posted the table sql with the backticks that worked, etc.

So, there we are ... I think this is the solution. And now, I believe, if I back up the corrected DB tables, the restore should work accordingly. My very most important site is now on PHP5 and MySQL5, Linux instead of FreeBSD, so I shouldn't have any problems there when hopping to the next version(s). Wink

One lesson learned from this experience is that NEVER rely on a backup that was running on a previos version of PHP and MySQL to restore on a later version of each.

Cheers
 
Display posts from previous:       
Post new topic   Reply to topic    Ravens PHP Scripts And Web Hosting Forum Index -> v2.4 RN Issues

View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum


Powered by phpBB © 2001-2007 phpBB Group
All times are GMT - 6 Hours
 
Forums ©