Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    App "Not responding" after [2.6.0] update

    Tiny Tiny RSS
    5
    16
    358
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      p44 translator last edited by

      Dear All,

      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[42000]: 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[42000]: 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
      
      girish 2 Replies Last reply Reply Quote 0
      • girish
        girish Staff @p44 last edited by

        @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.

        P necrevistonnezr 3 Replies Last reply Reply Quote 0
        • P
          p44 translator @girish last edited by

          @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.

          1 Reply Last reply Reply Quote 0
          • P
            p44 translator @girish last edited by

            @girish Hello Girish, I tried again to update to 2.6.0 and problem is still there. Problem is always reproducible.

            1 Reply Last reply Reply Quote 0
            • necrevistonnezr
              necrevistonnezr @girish last edited by

              @girish No issues with two instances here...

              1 Reply Last reply Reply Quote 0
              • girish
                girish Staff last edited by

                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...

                P 1 Reply Last reply Reply Quote 2
                • B
                  borg last edited by

                  Also just updated with no issues here.

                  1 Reply Last reply Reply Quote 0
                  • P
                    p44 translator @girish last edited by

                    @girish Thank's Girish, I updated again and now is all fine. Thank's a lot

                    1 Reply Last reply Reply Quote 0
                    • ruihildt
                      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.

                      girish 2 Replies Last reply Reply Quote 1
                      • girish
                        girish Staff @ruihildt last edited by

                        @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.

                        ruihildt 1 Reply Last reply Reply Quote 1
                        • ruihildt
                          ruihildt @girish last edited by

                          @girish I duplicated the app from a backup and tried to update, and it still fails.

                          What should I do next?

                          1 Reply Last reply Reply Quote 0
                          • girish
                            girish Staff @p44 last edited by

                            @p44 said in App "Not responding" after [2.6.0] update:

                            Aug 05 08:54:06 PHP Warning: Failed to apply migration 147 for ttrss_version: SQLSTATE[42000]: Syntax error or access violation: 1061 Duplicate key name 'ttrss_entries_title_search_idx' in /app/code/classes/db/migrations.php on line 191

                            @ruihildt Do you get the same error as above? If so, can you put the app in repair mode and tell me what's on line 191 above?

                            ruihildt 1 Reply Last reply Reply Quote 0
                            • ruihildt
                              ruihildt @girish last edited by ruihildt

                              @girish

                              Here's the relevant function, line 191 is the second exception:

                              function migrate() : bool {
                              
                              		if ($this->get_version() == -1) {
                              			try {
                              				$this->migrate_to(0);
                              			} catch (PDOException $e) {
                              				user_error("Failed to load base schema for {$this->migrations_table}: " . $e->getMessage(), E_USER_WARNING);
                              				return false;
                              			}
                              		}
                              
                              		for ($i = $this->get_version() + 1; $i <= $this->get_max_version(); $i++) {
                              			try {
                              				$this->migrate_to($i);
                              			} catch (PDOException $e) {
                              				user_error("Failed to apply migration ${i} for {$this->migrations_table}: " . $e->getMessage(), E_USER_WARNING);
                              				return false;
                              				//throw $e;
                              			}
                              		}
                              
                              		return !$this->is_migration_needed();
                              	}
                              
                              girish 1 Reply Last reply Reply Quote 0
                              • girish
                                girish Staff @ruihildt last edited by

                                @ruihildt Is this fix there - https://dev.tt-rss.org/fox/tt-rss/commit/b148d2f5153f9711120b3a3ac50ee84509c9cdfb ?

                                ruihildt 1 Reply Last reply Reply Quote 0
                                • ruihildt
                                  ruihildt @girish last edited by

                                  @girish Yes.

                                  1 Reply Last reply Reply Quote 0
                                  • girish
                                    girish Staff @ruihildt last edited by

                                    @ruihildt said in App "Not responding" after [2.6.0] update:

                                    I tried to revert and update it again, but it still fails, here's where it gets stuck:

                                    Just to double check, is your issue same as the original issue? Or is the issue that the migration gets stuck (in which case, this is some other issue) ?

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post
                                    Powered by NodeBB