CUBE is not initialised
version 2.1. b2
error doing backup
what do I do ? thnx
version 2.1. b2
error doing backup
what do I do ? thnx
#3471 CUBE is not initialised
Posted in ‘UNiTE and Remote CLI’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
PHP version
n/a
Tool
UNiTE
Tool version
n/a
Latest post by user1796 on Thursday, 12 February 2009 05:49 CST
Sunday, 08 February 2009 05:06 CST
user1796
Sunday, 08 February 2009 09:11 CST
dlb
Please set your JoomlaPack log level to "All information and debug" and retry your backup. When it fails, please view the log, download it, zip it and post it here. That will give us a little more information to go on.
Dale
Dale
Dale L. Brackin
Support Specialist
English: nativePlease keep in mind my timezone and cultural differences when reading my replies. Thank you!
????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)
Sunday, 08 February 2009 10:56 CST
user1796
here you have
thanx
thanx
Monday, 09 February 2009 02:16 CST
dlb
JoomlaPack keeps a sort of bookmark in a temporary table that tells it what the next step in the process will be. This bookmark became corrupted, JoomlaPack lost it's place and this resulted in the CUBE not initialized error. That's the what, but I don't know why. I'll ask Nicholas to take a look and see what he can find.
Dale
Dale
Dale L. Brackin
Support Specialist
English: nativePlease keep in mind my timezone and cultural differences when reading my replies. Thank you!
????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)
Monday, 09 February 2009 03:06 CST
user1796
ok.. thank you anyway!
could it solve something if I go to 2.0?
could it solve something if I go to 2.0?
Monday, 09 February 2009 03:55 CST
dlb
I don't know why the record in the database is getting corrupted, so I really can't give you a good answer on that. There is no known error in 2.1.b2 in that table. If you are in a hurry, you can try 2.0.1, but I can't guess if it will be better.
Dale
Dale
Dale L. Brackin
Support Specialist
English: nativePlease keep in mind my timezone and cultural differences when reading my replies. Thank you!
????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)
Monday, 09 February 2009 23:16 CST
nicholas
Akeeba Staff
Manager
Please make sure that the "Force database keep-alive during long operations" option in the Advanced pane is enabled. You should also set the "Database Backup Algorithm" and "File Packing Algorithm" to "Smart", but make sure that you change the "Maximum operations per step" to 5.
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!
Tuesday, 10 February 2009 10:14 CST
user1796
thanx for your help
I did what you said (settings)
but the same message error
The backup operation has been halted because an error was detected.
"CUBE is not initialised"
anyway.. the precess is very very long..
thanx in advance
I did what you said (settings)
but the same message error
The backup operation has been halted because an error was detected.
"CUBE is not initialised"
anyway.. the precess is very very long..
thanx in advance
Wednesday, 11 February 2009 06:37 CST
nicholas
Akeeba Staff
Manager
OK, there's another thing I can still think of... What is the collation of the jos_jp_packvars table's fields? This error could happen if your database server erroneously used a weird collation, like latin1_swedish_ci, instead of the correct utf8_general_ci. In this case, a filename containing non-ASCII characters (e.g. accented, Cyrillic, Greek etc characters) could cause the CUBE to be stored erroneously in the database.
I am updating JoomlaPack for its 2.1 stable release to automatically work around this potential problem by using Base64 encoding for temporary data (which should work irrespectively of the collation of the database fields).
I am updating JoomlaPack for its 2.1 stable release to automatically work around this potential problem by using Base64 encoding for temporary data (which should work irrespectively of the collation of the database fields).
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!
Wednesday, 11 February 2009 10:33 CST
user1796
ok, I will wait for the next relaese as I don't know how to manage with tables
thnx
thnx
Thursday, 12 February 2009 05:20 CST
nicholas
Akeeba Staff
Manager
Or you can try an SVN release from the Bleeding Edge, our unofficial SVN builds repositories. Just give me 24 hours in order to update it with the latest release. Thanks!
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!
Thursday, 12 February 2009 05:49 CST
user1796
thank to you! ;)