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

    [#unknown] now appearing in logs

    Z-Push when using Kopano
    3
    4
    1062
    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.
    • robertwbrandt
      robertwbrandt last edited by

      Since upgrading z-push to 2.4.1 I noticed that in the logs there is now a field which is just [#unknown]

      Unfortunately I noticed it too late to be able to go back and see what was there before.

      What is this field suppose to contain and how do I fix it?

      Thanks
      Bob

      kopano-activesync-seg:~# tail -f /var/log/z-push/z-push.log
14/05/2018 14:04:07 [ 5593] [ INFO] [#unknown] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 470 seconds)
14/05/2018 14:04:07 [ 3494] [ INFO] [#unknown] The configuration parameter 'USE_X_FORWARDED_FOR_HEADER' was deprecated in favor of 'USE_CUSTOM_REMOTE_IP_HEADER'. Please update your configuration.
14/05/2018 14:04:07 [ 3494] [ INFO] [#unknown] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 470 seconds)
14/05/2018 14:04:08 [ 1523] [ INFO] [#unknown] The configuration parameter 'USE_X_FORWARDED_FOR_HEADER' was deprecated in favor of 'USE_CUSTOM_REMOTE_IP_HEADER'. Please update your configuration.
14/05/2018 14:04:08 [ 1523] [ INFO] [#unknown] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 470 seconds)
14/05/2018 14:04:09 [ 1470] [ INFO] [#unknown] StatusException: SyncCollections->CheckForChanges(): Timeout forced after 60s from 650s due to other process - code: 3 - file: /usr/share/z-push/lib/core/synccollections.php:579
14/05/2018 14:04:09 [ 1470] [ INFO] [#unknown] cmd='Ping' memory='5.14 MiB/2.00 MiB' time='60.49s' devType='SamsungDevice' devId='sec1f0a782fa8eda' getUser='username' from='192.168.1.xxx' idle='60s' version='2.4.1+0-0' method='POST' httpcode='200'
14/05/2018 14:04:09 [ 4897] [ INFO] [#unknown] The configuration parameter 'USE_X_FORWARDED_FOR_HEADER' was deprecated in favor of 'USE_CUSTOM_REMOTE_IP_HEADER'. Please update your configuration.
14/05/2018 14:04:10 [ 4897] [ INFO] [#unknown] cmd='Settings' memory='4.65 MiB/4.00 MiB' time='0.42s' devType='KFSOWI' devId='kfsowi1383092106083' getUser='username' from='192.168.1.xxx' idle='0s' version='2.4.1+0-0' method='POST' httpcode='200'
14/05/2018 14:04:11 [ 1523] [ INFO] [#unknown] cmd='Ping' memory='5.38 MiB/2.00 MiB' time='2.64s' devType='SAMSUNGSMAFL' devId='sec14886cc24bd87' getUser='domain\username' from='192.168.1.xxx' idle='3s' version='2.4.1+0-0' method='POST' httpcode='200'
14/05/2018 14:04:11 [ 4897] [ INFO] [#unknown] The configuration parameter 'USE_X_FORWARDED_FOR_HEADER' was deprecated in favor of 'USE_CUSTOM_REMOTE_IP_HEADER'. Please update your configuration.
14/05/2018 14:04:11 [ 4897] [ INFO] [#unknown] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 470 seconds)

kopano-activesync-seg:~# tail -f /var/log/z-push/z-push-error.log
14/05/2018 14:00:51 [ 5511] [FATAL] [#unknown] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect
14/05/2018 14:01:05 [ 3562] [WARN] [#unknown] /usr/share/z-push/backend/kopano/kopano.php:168 mapi_logon_zarafa(): Unable to setup service for provider (2)
14/05/2018 14:01:05 [ 3562] [ERROR] [#unknown] KopanoBackend->Logon(): login failed with error code: 0xFFFFFFFF80040111
14/05/2018 14:01:05 [ 3562] [FATAL] [#unknown] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect
14/05/2018 14:01:17 [ 2398] [WARN] [#unknown] /usr/share/z-push/backend/kopano/kopano.php:168 mapi_logon_zarafa(): Unable to setup service for provider (2)
14/05/2018 14:01:17 [ 2398] [ERROR] [#unknown] KopanoBackend->Logon(): login failed with error code: 0xFFFFFFFF80040111
14/05/2018 14:01:17 [ 2398] [FATAL] [#unknown] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect
14/05/2018 14:01:40 [ 5582] [WARN] [#unknown] /usr/share/z-push/backend/kopano/kopano.php:168 mapi_logon_zarafa(): Unable to setup service for provider (2)
14/05/2018 14:01:40 [ 5582] [ERROR] [#unknown] KopanoBackend->Logon(): login failed with error code: 0xFFFFFFFF80040111
14/05/2018 14:01:40 [ 5582] [FATAL] [#unknown] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect
14/05/2018 14:02:00 [ 2675] [WARN] [#unknown] /usr/share/z-push/backend/kopano/kopano.php:168 mapi_logon_zarafa(): Unable to setup service for provider (2)
14/05/2018 14:02:00 [ 2675] [ERROR] [#unknown] KopanoBackend->Logon(): login failed with error code: 0xFFFFFFFF80040111
14/05/2018 14:02:00 [ 2675] [FATAL] [#unknown] Exception: (AuthenticationRequiredException) - Access denied. Username or password incorrect
      1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano last edited by

        Hi @robertwbrandt ,

        I guess you upgraded from 2.3.x?

        The field contains the connecting username. It prints #unknown, if no user is was supplied.

        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/

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

          Hi Bob,

          you also should update the Z-Push config if you haven’t done it yet. USE_X_FORWARDED_FOR_HEADER is not used anymore, rename it to USE_CUSTOM_REMOTE_IP_HEADER.

          Manfred

          1 Reply Last reply Reply Quote 1
          • robertwbrandt
            robertwbrandt @fbartels last edited by

            @fbartels yes indeed.

            I didn’t update the z-push.conf.php during the upgrade.

            Once I transferred the settings to the new config file both problems were solved immediately.

            Thanks
            Bob

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