Support

Cron backup fails with 500 error.

Front end attempt fails with this message:

Detected errors prohibit intended operation

Akeeba Solo detected the following potential problems:
S012 Missing database connection information for backup


But - the configuration is for "generic or bespoke script" and the databsae choices are left blank (as much as possible).

Solo requires database information in two different places.

1. Under System Configuration (at the bottom of the Control Panel screen) on the Database configuration tab. This is the database where Solo stores its own information, configuration, backup archive information and statistics, etc.
2. Under Configuration, you need to enter the database credentials for the site that you are backing up.

These two databases may be the same database, you still need to enter the credentials in both locations.

1. Database is set up in System Configurations. We have multiple sites on the server, and each has its own Akeeba profile. The other profiles work.

2. This profile that breaks - the site for this profile does not have a database, so we do not put in the credentials.

That won't work. Solo still needs a place to store its own data. It requires this information once, no matter how many profiles you have. This is independent of your sites, it is for Solo.

As I said , the database for Solo to use IS set up in System Configuration, and it does work for all of the other profiles in this Solo installation.

I'm assuming that the database used for Akeeba Solo is dedicated for that use, and that connection information goes in System Configuration. And that inside each profile, the database connection information is for a database with the site being backed up. Are those assumptions correct? If so, then we have it set up correctly.

So I'm not sure exactly what you are telling me. Are you telling me to put the Akeeba database info into the profile that isn't working? Won't that attempt to back up the Akeeba database with the site?

OK, now I get it! I apologize for the confusion.

Version 1.7.1 of Solo has a databaseless mode for just this situation. Use the SQLite database driver in your Profile setup. That should keep it from complaining about the lack of credentials.

This is a new feature and the client it was written for never used it. It works in testing, but you are the first to try it in a live environment. We would very much appreciate any feedback you have on the operation.

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.