Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    [solved] Update Issue II

    Kopano Groupware Core
    5
    13
    1619
    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.
    • fbartels
      fbartels Kopano @Sinux last edited by

      @sinux said in Update Issue II:

      The server can not be started via force!

      What did you try so far? You either could delete the offending entry from the versions table in the database, of pass --ignore-database-version-conflict to the kopano-server binary.

      from man kopano-server:

         --ignore-database-version-conflict
             Ignore version information from the database. Kopano will normally not start the server if the database has a newer version than the kopano-server
             binary. This makes sure you cannot downgrade your server binary while keeping the same database. If you know what you're doing, you can use this
             option to bypass the start-up version check of the database.

      Regards Felix

      Resources:
      https://kopano.com/blog/how-to-get-kopano/
      https://documentation.kopano.io/
      https://kb.kopano.io/

      Support overview:
      https://kopano.com/support/

      1 Reply Last reply Reply Quote 0
      • Sinux
        Sinux last edited by

        Thank you fbartels,

        i know https://forum.kopano.io/topic/733/solved-update-issue/4. I thought the problem was solved but apparently not. It must have a cause that sporadically the DB versions are declared as higher!

        1 Reply Last reply Reply Quote 0
        • fbartels
          fbartels Kopano last edited by

          Hi @Sinux ,

          you database version was indeed higher “8,5,90,…” is higher than “8,5,81,…” after all. Since you had 8.5.90 before you must have been using one of the earliest builds after branching 8.5. we lowered the version number the next day, but those builds were online for a day or so.

          Regards Felix

          Resources:
          https://kopano.com/blog/how-to-get-kopano/
          https://documentation.kopano.io/
          https://kb.kopano.io/

          Support overview:
          https://kopano.com/support/

          A Former User 1 Reply Last reply Reply Quote 0
          • Sinux
            Sinux last edited by

            Whenever I want to use the community version productively something like that happens. If you then get a Warkouround on the DB level is not funny. Thank you anyway.

            1 Reply Last reply Reply Quote 0
            • umgfoin
              umgfoin last edited by

              @Sinux, if you use nightly-builds productively, that’s not really wise.
              As you may have experienced, problems like this will happen - accept it, or get a commercial build.
              If you find an issue, report it, but refrain from blaming the devs - you might end up with somebody @ Kopano deciding to stop the community-editions.
              Free Software does not mean, you have a natural right on impeccable ready meals.

              mysql <kopano_db>
              DELETE FROM versions WHERE CAST(CONCAT(major, minor, micro) AS INTEGER) >= 8590;
              
              Sinux 1 Reply Last reply Reply Quote 0
              • mcostan
                mcostan last edited by

                I would also add that Kopano is actually very very good at providing nightly BUILDS. They could simply just publish the source code and let you build it from scratch. They actually go through the effort of providing free nightly builds for a numerous amount of platforms.

                In return the users (I am a community user too) have the moral obligation (at least that’s the way I see it) to provide feedback and help to move the product forward. Part of it is also to find bugs that occasionally may occur as the software moves forward.

                I really can’t see anything wrong with this and, instead, I am extremely supportive and grateful to Kopano for the current solution.

                1 Reply Last reply Reply Quote 1
                • Sinux
                  Sinux @umgfoin last edited by

                  @umgfoin
                  Thank you and I hope you accept my opinion. I love Zarafa/Kopano since 2012!

                  1 Reply Last reply Reply Quote 0
                  • A Former User
                    A Former User last edited by

                    And we did not even have a 8.5.90 yet… odd.

                    1 Reply Last reply Reply Quote 0
                    • Sinux
                      Sinux last edited by

                      https://forum.kopano.io/topic/1016/update-issue-ii/5

                      ;)

                      1 Reply Last reply Reply Quote 0
                      • A Former User
                        A Former User @fbartels last edited by

                        @fbartels said in Update Issue II:

                        we lowered the version number the next day, but those builds were online for a day or so.

                        We did? Where?

                        Sinux 1 Reply Last reply Reply Quote 0
                        • Sinux
                          Sinux @Guest last edited by Sinux

                          @jengelh said in Update Issue II:

                          @fbartels said in Update Issue II:

                          we lowered the version number the next day, but those builds were online for a day or so.

                          We did? Where?

                          fbartels is probably the right person for this question.
                          You should know him.
                          closed

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post