• Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: 4.1.0
    • Fix Version/s: 4.8.0
    • Component/s: None
    • Labels:


      A customer has two artifactory pros. One is a hot standby that is using the same database. Presumably the filestore is shared as well, however at the time of this writing that has not been confirmed.

      In this configuration he upgraded the running node from 3.9.1 to 4.1.0. This went fine when he tried to upgrade the hot standby artifactory he got these logs:

      2015-09-16 21:52:09,981 [art-init] [INFO ] (o.a.s.d.v.ArtifactoryDBVersion:53) - Starting database conversion from v391 to v410
      2015-09-16 21:52:09,982 [art-init] [INFO ] (o.a.s.d.v.c.DBSqlConverter:38) - Starting schema conversion: /conversion/mysql/mysql_v410.sql
      2015-09-16 21:52:09,992 [art-init] [ERROR] (o.a.s.d.u.DbUtils :174) - Failed to execute query: Table 'user_props' already exists:
      CREATE TABLE user_props (
      user_id BIGINT NOT NULL,
      prop_key VARCHAR(64) NOT NULL,
      prop_value VARCHAR(2048),
      CONSTRAINT user_props_pk PRIMARY KEY (user_id, prop_key),
      CONSTRAINT user_props_users_fk FOREIGN KEY (user_id) REFERENCES users (user_id)
      2015-09-16 21:52:09,999 [art-init] [ERROR] (o.a.s.d.v.c.DBSqlConverter:44) - Could not convert DB from v410 due to Table 'user_props' already exists
      com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'user_props' already exists

      My understanding is the database has a table with the version number in it. Artifactory should be going to that table to see if the schema needs changing. I'm thinking due to the above logs that this is not the case.

      The ticket is 31720




            • Assignee:
              gidis Gidi Shabat
              denebeim Jay Denebeim (Inactive)
            • Votes:
              0 Vote for this issue
              4 Start watching this issue


              • Created: