Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.IO.PathTooLongException when running XP topology #1039

Open
3 tasks done
nathaniel-coxall-maersk opened this issue Jul 25, 2022 · 0 comments
Open
3 tasks done

Comments

@nathaniel-coxall-maersk
Copy link

nathaniel-coxall-maersk commented Jul 25, 2022

ISSUE

  • I have tried with the latest version of Docker for Windows (Stable or Edge) or Docker Enterprise.
  • Windows version is at least 1809 / ltsc2019.
  • Windows has the latest updates installed.

Expected behavior

Running docker compose should complete successfully and all containers should be running successfully.

Actual behavior

Multiple containers throw a System.IO.PathTooLongException, especially the 93x-xconnect-processingengine-1 container.

Additional information

  • This happens every time I try to run the XP topology (not that I've tried any other topologies)

  • The issue has occurred since my first attempt (it's always happened, I've never had the containers spin up successfully)

  • Output from docker info:

    Client:
     Context:    default
     Debug Mode: false
     Plugins:
      buildx: Docker Buildx (Docker Inc., v0.8.2)
      compose: Docker Compose (Docker Inc., v2.6.1)
      extension: Manages Docker extensions (Docker Inc., v0.2.7)
      sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
      scan: Docker Scan (Docker Inc., v0.17.0)
    
    Server:
     Containers: 8
      Running: 5
      Paused: 0
      Stopped: 3
     Images: 190
     Server Version: 20.10.17
     Storage Driver: lcow (linux) windowsfilter (windows)
      LCOW:
      Windows:
     Logging Driver: json-file
     Plugins:
      Volume: local
      Network: ics internal l2bridge l2tunnel nat null overlay private transparent
      Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
     Swarm: inactive
     Default Isolation: hyperv
     Kernel Version: 10.0 19044 (19041.1.amd64fre.vb_release.191206-1406)
     Operating System: Windows 10 Enterprise Version 2009 (OS Build 19044.1826)
     OSType: windows
     Architecture: x86_64
     CPUs: 8
     Total Memory: 31.69GiB
     Name: MMD5CG1413JRK
     ID: EZBM:BGWN:SYTQ:4H5Q:QPA5:N7XE:YPNF:NRG3:5SZS:GZVW:UYPM:6U45
     Docker Root Dir: C:\ProgramData\Docker
     Debug Mode: false
     Registry: https://index.docker.io/v1/
     Labels:
     Experimental: true
     Insecure Registries:
      127.0.0.0/8
     Live Restore Enabled: false
     Product License: Community Engine
    
  • Are you running inside a virtualized Windows machine or physical: Physical

  • I've attached a file containing the console log
    log.txt

  • Here's an excerpt of the exception:

    93x-xconnect-processingengine-1  | System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
    93x-xconnect-processingengine-1  |    at System.IO.LongPathHelper.Normalize(String path, UInt32 maxPathLength, Boolean checkInvalidCharacters, Boolean expandShortPaths)
    93x-xconnect-processingengine-1  |    at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
    93x-xconnect-processingengine-1  |    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    93x-xconnect-processingengine-1  |    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
    93x-xconnect-processingengine-1  |    at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
    93x-xconnect-processingengine-1  |    at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
    93x-xconnect-processingengine-1  |    at ‫‍‌​‫‏‏‭‎‮‪‎‪‫‫‏‫‌‎‭‎​‪‫‭‌‏‮‮‮.‎​‪‎‭‪‫‭‭‬‎‪‏‪‮‌‮‫‭‮(‭‪‌‏‪‌‬‎‎‌‍‮‍‫​‏‫‏​‮‏‍‏‮‬‎‮ , String )
    93x-xconnect-processingengine-1  |    at ‭‪‌‏‪‌‬‎‎‌‍‮‍‫​‏‫‏​‮‏‍‏‮‬‎‮..ctor(String )
    93x-xconnect-processingengine-1  |    at ‬‮‍‎‍​‭‎‮‮‪‏‮‏‌‪‎‭‌‍‭‪‬‮..ctor(String )
    93x-xconnect-processingengine-1  |    at Sitecore.XConnect.Configuration.Extensions.InitializeLicenseCheck(IServiceCollection collection, String licenseFileOrXml)
    93x-xconnect-processingengine-1  |    at Sitecore.XConnect.Configuration.Extensions.UseXConnectServiceInitializationConfiguration(IServiceCollection collection, IConfiguration configuration, String[] configurationSectionNames, String initializationSectionName, Boolean validateConfiguration)
    93x-xconnect-processingengine-1  |    at Sitecore.Processing.Engine.Startup.ConfigureServices(IServiceCollection services)
    93x-xconnect-processingengine-1  |    at Sitecore.Processing.Engine.Hosting.HostBuilder.CreateServiceCollection(IHostBuilderOptions options, IConfigurationBuilder configurationBuilder, String configurationEnvironmentName)
    93x-xconnect-processingengine-1  |    at Sitecore.Processing.Engine.Hosting.HostBuilder.Build(IHostBuilderOptions options,         IConfigurationBuilder configurationBuilder)
    93x-xconnect-processingengine-1  |    at Sitecore.Processing.Engine.App.Program.RunAsConsoleApp()
    

Steps to reproduce the behavior

  1. .\Build.ps1 -SitecoreVersion "9.3.0" -Topology "XP"
  2. Set the licence variable
  3. docker-compose -f .\build\windows\tests\9.3.x\docker-compose.xp.yml up
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant