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

Updater in production mode gets stuck #5431

Closed
helderdb opened this issue Jan 14, 2020 · 3 comments
Closed

Updater in production mode gets stuck #5431

helderdb opened this issue Jan 14, 2020 · 3 comments

Comments

@helderdb
Copy link

@helderdb helderdb commented Jan 14, 2020

Description

Sorry if this is already addressed, did not find it yet.

I just ran into a very annoying issue while upgrading one of our craft sites. We have multiple environments where we test from local to a semi-staging environment (this is where the root of the problem lays, devMode is enbaled here). All is dockerized.
When upgrading on our staging, an update prompt shows when navigating to /admin, you click finish up and the database upgrades with the craft installation. It does however say that it cannot backup the database, but since I manually did this I click 'continue anyway'. However, on our production stage, the prompt is not shown to skip the database backup and it hangs at "Checking environment..." and nothing happens. Until you enable devMode, you cannot update the craft installation.

Steps to reproduce

  1. Update craft installation in docker image
  2. Deploy docker to production (devMode = false)
  3. Navigate to example.com/admin
  4. Click 'finish up' button
  5. Update hangs!

Additional info

  • Craft version: 3.3.19
  • PHP version: 7.3
  • Database driver & version: MySQL 5.7.24
@brandonkelly

This comment has been minimized.

Copy link
Member

@brandonkelly brandonkelly commented Jan 14, 2020

It’s certainly possible to run update migrations when Dev Mode is disabled. So something else is going on here. Please zip up your storage/logs/ folder and send it into support@craftcms.com, and reference this issue. Maybe we’ll be able to find additional clues in there.

@helderdb

This comment has been minimized.

Copy link
Author

@helderdb helderdb commented Jan 14, 2020

@brandonkelly I accidentally deleted the logs while creating the docker volume. I'll send them next time I encounter this. However, I was not able to reproduce the problem on our staging env where I disabled devMode and did the same upgrade, so it's weird.

@brandonkelly

This comment has been minimized.

Copy link
Member

@brandonkelly brandonkelly commented Jan 14, 2020

Alright, will close this for now. If it happens again, please immediately check your logs or send them into support@craftcms.com.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.