Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Datovka Datovka
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Datovka projects
  • DatovkaDatovka
  • Issues
  • #423
Closed
Open
Created Apr 24, 2019 by Karel Slaný@kslanyOwner

Datovka Synchronisation Crashes with 'inv' Databases

Reported by @picekmartin:

In my case, OpenSSL upgrade (to 1.1.1b-5.fc29; Fedora) did help (or at least it seems so) with the initial issue but Datovka is still failing with

duplicate connection name 'GLOBALDBS_XXXXXX_inv', old connection removed.

As I am having two mailboxes in my Datovka, I found out that this happens only for one of them (when I commented out the second one in dsgui.conf, Datovka was working fine). I found the following files in storage of the failing mailbox:

  • XXXXXX_2018___0.db or XXXXXX_2019___0.db (year-based database)
  • XXXXXX_inv___0.db

After deletion of the XXXXXX_inv___0.db file, even this mailbox works fine. However, I don't know what the content of the "inv" file could be so I am keeping a copy of that. (I noticed that my first mailbox has no "inv" file.)

So - can I delete the "inv" file safely? Is it just a cache? Or what is it?

Assignee
Assign to
Time tracking