On Wednesday, March 28, 2012 04:16:18 PM silverbear wrote: > Sorry to take so long to get back to you - busy day!
No problem! > I tried the sync with the 'check for changed media files' unchecked on > both m/c's and it made no difference. What is then the message on the server when it hangs? > It occured to me that I get his problem for the first sync after a > reboot (I power down every night). I've justed tested this theory by > rebooting the m/c's again and lo, and behold, the sync failed again Strange, typically you'd expect this to be the other way around, with reboots fixing things :-) > and I ended up doing a full sync to get the process working again. Just to make absolutely sure: * both client and server are on beta 11b? * you never manually copied Mnemosyne files or directories between client and server? I.e. delete the *entire* Mnemosyne folder on the client, start Mnemosyne, notice that your database is empty, and then sync to the server? > A network issue? Perhaps... Unfortunately, the way to debug this is rather complex, with running a program called wireshark to capture all the network traffic. > Client not allowing enough time for Windows to get it's act together? Could be... Is your server an old machine? When there is not a full sync (full sync: messages like 'getting entire binary database) but an incremental sync (messages like getting/sending log entries), how long does a sync typically take? Few seconds? Half a minute? Minutes? Normally it's a matter of seconds, but if for some reason it's slow on your machine, we might need to increase the default timeout. When you get the timeout on the client, after how much time is this? Cheers, Peter -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
