App "Not responding" after [2.6.0] update
I've app "Not responding" after 2.6.0 update, with this error code:
Aug 05 08:54:06 [06:54:06/13] Lock: update.lock Aug 05 08:54:06 [06:54:06/13] Type 'yes' to continue. Aug 05 08:54:06 [06:54:06/13] Starting migration to 147... Aug 05 08:54:06 [06:54:06/13] Failed on line: create fulltext index ttrss_entries_title_search_idx on ttrss_entries(title) Aug 05 08:54:06 [06:54:06/13] Migration failed: SQLSTATE: Syntax error or access violation: 1061 Duplicate key name 'ttrss_entries_title_search_idx' Aug 05 08:54:06 PHP Warning: Failed to apply migration 147 for ttrss_version: SQLSTATE: Syntax error or access violation: 1061 Duplicate key name 'ttrss_entries_title_search_idx' in /app/code/classes/db/migrations.php on line 191 Aug 05 08:54:19 ==> Creating config Aug 05 08:54:19 ==> Changing permissions Aug 05 08:54:19 ==> Updating schema
@p44 Is it always reproducible? If you roll back to previous version and then try to update again?
I have stopped ttrss updates in the meantime.
@girish I went back to 2.5.0 and now it works... Later on I'll try again to update and I'll let to know.
@girish Hello Girish, I tried again to update to 2.6.0 and problem is still there. Problem is always reproducible.
necrevistonnezr last edited by
@girish No issues with two instances here...
Yeah quite strange because all our other instances updated well.
But this exact same error is reported upstream at https://community.tt-rss.org/t/plugin-suggestion-similar-articles-as-read-but-for-mysql/4994 and the fix is https://dev.tt-rss.org/fox/tt-rss/commit/b148d2f5153f9711120b3a3ac50ee84509c9cdfb which is already in the package...
Also just updated with no issues here.
@girish Thank's Girish, I updated again and now is all fine. Thank's a lot
ruihildt last edited by ruihildt
@girish I have has the same issue after automatic update to 2.6
I tried to revert and update it again, but it still fails, here's where it gets stuck:
ug 07 16:18:28 ==> Creating config Aug 07 16:18:28 ==> Changing permissions Aug 07 16:18:28 ==> Updating schema Aug 07 16:18:28 [14:18:28/12] Lock: update.lock Aug 07 16:18:28 [14:18:28/12] Type 'yes' to continue. Aug 07 16:18:28 [14:18:28/12] Starting migration to 147...
Have reverted to 2.5 for now.
@ruihildt Looks like maybe there is some race in upstream migration logic, maybe you can try to clone+update and see if it's reproducible.