Overriding URLs



  • Hi Folks,

    Recently I updated my z-push to the most recent patch level, which z-push-top tells me is 2.4.4+0. I know it as version 68. I have noticed a lot of messages (… hundreds per day) in /var/log/z-push-error.log:

    ... [#unknown] Zimbra->GetUserInfo():   Overriding  Logon URL [https://mail.tclc.org/service/soap/] with ZIMBRA soapURL [https://mail.tclc.org:8443/service/soap/]
    ... [#unknown] Zimbra->GetUserInfo():   Overriding ZIMBRA_URL [https://mail.tclc.org] from config.php with ZIMBRA publicURL [https://mail.tclc.org:8443]
    

    I’m not sure the update and the log flood are related, because I simply discovered the log flood while troubleshooting the new installation, but they are coincident. I seek explanation and advice.

    Thanks for the help,

    Chris.

    P.S.:

    I have also discovered some messages that request reports to developers. There are four messages all incriminating PID 30501, which appears nowhere in /var/log/messages. I don’t think I’m too worried about this, but you asked that I report it, so I have. If you have any logs you want me to check, I’m quite happy to do that.

    Insert Code Here18/10/2018 09:25:07 [30501] [ERROR] [#unknown] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Sync' at 18/10/2018 09:25:07 with pid '30501' terminated unexpectedly or is still running.
    18/10/2018 09:25:07 [30501] [ERROR] [#unknown] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team.
    18/10/2018 09:25:07 [30495] [ERROR] [#unknown] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Sync' at 18/10/2018 09:25:07 with pid '30501' terminated unexpectedly or is still running.
    18/10/2018 09:25:07 [30495] [ERROR] [#unknown] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team.
    18/10/2018 09:25:07 [18471] [ERROR] [#unknown] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Sync' at 18/10/2018 09:25:07 with pid '30501' terminated unexpectedly or is still running.
    18/10/2018 09:25:07 [18471] [ERROR] [#unknown] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team.
    18/10/2018 09:25:07 [21248] [ERROR] [#unknown] LoopDetection->ProcessLoopDetectionPreviousConnectionFailed(): Command 'Sync' at 18/10/2018 09:25:07 with pid '30501' terminated unexpectedly or is still running.
    18/10/2018 09:25:07 [21248] [ERROR] [#unknown] Please check your logs for this PID and errors like PHP-Fatals or Apache segmentation faults and report your results to the Z-Push dev team.
    

  • Kopano

    Hi Chris,

    I’m not involved in Zimbra backend development, so I can’t tell you anything about the overriding URLs, but do you also have entries in z-push.log like:

    18/10/2018 17:03:21 [29496] [ INFO] [#unknown] The configuration parameter 'USE_X_FORWARDED_FOR_HEADER' was deprecated in favor of 'USE_CUSTOM_REMOTE_IP_HEADER'. Please update your configuration.
    

    ?

    If yes, you should update the main Z-Push config file by replacing USE_X_FORWARDED_FOR_HEADER with USE_CUSTOM_REMOTE_IP_HEADER.

    Manfred



  • Hi Manfred,

    No. I don’t have any such entries.

    Thanks for the help,

    Chris.



  • @cjm51213 said in Overriding URLs:

    … [#unknown] Zimbra->GetUserInfo(): Overriding Logon URL [https://mail.tclc.org/service/soap/] with ZIMBRA soapURL [https://mail.tclc.org:8443/service/soap/]
    … [#unknown] Zimbra->GetUserInfo(): Overriding ZIMBRA_URL [https://mail.tclc.org] from config.php with ZIMBRA publicURL [https://mail.tclc.org:8443]

    You should check your zimbra configuration and proxy configuration.

    z-push will pick up whatever is set in your zimbra configuration for your domain under The General Information tab - Public service host name/protocol/port

    Note: z-push should be pointed at the nginx proxy - not directly at a mailbox server - as connecting through the proxy is required in order to establish and maintain sessions.


Log in to reply