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

Changes to the project config are not possible while in read-only mode #4101

Open
lukebailey opened this Issue Apr 5, 2019 · 6 comments

Comments

Projects
None yet
3 participants
@lukebailey
Copy link

commented Apr 5, 2019

Description

We are seeing a migration failure when updating to Craft 3.1.21 with the following stack trace:

image

Steps to reproduce

  1. Update from Craft 3.1.20.1 to Craft 3.1.21

Additional info

  • Craft version: 3.1.21
  • PHP version: 7.1
  • Database driver & version: MySQL
  • Plugins & versions: Various
@brandonkelly

This comment has been minimized.

Copy link
Member

commented Apr 5, 2019

The error you’re getting looks pretty serious, actually… it’s saying there is no row in the craft_info table. Is that in fact the case? Any idea how it got deleted? (Or perhaps there was an error when you first installed Craft that went ignored, so it was never created in the first place?)

@lukebailey

This comment has been minimized.

Copy link
Author

commented Apr 8, 2019

The row definitely exists and never been deleted, can see it is correctly dated from our upgrade to Craft 3:

image

I can see there is another occurrence of the error back in March this year around the time of Craft 3.1 upgrade,. However we have never seen this migration failure before, the error shown in the GUI actually relates to project config changes not being possible while in read-only mode, assume that the missing info row is a red herring?

@brandonkelly

This comment has been minimized.

Copy link
Member

commented Apr 8, 2019

Hm, yeah maybe. Pretty strange though.

@lukebailey

This comment has been minimized.

Copy link
Author

commented Apr 10, 2019

Is there anything else we could do to diagnose/reproduce? Running the update again and has gone through ok this time but feel uneasy about such 'transient' errors...

@andris-sevcenko

This comment has been minimized.

Copy link
Member

commented Apr 10, 2019

@lukebailey are you seeing anything around that time in your mysql error logs, perhaps?

@lukebailey

This comment has been minimized.

Copy link
Author

commented Apr 12, 2019

@andris-sevcenko nothing in the SQL logs of note, are you thinking that there was a query failure rather than the row actually missing then (which it's not)?

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