Support

Akeeba Backup for Joomla!

#9186 s3 fail, & site periodically crashing since pro upgrade

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
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

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Thursday, 01 December 2011 01:07 CST

user34641
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? None related
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? S3 pages
Joomla! version: (unknown) 1.5.23
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you) hostgator
Akeeba Backup version: (unknown) latest pro

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:
When I do a backup I get this message:
AEUtilAmazons3::startMultipart(): [SignatureDoesNotMatch] The request signature we calculated does not match the signature you provided. Check your key and signing method.


Also, periodically my entire site is down since I have installed backup pro. There is an error message but I need to see it go down again to copy it.

nicholas
Akeeba Staff
Manager
Hi,

Your backup log tells me that you have a broken installation and you are not actually backing up your site. No file and database table ends up in the backup.

Please uninstall Akeeba Backup and then install Akeeba Backup 3.3.8 on your site. You will have to set it up again, but that's the only reliable way to fix a potentially broken installation of Akeeba Backup.

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!

user34641
Hi Nicholas,

I uninstalled and then reinstalled 3.3.8 and reconfigured. Tried a backup and exact same problem as above error message in quotes.

nicholas
Akeeba Staff
Manager
OK, since you haven't posted a new log file, I will try to go a little blind here.

The last tow times I saw this error was three days and five days ago, respectively. In the most recent case, the client had swapped his bucket and directory name. In the older case, the client had created a bucket in all capital letters (something like BUCKET), but he hadn't unchecked the "Lowercase bucket name" checkbox. Please check if you're doing the same thing yourself.

If you can't get it to work, please send me a Personal Message (I am user "nicholas") with the following information:
- URL to your site's administrator area
- Super administrator username/password
- A link back to this thread so that I know what you're talking about
and I will visit your site, see what's the problem, fix it and tell you what you have to do in order to not have this problem again.

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!

user34641
Nicholas, Thank you! It's working!


I went into s3 and made a bucket in all lowercase and it worked.


One suggestions I would like to see in the pro admin, a test to see if you are able to upload to your bucket. Instead of having to perform a backup and see something is wrong.


It's a minor thing and not necessary for people that follow directions right the first time, but stubborn kooks like myself could benefit from it!

nicholas
Akeeba Staff
Manager
You're welcome!

There's an easy way to test your S3 settings. You can create a new backup profile and exclude all folders, all files and all database tables (use the Files & Directories Exclusion as well as the Database Tables Exclusions). This will allow you to create a tiny file, very fast, to test the S3 transfer.

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!

user34641
Here is that periodic site crash or error I was talking about earlier, it's still happening. Has any of your users ever experienced this on the front end after installing backup pro?

Catchable fatal error: Object of class JParameter could not be converted to string in /home/mjind/public_html/nicecarvings/libraries/joomla/html/parameter.php on line 83

nicholas
Akeeba Staff
Manager
The error message only tells me which part of Joomla!'s core triggers the message, not what called it. However, I think that you are using the obsolete "Akeeba Lazy Scheduling" plugin which has been discontinued for more than six months and as of Akeeba Backup 3.3.5 we announced that it will cause site crashes. Can you please check with your site's plugin manager to see if this plugin is installed and, if so, remove it?

That said, the only other plugins installed by Akeeba Backup Professional are "System - One Time Password" and "System - Akeeba Backup Update Check". You can try disabling them. If that works please tell me the exact version of PHP you are using.

Off-topic: your Joomla! core files are out of date, too. Please upgrade to 1.5.25. The version you're using has known vulnerabilities.

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 Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!