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

    Kopano Search Returns MAPI Error -> entire Kopano server stops working

    Kopano Groupware Core
    4
    31
    6709
    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.
    • yep_DD
      yep_DD last edited by

      Hi @fbartels ,

      thank you. I saw the issue is a duplicate and of another one. But may be it is important to not just narrow it to RHEL because this happened on Debian and can be reproduced with a long logwatch mail sent every day.

      Regs,

      Stephan

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

        Hi @fbartels ,

        my Kopano server now completely stopped responding. The error logs show:

        Mon Oct 16 07:49:37 2017: [error  ] SQL [00010431] result failed: BIGINT UNSIGNED value is out of range in '(`zarafa`.`properties`.`tag` - 0x8501)', Query: "SELECT 0,properties.tag,properties.type,properties.val_ulong,properties.val_string,properties.val_binary,properties.val_double,properties.val_longint,properties.val_hi,properties.val_lo, hierarchyid, names.nameid, names.namestring, names.guid FROM properties FORCE INDEX (PRIMARY) LEFT JOIN names ON (properties.tag-0x8501)=names.id WHERE hierarchyid=9 AND (tag <= 0x8500 OR names.id IS NOT NULL)"
        

        Any idea?

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

          Hi @yep_dd ,

          the required fix for this has been merged to master some days ago (https://stash.kopano.io/projects/KC/repos/kopanocore/commits/2d8b04dd8299aa52a60d4fd0c9e374c6fa94e7d8#common/database.cpp).

          If I look at the timestamps with the community downloads the latest available package should include the fix for this.

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

            Hi,

            I am using the Version »core-8.4.90.492_0+85-Ubuntu_16.04-amd64.tar.gz, the error is still occuring.
            Can you please verify that the fix is included?

            Thanks,

            Ihon

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

              I’ive just installed the lattest 492 release. Let’s see

              PS:

              dpkg: warning: downgrading libjansson4:amd64 from 2.9-1 to 2.7-1
              

              I’ve been getting these since every Kopano update in the last months. Is there a reason Kopano is using 2.7-1?

              Stephan

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

                Hi,

                I am getting this error message multiple times:

                Tue Oct 17 22:45:43 2017: [error ] SQL [00000200] result failed: BIGINT UNSIGNED value is out of range in ‘Zarafa.properties.tag - 0x8501’, Query: “SELECT 0,properties.tag,properties.type,properties.val_ulong,properties.val_string,properties.val_binary,properties.val_double,properties.val_longint,properties.val_hi,properties.val_lo, hierarchyid, names.nameid, names.namestring, names.guid FROM properties FORCE INDEX (PRIMARY) LEFT JOIN names ON (properties.tag-0x8501)=names.id WHERE hierarchyid=316249 AND (tag <= 0x8500 OR names.id IS NOT NULL)”

                The server not working in that case anymore.

                Regards,

                Steffen

                1 Reply Last reply Reply Quote 1
                • yep_DD
                  yep_DD last edited by

                  Hi @fbartels ,

                  I can confirm what @Ihon wrote. The problem persists.

                  Stephan

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

                    @yep_dd @Ihon

                    Ok, I see. The last days our nightly upload did not succeed because of test failures. We are hopeful to resolve them today and have a new master build online later today.

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

                      ok, thank you :-)

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

                        and also when the server crashes apache shows the following error occasionally:

                        [:error] [pid 22638] [client xxxxxxxxxx:44132] PHP Fatal error:  Uncaught MAPIException: MAPI error  in /usr/share/kopano-webapp/server/includes/util.php:225\nStack trace:\n#0 /usr/share/kopano-webapp/server/includes/util.php(225): mapi_msgstore_openentry(Resource id #36, '\\x00\\x00\\x00\\x00\\x00\\x0E\\xEA=`\\xE6I5\\xB5\\x8D"...')\n#1 /usr/share/kopano-webapp/index.php(242): cleanSearchFolders()\n#2 {main}\n  thrown in /usr/share/kopano-webapp/server/includes/util.php on line 225,```
                        1 Reply Last reply Reply Quote 0
                        • yep_DD
                          yep_DD last edited by

                          This is the properties table. Changing tag to BIGINT has no effect. The error is getting really serious now, as I have a couple of messages in my postfix queue I can not get delivered!

                          0_1508326973203_Bildschirmfoto 2017-10-18 um 13.42.22.png

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

                            @fbartels any update on the community build?
                            Still having the errors and server is crashing

                            Thanks,

                            Ihon

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

                              @Ihon same here, and also the community packages haven’t been updated in 7 days…

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

                                @all same here and crash send my xen server in the eternal datagrounds

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

                                  Hi @yep_dd ,

                                  yes we were still battling some test failures and prevented new packages from being uploaded. In the afternoon all tests were successful again so on monday there should be a new upload.

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

                                    Hi @fbartels ,

                                    could you just tell us if that issue has been specifically addressed? I see there are already new packages. I will deploy them in a second. Thanks for your help.

                                    Stephan

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

                                      Hi,

                                      I did the update to the new version.
                                      Now kopano-server is providing the following error:

                                      Sat Oct 21 20:37:54 2017: [ notice] Starting kopano-server version 8.4.90 (pid 19164)
                                      Sat Oct 21 20:37:54 2017: [ notice] Server shutdown complete.
                                      Sat Oct 21 20:38:48 2017: [ notice] Starting kopano-server version 8.4.90 (pid 19244)
                                      Sat Oct 21 20:38:48 2017: [notice ] Listening for TCP connections on port 236
                                      Sat Oct 21 20:38:48 2017: [notice ] Listening for SSL connections on port 237
                                      Sat Oct 21 20:38:48 2017: [notice ] Coredumps are disabled via configuration file.
                                      Sat Oct 21 20:38:48 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
                                      Sat Oct 21 20:38:48 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
                                      Sat Oct 21 20:38:48 2017: [notice ] Connection to database ‘Zarafa’ succeeded
                                      Sat Oct 21 20:38:48 2017: [warning] WARNING: DB schema is 49 and older than v63 (ZCP 7.2). KC 8.4 was the last version able to upgrade such.
                                      Sat Oct 21 20:38:48 2017: [warning] You can force the server to start with --ignore-database-version-conflict
                                      Sat Oct 21 20:38:48 2017: [warning] Warning, you can lose data! If you don’t know what you’re doing, you shouldn’t be using this option!
                                      Sat Oct 21 20:38:48 2017: [notice ] Waiting for mysql_server_end
                                      Sat Oct 21 20:38:48 2017: [notice ] Waiting for mysql_library_end
                                      Sat Oct 21 20:38:48 2017: [ notice] Server shutdown complete.

                                      @yep_DD , do you have the same issue?

                                      Regards,

                                      Ihon

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

                                        @Ihon no i din’t get that problem I’d recommend /etc/init.d/kopano-server stop and then run

                                        kopano-server -c /path/to/your/config/file (etc/kopano/server.cfg) --ignore-database-conflict and see if it starts if it does then restart with: /etc/init.d/kopano-server start and check again

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

                                          Hi,

                                          kopano-server is starting with the parameter --ignore-database-version-conflict.
                                          but when I start it without the parameter, getting the errror again and kopano-server is not starting anymore :-(

                                          In the database, table “versions” I have the folling entries:

                                          7 	0 	0 	24874 	49 	2011-02-22 09:45:42
                                          7 	0 	0 	25734 	50 	2011-03-12 21:33:50
                                          7 	0 	0 	25734 	51 	2011-03-12 21:40:23
                                          7 	0 	0 	25734 	52 	2011-03-12 22:18:00
                                          ...
                                          ...
                                          ...
                                          8 	4 	0 	825 	66 	2017-06-18 15:14:29
                                          8 	4 	0 	1004 	66 	2017-07-03 19:41:15
                                          8 	4 	0 	1054 	66 	2017-07-07 11:37:54
                                          8 	4 	90 	2153381888 	66 	2017-08-01 12:17:35
                                          

                                          @fbartels do you have an idea what to do?

                                          Regards,

                                          Ihon

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

                                            @Ihon which version exactly have you installed?

                                            Can you just make sure your kopano server completed the install successfully?

                                            I installed:

                                            core-8.4.90.550_0+93-Debian_9.0-amd64/
                                            

                                            and that is my versions table and it looks like yours:

                                            0_1508684707499_Bildschirmfoto 2017-10-22 um 17.04.31.png

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