Failed to initialize DB

Options
System
System
in Secrets Automation
This discussion was created from comments split from: Docker (compose) Permission denied.

Comments

  • alex_u13
    alex_u13
    Community Member
    Options

    I have the same problem

    {"log_message":"(W) configured to use HTTP with no TLS","timestamp":"2022-01-26T19:54:44.966092299Z","level":2}
{"log_message":"(I) [discovery-local] starting discovery, advertising endpoint 46221 /meta/message","timestamp":"2022-01-26T19:54:44.966293265Z","level":3}
{"log_message":"(I) established incoming bus peer connection","timestamp":"2022-01-26T19:54:44.968632921Z","level":3}
{"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2022-01-26T19:54:44.968732005Z","level":3}
{"log_message":"(I) serving on :8080","timestamp":"2022-01-26T19:54:44.968750884Z","level":3}
Error: Server: (failed to OpenDefault), Wrapped: (failed to initialize database), DB: (failed to apply schema 11), duplicate column name: initial_files_synced
  • Joris_1P
    Joris_1P
    Options

    @alex_u13 What you seem to be running into should be easier to fix. We have seen this before and are investigating it. Fortunately, we have had good results so far with a simple workaround: just delete the local database and restart Connect.

    You can do that by deleting the volume mounted to home/opuser/.op/data. If you're using docker-compose, you can use docker-compose down -v.

    Let me know if that works.

  • alex_u13
    alex_u13
    Community Member
    Options

    @Joris_1P
    Yes, I have already cleared the docker's volume data. Accidentally stumbled upon such a solution. But thanks for the answer!

  • Joris_1P
    Joris_1P
    Options

    That's good to hear!

This discussion has been closed.