Programmabsturz nach Update

Nach dem Update von 6.6.7.1 auf 6.6.8.0 kann ich den Shop und das Backend nicht mehr öffnen.
Anscheinend ist ein Plugin doppelt geladen. Es trägt die Bezeichnung: „PentatrionViteBundle“ . Kann jemannd damit etwas anfangen.

Hier habe ich auch die Log-Datei:
Run Update preparations

pre-update-cmd: Symfony\Flex\Flex->configureInstaller
Loading composer repositories with package information
pre-pool-create: Symfony\Flex\Flex->truncatePackages
Updating dependencies
Dependency resolution completed in 0.007 seconds
Analyzed 1184 packages to resolve dependencies
Analyzed 14960 rules to resolve dependencies
Dependency resolution completed in 0.001 seconds
Lock file operations: 2 installs, 63 updates, 0 removals
Installs: pentatrion/vite-bundle:v7.0.5, async-aws/core:1.22.1
Updates: symfony/runtime:v7.1.7, shopware/core:v6.6.8.0, twig/twig:v3.14.1, symfony/yaml:v7.1.6, symfony/finder:v7.1.6, symfony/string:v7.1.6, symfony/intl:v7.1.7, symfony/var-exporter:v7.1.6, symfony/validator:v7.1.7, symfony/http-foundation:v7.1.7, symfony/event-dispatcher:v7.1.6, symfony/var-dumper:v7.1.7, symfony/error-handler:v7.1.7, symfony/http-kernel:v7.1.7, symfony/twig-bridge:v7.1.6, symfony/dependency-injection:v7.1.6, symfony/filesystem:v7.1.6, symfony/config:v7.1.7, symfony/twig-bundle:v7.1.6, symfony/translation:v7.1.6, symfony/stopwatch:v7.1.6, symfony/serializer:v7.1.6, symfony/password-hasher:v7.1.6, symfony/security-core:v7.1.6, symfony/clock:v7.1.6, symfony/scheduler:v7.1.6, symfony/routing:v7.1.6, symfony/options-resolver:v7.1.6, symfony/rate-limiter:v7.1.7, symfony/psr-http-message-bridge:v7.1.6, laminas/laminas-code:4.15.1, symfony/proxy-manager-bridge:v6.4.13, symfony/type-info:v7.1.6, symfony/property-info:v7.1.6, symfony/property-access:v7.1.6, symfony/process:v7.1.7, symfony/monolog-bridge:v7.1.6, symfony/mime:v7.1.6, symfony/messenger:v7.1.6, symfony/mailer:v7.1.6, symfony/lock:v7.1.6, symfony/http-client:v7.1.7, symfony/cache:v7.1.7, symfony/framework-bundle:v7.1.6, symfony/dotenv:v7.1.6, symfony/doctrine-messenger:v7.1.6, symfony/debug-bundle:v7.1.6, symfony/console:v7.1.7, symfony/asset:v7.1.6, lcobucci/jwt:5.4.1, ezyang/htmlpurifier:v4.18.0, tecnickcom/tcpdf:6.7.7, sabberworm/php-css-parser:v8.7.0, composer/ca-bundle:1.5.3, shopware/administration:v6.6.8.0, symfony/dom-crawler:v7.1.6, symfony/browser-kit:v7.1.6, phpunit/phpunit:10.5.38, symfony/web-profiler-bundle:v7.1.7, doctrine/persistence:3.4.0, symfony/doctrine-bridge:v7.1.6, shopware/elasticsearch:v6.6.8.0, shopware/storefront:v6.6.8.0

  • Locking async-aws/core (1.22.1)
  • Upgrading composer/ca-bundle (1.5.2 => 1.5.3)
  • Upgrading doctrine/persistence (3.3.3 => 3.4.0)
  • Upgrading ezyang/htmlpurifier (v4.17.0 => v4.18.0)
  • Upgrading laminas/laminas-code (4.14.0 => 4.15.1)
  • Upgrading lcobucci/jwt (5.4.0 => 5.4.1)
  • Locking pentatrion/vite-bundle (v7.0.5)
  • Upgrading phpunit/phpunit (10.5.37 => 10.5.38)
  • Upgrading sabberworm/php-css-parser (v8.6.0 => v8.7.0)
  • Upgrading shopware/administration (v6.6.7.1 => v6.6.8.0)
  • Upgrading shopware/core (v6.6.7.1 => v6.6.8.0)
  • Upgrading shopware/elasticsearch (v6.6.7.1 => v6.6.8.0)
  • Upgrading shopware/storefront (v6.6.7.1 => v6.6.8.0)
  • Upgrading symfony/asset (v7.1.1 => v7.1.6)
  • Upgrading symfony/browser-kit (v7.1.1 => v7.1.6)
  • Upgrading symfony/cache (v7.1.5 => v7.1.7)
  • Upgrading symfony/clock (v7.1.1 => v7.1.6)
  • Upgrading symfony/config (v7.1.1 => v7.1.7)
  • Upgrading symfony/console (v7.1.5 => v7.1.7)
  • Upgrading symfony/debug-bundle (v7.1.1 => v7.1.6)
  • Upgrading symfony/dependency-injection (v7.1.5 => v7.1.6)
  • Upgrading symfony/doctrine-bridge (v7.1.5 => v7.1.6)
  • Upgrading symfony/doctrine-messenger (v7.1.5 => v7.1.6)
  • Upgrading symfony/dom-crawler (v7.1.5 => v7.1.6)
  • Upgrading symfony/dotenv (v7.1.5 => v7.1.6)
  • Upgrading symfony/error-handler (v7.1.3 => v7.1.7)
  • Upgrading symfony/event-dispatcher (v7.1.1 => v7.1.6)
  • Upgrading symfony/filesystem (v7.1.5 => v7.1.6)
  • Upgrading symfony/finder (v7.1.4 => v7.1.6)
  • Upgrading symfony/framework-bundle (v7.1.5 => v7.1.6)
  • Upgrading symfony/http-client (v7.1.5 => v7.1.7)
  • Upgrading symfony/http-foundation (v7.1.5 => v7.1.7)
  • Upgrading symfony/http-kernel (v7.1.5 => v7.1.7)
  • Upgrading symfony/intl (v7.1.5 => v7.1.7)
  • Upgrading symfony/lock (v7.1.1 => v7.1.6)
  • Upgrading symfony/mailer (v7.1.5 => v7.1.6)
  • Upgrading symfony/messenger (v7.1.5 => v7.1.6)
  • Upgrading symfony/mime (v7.1.5 => v7.1.6)
  • Upgrading symfony/monolog-bridge (v7.1.1 => v7.1.6)
  • Upgrading symfony/options-resolver (v7.1.1 => v7.1.6)
  • Upgrading symfony/password-hasher (v7.1.1 => v7.1.6)
  • Upgrading symfony/process (v7.1.5 => v7.1.7)
  • Upgrading symfony/property-access (v7.1.4 => v7.1.6)
  • Upgrading symfony/property-info (v7.1.3 => v7.1.6)
  • Upgrading symfony/proxy-manager-bridge (v6.4.8 => v6.4.13)
  • Upgrading symfony/psr-http-message-bridge (v7.1.4 => v7.1.6)
  • Upgrading symfony/rate-limiter (v7.1.1 => v7.1.7)
  • Upgrading symfony/routing (v7.1.4 => v7.1.6)
  • Upgrading symfony/runtime (v7.1.1 => v7.1.7)
  • Upgrading symfony/scheduler (v7.1.1 => v7.1.6)
  • Upgrading symfony/security-core (v7.1.5 => v7.1.6)
  • Upgrading symfony/serializer (v7.1.5 => v7.1.6)
  • Upgrading symfony/stopwatch (v7.1.1 => v7.1.6)
  • Upgrading symfony/string (v7.1.5 => v7.1.6)
  • Upgrading symfony/translation (v7.1.5 => v7.1.6)
  • Upgrading symfony/twig-bridge (v7.1.5 => v7.1.6)
  • Upgrading symfony/twig-bundle (v7.1.5 => v7.1.6)
  • Upgrading symfony/type-info (v7.1.5 => v7.1.6)
  • Upgrading symfony/validator (v7.1.5 => v7.1.7)
  • Upgrading symfony/var-dumper (v7.1.5 => v7.1.7)
  • Upgrading symfony/var-exporter (v7.1.2 => v7.1.6)
  • Upgrading symfony/web-profiler-bundle (v7.1.4 => v7.1.7)
  • Upgrading symfony/yaml (v7.1.5 => v7.1.6)
  • Upgrading tecnickcom/tcpdf (6.7.6 => 6.7.7)
  • Upgrading twig/twig (v3.14.0 => v3.14.1)
    Writing lock file
    Installing dependencies from lock file (including require-dev)

pre-operations-exec: Symfony\Flex\Flex->recordOperations
Package operations: 2 installs, 63 updates, 0 removals
Installs: pentatrion/vite-bundle:v7.0.5, async-aws/core:1.22.1
Updates: symfony/runtime:v7.1.7, symfony/process:v7.1.7, shopware/core:v6.6.8.0, symfony/yaml:v7.1.6, symfony/finder:v7.1.6, twig/twig:v3.14.1, symfony/string:v7.1.6, symfony/intl:v7.1.7, tecnickcom/tcpdf:6.7.7, symfony/var-exporter:v7.1.6, symfony/validator:v7.1.7, symfony/twig-bridge:v7.1.6, symfony/http-foundation:v7.1.7, symfony/event-dispatcher:v7.1.6, symfony/var-dumper:v7.1.7, symfony/error-handler:v7.1.7, symfony/http-kernel:v7.1.7, symfony/dependency-injection:v7.1.6, symfony/filesystem:v7.1.6, symfony/config:v7.1.7, symfony/twig-bundle:v7.1.6, symfony/translation:v7.1.6, symfony/stopwatch:v7.1.6, symfony/serializer:v7.1.6, symfony/password-hasher:v7.1.6, symfony/security-core:v7.1.6, symfony/clock:v7.1.6, symfony/scheduler:v7.1.6, symfony/routing:v7.1.6, symfony/options-resolver:v7.1.6, symfony/rate-limiter:v7.1.7, symfony/psr-http-message-bridge:v7.1.6, laminas/laminas-code:4.15.1, symfony/proxy-manager-bridge:v6.4.13, symfony/type-info:v7.1.6, symfony/property-info:v7.1.6, symfony/property-access:v7.1.6, symfony/monolog-bridge:v7.1.6, symfony/mime:v7.1.6, symfony/messenger:v7.1.6, symfony/mailer:v7.1.6, symfony/lock:v7.1.6, symfony/http-client:v7.1.7, symfony/cache:v7.1.7, symfony/framework-bundle:v7.1.6, symfony/dotenv:v7.1.6, symfony/doctrine-messenger:v7.1.6, symfony/debug-bundle:v7.1.6, symfony/console:v7.1.7, symfony/asset:v7.1.6, lcobucci/jwt:5.4.1, ezyang/htmlpurifier:v4.18.0, sabberworm/php-css-parser:v8.7.0, composer/ca-bundle:1.5.3, shopware/administration:v6.6.8.0, symfony/web-profiler-bundle:v7.1.7, doctrine/persistence:3.4.0, symfony/doctrine-bridge:v7.1.6, symfony/dom-crawler:v7.1.6, symfony/browser-kit:v7.1.6, phpunit/phpunit:10.5.38, shopware/elasticsearch:v6.6.8.0, shopware/storefront:v6.6.8.0

  • Downloading symfony/runtime (v7.1.7)
  • Downloading symfony/process (v7.1.7)
  • Downloading twig/twig (v3.14.1)
  • Downloading symfony/intl (v7.1.7)
  • Downloading symfony/validator (v7.1.7)
  • Downloading symfony/http-foundation (v7.1.7)
  • Downloading symfony/var-dumper (v7.1.7)
  • Downloading symfony/error-handler (v7.1.7)
  • Downloading symfony/http-kernel (v7.1.7)
  • Downloading symfony/config (v7.1.7)
  • Downloading symfony/rate-limiter (v7.1.7)
  • Downloading symfony/http-client (v7.1.7)
  • Downloading symfony/cache (v7.1.7)
  • Downloading symfony/console (v7.1.7)
  • Downloading lcobucci/jwt (5.4.1)
  • Downloading shopware/administration (v6.6.8.0)
  • Downloading symfony/web-profiler-bundle (v7.1.7)
  • Downloading shopware/elasticsearch (v6.6.8.0)
  • Downloading shopware/storefront (v6.6.8.0)
  • Upgrading symfony/runtime (v7.1.1 => v7.1.7): Extracting archive

post-package-update: Symfony\Flex\Flex->enableThanksReminder

  • Upgrading symfony/process (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading shopware/core (v6.6.7.1 => v6.6.8.0): Extracting archive
  • Upgrading symfony/yaml (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/finder (v7.1.4 => v7.1.6): Extracting archive
  • Upgrading twig/twig (v3.14.0 => v3.14.1): Extracting archive
  • Upgrading symfony/string (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/intl (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading tecnickcom/tcpdf (6.7.6 => 6.7.7): Extracting archive
  • Upgrading symfony/var-exporter (v7.1.2 => v7.1.6): Extracting archive
  • Upgrading symfony/validator (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/twig-bridge (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/http-foundation (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/event-dispatcher (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/var-dumper (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/error-handler (v7.1.3 => v7.1.7): Extracting archive
  • Upgrading symfony/http-kernel (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/dependency-injection (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/filesystem (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/config (v7.1.1 => v7.1.7): Extracting archive
  • Upgrading symfony/twig-bundle (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/translation (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/stopwatch (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/serializer (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/password-hasher (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/security-core (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/clock (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/scheduler (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/routing (v7.1.4 => v7.1.6): Extracting archive
  • Upgrading symfony/options-resolver (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/rate-limiter (v7.1.1 => v7.1.7): Extracting archive
  • Upgrading symfony/psr-http-message-bridge (v7.1.4 => v7.1.6): Extracting archive
  • Upgrading laminas/laminas-code (4.14.0 => 4.15.1): Extracting archive
  • Upgrading symfony/proxy-manager-bridge (v6.4.8 => v6.4.13): Extracting archive
  • Upgrading symfony/type-info (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/property-info (v7.1.3 => v7.1.6): Extracting archive
  • Upgrading symfony/property-access (v7.1.4 => v7.1.6): Extracting archive
  • Upgrading symfony/monolog-bridge (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/mime (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/messenger (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/mailer (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/lock (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/http-client (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/cache (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/framework-bundle (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/dotenv (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/doctrine-messenger (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/debug-bundle (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading symfony/console (v7.1.5 => v7.1.7): Extracting archive
  • Upgrading symfony/asset (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading lcobucci/jwt (5.4.0 => 5.4.1): Extracting archive
  • Upgrading ezyang/htmlpurifier (v4.17.0 => v4.18.0): Extracting archive
  • Upgrading sabberworm/php-css-parser (v8.6.0 => v8.7.0): Extracting archive
  • Upgrading composer/ca-bundle (1.5.2 => 1.5.3): Extracting archive
  • Installing pentatrion/vite-bundle (v7.0.5): Extracting archive
  • Upgrading shopware/administration (v6.6.7.1 => v6.6.8.0): Extracting archive
  • Upgrading symfony/web-profiler-bundle (v7.1.4 => v7.1.7): Extracting archive
  • Upgrading doctrine/persistence (3.3.3 => 3.4.0): Extracting archive
  • Upgrading symfony/doctrine-bridge (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/dom-crawler (v7.1.5 => v7.1.6): Extracting archive
  • Upgrading symfony/browser-kit (v7.1.1 => v7.1.6): Extracting archive
  • Upgrading phpunit/phpunit (10.5.37 => 10.5.38): Extracting archive
  • Installing async-aws/core (1.22.1): Extracting archive
  • Upgrading shopware/elasticsearch (v6.6.7.1 => v6.6.8.0): Extracting archive
  • Upgrading shopware/storefront (v6.6.7.1 => v6.6.8.0): Extracting archive

post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-install: Symfony\Flex\Flex->recordFlexInstall
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-install: Symfony\Flex\Flex->recordFlexInstall
post-package-update: Symfony\Flex\Flex->enableThanksReminder
post-package-update: Symfony\Flex\Flex->enableThanksReminder
Generating optimized autoload files
post-autoload-dump: Symfony\Component\Runtime\Internal\ComposerPlugin_composer_tmp0->updateAutoloadFile
128 packages you are using are looking for funding.
Use the composer fund command to find out more!
post-update-cmd: Symfony\Flex\Flex->update

What about running composer global require symfony/thanks && composer thanks now?
This will spread some :sparkling_heart: by sending a ★ to the GitHub repositories of your fellow package maintainers.

Symfony operations: 1 recipe (0089b5cba559ee2225cfeb3c8d521280)

  • Configuring pentatrion/vite-bundle (>=6.5): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    No security vulnerability advisories found.

Symfony operations: 20 recipes (2393c879bc21e8ecda0a41ce2aa7d6d7)

  • Configuring symfony/flex (>=1.0): From github.com/symfony/recipes:main
    Copying files from recipe
    Created „./.env“
  • Configuring symfony/framework-bundle (>=6.4): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Created „./config/services.yaml“
    Created „./src/Controller/.gitignore“
  • Configuring nyholm/psr7 (>=1.0): From github.com/shopware/recipes:main
    Copying files from recipe
    Created „./config/packages/nyholm_psr7.yaml“
  • Configuring pentatrion/vite-bundle (>=6.5): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
  • Configuring shopware/administration (>=6.6): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Created „./bin/build-administration.sh“
    Created „./bin/watch-administration.sh“
  • Configuring shopware/core (>=6.6): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Created „./bin/.htaccess“
    Created „./bin/build-js.sh“
    Created „./bin/ci“
    Created „./bin/console“
    Created „./bin/functions.sh“
    Created „./config/jwt/.gitignore“
    Created „./custom/.htaccess“
    Created „./custom/apps/.gitignore“
    Created „./custom/plugins/.gitignore“
    Created „./custom/static-plugins/.gitignore“
    Created „./files/.htaccess“
    Created „./public/.htaccess.dist“
    Created „./public/index.php“
    Created „./public/maintenance.html“
    Created „./var/.htaccess“
    Created „./.htaccess“
    Adding environment variable defaults
    Setting parameters
    Adding entries to .gitignore
  • IGNORING shopware/core (>=6.6): From github.com/shopware/recipes:main
    Adding Docker Compose definitions to „./docker-compose.yml“
    Adding Docker Compose definitions to „./docker-compose.override.yml“
    Docker Compose definitions have been modified. Please run „docker compose up --build“ again to apply the changes.
  • Configuring shopware/elasticsearch (>=6.6): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Adding environment variable defaults
    Setting parameters
    Adding Docker Compose definitions to „./docker-compose.yml“
    Adding Docker Compose definitions to „./docker-compose.override.yml“
    Docker Compose definitions have been modified. Please run „docker compose up --build“ again to apply the changes.
  • Configuring shopware/storefront (>=6.6): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Created „./bin/build-storefront.sh“
    Created „./bin/watch-storefront.sh“
    Adding environment variable defaults
  • Configuring symfony/console (>=5.4): From github.com/shopware/recipes:main
  • Configuring symfony/debug-bundle (>=5.3): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
  • Configuring symfony/lock (>=5.2): From github.com/symfony/recipes:main
    Copying files from recipe
    Created „./config/packages/lock.yaml“
    Adding environment variable defaults
  • Configuring symfony/mailer (>=4.3): From github.com/shopware/recipes:main
    Adding environment variable defaults
    Adding Docker Compose definitions to „./docker-compose.override.yml“
    Docker Compose definitions have been modified. Please run „docker compose up --build“ again to apply the changes.
  • Configuring symfony/messenger (>=6.0): From github.com/shopware/recipes:main
    Copying files from recipe
    Adding environment variable defaults
  • Configuring symfony/monolog-bundle (>=3.3): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
  • Configuring symfony/routing (>=6.4): From github.com/shopware/recipes:main
    Copying files from recipe
    Created „./config/routes.yaml“
  • Configuring symfony/translation (>=5.4): From github.com/shopware/recipes:main
  • Configuring symfony/twig-bundle (>=5.4): From github.com/shopware/recipes:main
    Enabling the package as a Symfony bundle
  • Configuring symfony/validator (>=5.3): From github.com/shopware/recipes:main
  • Configuring phpunit/phpunit (>=9.6): From github.com/symfony/recipes:main
    Copying files from recipe
    Created „./.env.test“
    Created „./phpunit.xml.dist“
    Created „./tests/bootstrap.php“
    Adding entries to .gitignore
  • Configuring symfony/web-profiler-bundle (>=6.1): From github.com/symfony/recipes:main
    Enabling the package as a Symfony bundle
    Copying files from recipe
    Created „./config/packages/web_profiler.yaml“
    Created „./config/routes/web_profiler.yaml“

Files have been reset to the latest version of the recipe.

  • Use git diff to inspect the changes.

    Not all of the changes will be relevant to your app: you now
    need to selectively add or revert them using e.g. a combination
    of git add -p and git checkout -p

  • Use git checkout . to revert the changes.

    New (untracked) files can be inspected using git clean --dry-run
    Add the new files you want to keep using git add
    then delete the rest using git clean --force

LogicException {#76
#message: „Trying to register two bundles with the same name „PentatrionViteBundle“.“
#code: 0
#file: „/var/www/web1732/htdocs/shopware6_Privat/vendor/symfony/http-kernel/Kernel.php“
#line: 342
trace: {
/var/www/web1732/htdocs/shopware6_Privat/vendor/symfony/http-kernel/Kernel.php:342 { …}
/var/www/web1732/htdocs/shopware6_Privat/vendor/shopware/core/Kernel.php:176 { …}
/var/www/web1732/htdocs/shopware6_Privat/bin/console:54 {
{closure}
› $application = new Application($kernel);
› $kernel->boot();

}
/var/www/web1732/htdocs/shopware6_Privat/vendor/autoload_runtime.php:24 { …}
/var/www/web1732/htdocs/shopware6_Privat/bin/console:17 { …}
}
}

Vor dem Update ein komplettes Backup gemacht? Alle Plugins deaktiviert und dann das Backup durchgeführt?

Nein leider nicht. Der Hoster hat ein altes Backup wieder eingespielt damit ich wieder ins Backend komme. Danach habe ich noch einmal ein Update durchgeführt und wieder ist Shopware abgestürzt.

Ich hänge mein Problem mal mit ran.

Update Fehler 6.6.8.0? - Shopware 6 (German) / Installation / Einstieg - Shopware Community Forum

Konnte das Problem lokalisiert werden?

Weiß man schon warum/weshalb das o. g. Problem auftritt und gibt es eine Lösung?

Also ich hätte einfach die Vermutung dass eventuell in der composer.json oder lock das bundle pentatrion/vite-bundle explizit vorhanden ist. Falls es vorhanden ist mal entfernen.
Ich habe leider grade nicht die neueste Shopware Version irgendwo zur Hand - deshalb nur Mutmaßungen

EDIT: ich habe grad mal einen Testshop von 6.6.6 auf 6.6.8.1 angehoben und kam „zum Glück? :)“ kein Fehler… also liegt es vermutlich nicht am Update allgemein, da dieser Shop rein ein DEV Shop ist für Plugins…

Du meinst Suchen unter composer.json und unter composer.lock?

Wird nicht gefunden.

genau da meinte ich,
ok alternativ wäre noch die config/bundles.php eine Idee.
Ansonsten ist es rätselraten und wenn müsste ich selbst mal danach schauen, sonst fehlt mir glaube ich grade eine Idee.

Die config/bundles.php sieht so aus:

<?php

return [
    Symfony\Bundle\FrameworkBundle\FrameworkBundle::class => ['all' => true],
    Shopware\Core\Framework\Framework::class => ['all' => true],
    Shopware\Core\System\System::class => ['all' => true],
    Shopware\Core\Content\Content::class => ['all' => true],
    Shopware\Core\Checkout\Checkout::class => ['all' => true],
    Shopware\Core\Maintenance\Maintenance::class => ['all' => true],
    Shopware\Core\DevOps\DevOps::class => ['e2e' => true],
    Shopware\Core\Profiling\Profiling::class => ['all' => true],
    Symfony\Bundle\TwigBundle\TwigBundle::class => ['all' => true],
    Symfony\Bundle\MonologBundle\MonologBundle::class => ['all' => true],
    Symfony\Bundle\DebugBundle\DebugBundle::class => ['dev' => true],
    Shopware\Administration\Administration::class => ['all' => true],
    Shopware\Elasticsearch\Elasticsearch::class => ['all' => true],
    Shopware\Storefront\Storefront::class => ['all' => true],
];

Mich wundert nur, dass bisher alle uodates Problemlos durchgeführt wurden. Ab der 6.6.8.0 gibt es dieses Problem. Ich schaue die 2 anderen auch nochmal durch.

Kann man eigentlich die 6.6.8.0 übersüringen und mit der 6.6.8.1 weiterfahren?

@info30

Moin, konnte der Fehler behoben werden bzw. weiß man woran es gelegen hat?

ja ich habe direkt von 6.6.6 auf 6.8.1 upgedatet und hatte kein Problem.

Hallo zusammen ,
ich habe denselben Problem und komme leider nicht weiter … update von 6.6.7.0 → 6.6.7.1 oder 6.6.8.0

LogicException {#84
#message: „Trying to register two bundles with the same name „PentatrionViteBundle“.“
#code: 0
#file: „/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/vendor/symfony/http-kernel/Kernel.php“
#line: 342
trace: {
/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/vendor/symfony/http-kernel/Kernel.php:342 { …}
/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/vendor/shopware/core/Kernel.php:176 { …}
/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/bin/console:54 {
{closure}
› $application = new Application($kernel);
› $kernel->boot();

}
/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/vendor/autoload_runtime.php:24 { …}
/var/www/vhosts/h649834.webshop2.dogado.net/canna-neo.de/staging/bin/console:17 { …}
}
}
2024-11-11T21:27:08+00:00 [info] User Deprecated: The „url“ connection parameter is deprecated. Please use Doctrine\DBAL\Tools\DsnParser to parse a database url before calling Doctrine\DBAL\DriverManager. (DriverManager.php:257 called by DriverManager.php:173, Standalone DSN parser by derrabus · Pull Request #5843 · doctrine/dbal · GitHub, package doctrine/dbal)
2024-11-11T21:27:08+00:00 [info] User Deprecated: Not configuring a schema manager factory is deprecated. Use Doctrine\DBAL\Schema\DefaultSchemaManagerFactory which is going to be the default in DBAL 4. (Connection.php:222 called by DriverManager.php:197, Create an easy way to extend the schema manager · Issue #5812 · doctrine/dbal · GitHub, package doctrine/dbal)
2024-11-11T21:27:08+00:00 [critical] Uncaught Exception: Trying to register two bundles with the same name „PentatrionViteBundle“.

:pensive:

Mal auf 6.6.8.1 probiert? Alle bisherig betroffenen hatten das mit 6.6.8.0, vielleicht hat es was mit der Version zu tun.

Was mir gerade geholfen hat war folgendes:

In der /config/packages habe ich in der messenger.yaml die Zeile mit dem reset_on_message: true auskommentiert. Mehr war nicht notwendig und dann gings durch. Habs jetzt auch mal mit einer anderen 6.6er verglichen und da existierte die Datei nicht.

Also bei mir hat jetzt auch geklappt .

ich habe mein Theme (von Zenit) und sein Child komplett deaktiviert .

Und in der ArrayNode.php die Zeilen 304 bis 307 auskommentiert.

/*$ex = new InvalidConfigurationException($msg);
$ex->setPath($this->getPath());
throw $ex; */

irgendwie habe ich das Gefühl, dass der Theme dran schuld war …

@cannaneo Das Problem liegt nicht am Theme. Bei dir ist ein Symfony Fehler aufgetreten. In deiner Nachricht hast du die Prüfung auf ungültige Symfony-Konfigurations-Variablen auskommentiert. Die Ursache ist also nicht unbedingt behoben und es könnte in Zukunft erneut zu diesem Fehler kommen oder Folgefehler entstehen. In einer der letzten Symfony-Versionen wurde „reset_on_message“ entfernt. Wenn diese Variable noch vorhanden ist, wird genau dieser Fehler geschmissen. Am besten prüfst du einmal, ob in der Datei „SHOPWAREROOT/config/packages/messenger.yaml“ dieser Wert noch vorhanden ist und entfernst diesen.

Gruß

Danke für die Info …
Die Datei messenger.yaml existiert bei mir nicht . auch in vorherige Version (6.6.7.0) war der nicht da …

jetzt bei v6.6.8.2 InOrdner /packages sind nur 2 Dateien - lock.yaml & nyholm_psr7.yaml

@cannaneo anscheinend wird die Datei nach dem erfolgreichen Update entfernt.

Hallo,
ich habe jetzt das Update von der Version 6.6.7.1 auf die 6.6.8.1 gemacht und keine Fehlermeldung mehr erhalten. Danach habe ich auch gleich die version 6.6.8.2 installiert, alles ohne Probleme. Es muss wohl an der Version 6.6.8.0 gelegen haben.
Vielen Dank für Eure Unterstützung.