Synchronizer-base for any backup provider


(Christoph) #41

Yes, except that Jay doesn’t see any files on Google drive while I seem to get a few bytes transferred. Also, I’ve had this working for months. Not sure about Jay.

Can anyone confirm that the plugins are working for them?


(Jay Abie) #42

I hope the author fix it soon.


(Christoph) #43

I’m not sure we’ve confirmed that there is a problem with the plugin. I’m sure many are using this plugin but it seems only we are having problems.

On the other side, the problem is quite unlikely to be discovered and nobody has confirmed that the plugin is working for them either…


(Coin-coin le Canapin) #44

Hi, I’m trying to install the google drive storage plugin but I have an error during the rebuild of Discourse.
I have added

- git clone https://github.com/berlindiamonds/discourse-sync-base.git

in my app.yml and the rebuild works. However, as soon as I add

- git clone https://github.com/berlindiamonds/discourse-sync-to-googledrive.git

on the next line, my rebuild fails:

185:M 27 May 10:52:31.659 # User requested shutdown...
185:M 27 May 10:52:31.659 * Saving the final RDB snapshot before exiting.
2018-05-27 10:52:31.684 UTC [69] LOG:  database system is shut down
185:M 27 May 10:52:33.213 * DB saved on disk
185:M 27 May 10:52:33.213 # Redis is now ready to exit, bye bye...
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 403 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]}
5c0c7ec5ac63127128822d5f5175eb5874753b7f34f30d05bc4e90013b306b26
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
root@canapin:/var/discourse#

Here’s the cmd part of my app.yml:

    cmd:
      - git clone https://github.com/discourse/docker_manager.git
      - git clone https://github.com/discoursehosting/discourse-migratepassword.git
      - git clone https://github.com/berlindiamonds/discourse-sync-base.git
      - git clone https://github.com/berlindiamonds/discourse-sync-to-googledrive.git

Note that I have no issue with sync-to-dropbox so this seems to be specific to sync-to-googledrive.


(Daniela) #45

I temporarily moved it in #plugin:broken-plugin .
As soon as one of the engineers gets rid of the other jobs he will fix it properly.


(Christoph) #46

Are you sure that the files that end up in your dropbox are actually full backups? I only get files sized 48 bytes.


(Daniela) #47

My issue with Dropbox is quite different from yous. New backups goes to Dropbox but the old backups are not canceled. In this way, the storage space fills up quickly and the new backups are no longer synchronized and remain on the server.


(Coin-coin le Canapin) #48

I didn’t try to restore from them but they are the same size as on Discourse, ~300MB so I guess they are good.

However, the first (auto ?) backup from Discourse, before importing my phpbb, didn’t import successfully (1KB file instead of 2 MB), which I didn’t care.

I didn’t try to pass the limit of max backups so I don’t know if I’ll have the same issue as you Daniela, however an option I’d like to have would be that if we delete a backup manually from Discourse, it would get deleted on Dropbox as well.


(kaja santro) #49

Hey hey,
I am very sorry but I don’t currently have time anymore to volunteer to the project due to my job.
But if you want, you can always make pull requests to our repo on github or open an issue there and document exactly what the problem is.


(Christoph) #50

Hm, for me the deletion of old backup works.

This is very weird. Now we have at least three different issues with the backup plugins but none of these issues seem to occur simultaneously or multiple times (except for by Dropbox issue which I have on two independent forums).

Does it make sense to try and get to the bottom of this or will it simply be fixed via


(Daniela) #51

You just have to be patient, we are at the finish line for a new release and, as always, we are under pressure during this period :wink:


(Jay Abie) #52

Dear,

Noted, we will take an action when required.
Do we have any hope for fixing this soon ?


(Erlend Sogge Heggen) #53

@misaka4e21 is updating this plugin but there is no ETA.


(Coin-coin le Canapin) #63

Hi,
I want to switch from dropbox to gdrive, but I’m confused about the service account key.
I enabled the Drive api:
image

I followed the plugin instructions and downloaded the json file here: image

I pasted the content of the json here:

But when I do a backup from Discourse, no backup is sent to gdrive. Plus, when creating the json, it is never stated that the purpose is managing google drive.

Also in drive credentials, it doesn’t show the service account key (the api key shown is something else):
image

And in Discourse, the “Google Drive Downloader” added button leads to a 404:

What am I missing? Plus, it is possible to chose the destination directory of the backups?


(Christoph) #65

Can’t find the plugin anywhere on meta anymore. Does that mean it will not be fixed?

I was looking for the topic to share the following information: I noticed that the dropbox cache on my local PC actually seems to contain the backups:

So somehow the backups do get uploaded but then they seem to be deleted again. Hope that helps in fixing the plugin.