Akeeba Backup for Joomla!

Friday, 18 November 2011 05:14 CST

user9084

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 1.6.6
PHP version: 5.2.17
MySQL version: 5.1.41
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.3.6

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

Description of my issue:
We are about to upgrade this site to Joomla 1.7.x and need to backup and restore it beforehand.
when trying to accsess the site (both front- and back-end) we recive the following message:
Table 'joomlared3_.SunditThree_session' doesn't exist SQL=INSERT INTO `SunditThree_session` (`session_id`, `client_id`, `time`) VALUES ('63311b786d56cc7118a591fbb47ee121', 0, 1321613596)

where joomlared3_ is the database and SunditThree_ is the suffix

The tabel _session does exist and is empty!

Loocking forward to hear from you
Regards
Jan

Friday, 18 November 2011 05:18 CST

nicholas

I can see two potential problems an also think of a third one.

1. Your database name is a little strange. Can you try using a database name which only contains alphanumeric (a-z, 0-9) characters?

2. The table name prefix has two problems. It's very long and contains lower and upper case letters. I'd recommend sticking with a short prefix (3-5 character and an underscore) which only uses lowercase latin letters and/or numbers.

3. There is an off-chance that your database is corrupt. The easiest way around it is to delete the database and create a new one.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 06:01 CST

user9084

Hi,
I have now changed database name and the table name prefix and also created a new database.
Unfortunately the problem remains :

Table 'kontroll.sund_session' doesn't exist SQL=INSERT INTO `sund_session` (`session_id`, `client_id`, `time`) VALUES ('b94eb1960e50a1f90894db8de29e35b4', 0, 1321617451)

I read something about an issue in 1.6 simular to this

Friday, 18 November 2011 06:06 CST

nicholas

If you try typing this SQL command in phpMyAdmin, do you get an error message?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 06:13 CST

user9084

I am afraid that we now are on the verge of my knowledge.
Can you please help me specify the sql question.
I can then try to run the command.

Friday, 18 November 2011 06:15 CST

nicholas

Look at the error message you paster. As it reads, in plain English, the SQL command it was trying to run was

INSERT INTO `sund_session` (`session_id`, `client_id`, `time`) VALUES ('b94eb1960e50a1f90894db8de29e35b4', 0, 1321617451)

So, what I'm saying is, can you try to run this command manually from phpMyAdmin's SQL tab? Do you see an error message or something?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 06:20 CST

user9084

after runing:
SQL=INSERT INTO `sund_session` (`session_id`, `client_id`, `time`) VALUES ('b94eb1960e50a1f90894db8de29e35b4', 0, 1321618602)

i get this response:

#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 'SQL=INSERT INTO `sund_session` (`session_id`, `client_id`, `time`) VALUES ('b94e' at line 1

Friday, 18 November 2011 06:23 CST

nicholas

Read my post above. Did I mention putting "SQL=" before the SQL command? Nope. Retry WITHOUT the "SQL=" prefix ;)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 07:32 CST

user9084

Hi again,
after trying to correct as above I checked the tables and realies that the Akeeba doesn't create any tables with the new prefix. thus, all tables are still with the"sundittwo_ suffix!

Then checking the configuration.php i notice that it hasnn't owerwriten old database name, pw.
After manualy editing it all, I made it work

Thank you for your help anyway

Regards
Jan

Friday, 18 November 2011 07:47 CST

nicholas

Hello Jan,

This reminds me of a bug in Akeeba Backup 3.0.something which I fixed about 20 months ago. Which version of Akeeba Backup did you use to produce your backup? Are you sure you are using the latest release (3.3.6 at the time of this writing)? I have not been able to replicate this issue with Akeeba Backup Core 3.3.6 on various server configurations I have access to. Furthermore, nobody else has reported something like that with any stable release in the 3.3.x series.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 07:51 CST

user9084

I remember having that problem with earlier versions. This backup, however, is taken with 3.3.6
Regards
Jan

Friday, 18 November 2011 08:21 CST

nicholas

I can understand the part about the configuration.php not being updated. If the file is not writable, it's not updated and a warning (which most users dismiss without reading first) is displayed in a modal popup. But the part of not updating the prefix when restoring the tables, this can only happen if you forget to change the prefix in Akeeba Backup Installer's second step.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 18 November 2011 08:26 CST

user9084

neater can I, but I can enshure you that I have, many times, read the modal, and then deleted the server settings. So I did this time.
If you come up with any ideas of what had happend, please let me know.

regards
Jan

Friday, 18 November 2011 08:29 CST

nicholas

Unless I get to run the restoration myself, very carefully, I can't know if it's something ABI warned you about or something went wrong. I tend to believe it's the former, because logic says that if it were a bug, someone would have already reported it (the restoration script's code hasn't changed for over 9 months).

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support