cells-cal data sync fails about cells HOT 19 CLOSED

Is this a case where the feature is simply not being implemented yet?

from cells.

hi Yannick
It's a bug. Just fixed in master - will be in next release, sorry about that.

from cells.

That said, the error you see in your post is normal when not specifying a service name (--service=pydio.grpc.data.sync.DsName).
(but the actual command is failing even with service name)

from cells.

Thanks Charles.

By the way, here's my use case.

We use your cells product to provide files to clients and receive files from client. I need to implement an automatic purge mechanism so that all files are deleted after something like 15/30 days (haven't decided yet). The system allows purging previous versions but not actual files like I described earlier.

So the plan would be to create a script on the serveur to find all files older than the chosen threshold, delete them and run cells-cal data sync to update the index.

Makes sense? Or you already thought of this use case?

If that's something you thought about, I could open another ticket :)

Thanks,

from cells.

hi, actually you should have everything already with the scheduler, but for the moment it's a bit awkward to program as it's only via API. We will probably add the feature at one point (we had it pydio 8).
Still, you could use the API (with e.g. pydio/cells-sdk-go) to browse the files and delete them under the same conditions, but in the end I think your approach is pragmatic and a good way to go.
-c

from cells.

Good to know. Thanks.

from cells.

Hey, I updated my cells-ctl version with the one from:

https://download.pydio.com/pub/cells/release/1.2.4/linux-amd64/

and I get the following message now:

./cells-ctl data sync --service=pydio.grpc.data.sync.personal --path=/datastore/pydio-data/personal/
Resync Failed: {"id":"go.micro.client","code":408,"detail":"context deadline exceeded","status":"Request Timeout"}
[Time taken : 30m0.000593868s]

Any idea?

from cells.

Yannick, are you sure of the path parameter ? Did you try without it ?

from cells.

Yes I did without it first, but I thought that since default path value is /, it could be why it took too long.
Any idea or mean to trace what's happening?

Just to be clear, I updated my cells-ctl with version 1.2.4, but not my cells.

from cells.

Anything happening in the server logs when you send the command? Is the data source very « big »?

from cells.

There is nothing in the Pydio.log or Cells.log located in: ~/.config/pydio/cells/logs
Any other logs I should be check?

Else, there is only one file in the specified (a 15M dmg file) datasource as I'm setting it up for new year deployment.

from cells.

Mmm - dumb question, but cells server is started, right?

from cells.

Yes, it is indeed, but as I said, my cells server is still version 1.2.3, does it make a difference? I only copied cells-ctl over.

from cells.

try to upgrade and let's see - it should be painless, there is no specific migrations implied, just the binary differs

from cells.

Do I just replace both binaries and start cells service again? or there is an upgrade command to run? Cause I did replace the cells binary and now the service appears to be running, but I can't load the website anymore.

from cells.

did you wait long enough? can you post the full log after restart?

from cells.

Alright, I figured it out, here was the issue in the log:

{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":""}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":" ERROR: Cannot bind to port 443. "}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":" You should probably run the following command "}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":" otherwise the main internal proxy cannot start"}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":" and your application will be unreachable."}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":" $ sudo setcap 'cap_net_bind_service=+ep' "}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":""}
{"level":"error","ts":"2018-12-14T16:03:36Z","logger":"pydio.gateway.proxy","msg":"Could not run ","error":"listen tcp :443: bind: permission denied"}

I already ran the following command in the past: "sudo setcap 'cap_net_bind_service=+ep' " Any reason I needed to do it again to work?

But appart from that, it all works now. So thanks you very much for your help.

from cells.

Indeed, you have to do it each time you update the binary. The next in-app upgrades starting with 1.2.4 will now show a warning in the interface to remind you of that :-)
So the Resync is working as well?

from cells.

Yes, it all works out perfectly now. Great work and awesome support.

Thanks

from cells.