5.3 - Update auf aktuelle 5.3-Version - composer install wird nicht weiter ausgeführt

[Ofz]

Hallo zusammen,

ich hatte beabsichtigt, in Vorbereitung auf ein Update auf die 5.7er-Version, meine Instanz aus dem Zweig 5.3 auf die aktuelle 5.3er-Version zu aktualisieren. Hier sind beiden ersten Schritte anscheinend erfolgreich abgeschlossen worden.

Im Augenblick steht der Contao Manager in dem Schritt "composer install" - es gibt aber keine weitere Verarbeitung bzw. keinen Fortschritt.

Welche Möglichkeiten habe ich, den Update-Prozess noch einmal zu starten bzw. in wie weit könnte ich den Update-Prozess abbrechen?

Über eine Rückmeldung würde ich mich freuen und bedanke mich im Voraus.


####################################

Ausgabe Contao Manager:

composer update contao/manager-bundle contao/news-bundle contao/calendar-bundle contao/faq-bundle contao/comments-bundle contao/newsletter-bundle contao/listing-bundle contao/conflicts contao/core-bundle --no-installErfolgreich nach 18 Sekunden. RAM-Verbrauch: 17.9MB (Spitze: 228.9MB), Dauer: 21.63s.

> Resolving dependencies using Composer Cloud v3.9.2
[8.4MiB/0.26s] Loading composer repositories with package information
[93.7MiB/20.32s] Updating dependencies
[31.0MiB/21.00s] Lock file operations: 0 installs, 68 updates, 0 removals
[31.0MiB/21.00s] - Upgrading composer/ca-bundle (1.5.10 => 1.5.11)
[31.0MiB/21.00s] - Upgrading contao-components/contao (9.4.1 => 9.4.2)
[31.0MiB/21.00s] - Upgrading contao-components/swiper (12.1.2 => 12.1.3)
[31.0MiB/21.00s] - Upgrading contao-components/tristen-tablesort (5.7.0 => 5.7.1)
[31.0MiB/21.00s] - Upgrading contao/calendar-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.00s] - Upgrading contao/comments-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.00s] - Upgrading contao/conflicts (dev-main 191b084 => dev-main 0074604)
[31.0MiB/21.01s] - Upgrading contao/core-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading contao/faq-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading contao/listing-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading contao/manager-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading contao/news-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading contao/newsletter-bundle (5.3.45 => 5.3.46)
[31.0MiB/21.01s] - Upgrading doctrine/orm (2.20.9 => 2.20.10)
[31.0MiB/21.01s] - Upgrading doctrine/persistence (3.4.3 => 3.4.4)
[31.0MiB/21.01s] - Upgrading league/commonmark (2.8.1 => 2.8.2)
[31.0MiB/21.01s] - Upgrading league/flysystem (3.32.0 => 3.33.0)
[31.0MiB/21.01s] - Upgrading league/uri (7.8.0 => 7.8.1)
[31.0MiB/21.01s] - Upgrading league/uri-components (7.8.0 => 7.8.1)
[31.0MiB/21.01s] - Upgrading league/uri-interfaces (7.8.0 => 7.8.1)
[31.0MiB/21.01s] - Upgrading php-feed-io/feed-io (v6.2.0 => v6.3.1)
[31.0MiB/21.01s] - Upgrading symfony-cmf/routing-bundle (3.1.2 => 3.2.0)
[31.0MiB/21.01s] - Upgrading symfony/cache (v6.4.35 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/config (v6.4.34 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/console (v6.4.35 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/css-selector (v7.4.6 => v7.4.9)
[31.0MiB/21.02s] - Upgrading symfony/debug-bundle (v6.4.27 => v6.4.35)
[31.0MiB/21.02s] - Upgrading symfony/dependency-injection (v6.4.35 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/dotenv (v6.4.30 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/error-handler (v6.4.32 => v6.4.36)
[31.0MiB/21.02s] - Upgrading symfony/event-dispatcher (v6.4.32 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/filesystem (v6.4.34 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/form (v6.4.35 => v6.4.36)
[31.0MiB/21.02s] - Upgrading symfony/framework-bundle (v6.4.35 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/http-client (v6.4.34 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/http-kernel (v6.4.35 => v6.4.36)
[31.0MiB/21.02s] - Upgrading symfony/intl (v6.4.34 => v6.4.36)
[31.0MiB/21.02s] - Upgrading symfony/lock (v7.4.6 => v7.4.9)
[31.0MiB/21.02s] - Upgrading symfony/messenger (v6.4.35 => v6.4.37)
[31.0MiB/21.02s] - Upgrading symfony/mime (v6.4.35 => v6.4.37)
[31.0MiB/21.03s] - Upgrading symfony/monolog-bridge (v6.4.34 => v6.4.37)
[31.0MiB/21.03s] - Upgrading symfony/monolog-bundle (v3.11.1 => v3.11.2)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-ctype (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-intl-grapheme (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-intl-icu (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-intl-idn (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-intl-normalizer (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-mbstring (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-php73 (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-php80 (v1.33.0 => v1.37.0)
[31.0MiB/21.03s] - Upgrading symfony/polyfill-php83 (v1.33.0 => v1.37.0)
[31.0MiB/21.04s] - Upgrading symfony/polyfill-php84 (v1.33.0 => v1.37.0)
[31.0MiB/21.04s] - Upgrading symfony/polyfill-uuid (v1.33.0 => v1.37.0)
[31.0MiB/21.04s] - Upgrading symfony/property-info (v7.4.7 => v7.4.8)
[31.0MiB/21.04s] - Upgrading symfony/rate-limiter (v6.4.35 => v6.4.37)
[31.0MiB/21.04s] - Upgrading symfony/routing (v6.4.34 => v6.4.37)
[31.0MiB/21.04s] - Upgrading symfony/security-bundle (v6.4.34 => v6.4.36)
[31.0MiB/21.04s] - Upgrading symfony/security-core (v6.4.31 => v6.4.36)
[31.0MiB/21.04s] - Upgrading symfony/twig-bridge (v6.4.35 => v6.4.36)
[31.0MiB/21.04s] - Upgrading symfony/type-info (v7.4.7 => v7.4.9)
[31.0MiB/21.05s] - Upgrading symfony/validator (v6.4.35 => v6.4.37)
[31.0MiB/21.05s] - Upgrading symfony/var-dumper (v6.4.32 => v6.4.36)
[31.0MiB/21.05s] - Upgrading symfony/var-exporter (v7.4.0 => v7.4.9)
[31.0MiB/21.05s] - Upgrading symfony/web-profiler-bundle (v6.4.32 => v6.4.36)
[31.0MiB/21.05s] - Upgrading toflar/cronjob-supervisor (2.1.1 => 2.1.2)
[31.0MiB/21.05s] - Upgrading twig/extra-bundle (v3.23.0 => v3.24.0)
[31.0MiB/21.05s] - Upgrading twig/string-extra (v3.23.0 => v3.24.0)
[31.0MiB/21.05s] - Upgrading twig/twig (v3.23.0 => v3.24.0)
[30.0MiB/21.08s] Writing lock file
[17.0MiB/21.11s] <warning>Package doctrine/annotations is abandoned, you should avoid using it. No replacement was suggested.</warning>
[17.0MiB/21.12s] <warning>Package doctrine/cache is abandoned, you should avoid using it. No replacement was suggested.</warning>
[17.0MiB/21.12s] <warning>Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.</warning>
[17.2MiB/21.61s] <warning>Found 2 security vulnerability advisories affecting 1 package.</warning>
[17.2MiB/21.61s] Run "composer audit" for a full list of advisories.
[17.9MiB/21.62s] Memory usage: 17.9MB (peak: 228.9MB), time: 21.63s.
[17.9MiB/21.62s] Finished Composer Cloud resolving.
# Job ID uYoc36n[....]65JkHzctp completed in 18 seconds
# Memory usage: 17.9MB (peak: 228.9MB), time: 21.63s.
vendor/bin/contao-console contao:maintenance-mode enable

Hoster ist Alfahosting mit PHP 8.3

[mlweb]

Einfach abbrechen und ggf. einen noch laufenden Job löschen ( Datei /contao-manager/task.json löschen)

[JamesdK]

Ich habe in der letzten Zeit die Erfahrung bei Alfahosting gemacht, dass Updates besser nur via Konsole durchgeführt werden. Ist seit ca. 2-3 Monaten so. Der Contao-Manager blieb hier auch immer hängen.
Dann Marens Vorschlag: abbrechen, task.json löschen und auf der Konsole neu anstoßen:

/opt/plesk/php/8.X/bin/php public/contao-manager.phar.php composer update
/opt/plesk/php/8.X/bin/php bin/console contao:migrate 

(PHP-Version anpassen)

[mlweb]

Scheint aber dann am einzelnen Server zu liegen, möglicherweise auch daran, ob es einer der neueren ist oder noch ein alter. Ich habe auch einen Kunden bei Alfahosting und alle Updates - auch in den letzten Monaten - liefen problemlos durch.

[Ofz]

Vielen Dank für die Rückmeldungen - anscheinend geht es in dem Account jetzt nur noch über die Console.