Anyone willing to test some things for me?

Started by [Unknown], October 17, 2004, 01:22:35 AM

Previous topic - Next topic

[Unknown]

#40
It cannot create one gzip file (.sql.gz) unless it waits until it has the entire data to compress.  You can't just compress it in chunks and slap them together :P.

The error you got was a MySQL version difference, and caused the topics table not to be created :/.

Errors refer to batches.  I would edit the database dump, and copy out all the topics table information.  Then I would edit the CREATE TABLE for the topics table to be compatible with the MySQL on your new server.

> I noticed that the progress bar isn't very reliable
It SAYS it's not reliable.  It gives you an approximate idea, but if it were to be even somewhat more accurate, the database dumping itself would take about twice as long.  Obviously, you cannot do it by bytes without calculating how many bytes there are to do.  The whole freaking point of this utility is not to waste time on that.

Pulling it from a URL is possible, yes.  Just use the http://.... URL.

But, like I said... the errors you got with the topics table are not the backup or restore's fault.

-[Unknown]

Anguz

#41
Quote from: [Unknown] on December 21, 2004, 09:45:34 PM
It cannot create one gzip file (.sql.gz) unless it waits until it has the entire data to compress. You can't just compress it in chunks and slap them together :P.

Yes, I can understand that, I just didn't think about it much at first and thought that the gzipped version would require little free space. About the chunks thing I suggested, I was talking about creating and gzipping them separately, not putting them together.

Quote from: [Unknown]
The error you got was a MySQL version difference, and caused the topics table not to be created :/.

Errors refer to batches. I would edit the database dump, and copy out all the topics table information. Then I would edit the CREATE TABLE for the topics table to be compatible with the MySQL on your new server.

I got the topics table out, but am not sure what to change to make it compatible. My server is running MySQL 4.0.22-standard. This is the table creation code from the dump:


DROP TABLE IF EXISTS `yabbse_topics`;

CREATE TABLE `yabbse_topics` (
  `ID_TOPIC` int(11) NOT NULL auto_increment,
  `ID_BOARD` int(11) NOT NULL default 0,
  `ID_MEMBER_STARTED` int(11) NOT NULL default 0,
  `ID_MEMBER_UPDATED` int(11) NOT NULL default 0,
  `ID_FIRST_MSG` int(11) NOT NULL default 0,
  `ID_LAST_MSG` int(11) NOT NULL default 0,
  `ID_POLL` int(11) NOT NULL default -1,
  `numReplies` int(11) NOT NULL default 0,
  `numViews` int(11) NOT NULL default 0,
  `locked` tinyint(4) NOT NULL default 0,
  `notifies` text,
  `isSticky` tinyint(4) NOT NULL default 0,
  PRIMARY KEY (`ID_TOPIC`),
  KEY `notifies` (`notifies`)
) TYPE=MyISAM;


Looking at the MySQL manual, the error seems to be obviously related to this:
13.2.6 CREATE TABLE Syntax
Quote
When indexing a BLOB or TEXT column, you must specify a prefix length for the index. For example:

CREATE TABLE test (blob_col BLOB, INDEX(blob_col(10)));

Prefixes can be up to 255 bytes long (or 1000 bytes for MyISAM and InnoDB tables as of MySQL 4.1.2). Note that prefix limits are measured in bytes, whereas the prefix length in CREATE TABLE statements is interpreted as number of characters.

So the line I have to modify is that, but what to? Would this be right?

  KEY `notifies` (`notifies`(255))


Quote from: [Unknown]
> I noticed that the progress bar isn't very reliable
It SAYS it's not reliable. It gives you an approximate idea, but if it were to be even somewhat more accurate, the database dumping itself would take about twice as long. Obviously, you cannot do it by bytes without calculating how many bytes there are to do. The whole freaking point of this utility is not to waste time on that.

I didn't say "I hate your tool for not being accurate!" I just made an observation and am aware that it's not very important. I think you utility rocks and is really helping me here.

Quote from: [Unknown]
Pulling it from a URL is possible, yes. Just use the http://.... URL.

Ah.. I assumed it had to be in the same account. Thanks.

Quote from: [Unknown]
But, like I said... the errors you got with the topics table are not the backup or restore's fault.

Ok. I didn't think it was, since everything else went just fine. I did think that you would probably know how to prevent this kind of error though, like figuring out how to create the table depending on MySQL's version. Again, I'm not criticizing.
Cristián Lávaque http://cristianlavaque.com

[Unknown]

KEY `notifies` (`notifies`(30))

Should be fine.  Or just no key at all.  I'm curious... the server you're moving from, what version of MySQL was it?  If you do:

SHOW CREATE TABLE yabbse_topics;

What do you get?

-[Unknown]

Anguz

Quote from: [Unknown]
KEY `notifies` (`notifies`(30))
Should be fine. Or just no key at all.

Is 30 for lenght enough? I thought it had to be much larger... Wouldn't not having the key, make it slower? Not that it bothers me much, I'm planning to upgrade this forum to SMF in a few days anyway. I've been really neglecting it lately, since the other December. :P

Quote from: [Unknown]
I'm curious... the server you're moving from, what version of MySQL was it?  If you do:
SHOW CREATE TABLE yabbse_topics;
What do you get?

It's the same MySQL version: 4.0.22-standard.

The query returns

CREATE TABLE `yabbse_topics` (
`ID_TOPIC` int(11) NOT NULL auto_increment,
`ID_BOARD` int(11) NOT NULL default '0',
`ID_MEMBER_STARTED` int(11) NOT NULL default '0',
`ID_MEMBER_UPDATED` int(11) NOT NULL default '0',
`ID_FIRST_MSG` int(11) NOT NULL default '0',
`ID_LAST_MSG` int(11) NOT NULL default '0',
`ID_POLL` int(11) NOT NULL default '-1',
`numReplies` int(11) NOT NULL default '0',
`numViews` int(11) NOT NULL default '0',
`locked` tinyint(4) NOT NULL default '0',
`notifies` text,
`isSticky` tinyint(4) NOT NULL default '0',
PRIMARY KEY  (`ID_TOPIC`),
FULLTEXT KEY `notifies` (`notifies`)
) TYPE=MyISAM


That's odd, if it's invalid for this MySQL version, why does it show the result without the length?
Cristián Lávaque http://cristianlavaque.com

[Unknown]

FULLTEXT?!?!?  I guess my backup utility doesn't support FULLTEXT...

(but why in the world do you have a full text key there??!)

-[Unknown]

Anguz

Quote from: [Unknown] on December 22, 2004, 03:56:15 AM
FULLTEXT?!?!? I guess my backup utility doesn't support FULLTEXT...

(but why in the world do you have a full text key there??!)

-[Unknown]

To tell the truth,  I haven't got a clue.
Cristián Lávaque http://cristianlavaque.com

Anguz

I finished restoring the missing table.

In general, I'd say your scripts are just awesome. ;)
Cristián Lávaque http://cristianlavaque.com

[Unknown]

Test please.  I can't seem to figure out why, but the YaBB converter doesn't do read topic data *completely* right.  Everything else is good, though.

Please report any timeouts.

Thanks,
-[Unknown]

Jerry

, with the backup restore/create scripts I now have a new problem. creating a backup works fine.. but restoring a database gives a small error:
QuoteSome of the queries were not executed properly. Technical information about the queries:
Line #15790: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ''L 11/06/2004 - 15:36:07: Log file started (file "logs\\L1
Line #15892: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'joined team "CT"', 'xx'),
(4379, 372, 14, 1099863449
Everything seems to have been restored from looking at phpmyadmin. Is this anything I should worry about?


- Jerry
Find me on:
Facebook
Twitter
PlanetSMF

"If all you look for is the negative in things, you will never see the positive."

[Unknown]

Can you post those lines of the backup file?

-[Unknown]

Jerry

lhere is line 15790 http://www.raclan.org/15790.txt

and here is (on and around 15892)
QuoteINSERT INTO `smf_messages`
   (`ID_MSG`, `ID_TOPIC`, `ID_BOARD`, `posterTime`, `ID_MEMBER`, `subject`, `posterName`, `posterEmail`, `posterIP`, `smileysEnabled`, `modifiedTime`, `modifiedName`, `body`, `icon`)
VALUES (4493, 384, 51, 1100103551, 21, 'Re: want to join your clan', 'Jimmy', '[email protected]', '81.229.77.158', 1, 0, NULL, 'Yeah, in my opinion this is our VERY last CS player!', 'xx'),
the INSERT INTO `smf_messages` doesn't look good in the second error..


- Jerry
Find me on:
Facebook
Twitter
PlanetSMF

"If all you look for is the negative in things, you will never see the positive."

[Unknown]

Strange, I don't see anything wrong with those lines.

Can phpMyAdmin read it?

-[Unknown]

Jerry

yes, worked fine with phpMyAdmin :). Amazing though, usually it times out :P


- Jerry
Find me on:
Facebook
Twitter
PlanetSMF

"If all you look for is the negative in things, you will never see the positive."

[Unknown]

Quote from: Jerry on January 21, 2005, 11:24:57 AM
yes, worked fine with phpMyAdmin :). Amazing though, usually it times out :P

Would you be willing to email me the entire file ([email protected]) so I can figure out what is going wrong?

-[Unknown]

Jerry

I have sent you the email, don't know if hotmail send it though :-X


- Jerry
Find me on:
Facebook
Twitter
PlanetSMF

"If all you look for is the negative in things, you will never see the positive."

Tomer

[Unknown], great scripts, anyway to email the file to an email instead of saving it.

- Thanks

[Unknown]

No.  It at least needs a temporary location to save the file, if nothing else.

-[Unknown]

Eagle1

Ok I input all the info from repair_settings.php into create_backup.php and I get this meaage:

Cannot connect to the MySQL database server with the supplied data.

If you are not sure about what to type in, please contact your host.


Also I tried a backup of my forum create from the admins panel on 03-04-2005 and tried using restore_backup.php and get these messages

Warning: Unknown(): open(d:\php\sessiondata\sess_21badb8b0625361069fb2d030ce5c83b, O_RDWR) failed: Permission denied (13) in Unknown on line 0

Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save [nofollow]_path is correct (d:\php\sessiondata) in Unknown on line 0



Also my forum will not display and has not since right after the backup on the 4th I am trying to make sure I have a good backup for a reinstall as we have had some problem as of late. Member are getting restless and starting to send nasty emails pleases help!!

[Unknown]

Quote from: Eagle1 on March 05, 2005, 05:06:39 AM
Cannot connect to the MySQL database server with the supplied data.

If you are not sure about what to type in, please contact your host.

Are you entirely certain the password you used corresponded properly with the MySQL (not SMF!) account you specified?

Quote
Warning: Unknown(): open(d:\php\sessiondata\sess_21badb8b0625361069fb2d030ce5c83b, O_RDWR) failed: Permission denied (13) in Unknown on line 0

Warning: Unknown(): Failed to write session data (files). Please verify that the current setting of session.save_path is correct (d:\php\sessiondata) in Unknown on line 0

Contact your host about these errors.  Either SYSTEM or IUSR_COMPUTERNAME needs write access to d:\php\sessiondata and the files within.

Really sorry for responding later than I meant to... so many posts I end up missing the important ones sometimes :/.

-[Unknown]

Slack

Backedup from Mysql version 4.1.9-log  and resotred to 4.0.2.3  and I get these errors.... which don't look good at all. :(

Some of the queries were not executed properly. This could be caused by an unsupported (development or old) version of MySQL.

Technical information about the queries:
Line #369: BLOB column 'caption' used in key specification without a key length
Line #632: Table 'blooz_bloozbox.gallery_pictures' doesn't exist
Line #669: Table 'blooz_bloozbox.gallery_pictures' doesn't exist
Line #977: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'option varchar(50) NOT NULL default '',
ordering int(11) NOT
Line #1012: Table 'blooz_bloozbox.mos_components' doesn't exist
Line #1099: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'mediumtext NOT NULL default '',
state tinyint(3) NOT NULL def
Line #1121: Table 'blooz_bloozbox.mos_content' doesn't exist
Line #66908: BLOB column 'text' used in key specification without a key length
Line #66922: Table 'blooz_bloozbox.smf_quotes' doesn't exist

2nd try -- exact same errors. 

Advertisement: