Cloud I/O

Dirk Hohndel dirk at hohndel.org
Sat Dec 5 06:11:10 PST 2015


On Sat, Dec 05, 2015 at 01:39:36PM +0200, Willem Ferguson wrote:
> There must be a fundamental problem with the cloud interface. Since the
> upload/download of cloud data is active, I assume this means that the
> credentials for accessing cloud storage are in place. My cloud repository
> should be empty. Since resetting this repository, I tried on a number of
> occasions to upload four test dives comprising about 250 kBytes of XML onto
> the cloud storage without any success. I get a message saying that the cloud
> storage could not be located and that only the local repository was updated.
> 
> Then I tried download. The repository should be empty. However, After
> Subsurface has run for over 70 minutes, I get the screen depicted in the
> attached image. It has downloaded 20% of the repository.   See the
> highlighted text in the terminal within the attached image. My router is
> working furiously and a large amount of information is being passed on the
> Internet. However if I ping cloud.subsurface-divelog.org, there is no
> response. This fits with the message when uploading the test dives. But
> maybe the cloud server is set up not to respond to ping requests. Several of
> our servers are set up that way.

The AWS instance doesn't respond to pings it seems.

> Irony is, only a few days ago I was able to read from and write to the cloud
> storage, including a reference copy of V4.5.1 that I keep. Now that version
> as well as 4.5.2-336 behave identically as far as I can see.

You had a partially written git repository with about 300MB of data on
ther server. I once again cleaned this out and re-initialized the repo.

My theory is that your local cache still has the full 1.6GB of data and
when you try to sync again, Subsurface tries to get the remote in sync
with that cache.

So please manually delete the cloudstorage folder in ~/.subsurface and try
again.

/D


More information about the subsurface mailing list