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

    Unable to bind to port 236

    Kopano Groupware Core
    3
    22
    6475
    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.
    • BMWfan
      BMWfan @AnotherAndy last edited by

      @anotherandy in the 5th post you can see the asked output.

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

        ok - the folder /var/lib/kopano/search/ belongs to the user kopano?
        also /var/lib/kopano ?

        have you tried to clean the folder and restart the search? If you have vmware snapshot the vm before doing this.
        And - sounds stupid, but did you reboot the machine?

        BMWfan 1 Reply Last reply Reply Quote 0
        • BMWfan
          BMWfan @AnotherAndy last edited by BMWfan

          @anotherandy thank you, the permissions are the same. The group and the owner is kopano (755).
          I’ve cleaned the search folder and rebooted the machine with no result.

          I`ve changed now the search log level to 6 (debug). Many index entrys are running over the screen until these entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000. When these entryid is there then the MAPI Errors begins.

          2018-01-22 19:49:25,920 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F4501000000050000005AA0C047B2434A8C8D710000D392503600000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402783A01000000, docid 126306
          2018-01-22 19:49:25,952 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F4501000000050000001C00CC2D3E314C3C95C7F592B26F485900000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402743A01000000, docid 126297
          2018-01-22 19:49:25,979 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:25,993 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=0/5)
          2018-01-22 19:49:26,448 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:26,456 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=1/5)
          2018-01-22 19:49:27,304 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:27,313 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=2/5)
          2018-01-22 19:49:28,971 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:28,980 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=3/5)
          2018-01-22 19:49:32,230 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:32,238 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=4/5)
          2018-01-22 19:49:38,688 - index0 - DEBUG - store A497753E7B1B4CE3894BB06ABB7C1F45, folder 203: new/updated document with entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000, sourcekey 1C244D94A69B4E8CA4F9CB245BF4D402523A01000000, docid 126228
          2018-01-22 19:49:38,696 - index0 - WARNING - Received a MAPI error or timeout (error=0x80040115, retry=5/5)
          2018-01-22 19:49:45,102 - index0 - ERROR - Too many retries, skipping change
          

          Ive searched the entryid in the whole log and found these message:

          2018-01-22 19:29:06,669 - index0 - ERROR - could not process change for entryid 00000000A497753E7B1B4CE3894BB06ABB7C1F450100000005000000A83C9472B9D046E6B89FE57F34DA9B3800000000 ([SPropValue(0x65E00102, '\x1c$M\x94\xa6\x9bN\x8c\xa4\xf9\xcb$[\xf4\xd4\x02R:\x01\x00\x00\x00'), SPropValue(0x30080040, 2017/02/03 20:07:12 GMT), SPropValue(0x65E20102, '\x1c$M\x94\xa6\x9bN\x8c\xa4\xf9\xcb$[\xf4\xd4\x02\xdez\x03\x00'), SPropValue(0x65E10102, '\x1c$M\x94\xa6\x9bN\x8c\xa4\xf9\xcb$[\xf4\xd4\x02\x02\x01\x00\x00\x00\x00'), SPropValue(0x65E30102, '\x14\x1c$M\x94\xa6\x9bN\x8c\xa4\xf9\xcb$[\xf4\xd4\x02\xdez\x03\x00'), SPropValue(0x0FFF0102, '\x00\x00\x00\x00\xa4\x97u>{\x1bL\xe3\x89K\xb0j\xbb|\x1fE\x01\x00\x00\x00\x05\x00\x00\x00\xa8<\x94r\xb9\xd0F\xe6\xb8\x9f\xe5\x7f4\xda\x9b8\x00\x00\x00\x00'), SPropValue(0x67AA000B, False), SPropValue(0x0E070003, 3L), SPropValue(0x0FFA0102, '\xa4\x97u>{\x1bL\xe3\x89K\xb0j\xbb|\x1fE'), SPropValue(0x67110003, 126228L), SPropValue(0x67150003, 203L)]):
          

          What kind of index is this and how can i fix this?

          I thought i could reindex easily my user and then should the error go away, but also this is not functioning:

          kopano-search --reindex=MyUser
          Traceback (most recent call last):
            File "/usr/sbin/kopano-search", line 7, in <module>
              sys.exit(kopano_search.main())
            File "/usr/lib/python2.7/dist-packages/kopano_search/__init__.py", line 419, in main
              service.reindex()
            File "/usr/lib/python2.7/dist-packages/kopano_search/__init__.py", line 406, in reindex
              with closing(kopano.client_socket(self.config['server_bind_name'], ssl_cert=self.config['ssl_certificate_file'])) as s:
            File "/usr/lib/python2.7/dist-packages/kopano/service.py", line 266, in client_socket
              s.connect(addr2)
            File "/usr/lib/python2.7/socket.py", line 228, in meth
              return getattr(self._sock,name)(*args)
          socket.error: [Errno 2] No such file or directory
          

          @fbartels have you perhaps any idea?

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

            Can nobody help me or has further tips?

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

              I’m sorry no other idea from here.
              Maybe on sunday afternoon ~ 3 p.m. we can chat and try to find a solution together?

              BMWfan 1 Reply Last reply Reply Quote 0
              • BMWfan
                BMWfan @AnotherAndy last edited by

                @anotherandy thank you. This would be really cool.

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

                  Today i had a chat with AnotherAndy which gaves me some tips. @AnotherAndy Thanks for that
                  I would update now here the “diary” perhaps someone had then further ideas.

                  In my server log are these entries:

                  Sun Feb  4 15:55:16 2018: [error  ] K-1562: cannot open attachment "/var/lib/kopano/attachments/2/16/1762.gz": No such file or directory
                  Sun Feb  4 15:55:16 2018: [error  ] SerializeObject failed with error code 0x80000002 for object 24020
                  Sun Feb  4 15:55:22 2018: [error  ] K-1562: cannot open attachment "/var/lib/kopano/attachments/2/16/1762.gz": No such file or directory
                  Sun Feb  4 15:55:22 2018: [error  ] SerializeObject failed with error code 0x80000002 for object 24020
                  Sun Feb  4 15:55:29 2018: [error  ] K-1562: cannot open attachment "/var/lib/kopano/attachments/2/16/1762.gz": No such file or directory
                  Sun Feb  4 15:55:29 2018: [error  ] SerializeObject failed with error code 0x80000002 for object 24020
                  Sun Feb  4 15:55:35 2018: [error  ] K-1562: cannot open attachment "/var/lib/kopano/attachments/2/16/1762.gz": No such file or directory
                  Sun Feb  4 15:55:35 2018: [error  ] SerializeObject failed with error code 0x80000002 for object 24020
                  Sun Feb  4 15:55:42 2018: [error  ] K-1562: cannot open attachment "/var/lib/kopano/attachments/2/16/1762.gz": No such file or directory
                  Sun Feb  4 15:55:42 2018: [error  ] SerializeObject failed with error code 0x80000002 for object 2402
                  

                  Perhaps the MAPI Service is searching for that?

                  In the time when iam overtaking the database and attachments from my old zarafa installation to the new Kopano installation there was no file under /var/lib/zarafa/attachments/2/16/ which is called 1762.gz .
                  Is there a way to find the dependencies between the attachments and MAPI and delete this in the database?

                  Best Regards

                  Daniel

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

                    Hi @bmwfan ,

                    since you know the filename, which includes the instanceid you could look up the hierarchyid of the attachment in the singleinstances table in the database. Based on the hierarchyid you can then identify the mapi object the attachment belongs to in the properties table. But you should not delete it directly from the database, instead you should then locate the email with e.g. WebApp and delete the message from there.

                    An alternative and easier approach is to just create an empty gz archive with the name the server wants to lookup.

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

                      Thank you @fbartels.
                      How can i identify in the webapp which mails belongs to the not available attachments?

                      Regards

                      Daniel

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

                        @bmwfan said in Unable to bind to port 236:

                        How can i identify in the webapp which mails belongs to the not available attachments?

                        By using search? From the properties table you will learn details such as subject, recipients/sender, body etc.

                        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
                        • First post
                          Last post