strange behaviours

[dafuer]

Hello,

I have two problems that I would like to share and to know if someone else have same issues:

• I have the backup command written in crontab and it is executed everyday. After the execution of the command I always receive following email:

Curl error: (#52) Empty reply from server( code: 268697857; file: /var/www/vhosts/my.domain.com/my_symfony_project/vendor/hakre/dropbox-uploader/DropboxUploader.php; line: 241)

• Second issue is that I have configured in config.yml two email directions to receive backup notifications and only one of them receive this error.

  Someone else has similar problems?

[dizda]

Hey @dafuer !

Did you try to run this command composer update hakre/dropbox-uploader ?

Can you share an exemple of your config.yml ?

[dafuer]

Hi @dizda !

I have typed:

$ php composer.phar update hakre/dropbox-uploader
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Writing lock file
Generating autoload files

My config.yml:

dizda_cloud_backup:
    output_file_prefix: backup 
    folders: [ web/uploads/productos, web/uploads/marcas, app/data ]
    error_notification: 
        from: xxx@mydomain.com
        to: [ xxx@gmail.com, yyy@gmail.com ]
    cloud_storages:       
        dropbox:
            user:     %dizda_cloud_dropbox_user%
            password: %dizda_cloud_dropbox_password%
            remote_path: /BACKUP/
    databases:
        mysql:
            all_databases: false
            database: %database_name%
            db_host: %database_host%
            db_port: %database_port%
            db_user: %database_user%
            db_password: %database_password%

Any idea?

Thanks!!!

[dizda]

Ok so, you should try to update the cloud-backup-bundle itself: composer update dizda/cloud-backup-bundle

Because the error_notification has been deprecated, and you should now use monolog instead to be notified with ease : http://symfony.com/doc/current/cookbook/logging/monolog.html

[dafuer]

Hi!

I thought I have last version also:

$ php composer.phar update dizda/cloud-backup-bundle
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
update [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--lock] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--with-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [packages1] ... [packagesN]

But It is true that in last version error_notification is removed and not in mine. I have checked my composer.json where I have written:

"dizda/cloud-backup-bundle": "~1.6"

So, I don't understand why I don't have last version of this repository without error_notification... Probably the solution is to get last version of this bundle and dropbox-uploader (now I have doubts if it is also in last version or not) but how? I don't want to do it manually. Do you see any error in my composer.json?

About monolog, now it is not possible to have a quick feedback is something is wrong during backup process? The email was really reactive.

Thanks!

[dizda]

Oh I forget to remove the error_notification from the configuration's tree, fixed d93b87969e245995a46646ed15f05513452a8010.

You can replace your composer.json's line with:

"dizda/cloud-backup-bundle": "~2.0"

To get the last version of the bundle. Last but not least, there is a good exemple to send email when error occurs http://symfony.com/doc/current/cookbook/logging/monolog_email.html. We wanted to use monolog because you can choose the provider you want, it could be email, notification, or slack, etc.

[dafuer]

Hi,

I have updated cloud-backup-bundle and I have updated configuration file also. I didn't start with monolog yet... I'm doing test because backups are not always working for me. Sometimes it works, sometimes it gives:

[2015-06-27 14:39:40] app.CRITICAL: [dizda-backup] Unexpected exception. {"exception":"[object] (Exception(code: 268697857): Curl error: (#52) Empty reply from server at /symfony_project/vendor/hakre/dropbox-uploader/DropboxUploader.php:241)"} []

or

[2015-06-27 15:05:10] app.CRITICAL: [dizda-backup] Unexpected exception. {"exception":"[object] (Exception(code: 268698625): Upload failed! at /symfony_project/vendor/hakre/dropbox-uploader/DropboxUploader.php:141)"} []

Perhaps this is something to ask in dropbox-uploader github repository. What do you think? Another issue: I have seen that --folder option is not working anymore. But it described in documentation. Now by default, are folders copied?

Thank you very much!

[dizda]

Is it fixed?

[dafuer]

No yet but I did not do too many tests... The problem is there yet but I have not had too much time to resolve it. Next week I will update all dependencies and I will try again. I have in my crontab a task every day to do a backup and in the last month this task worked 30% times...

[dafuer]

Hi @dizda , I think you can close the issue. I was delaying the answer because I was waiting for dropbox uploader (this package currently is not working). In any case, the questions are not related directly with this bundle and I will wait for a fix for dropbox. Once, that works again I will check the backup system again and if I have doubts I will ask you. Thank you very much.

[dizda]

Ok thanks @dafuer for these informations, looking forward to fix this dropbox issue.