@hjohanns (Hubert Johannsen) posted a new topic, subject "NC client freeze with errors". It read:

   Hello,  
    we have problems of instability of the desktop client on windows. The client freezes, so it is also difficult to collect the log. In the attached screenshot, you can see that the client has a ‘Error: “locking protocol”' on a file, and then stops and freezes.  
    On other circumstances, the client also received an Error 500 from the server due to a known race condition on locks (if that can be related).  
    Any suggestion on how to pursue troubleshooting would be welcome, thanks, hj  
    
    
    ncLogError201809596×652 51.8 KB

So @tflidd (tflidd) replied

    You can also write a log to a file:  
    https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#saving-files-directly

Then @hjohanns (Hubert Johannsen) said

    Thanks for the suggestion. We have several users of the same machine, in addition to having to require an admin to set that up for us. Adding the flag to save the files automatically would be valid for all the NC client users on that machine?  
    Best regards, and kudos for the great work!  
    hj

To which @hjohanns (Hubert Johannsen) replied

    Hello, after some efforts, we managed to have the client start with --logdir.  
    Out of the saved logs, I oculd not spot anything. The log is ending brutally with a crash of the client.
    
    > O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  11-25 17:00:47:559 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  11-25 17:01:17:563 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2601 s)  
    >  11-25 17:01:17:563 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  11-25 17:01:17:563 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  11-25 17:01:47:564 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2631 s)  
    >  11-25 17:01:47:564 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  11-25 17:01:47:564 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  11-25 17:01:48:110 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069JsonApiJob created for “https://server/dir” + “ocs/v2.php/apps/notifications/api/v1/notifications” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069ServerNotificationHandler”  
    >  11-25 17:02:17:559 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2661 s)  
    >  11-25 17:02:17:560 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  11-25 17:02:17:560 27772 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  *** end of file ***

After which, @hjohanns (Hubert Johannsen) added

    Strange, I got a second case of crash with exactly the same value 2661 s. Is that a default value?
    
    > 12-12 12:32:24:951 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2481 s)  
    >  12-12 12:32:24:951 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:32:24:951 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:32:25:514 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:32:54:949 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2511 s)  
    >  12-12 12:32:54:949 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:32:54:949 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:32:55:578 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:33:24:947 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2541 s)  
    >  12-12 12:33:24:947 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:33:24:947 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:33:25:642 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:33:54:952 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2571 s)  
    >  12-12 12:33:54:953 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:33:54:953 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:33:55:703 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:34:24:958 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2601 s)  
    >  12-12 12:34:24:958 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:34:24:958 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:34:25:766 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:34:54:954 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: 2631 s)  
    >  12-12 12:34:54:954 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:34:54:955 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:34:56:045 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”  
    >  12-12 12:35:24:960 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunEtagJob: * Trying to check “https://server/dir/remote.php/dav/files//” for changes via ETag check. (time since last sync: **2661** s)  
    >  12-12 12:35:24:960 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069FolderMan8b7c:f320:99b9:690f:4595:cd17:293a:c069slotRunOneEtagJob: Scheduling “https://server/dir/remote.php/dav/files//” to check remote ETag  
    >  12-12 12:35:24:960 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069RequestEtagJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069Folder”  
    >  12-12 12:35:26:337 8624 O8b7c:f320:99b9:690f:4595:cd17:293a:c069AbstractNetworkJo8b7c:f320:99b9:690f:4595:cd17:293a:c069start: !!! O8b7c:f320:99b9:690f:4595:cd17:293a:c069PropfindJob created for “https://server-wo-port/dir” + “/” “O8b7c:f320:99b9:690f:4595:cd17:293a:c069QuotaInfo”
    
    Moreover, I noticed that some of the URLs in the log are with the server port (https://server/) and others are without the port (https://server-wo-port). I changed the values to represent that in the log one is with https://server1:333, whereas the other one is on https://server1 simply.  
    Is there any possibility that the client tries to communicate on different ports or is it just an effect of logging?  
    Also if you can hint towards an area of code in the client I would do a check. These crashes are annoying. Thanks a lot for the new release btw!  
    hj

To which @tflidd (tflidd) replied

    I can't see anything obvious, it's probably the best to use the logs and file a bug report https://github.com/nextcloud/desktop/issues


{'source': 'discourse', 'url': 'https://help.nextcloud.com/t/nc-client-freeze-with-errors/37127', 'title': 'NC client freeze with errors', 'views': 1175, 'has_accepted_answer': False, 'word_count': 1317, 'like_count': 0, 'reply_count': 1, 'participant_count': 2, 'posts': 6, 'tags': '', 'author': '@hjohanns (Hubert Johannsen)', 'participants': '@hjohanns (Hubert Johannsen), @tflidd (tflidd)', 'image_url': ['https://help.nextcloud.com/uploads/default/original/2X/0/07990a15d7a855f857d95bdde899e1e92d6d70f0.png'], 'created_at': '2018-09-19T02:26:15.834Z', 'last_posted_at': '2018-12-14T19:06:55.133Z'}