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

Fehlermeldung bei das updaten von 4.3 auf 5.0 #822

Open
mrmikeeu opened this issue Aug 23, 2024 · 19 comments
Open

Fehlermeldung bei das updaten von 4.3 auf 5.0 #822

mrmikeeu opened this issue Aug 23, 2024 · 19 comments

Comments

@mrmikeeu
Copy link

Fehlermeldung bei das updaten von 4.3 auf 5.0:

Hintergrund-Prozess
Der Contao Manager konnte den Hintergrund-Prozess nicht starten.
Die Ausführung der Aufgabe ist fehlgeschlagen.
Sollte dies wiederholt geschehen, wird dein Server möglicherweise nicht unterstützt.

composer require contao/manager-bundle=5.0 contao/news-bundle=5.0 contao/calendar-bundle=5.0 contao/faq-bundle=5.0 contao/comments-bundle=5.0 contao/newsletter-bundle=5.0 contao/listing-bundle=5.0
composer update --no-install --dry-run
vendor/bin/contao-console contao:maintenance-mode enable
composer install --dry-run
vendor/bin/contao-console contao:maintenance-mode disable

Wäre gut zu wissen was nicht unterstützt wird, es gibt nirgendswo infos dazu.
Server ist bei Hostpoint, Schweiz, PHP8.3.10, MySQL10.6-MariaDB

@fritzmg
Copy link
Contributor

fritzmg commented Aug 23, 2024

Fehlermeldung bei das updaten von 4.3 auf 5.0:

Contao 5.0 has reached the end of its life, you need to update to Contao 5.3.* or 5.4.*.

You also need to update to Contao 4.13 first - you cannot update directly from Contao 4.3 to 5.

@mrmikeeu
Copy link
Author

I have version 4.13.46 installed. Update to 5.3.* gives the same error. Contao Manager 1.8.9.
Screenshot 2024-08-23 124004
image

@aschempp
Copy link
Member

The error does not look like it is related to the actually updated Contao versions. Do you get the same message when installing or updating any other package?

@mrmikeeu
Copy link
Author

On other Contao sites (on the same server) I could install packages (like the rocksolid packages) without problem.

As a test, on this site, I now installed madeyourday/contao-rocksolid-slider: same error.

So, your assumption is right.

What can be the reason that on the same server, but on other sites, this works fine, but not on this site? How can I see what the problem is? The error is vague, and the server obviously is supported.

@zoglo
Copy link
Member

zoglo commented Aug 26, 2024

You could try to run the same command via CLI if that's possible for you.

@mrmikeeu
Copy link
Author

I have no experience with CLI, I depend on the Contao UI

@zoglo
Copy link
Member

zoglo commented Aug 26, 2024

When updating, can you see more information in the posted screenshot? There should be a button to show more details.
That's what we are trying to figure out.

Did you try it with a blank contao installation? Are you sure it's not any dependencies that don't work on your setup?

I know that you depend on the Contao UI but we can't help you if all you are giving us is a:
It doesn't work + screenshots of us not seeing more information :/

@mrmikeeu
Copy link
Author

After refreshing the contao manager, it now added the madeyourday/contao-rocksolid-slider:

$ /usr/local/php83/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Zurich /home/eniseu1/www/2024.denisebucher.ch/public/contao-manager.phar.php composer require madeyourday/contao-rocksolid-slider --no-update --no-scripts --prefer-stable --sort-packages --no-ansi --no-interaction

Using version ^2.2 for madeyourday/contao-rocksolid-slider
/home/eniseu1/www/2024.denisebucher.ch/composer.json has been updated

Process terminated with exit code 0

Result: OK

Resolving dependencies using Composer Cloud v3.7.1

[6.8MiB/0.18s] Loading composer repositories with package information
[63.1MiB/7.77s] Updating dependencies
[26.0MiB/8.09s] Lock file operations: 1 install, 0 updates, 0 removals
[26.0MiB/8.09s] - Locking madeyourday/contao-rocksolid-slider (v2.2.6)
[25.4MiB/8.10s] Writing lock file
[12.6MiB/8.12s] Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
[12.8MiB/8.34s] No security vulnerability advisories found.
[13.3MiB/8.35s] Memory usage: 13.29MB (peak: 170.86MB), time: 8.35s.
[13.3MiB/8.35s] Finished Composer Cloud resolving.

Job ID floYF7BiV27pjBQBv47fhlWGzwdKeNgH7NwnCUpM53moVXfE8MkGfxVd2gsqN7k5rUa8n0IHdBjNCk1 completed in 1724662389 seconds

Memory usage: 13.29MB (peak: 170.86MB), time: 8.35s.

$ /usr/local/php83/bin/php -q -dmax_execution_time=0 -dmemory_limit=-1 -ddisplay_errors=0 -ddisplay_startup_errors=0 -derror_reporting=0 -dallow_url_fopen=1 -ddisable_functions= -ddate.timezone=Europe/Zurich /home/eniseu1/www/2024.denisebucher.ch/public/contao-manager.phar.php composer install --no-dev --no-progress --no-ansi --no-interaction --optimize-autoloader

Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Generating optimized autoload files
contao/manager-plugin: Dumping generated plugins file...
contao/manager-plugin: ...done dumping generated plugins file
103 packages you are using are looking for funding.
Use the composer fund command to find out more!

@php vendor/bin/contao-setup
Added the /home/eniseu1/www/2024.denisebucher.ch/public/app.php file.
Added the /home/eniseu1/www/2024.denisebucher.ch/public/index.php file.
Added the /home/eniseu1/www/2024.denisebucher.ch/public/preview.php file.

Trying to install assets as relative symbolic links.


  Bundle                   Method / Error    

✔ --- ------------------------ ------------------
Bundle Method / Error


✔ ContaoCoreBundle relative symlink
✔ ContaoFaqBundle relative symlink
✔ ContaoCommentsBundle relative symlink
✔ ContaoNewsBundle relative symlink
✔ ContaoCalendarBundle relative symlink
✔ ContaoNewsletterBundle relative symlink
✔ RockSolidSliderBundl


  Symlink                                     Target / Error                                                  

✔ public/files/bilder files/bilder
✔ public/files/gfx files/gfx
✔ public/files/headers files/headers
✔ public/files/tags files/tags
✔ public/files/tiny_templates files/tiny_templates
✔ public/files/css files/css
✔ system/themes/flexible vendor/contao/core-bundle/src/Resources/contao/themes/flexible
✔ public/assets assets
✔ public/system/themes system/themes
✔ system/logs var/logs
✔ public/vendor/scrivo/highlight_php/styles vendor/scrivo/highlight.php/styles


// Clearing the cache for the prod environment with debug
// false

[OK] Cache for the "prod" environment (debug=false) was successfully cleared.

// Clearing the cache for the dev environment with debug
// true

[OK] Cache for the "dev" environment (debug=true) was successfully cleared.

// Warming up the cache for the prod environment with debug
// false

[OK] Cache for the "prod" environment (debug=false) was successfully warmed.

[INFO] Done! Please open the Contao install tool or run the contao:migrate
command to make sure the database is up-to-date.

w/2024.denisebucher.ch/vendor/contao/manager-bundle/bin/contao-console cache:clear --no-warmup --env=prod --no-ansi" command:
In Filesystem.php line 297:

Cannot rename because the target "/home/eniseu1/www/2024.denisebucher.ch/va
r/cache/pro~" already exists.

cache:clear [--no-warmup] [--no-optional-warmers]

" ["exception" => RuntimeException { …},"message" => """ An error occurred while executing the "/usr/local/php83/bin/php -dmemory_limit=-1 /home/eniseu1/www/2024.denisebucher.ch/vendor/contao/manager-bundle/bin/contao-console cache:clear --no-warmup --env=prod --no-ansi" command: \n In Filesystem.php line 297:\n \n Cannot rename because the target "/home/eniseu1/www/2024.denisebucher.ch/va \n r/cache/pro~" already exists. \n \n \n cache:clear [--no-warmup] [--no-optional-warmers]\n \n """]

In ContaoSetupCommand.php line 146:

An error occurred while executing the "/usr/local/php83/bin/php -dmemory_li
mit=-1 /home/eniseu1/www/2024.denisebucher.ch/vendor/contao/manager-bundle/
bin/contao-console cache:clear --no-warmup --env=prod --no-ansi" command:
In Filesystem.php line 297:

Cannot rename because the target "/home/eniseu1/www/2024.denisebucher.ch/  

va
r/cache/pro~" already exists.

cache:clear [--no-warmup] [--no-optional-warmers]

contao:setup

Script @php vendor/bin/contao-setup handling the post-install-cmd event returned with error code 1

Process terminated with exit code 0

Result: OK

@mrmikeeu
Copy link
Author

I then tried to run the Contao Update to 5, but the same error happens. I cannot copy the full log, as the button to show more details does not do anything when this error happens.

@mrmikeeu
Copy link
Author

There are no dependencies, it's a pure Contao installation, an upgrade of a 3.* site, which went well and is running.

@mrmikeeu
Copy link
Author

Update: I now refreshed the contao manager again, when getting the error. It then proceeeds with the upgrade. Apparently, the status of the installation is not communicated well to the UI. After refreshing, the status is communicated properly.

@zoglo
Copy link
Member

zoglo commented Aug 26, 2024

It looks like it's trying to rename something but you are missing permissions.
How did you upgrade the website?

Did you simply copy everything?

Did you follow this guide?
https://docs.contao.org/manual/de/migration/

@mrmikeeu
Copy link
Author

@mrmikeeu
Copy link
Author

With other sites this worked flawlessly, funny enough, only this site gives problems

@zoglo
Copy link
Member

zoglo commented Aug 26, 2024

Could you delete the /var/cache folder and then run an update again and see if you get the same errors?

@mrmikeeu
Copy link
Author

I did, but it did not make a difference. Every time this error pops up, I have to do a hard reload on the contao manager, then it proceeds.

@aschempp
Copy link
Member

Every time this error pops up, I have to do a hard reload on the contao manager, then it proceeds.

You mean the task continues to run even though it did give you an error in the first place?

@mrmikeeu
Copy link
Author

Exactly. The contao manager front end gives the error, but when I do a hard reload, apparently the the task ran and completed.

@aschempp
Copy link
Member

can you check your browser console for the /task request? Does it ever give a response?

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

4 participants