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

    New batches of errors since upgrading

    Synchronising (mobile) devices via Z-Push
    4
    13
    2825
    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.
    • Sebastian
      Sebastian Kopano last edited by

      This code are wasn’t changed. Could you enable the wbxml log and post what is going on in general?

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

        Hi Caldwell,

        did you also update Kopano?

        Manfred

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

          Hi @caldwell ,

          can you tell us which version of Kopano and Z-Push you are using?

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

            Zarafa
            Product version: 7,2,4,28
            File version: 28

            z-push-common.noarch 2.3.8+0-73.1

            Perhaps this version doesn’t play nicely with Zarafa?

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

              Hi Caldwell,

              it should actually work, but we didn’t test the latest Z-Push versions with Zarafa.

              Does it happen for every user? Do you also have WBXML log?

              Manfred

              Caldwell 1 Reply Last reply Reply Quote 0
              • Caldwell
                Caldwell @Manfred last edited by

                @manfred

                I turned on “LOGLEVEL_WBXML” in the conf file. Nothing seems to have changed in the output. This is what I get for, it appears, every user:

                20/09/2017 13:48:00 [ 6490] [WARN] [user@domain] /usr/share/z-push/backend/kopano/importer.php:146 mapi_importcontentschanges_config() expects parameter 3 to be long, string given (2)
                20/09/2017 13:48:00 [ 6490] [WARN] [user@domain] StatusException: ImportChangesICS->Config(): Error, mapi_import_*_changes_config() failed: 0xFFFFFFFF80070057 - code: 12 - file: /usr/share/z-push/backend/kopano/importer.php:152
                20/09/2017 13:48:00 [ 6490] [WARN] [user@domain] Ignored incoming change, global status indicates problem.

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

                  Hi Caldwell,

                  it looks like the z-push-error.log. What’s in z-push.log?

                  Manfred

                  Caldwell 1 Reply Last reply Reply Quote 0
                  • Caldwell
                    Caldwell @Manfred last edited by

                    @manfred

                    The z-push.log has been empty since the upgrade. Same settings obviously in z-push conf file. I’ve restarted apache multiple times and removed the zero byte z-push.log file. Nothing changes. It’s not logging ANYTHING there.

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

                      Hi Caldwell,

                      did you change LOGBACKEND, LOGFILEDIR or LOGFILE in config.php of z-push? Has the webserver user permissions to write to the log file? Are there any errors in apache log?

                      Manfred

                      Caldwell 1 Reply Last reply Reply Quote 0
                      • Caldwell
                        Caldwell @Manfred last edited by

                        @manfred

                        No. They are the same. The only changed thing in the config is 1-2 new sections added by this version of z-push. Everything else is the same:

                        define('LOGBACKEND', 'filelog');
                        define('LOGFILEDIR', '/var/log/z-push/');
                        define('LOGFILE', LOGFILEDIR . 'z-push.log');
                        

                        I tried also doing specialLogUsers, but that doesn’t work either. The users certainly exist, but it’s not writing anything.

                        Permissions are apache.apache / 644. Same as the error log, which it writes to just fine. Nothing has changed there either.

                        This thing is screwed up since the upgrade, as far as new errors and no logging.

                        No errors in apache worth mentioned from what I can see.

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

                          Hi Caldwell,

                          do you have SELinux enabled? Maybe there are some its restrictions in place? It is strange that Z-Push is able to write to the error log, but not the regular log.

                          Manfred

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

                            No. It’s set as “Permissive” and not “Enforcing” on that server currently. The only change that was made was a yum update to pick up the new z-push.

                            How can I downgrade to the previous version?

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