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

    Cannot delete orphaned store

    Kopano Groupware Core
    3
    5
    495
    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.
    • nickh
      nickh last edited by

      I am seeing a difference between kopano-admin and kopano-cli listing orphans:

      [root@cls ~]# kopano-admin  --list-orphans
      Stores without users:
              Store guid                              Guessed username        Last login              Store size      Store type
              --------------------------------------------------------------------------------------------------------------------------
              5E8823866FA748A4B4525CC7E187018A        t.test                  08/06/2018 11:35:30 AM  2.05 MB         private
              D69B5420C3EE4AE594238A911746CF52        t.bauer                 12/13/2018 09:03:57 AM  0.01 MB         private
      
      Users without stores:
              Username
              --------------------------------
              Everyone
              t.test
      [root@cls ~]# kopano-admin  --remove-store D69B5420C3EE4AE594238A911746CF52
      Unable to remove store: "object" already exists
      Using the -v option (possibly multiple times) may give more hints.
      [root@cls ~]# kopano-cli  --list-orphans
      Stores without users:
                                    Store guid            Username      Last login      Store size      Store type
              ----------------------------------------------------------------------------------------------------
      
      Users without stores (1):
                  User           Full Name          Homeserver                                   Store
      ------------------------------------------------------------------------------------------------
                t.test           test test              Kopano
      

      Is D69B5420C3EE4AE594238A911746CF52 really orphaned and, if so, how do I delete it? If it is not orphaned, why does kopano-admin show it as orphaned and how do I fix it?

      TIA,
      Nick

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

        @nickh said in Cannot delete orphaned store:

        D69B5420C3EE4AE594238A911746CF52

        Looks logical to me.

        1. kopano-admin --list-orphans
        2. kopano-admin --remove-store D69B5420C3EE4AE594238A911746CF52
        3. kopano-cli --list-orphans

        step 2, you deleted t.bauer.

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

          I think you missed the result of step 2 or I have misunderstood:

          Unable to remove store: "object" already exists
          Using the -v option (possibly multiple times) may give more hints.
          

          kopano-admin failed to remove the store but kopano-cli does not then list it as an orphan.

          1 Reply Last reply Reply Quote 0
          • robing
            robing Kopano (Inactive) last edited by

            @nickh ,

            kopano-cli --list-orphans is not working see https://jira.kopano.io/browse/KC-1166

            Can you run this kopano-admin --remove-store D69B5420C3EE4AE594238A911746CF52 -vvvvvvvv

            This should give you more logging or check the kopano-server log

            But i think you hit this bug https://jira.kopano.io/browse/KC-1137 but that is already fixed some versions ago.

            Regards Robin,

            Need support?
            Have a look at https://kopano.com/support/ for options.

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

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

              Yes, it looks like the bug. I’ll have to ask the distro for an upgrade.

              Thanks for your help.

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