Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-1492

Access to the local socket is denied

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 4.0.3
    • Fix Version/s: 4.1.0
    • Component/s: Framework
    • Environment:
      Windows
    • Tags:
    • Backlog priority:
      800
    • Sprint:
      nxDrive 11.1.1
    • Story Points:
      2

      Description

      For a unknown reason, on one Windows 10 machine, the local socket is denied access to Drive:

      2019-01-14 16:21:02 3408 8436 DEBUG nxdrive.commandline Command line: argv=['nxdrive://token...'], options=...)
      2019-01-14 16:21:02 3408 8436 INFO nxdrive.commandline Running on version 4.0.3
      2019-01-14 16:21:03 3408 8436 DEBUG nxdrive.osi OS integration type: Windows
      2019-01-14 16:21:03 3408 8436 WARNING nxdrive.utils qt process with PID 15152 already running
      2019-01-14 16:21:03 3408 8436 DEBUG nxdrive.commandline Opening local socket to send to the running instance (payload=b'<REDACTED>')
      2019-01-14 16:21:03 3408 8436 ERROR nxdrive.commandline Unable to open client socket: QLocalSocket::connectToServer: Access denied

       This prevents the account creation.

      In  addtion to the fix, we should log in TRACE the fullServerName when creating the socket.

      Update

      As we were unable to reproduce this specific error, we've taken several measures to prevent it from happening again:

      • Set World access on the socket to avoid permission issues.
      • Close listener before stopping the engine, in case a thread doesn't terminate and we have a zombie app, it won't block the socket.
      • Add the pid of the running instance to the name of the pipe to avoid reusing a busy pipe.

        Attachments

          Activity

            People

            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 3 hours
                1d 3h