Support

Hello,

I have 2 joomla sites and both upgraded with joomlapack v2.3. By one site it works well.
By the other site is a problem with restoring the database. That site is a joomlasite with a PHPBB forum.
They use the same database. For joomla with prefix "jos_" and for the forum with prefix "phpbb_".
With earlier versions It was no problem to restore, but now I get the error message while restoring.
See the screenshot.



I hope someone can help me with it...

Thanks,
Marco.

Sorry for my bad English, I'm Dutch... :D

Your English is fine, but your screen shot cut off the error message at the bottom. :D Please give me the error message after the second CREATE TABLE command.

Thanks for your compliment and your fast reaction. ;)

I send 2 images extra, so you have the complete error maessage.

Yesterday evening I tried to backup with excuding the PHPBB tables and that works fine.
I like to backup the complete site, including the PHPBB tables.

The rest of the error message:




I hope you can find the problem.

Regards,
Marco.

Marco,

I see the problem. It looks like a part of the joomla.sql file, the database dump, is missing. I need to see that file if possible. I will send you a PM.

Marco,

The good news is that the file itself looks fine. The damaged line that caused the error is correct in the database dump file. It must have been a error when the file was read by the installer.

The bad news is that I can't fix it. This error has to go to Nicholas. He is on vacation this week, he'll be back on Sunday.

If this is a restore that has to be done, we can do it manually, but we will have to wait for Nicholas to get the installer to work.

Hi Dale,

Thanks for you reply.
It is not a restore that has to be done, it was to put the website on a local host for testing.

But I'm used to make on a regular base backups with joomplapack, because there are a few people how produces articles for the site.

I wait till Nicholas is back.
Till then I will make backups without the PHPBB tables.

Regards,
Marco.

[strike]Hi,

I have the same MySQL 1064 error but I cant wait till sundays, I have to complete the site transfer before thursday, is there a possibility i can manualy install my backup? I have an empty domain where it should be put on.

Thanks in advance,
Raoul[/strike]

EDIT:

somehow the problem solved itself and a new problem came up, i no longer get the error but kickstart hsa run only a robot.txt is in my directory

i have a similar problem. i cant restore my site. Its a live community website and its currently down! please help.

im trying to restore using JPI4 kickstart 2.3 and i get a database error for my civicrm tables and i can't even proceed further. to make matters worse my entire database has been dropped and i can only rely on this single joomlapack backup.

when i use the extract wizard the program gets stuck on "logs/g2bridge.log" every time. i get an error warning saying invalid archive format.

please what do i do?

update: i only have two joomlapack .jpa backups my previous post was regarding the latest one. so i tryed the older backup and this was the error i got (not civicrm related.

Error at the line 310: CREATE TABLE `wiki_categorylinks` ( `cl_from` int(8) unsigned NOT NULL default '0', `cl_to` varchar(255) character set utf8 collate utf8_bin NOT NULL default '', `cl_sortkey` varchar(86) character set utf8 collate utf8_bin NOT NULL default '', `cl_timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, UNIQUE KEY `cl_from` (`cl_from`,`cl_to`), KEY `cl_sortkey` (`cl_to`,`cl_sortkey`), KEY `cl_timestamp` (`cl_to`,`cl_timestamp`) );



Query:CREATE TABLE `wiki_categorylinks` ( `cl_from` int(8) unsigned NOT NULL default '0', `cl_to` varchar(255) character set utf8 collate utf8_bin NOT NULL default '', `cl_sortkey` varchar(86) character set utf8 collate utf8_bin NOT NULL default '', `cl_timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, UNIQUE KEY `cl_from` (`cl_from`,`cl_to`), KEY `cl_sortkey` (`cl_to`,`cl_sortkey`), KEY `cl_timestamp` (`cl_to`,`cl_timestamp`) );



MySQL: MySQL query failed with error 1071 (Specified key was too long; max key length is 1000 bytes). The query was:CREATE TABLE `wiki_categorylinks` ( `cl_from` int(8) unsigned NOT NULL default '0', `cl_to` varchar(255) character set utf8 collate utf8_bin NOT NULL default '', `cl_sortkey` varchar(86) character set utf8 collate utf8_bin NOT NULL default '', `cl_timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, UNIQUE KEY `cl_from` (`cl_from`,`cl_to`), KEY `cl_sortkey` (`cl_to`,`cl_sortkey`), KEY `cl_timestamp` (`cl_to`,`cl_timestamp`) );

i reattempted the same restore, now i get this error.

AJAX error:

parsererror(undefined)



Raw Data:

now what do i do, i getting a little paranoid here.

@krahk - can you see the file counter increasing while the files are extracted? How big is your archive file?

@fezzicnex - your CREATE TABLE is a bug in MySQL, see Nicholas' comments here.

civicrm uses foreign keys and innoDB. That shouldn't be a problem any more, the foreign key checks are turned off during restore now. Are you restoring to the same version of MySQL that you backed up from?

What are you using to get an xml error during restore?

this is what i did. since the older backup got me to restore all the files on my site, i edited the joomla.sql file in the installation folder to remove the trouble with the wiki create table. then once every was a go i logged into the phpmyadmin and create the table like nicholas said in the link you provided me.

so now that i restored the site (not to its latest version (which ill ask you about in another post) when i log in through the frontend of the site i get this error

Not Found



The requested URL /component/comprofiler/login.html was not found on this server.



Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Apache/2.2.11 (Unix) mod_ssl/2.2.11 OpenSSL/0.9.8k DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.pisigmachi.com Port 80

But as soon as i turn off the Joomla SEF URLs i can login fine. i think my htaccess file got screwed up. is there anyway i can fix this?

indeed it was my htaccess file i just recreated it. no biggie.

however, i dont know if this was a restoration problem because i was not aware of this link not working prior to the restore. but my member list for community builder has a database problem. and i am not familiar with a debug screen, i dont know what these errors mean. So can you help me out or point me in the right direction?

@fezzicnex - What version of JoomlaPack are you using? There was a bug in 2.3.b1 that would damage the CB data files during restore. It had something to do with the table prefix (jos_) being used in data fields and being replaced with the place holder (akb_). We had several reports of this and got it figured out just before 2.3 stable was released.

the backup that worked was taken august 1st so I would only assume that it was done with 2.3.b1 since the stable release came out on august 7th.

Now what do I do? the backup I wanted to restore from (which had backed up successfully in 2.3.stable w/o errors or warnings) is apparently a bad file because I cant restore it or extract it.

Is there anything I can do to fix the database file? Since I don’t have a separate sql backup, only those two .jpa’s.

I hate it, absolutely hate it when I can't save a backup. Don't count me out. :D

The problem with the 08/01 backup is not in the database dump, that is fine. The problem is in the installer, which will damage the data if we use it to restore. Good backup, bad installer. So we replace the installer.

Put the backup archive on the site and extract it. Don't install it. Delete the contents of the /installation folder and the subfolders EXCEPT for the /installation/sql folder and it's contents. Replace with the contents of the attached zip file. This is the JPI4 installer from the 2.3. stable release. Point your browser to the site address and you'll be redirected to the install script. You'll need to delete the /installation folder manually when the install is complete. installation-20090812.zip

i tryed that (exactly as you described). but im still getting that same error i sent in that screen capture.

how could it not be the database dump or the 2.3 stable installation folder?

Hi dlb,

Here I am again (the starter of this topic).
I have tried a lot of things for a good restoring and there is a way I can restore the total site, including the PHPBB tables. This is what I did:

1- make a backup of the site, excluding the PHPBB tables
2- make a seperate backup of the total database (including the PHPBB tables)

3- Restore the backup of the site (without the PHPBB tables)
4- Go to the PHPMyAdmin and delete the database
5- Import in PHPMyAdmin the database, which is backuped in step 2.

Now the site is working, but I don't think this is the way you had planned while making Joomlapack. ;)

I hope this will help you to find a solution for the problem.

By the way: The remote backup is a wonderfull tool, so different people can make a backup of our site, so we have it on different places.. But the restoring of the whole site has to be OK :roll: :D

Regards,
Marco.

Marco - It isn't supposed to be that hard. :(

@fezzicnex - Sorry for the delay, I had to install CB and 2.3.b1 locally to see what was happening with the data. The jos_comprofilere_fields table includes table names with "akb_" table prefixes as data. When JoonmlaPack does the full site database backup, it changes the table prefixes from jos_ to akb_, this is to aid in changing the prefixes during the restore. So at the end of the backup, we have CB storing table names as data with the akb_ prefixes, and JoomlaPack has all the actual table names with akb_ prefixes. During the restore with 2.3.b1, JoomlaPack did a "search and replace" searching for akb_ and replacing with jos_ (or your table prefix). That isn't technically accurate, but close enough for our discussion. That messed up CB's data. The 2.3 stable only changes the akb_ prefixes in the MySQL commands, not the data portion. So the 2.3.b1 backed up data is not trashed, it can be restored. It does take special handling and our manual restore instructions are not correct for this new situation. We now need to[ul][li]search for "CREATE TABLE `akb_" replace with "CREATE TABLE `jos_"[/li]
[li]search for "DROP TABLE IF EXISTS `akb_" replace with "DROP TABLE IF EXISTS `jos_"[/li]
[li]search for "INSERT INTO `akb_" replace with "INSERT INTO `jos_"[/li][/ul]Those instructions don't take into consideration views, but I don't have an example in my test data to know the format.

Nicholas,

I'm the starter of this topic and had contact with Dale about the error-messages (see the first topics).

Please, will you contact me about the problem?
The PHPBB tables will not restore at one time.

I hope you have a bit time for looking at this problem.

By the way: Did you had a nice holliday... ;)

Marco.

hello,

i have the same problem here. I made a backup with version 2.3. on the domain/concept site and then tried to restore it in the domain path (so from concept to production) however, kickstart (all versions...) give me the error :

Error at the line 0: CREATE TABLE `jos_aicontactsafe_config` ( `id` int(11) unsigned NOT NULL auto_increment COMMENT 'config id', `config_key` varchar(50) NOT NULL default '' COMMENT 'the key of the config variable', `config_value` text NOT NULL COMMENT 'the value of the config variable', PRIMARY KEY (`id`) ) ENGINE=MyISAM AUTO_INCREMENT=14 DEFAULT CHARSET=utf8 COMMENT='Configuration table of aiContactSafe';

Query:CREATE TABLE `jos_aicontactsafe_config` ( `id` int(11) unsigned NOT NULL auto_increment COMMENT 'config id', `config_key` varchar(50) NOT NULL default '' COMMENT 'the key of the config variable', `config_value` text NOT NULL COMMENT 'the value of the config variable', PRIMARY KEY (`id`) ) ENGINE=MyISAM AUTO_INCREMENT=14 DEFAULT CHARSET=utf8 COMMENT='Configuration table of aiContactSafe'

MySQL: MySQL query failed with error 1064 (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 'lir_ATE TABLE `jos_aicontactsafe_config` ( `id` int(11) unsigned NOT NULL auto' at line 1). The query was:lir_ATE TABLE `jos_aicontactsafe_config` ( `id` int(11) unsigned NOT NULL auto_increment COMMENT 'config id', `config_key` varchar(50) NOT NULL default '' COMMENT 'the key of the config variable', `config_value` text NOT NULL COMMENT 'the value of the config variable', PRIMARY KEY (`id`) ) ENGINE=MyISAM AUTO_INCREMENT=14 DEFAULT CHARSET=utf8 COMMENT='Configuration table of aiContactSafe'

PLease please please help me, the only backup I have is the backup file....

Kind regards

Barry

thank you nicholas. but how can you be sure that this is not a problem that resulted in my restoration through joomlapack? if it was working prior what would the variable be that made this error occur?

What do you mean by

My guess: the MySQL version you backed up from and the MySQL version you restored to are not compatible

Also i didnt change any list or create a custom field, "username" is the standard jos_users field referenced by community builder.

i just want to be sure i have all my ammo (so to speak) before i go over to joomlapolis website about this (cause they already blamed joomlapack).

finally, nicholas can you split this forum because from marco 007 "tone" he doesnt sound too happy i post in "his thread"

or...

can i unpack the backup file somehow and can i find the database tables in it ? so i can restore them manually?

hope so much you can help me ?

Kind regards,

Barry

@fezzicnex - good idea to split the thread, but there is no obvious way to do it. It will take some research on the Kunena forum.

@bsakkers - it isn't kickstart that is giving you the error, it is the installer code embedded in your backup. What version of the installer are you using?

Standard procedure when you are dealing with one irreplaceable backup file:[ol][li]Make a copy of the backup file, put it in a safe place.[/li][li]Go to step #1[/li][/ol]Yes, you can manually restore. The database dump file is /installation/sql/joomla.sql. It is not in a format that can be directly restored, it needs to be edited. The detailed instructions are here. Note that if you have Community Builder installed, the directions need to be modified. We discovered a problem a little over a week ago.

Nicholas,

What doe you mean with JP14 ?
I use JP2.3 stable, Dutch translation.

If you make a hotfix, where can I find it for download?

Thanks for answering (and the hotfix ;) )

Marco.

Hello there,

just wanted to let you know I solved my problem with the manual restore. Super instructions!

The cause of my problemen, however I haven't found yet.

Super forum this way with a fast reply by the operators, Thanks again for making my day :D

Kind regards,

Barry

nicholas,

the backup thats is working for me was taken w/ 2.3.b1 and restored using dale's installation folder from 2.3 stable both with JPI4.

im not clear on your last post, where do i go from here? will your hotfix help w/ my problem? can i get the user lists to work again?

The hotfix is coming, but it isn't ready yet. We expect it in the next couple of days. Since Nicholas referred to a "hotfix" as opposed to an SVN release, he's planning on putting it on the regular download page, there will be an announcement on the front page and your JoomlaPack Control Panel will notify you of the available update.

There aren't any changes posted to SVN yet, so I can't give yo any guesses about what changes will be in it.

Nicholas and dlb,

It works fine... the new hotfix! :D

I can now restore my site with the PHPBB tables.

Thank you for answering and supporting so fast.

Marco.