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

    Error in Kopano Core

    Kopano Groupware Core
    4
    14
    1470
    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.
    • mcostan
      mcostan last edited by fbartels

      When deleting a user with this command:

      root@mrc-ubz64:~# kopano-admin -d test
      Unable to delete user: disk error (0x80040116)
      

      I get this in server.log:

      Sat May 12 21:30:02 2018: [info   ] Auto-deleting user 164 from external source
      Sat May 12 21:30:02 2018: [error  ] SQL [00000083] Failed: Table 'zarafa.clientupdatestatus' doesn't exist, Query Size: 47, Query: "DELETE FROM clientupdatestatus where userid=164"
      Sat May 12 21:30:02 2018: [error  ] KDatabase::I_Update() query failed: "Table 'zarafa.clientupdatestatus' doesn't exist", query: DELETE FROM clientupdatestatus where userid=164
      Sat May 12 21:30:02 2018: [info   ] Auto-deleting user 164 done. Error code 0x80000007
      Sat May 12 21:30:02 2018: [info   ] Auto-deleting user 192 from external source
      Sat May 12 21:30:02 2018: [error  ] SQL [00000084] Failed: Table 'zarafa.clientupdatestatus' doesn't exist, Query Size: 47, Query: "DELETE FROM clientupdatestatus where userid=192"
      Sat May 12 21:30:02 2018: [error  ] KDatabase::I_Update() query failed: "Table 'zarafa.clientupdatestatus' doesn't exist", query: DELETE FROM clientupdatestatus where userid=192
      Sat May 12 21:30:02 2018: [info   ] Auto-deleting user 192 done. Error code 0x80000007
      Sat May 12 21:30:02 2018: [info   ] Auto-deleting user 182 from external source
      

      Versions below:

      WebApp:
      3.4.14.1475+840.1
      Kopano Core:
      8.5.8
      Z-Push:
      2.4.1+0-0

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

        This can be replicated over and over as following:

        oot@mrc-ubz64:~# kopano-admin -c test -f test -e test@test.com -p test
        User created.
        root@mrc-ubz64:~# kopano-admin -d test
        Unable to delete user: disk error (0x80040116)
        Using the -v option (possibly multiple times) may give more hints.
        

        and in the log file:

        Sat May 12 21:56:29 2018: [info   ] Command "/etc/kopano/userscripts/createuser" ran successfully
        Sat May 12 21:56:40 2018: [info   ] Auto-deleting user 193 from external source
        Sat May 12 21:56:40 2018: [error  ] SQL [00000081] Failed: Table 'zarafa.clientupdatestatus' doesn't exist, Query Size: 47, Query: "DELETE FROM clientupdatestatus where userid=193"
        Sat May 12 21:56:40 2018: [error  ] KDatabase::I_Update() query failed: "Table 'zarafa.clientupdatestatus' doesn't exist", query: DELETE FROM clientupdatestatus where userid=193
        Sat May 12 21:56:40 2018: [info   ] Auto-deleting user 193 done. Error code 0x80000007
        ^C
        

        I can’t see what’s going on… I just created a new user…

        This database was migrated from Zarafa over the years but surely a newly created user shouldn’t cause issues?

        Database changed
        MariaDB [zarafa]> select * from versions;
        +-------+-------+-------+------------+------------------+---------------------+
        | major | minor | micro | revision   | databaserevision | updatetime          |
        +-------+-------+-------+------------+------------------+---------------------+
        |     7 |     0 |     0 |      30515 |               59 | 2012-01-25 15:03:49 |
        |     7 |     0 |     0 |      31235 |               60 | 2012-01-26 17:13:06 |
        |     7 |     0 |     0 |      31235 |               61 | 2012-01-26 17:13:06 |
        |     7 |     0 |     0 |      31235 |               62 | 2012-01-26 17:13:06 |
        |     7 |     0 |     0 |      32752 |               62 | 2012-05-09 10:43:31 |
        |     7 |     0 |     0 |      34256 |               62 | 2012-05-27 15:17:36 |
        |     7 |     0 |     0 |      35178 |               62 | 2012-07-09 15:30:52 |
        |     7 |     0 |     0 |      36358 |               62 | 2012-09-12 10:26:43 |
        |     7 |     0 |     0 |      40336 |               62 | 2013-02-25 11:24:47 |
        |     7 |     0 |     0 |      41388 |               62 | 2013-03-15 09:32:09 |
        |     7 |     1 |     0 |      42779 |               63 | 2014-01-05 22:53:50 |
        |     7 |     1 |     0 |      43801 |               63 | 2014-02-03 12:07:04 |
        |     7 |     1 |     0 |      44004 |               63 | 2014-04-22 15:20:28 |
        |     7 |     1 |     0 |      44333 |               63 | 2014-05-27 13:25:44 |
        |     7 |     1 |     0 |      44973 |               63 | 2014-08-03 18:03:52 |
        |     7 |     1 |     0 |      46050 |               63 | 2014-11-17 17:42:54 |
        |     7 |     1 |     0 |      48726 |               63 | 2015-06-01 09:32:23 |
        |     7 |     1 |     0 |      49411 |               63 | 2015-06-23 13:25:23 |
        |     7 |     1 |     0 |      51032 |               63 | 2015-11-19 22:24:38 |
        |     7 |     1 |     0 |      51822 |               63 | 2015-12-02 21:24:50 |
        |     7 |     2 |     0 |        657 |               64 | 2016-06-17 13:56:27 |
        |     7 |     2 |     0 |      51838 |               63 | 2016-03-18 20:01:12 |
        |     7 |     2 |     3 |        657 |               64 | 2016-06-17 14:02:34 |
        |     7 |     2 |     4 |         28 |               64 | 2016-07-18 20:32:38 |
        |     7 |     2 |     4 |         29 |               64 | 2016-07-25 21:42:12 |
        |     8 |     1 |     0 |        335 |               65 | 2016-10-08 19:55:31 |
        |     8 |     1 |     0 |        335 |               66 | 2016-10-08 19:55:31 |
        |     8 |     3 |     0 |        500 |               66 | 2017-01-04 11:42:20 |
        |     8 |     3 |     4 |         12 |               66 | 2017-09-01 21:05:48 |
        |     8 |     4 |     0 | 2151679492 |               66 | 2018-03-06 20:37:36 |
        |     8 |     5 |     4 | 2152988672 |               66 | 2018-03-08 09:16:16 |
        |     8 |     5 |     5 | 2153054208 |               66 | 2018-03-18 17:18:43 |
        |     8 |     5 |     7 | 2153185280 |               67 | 2018-04-19 12:25:19 |
        |     8 |     5 |     7 | 2153185280 |               68 | 2018-04-19 12:25:19 |
        |     8 |     5 |     7 | 2153185280 |               69 | 2018-04-19 12:46:44 |
        |     8 |     5 |     7 | 2153185280 |               70 | 2018-04-19 12:46:45 |
        |     8 |     5 |     8 | 2153250816 |               70 | 2018-04-20 21:54:37 |
        +-------+-------+-------+------------+------------------+---------------------+
        37 rows in set (0.00 sec)
        
        1 Reply Last reply Reply Quote 0
        • Gerald
          Gerald last edited by

          Works for me on kopano-server 8.6.80.752-0+85.1 amd64 (ubuntu 16.04). Perhaps broken only in the stable packages?

          root@myhost.net:~# kopano-admin -c test -f test -e test@test.com -p test
          User created.
          root@myhost.net:~# kopano-admin -d test
          User deleted.
          
          1 Reply Last reply Reply Quote 0
          • jengelh
            jengelh Banned last edited by jengelh

            [The fix is] in 8.5.8.5+/8.6.1.58+/8.6.80.693+.

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

              This must be something specific for the 8.5.8 (official release). I have never seen this error before…

              The question I am worried is whether it will corrupt my database in any shape or form…

              So what do I do? Do I upgrade to the latest in the community packages?

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

                @mcostan said in Error in Kopano Core:

                So what do I do? Do I upgrade to the latest in the community packages?

                I think @jengelh above meant to imply that he could not reproduce your issue either on the 8.5 release, the latest 8.6 build or the current master. So upgrading to master likely does not change anything for you.

                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
                • mcostan
                  mcostan last edited by

                  Felix,

                  It looks like I am not the only one coming up with this error.

                  It was also mentioned in this post:

                  https://forum.kopano.io/topic/1300/kopano-core-8-5-8-a-quickfix-release/8

                  I am very concerned that I will end up with a corrupted database… (as per that post).

                  Something in the code or some database code must be still referring to an old zarafa table.

                  What do we do?

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

                    @mcostan said in Error in Kopano Core:

                    this error

                    if you are referring to the “Failed: Table ‘zarafa.clientupdatestatus’ doesn’t exist” message, yes that is known and already fixed for the next 8.5 update. There is no harm of a corrupt database in this relation, since we removed the table, but there were still some code paths, which made reference to it.

                    What is new here in your post are the error messages on deletion. This still remains to be reproduced.

                    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
                    • mcostan
                      mcostan last edited by

                      ok thanks.

                      If you have trouble reproducing this I can try cutting down the database to a single user and giving you access to it if that helps.

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

                        note in relation to my original post, that after the error, the user is actually deleted. So the command returns an error, but the user is then gone.

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

                          This (the inability to delete a user) is likely to be fixed by https://stash.kopano.io/projects/KC/repos/kopanocore/commits/656e02e7e7bea2469549253ad3af6d4177ae0df7 as well. Commit has been part of all master released produced afterteh 24th of april.

                          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
                          • mcostan
                            mcostan last edited by

                            thanks, I will try 8.6 and see how it goes.

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

                              root@mrc-ubz64:~# kopano-admin -c test -f test -e test@test.com -p test
                              User created.
                              root@mrc-ubz64:~# kopano-admin -d test
                              User deleted.

                              Fixed in 8.6.2 pre-release

                              Also the zarafa table missing error disappeared.

                              Thanks a lot, all good.

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

                                I tested 8.5.9 and the problem is fixed there too.

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