Automated Job "Index Search Engine - Updates" throwing 504 error
Permalink
Hello! So, I'm a week into debugging this and trying to figure out why the "Index Search Engine - Updates" job is failing. When trying to run it, I get a 504 gateway error and the message it returns is:
I think this started after our upgrade to 8.5.4. One thought I had was maybe i could truncate some tables to try getting it to resync? (based on articles i found with the same issue in magento, but not sure what the concrete5 equivalent is) Any prods in the right direction would be appreciated.
An exception occurred while executing 'DELETE FROM QueueMessages WHERE handle = ?' with params ["47c6f367ac70c35946604570faa24511"]: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction
I think this started after our upgrade to 8.5.4. One thought I had was maybe i could truncate some tables to try getting it to resync? (based on articles i found with the same issue in magento, but not sure what the concrete5 equivalent is) Any prods in the right direction would be appreciated.
# concrete5 Version Core Version - 8.5.4 Version Installed - 8.5.4 Database Version - 20200609145307 # Database Information Version: 5.6.34-log SQL Mode: NO_ENGINE_SUBSTITUTION # concrete5 Packages DPS Crashmap Import (0.0.0), Resource Library (1.0.0), Solr Search (1.1.0) # concrete5 Cache Settings Block Cache - On Overrides Cache - On Full Page Caching - On - If blocks on the particular page allow it. Full Page Cache Lifetime - Every 6 hours (default setting). # Server Software
Viewing 15 lines of 42 lines. View entire code block.
1. How did you update concrete5 through the User Interface or manually?
Manually
2. Have you manually cleared out the applications/files/cache folder?
Yes
3. Do you have access to the PHP logs to look for any strange errors?
no strange errors in the php log
4. What version of C5 did you have before the update?
8.5.2
Manually
2. Have you manually cleared out the applications/files/cache folder?
Yes
3. Do you have access to the PHP logs to look for any strange errors?
no strange errors in the php log
4. What version of C5 did you have before the update?
8.5.2
After some Google searching for your error is looks like the crown job is trying to write to the DB but its will not let it store the information. This sounds like you have some code somewhere that does not like the C5 update you just did. Make sure all of the addon are up to date and really take a look at the PHP log after you run the job. Sorry I could not be more help.
Try asking in the C5 Slack group the core team is in there and should be able to help.
Try asking in the C5 Slack group the core team is in there and should be able to help.
I tried this on a site that I upgraded to 8.5.4 and didn't have any problem.
That error means 2 processes are trying to do write operations at the same time on the same field.
Did you by any chance set that job to run automatically? It could be the case that it's running already while you're trying to run it manually?
That error means 2 processes are trying to do write operations at the same time on the same field.
Did you by any chance set that job to run automatically? It could be the case that it's running already while you're trying to run it manually?
First a few question.
1. How did you update concrete5 through the User Interface or manually?
2. Have you manually cleared out the applications/files/cache folder?
3. Do you have access to the PHP logs to look for any strange errors?
4. What version of C5 did you have before the update?