please collect all the logs and file  a bug with the usecase. Do mention in the bug about the folder structure [ large files, sym links ..... ]

Bump original post.

 

When connecting to OpenSUSE 11.3 running ifolder3 (3.8.0) server, all our Windows clients function properly (perfect sync up/down), but all 3.8.0.x clients on Mac OSX 10.6.x malfunction to a point that we cannot yet recommend (as we'd hoped) deployment of iFolder more widely throughout our company.

 

Specifically, when attempting to sync a file of 700MB up to the server, from a Mac Client, using "Synchronize now" (auto sync set to 15 minutes), the upload begins, churns away for about 2 minutes, and then fails.  After one or two failed attempts to sync upload, the client reverts to a status of "Synchronized: MM/DD/YYYY hh:mm:ss" and does not attempt to re-upload until the client is restarted (which just spawns the same behavior again).  This behavior is repeatable across Mac clients.

 

There is no relevant errors reported in "<data dir>/log/Simias.log" on the server.

 

Here is the relevant section of client-side "~/.local/simias/Simias.log":

2010-09-28 21:24:13,727 [Client Sync] DEBUG Simias.Sync.Log - Failed Uploading File, WebException

System.Net.WebException: Error getting response stream (ReadDone1): ReceiveFailure ---> Mono.Security.Protocol.Tls.TlsException: The authentication or decryption has failed.

at Mono.Security.Protocol.Tls.RecordProtocol.ProcessAlert (AlertLevel alertLevel, AlertDescription alertDesc) [0x00000] in <filename unknown>:0

at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0

--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0

at System.Net.HttpWebRequest.GetResponse () [0x00000] in <filename unknown>:0

at Simias.Sync.Http.HttpSyncProxy.WriteFile (Simias.Sync.StreamStream stream, Int64 offset, Int32 count, System.String encryptionAlgorithm, System.String EncryptionKey) [0x00000] in <filename unknown>:0

at Simias.Sync.HttpClientOutFile.UploadFile () [0x00000] in <filename unknown>:0

at Simias.Sync.CollectionSyncClient.ProcessFilesToServer () [0x00000] in <filename unknown>:0

 

... then it retries....

 

2010-09-28 21:24:38,474 [Client Sync] DEBUG Simias.Sync.Log - Failed Uploading File


System.IO.IOException: IO exception during Write. ---> System.NullReferenceException: Object reference not set to an instance of an object


 at Mono.Security.Protocol.Tls.SslStreamBase.InternalBeginWrite (Mono.Security.Protocol.Tls.InternalAsyncResult asyncResult) [0x00000] in <filename unknown>:0


  --- End of inner exception stack trace ---


 at Mono.Security.Protocol.Tls.SslStreamBase.InternalBeginWrite (Mono.Security.Protocol.Tls.InternalAsyncResult asyncResult) [0x00000] in <filename unknown>:0


  at Mono.Security.Protocol.Tls.SslStreamBase.BeginWrite (System.Byte[] buffer, Int32 offset, Int32 count, System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0


  at System.Net.WebConnection.BeginWrite (System.Net.HttpWebRequest request, System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.Object state) [0x00000] in <filename unknown>:0

 

In a small user test of 6 people using iFolder over three weeks for internal project collaboration, each with Mac and PC, our result was that the Mac client felt too flimsy (easily duped into thinking that it's sync'd) and was inherently distrusted compared with the Windows client and compared with our oldskool file server.

 

Any thoughts?  Seems to be a mono issue (using 2.6.7)...  Or is it somewhere else in the works?  Does the server need to be running OpenSUSE 11.1?  Has this anything to do with the apache config?  Is this a common bug, and the Mac Client is just not heavily used?