Failed Synchronization

[Panagiotarakos]

I with nothing to sync the device. Just connect my display blank page without loading the files.

[davivel]

Could you give us more details about your environment? What device are you using? What version of Android does it hold? What version of the app did you install?

Can you see a progress indicator (rotating circle) in the action bar?

Thanks in advance.

[Panagiotarakos]

I Have Samsung Galaxy S3 mini (GT-I8190), v4.1.2

ownCloud , the latest version.

i have my own domain name, linked from my device and I see this picture

h**ps://dl.dropboxusercontent.com/u/18617997/ownCloud_Support/Failed_Synchronization/2013-06-02%2015.44.15.png

[davivel]

Ok, then it's a failure in the synchronization process.

Can you share here the URL to your server, or do you prefer to keep it private?

Do you have SNI enabled in your server side? It is not supported in the client.

Do you use HTTP redirections? Some of them are problematic for the client.

[Panagiotarakos]

h**p://iatreiomz.gr/

[davivel]

Nothing strange at first sight.

Do you have many files in your account?

Could you provide us a test account in your server?

[Panagiotarakos]

Yes

demo / demo

From mobile I do not see anything from my archives

[davivel]

Ok, seems there is some misconfiguration in the server side. The WebDAV interface is not working well, the method PROPFIND is answered with an HTTP 501 - Not implemented.

Have a look to this : http://forum.owncloud.org/viewtopic.php?f=17&t=7536 , specially to this one linked from the former: http://forum.owncloud.org/viewtopic.php?f=17&t=7536 . That probably will help you.

[Panagiotarakos]

looked at them but unfortunately I can not find tip yet ...

*would at least a mobile version to operate the service;

[razorinc]

But, I have to add something to my issue, that now I activated the DAV and ext-dav support on nginx but if I press the Refresh button, nothing happen. And on the server side, I don't see any request.

[davivel]

@razorinc , do you get to see a progress indicator in the action bar of the app? Do you get to see any error in the notification bar?

@Panagiotarakos, @razorinc , how did you start the installation of your ownCloud server, did you use the 'Web installer' link here: http://owncloud.org/install/ , or did you follow some of the instructions of the 'Installation' chapter here: http://doc.owncloud.org/server/4.5/admin_manual/ ?

[razorinc]

@davivel No progress indicator, the interface load smootly and no errors on notification bar (i will connect with the usb cable and see if the logs from eclipse say something more useful)

@davivel I installed the ownCloud server from the freebsd ports, and the version is still 5.0.5 and I followed the Installation Chapter.

[razorinc]

@davivel The cable and the logs didn't give any useful information. My server didn't receive from the android client the PROPFIND request when the application is loaded or when i press Refresh, i forgot to mention that my phone have Cyanogen and it's an HTC Desire with Android Gingerbread 2.3.3

[davivel]

Ok. Sorry, but we don't support Cyanogen, we have limited resources and 'regular' Android involves enough fragmentation itself.

Anyway, it is very strange that not even tries to start synchronization.

[danimo]

@davivel I dobut that Cyanogen is the trouble maker. To me this looks like @razorinc has broken server setup. Note that anything but apache is basically untested on Linux. If you use nginx, know what you are doing, or at least check http://doc.owncloud.org/server/5.0/admin_manual/installation.html#nginx-configuration. owncloud handles webdav internally -- the web server has no business there, other than accepting the additional HTTP verbs (which nginx should do by default afaik).

[razorinc]

@davivel @danimo Exactly, I dubt as well that is Cyanogen. Before open an issue, I double check everything and followed all the instructions on the admin manual. More over, if the iPad client work perfectly, and the client on OSX and Linux work as well perfectly and I hit such problem with the android client that does not ask for the list of files, cannot be the the server.

[davivel]

Well, if I have to choose between Cyanogen and the app, my election is pretty obvious :) .

Can you provide us a test account in your server, and the URL?

[razorinc]

With pleasure, can you give me an email address?

[davivel]

You can send it to apps@owncloud.com . Include in the subject something like 'Android app issue#170'

[razorinc]

Done! 👍

[Panagiotarakos]

@davivel me with Web Installer

[razorinc]

Solved the issue. For me was the low space on internal phone, once I freed enough space to not have anymore "insufficient space left on the device" it worked like a charm.
So, the issue was with Android and not with ownCloud itself! 👍

[davivel]

@razorinc , Ok, thanks for coming back to tell about your solution. The local cache for the index of files is saved in internal storage, so it's necessary to have some free space in the phone to synchronize.

Nice to see than Cyanogen was not an additional factor to consider.

[razorinc]

@davivel You're welcome, I think that can surely help many people that will hit this issue. Well there was free space but 1 mb less than what android define as insufficient :)

[ryanleesipes]

I had this issue on the Samsung Galaxy S4, the only way I was finally able to get it to work was to uninstall and reinstall the app and the OwnCloud workaround. After that everything worked properly.

[davivel]

Thanks @ryanleesipes . Definitely, the order in the installation of the app and the JB workaround is determinant for the app can operate, as you say.

Anyway, the server configuration of @Panagiotarakos had a recognizable problem, since it was not responsing to WebDAV methods. @Panagiotarakos , any advance since the last time we talked? Did you try a server update?

[HeisSpiter]

Hi,

I'm encountering the same issue with a Sony XPERIA GO (also known as ST27i). I've just checked the web interface: it is working nice. Same goes for the webDAV that properly displays my files.
Also, I've more than 3GB available on internal memory and on memory stick.

I'm using latest release of ownCloud Android client available and of the server (version 5).

Thanks!

[davivel]

@HeisSpiter , how did you check the webDAV interface, in a web browser? Many wrong setups of WebDAV seems to be fine because the browser throws a GET method, that is solved by any HTTP server without intervention of the WebDAV module in ownCloud; but still fail because the PROPFIND method is not accepted by the server.

Did you check some of our desktop clients, or the iOS client, with the same account? Are they working?

[HeisSpiter]

I checked the remote.php/webdav as written in the board link you gave.

I've got the clients working on Debian, Ubuntu and CentOS. I can test Windows as well, if needed. I have no way to test iOS.

[schokobass]

Hallo,

with the owncloud android app v1.4.4 and theJellybean workaround being installed from Google Play Store on my Samsung Galaxy S2 (GT-i9600), there is no success yet in connecting to the webspace nor to load up any files - despite the login itself during the creation of the respective account does NOT fail.

Is there any known issue in case that the owncloud web service v5.0.10 is installed on a NAS which is exposed via dyndns.org, using a SSL connection at port 8443, with forced SSL connection in server side administration?

What does happen in detail?

I start the creation of the first account in the app, type in the URL of my target, i. e.
https://my_dyndns_account.dyndns.org:8443/owncloud
and will get in any case at this point the success information
"safe connection has been established" (in fact, I use the DE version and will read
"Sichere Verbindung hergestellt").
Now I will type in my user name and the password, will control the password - it will be typed in correctly - and will connect.

The "login attempt" seems to succeed then, i. e.: I will be lead to the account list with this only entry
my_user_name@my_dyndns_account.dyndns.org:8443
, but some seconds later a notice will arrive on my smartpone
"synchronization failed: invalid password for my_user_name"
(in German, of course . . . ;-D )

Having read this information, I will be thrown directly into the configuration dialogue of the app itself where I just will be able to type in my password once more . . .

My first intent would be to uninstall and completely delete any local files of the android app and the JB workaround, but perhaps there is anyone else knowing this issue and its solution?

[schokobass]

BTW: I forgot to mention that I did create port forwardings for ingoing requests for the ports 80 and 8443 from my DSL router to the NAS . . . and that the NAS and the owncloud web service in fact ARE accessible from the internet at this dyndns URL . . .

[schokobass]

Hallo again,

in my case the issue has been solved indeed by

uninstalling oc app and oc workaround, rebooting the device,

deleting the local directories and files being created/used by the owncloud app in the regular directory tree,

installing again the oc app and the jb workaround via play store.

Thereafter, all steps of the account creation succeeded and the root directory of the oc web service was mirrored immediately, giving opportunity to download the online files and to activate their synchronization.

[angel12]

I am having this issue on both my Galaxy Note 2 and my S4, no matter what version of Android I use, I always get "Failed to Sync" in my notifications. Here is my logcat of trying to sync:

D/WebdavClient(14648): Creating WebdavClient
D/FileSyncAdapter(14648): Synchronization of ownCloud account user@host.com starting
D/FileDisplayActivity(14648): sync of account user@host.com is in_progress: true
E/MP-Decision( 1613): num online cores: 1 reqd : 2 available : 4 rq_depth:1.900000 hotplug_avg_load_dw: 56
E/MP-Decision( 1613): UP cpu:1 core_idx:1 Nw:1.900000 Tw:140 total_time_up:42.000000
E/MP-Decision( 1613): num online cores: 2 reqd : 1 available : 4 rq_depth:0.700000 hotplug_avg_load_dw: 29
E/MP-Decision( 1613): DOWN cpu:1 core_idx:1 Ns:1.100000 Ts:190 total_time_down:401.000000
W/HttpMethodBase(14648): Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
E/MP-Decision( 1613): num online cores: 1 reqd : 2 available : 4 rq_depth:1.900000 hotplug_avg_load_dw: 50
E/MP-Decision( 1613): UP cpu:1 core_idx:1 Nw:1.900000 Tw:140 total_time_up:147.000000
D/UpdateOCVersionOperation(14648): Got new OC version 5.0.17
I/UpdateOCVersionOperation(14648): Check for update of ownCloud server version at http://host.com/owncloud/remote.php/webdav: Operation finished with HTTP status code -1 (success)
D/SynchronizeFolderOperation(14648): Synchronizing user@host.com, fetching files in /
D/RemoteOperationResult(14648): RemoteOperationResult has prcessed UNHANDLED_HTTP_CODE: 301
I/SynchronizeFolderOperation(14648): Synchronizing user@host.com, folder /: Operation finished with HTTP status code 301 (fail)
D/FileDisplayActivity(14648): sync of account user@host.com is in_progress: true
D/SyncManager( 701): failed sync operation user@host.com u0 (owncloud), org.owncloud, USER, earliestRunTime 307826356, reason: 10065, SyncResult: tooManyRetries: true delayUntil: 86400 stats []
D/SyncManager( 701): not retrying sync operation because it retried too many times: user@host.com u0 (owncloud), org.owncloud, USER, earliestRunTime 307827653, reason: 10065
D/FileDisplayActivity(14648): sync of account user@host.com is in_progress: false
E/MP-Decision( 1613): num online cores: 2 reqd : 1 available : 4 rq_depth:0.000000 hotplug_avg_load_dw: 29
E/MP-Decision( 1613): DOWN cpu:1 core_idx:1 Ns:1.100000 Ts:190 total_time_down:287.000000

Changed out my username / url for privacy.

Webdav does work though, as I can pull up webdav on my windows computers as well as a webdav app on my phone

I have tried with a clean install on a different domain as well. I am currently hosted on dreamhost, but am looking at moving my hosting somewhere else.

[HeisSpiter]

Still having the issue. Any news?
On my computers, the ownCloud clients (1.4.X now) work fine.

[davivel]

@angel12, you problem is due to an already-known bug with permanent redirections. We will fix it as soon as possible.

@HeisSpiter , do you know if your server is accessed through HTTP redirections?

[HeisSpiter]

@davivel What do you mean with HTTP redirection?
There's no redirection in the Apache configuration.

[davivel]

Hi everybody. Version 1.4.6 was released on Friday. Connections are improved, and now the server side can be reached through redirections.

@angel12 , @HeisSpiter , @Panagiotarakos , could you check if this makes some difference for you?

[stevedowe]

Just my £0.02-worth...

I ran into the "invalid password" synchronisation error message on my Samsung Galaxy S4 (running JB 4.2.2), and came across this thread after searching the web. To resolve this issue, the only way I could get this to work was by observing this exact order:

1. Install ownCloud app from Google Play
2. Set up account in ownCloud app, create a directory through the app to test syncing with server
3. Restart phone (<- not sure if this is necessary, but it's what I did)
4. Because I'm on Android JellyBean, I needed to log in to the ownCloud app again (providing my server and user/password credentials)
5. THEN install the JB workaround from Google Play
6. Check everything still works in the ownCloud app and then restart the phone - settings should now be persistent.

The mistake I originally made was installing the JB workaround at the same time as the main app. I kept getting "invalid password" errors when doing that.

Hope this helps someone.

[davivel]

Hi, @stevedowe . Your description is very helpful. The point of setting up account before installing the workaround app can be very important indeed, and we didn't notice.

Let's see if that helps somebody here.

[davivel]

Pinging here at @angel12 , @HeisSpiter , @Panagiotarakos . Still with this problem?

[HeisSpiter]

@davivel Still having this issue with everything up to date.
I tried to delete and recreate the account in the application, no success.

[davivel]

Hi again.

@HeisSpiter , do you have other DAV clients (WebDAV, CalDav or CardDAV) installed in your device and connected to the same ownCloud account?

[petervnv]

Hi,

I'm having a similar issue, except in my case it happens with both the android and linux sync clients.
I'm running owncloud 6.0.1 on Debian 7 with nginx. And yes I followed the config guide for nginx from here http://doc.owncloud.org/server/6.0/admin_manual/installation/installation_source.html

Looking at the server side logs and also logcat in Android, I think this maybe related to webdav.

In OC logs I see:

[06/Mar/2014:15:26:14 +0000] "PROPFIND /remote.php/webdav HTTP/1.1" 200 2731 "-" "Mozilla/5.0 (Linux) csyncoC/0.91.5 neon/0.29.6"
myuser [06/Mar/2014:15:12:13 +0000] "PROPFIND /remote.php/webdav/ HTTP/1.1" 200 605 "-" "Android-ownCloud"

And in logcat:
03-06 15:03:31.617 D/RemoteOperationResult(6263): RemoteOperationResult has processed UNHANDLED_HTTP_CODE: 200
03-06 15:03:31.617 E/SynchronizeFolderOperation(6263): Checked myuser@my.cloud.com/ : Operation finished with HTTP status code 200 (fail)

As you can see, both are returning HTTP status code 200, which strangely both clients seem to interpret as failure. WTF?

[petervnv]

Oddly enough, both CalDav and CardDav sync seem to be working fine on the same OC instance.
I just tried syncing my calendar from Android and it worked without a hitch.

[davivel]

The client is expecting a code 207 in case of success (multistatus). WebDAV specification is silent about the possibility of returning 200 as OK for PROPFINDs, and the examples it includes return 207 even when the response holds a single element.

Since the other WebDAV clients are working fine, we must supposs than the rest of the response is right. In this case, I think we should deal with this as a bug on the client side and relax the response parsing to accept 200 as valid.

[davivel]

@petervnv, your problem should be fixed from version 1.6.0 ; could you have a look?

Please, @HeisSpiter , test again too; maybe it fixed your problem also.

[HeisSpiter]

@davivel due to my configuration change on my webserver, I cannot test it anymore. With new configuration, it was already working fine.

[davivel]

Thanks, @HeisSpiter . Happy to read it's working for you, though the fix was from other source.

Seems we can close this issue. @petervnv , if your problem persists just comment it here anyway.

For anybody else, please, open a new issue although seems similar to this one.

Thanks,