Webtop 5 not syncing PHP error contacts

WebTop
1

I decided to switch from SOGo to Webtop5 because of the totp.

It turns out that my contacts on the android phone are not syncing when z-push is enabled. The log files give no errors at all no registrations in both z-push and z-push-error logfiles so far.
I checked over commandline the following which gave an error in php code:

php /usr/share/webtop/z-push/z-push-admin.php -a list
#!/usr/bin/env php

PHP Fatal error: Can’t use method return value in write context in /usr/share/webtop/z-push/backend/contacts/contacts.php on line 257

Any help would be appreciated.

Regards,

Guus

2

Are SOGo and Webtop5 running (or installed) side by side on the same server?

3

Because I’ve read that SOGo overrules Webtop I completely removed if, deinstalling.

4

Check if there are some leftovers:

5

I think the doc has not been updated after the switch to PHP 72.

Could you please try with:

scl enable rh-php72 -- php /usr/share/webtop/z-push/z-push-admin.php
1 Like
6

This gives the following:

[root@yz1web ~]# scl enable rh-php72 – php /usr/share/webtop/z-push/z-push-admin.php
#!/usr/bin/env php
Usage:
z-push-admin.php -a ACTION [options] …

7

I followed the instructions Marc suggested.

I get the following log messages:

/var/log/z-push/server.log:
18/11/2020 09:40:38 [32449] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
18/11/2020 09:41:01 [30661] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command

/var/log/z-push/server_error.log:
18/11/2020 09:40:38 [32449] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
18/11/2020 09:40:43 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:43 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:44 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:45 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:45 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:46 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:46 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:47 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:48 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:48 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:49 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:50 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:50 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:51 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:51 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:52 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:52 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:53 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:54 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:54 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:55 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:56 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:56 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:57 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:57 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:58 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:59 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:40:59 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:00 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:01 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:01 [30661] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
18/11/2020 09:41:01 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:02 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:03 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:05 [30657] [ERROR] [guus@ijzereef.nl] Ignored broken message (SyncAppointment). Reason: ‘4’ Folderid: ‘c/Agenda-Guus’ message id ‘93’
18/11/2020 09:41:12 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:13 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:13 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:14 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:14 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:15 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:16 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:16 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:17 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:18 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:18 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:19 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:19 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:20 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:21 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:21 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:22 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:23 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:23 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:24 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:25 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:25 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:26 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:27 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:27 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:28 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:29 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:29 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:30 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:31 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:31 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:32 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:33 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:33 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:34 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:35 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:35 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:36 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:37 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:37 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:38 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:39 [18987] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:39 [30671] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:40 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:41 [32586] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:42 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:42 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:43 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:44 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:44 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:49 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:49 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:50 [16666] [ERROR] [guus@ijzereef.nl] Ignored broken message (SyncAppointment). Reason: ‘4’ Folderid: ‘c/Agenda-Guus’ message id ‘93’
18/11/2020 09:41:51 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:52 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:53 [30661] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:54 [30657] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:55 [30658] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:56 [16666] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:57 [32449] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:41:58 [18915] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
18/11/2020 09:43:41 [32449] [WARN] [guus@ijzereef.nl] BackendIMAP->parse_meeting_calendar() - No method header, please report it to the developers

Both z-pusg.log and z-push_error.log remain empty

8

So it is working :wink:

Take a look at this: https://wiki.z-hub.io/display/ZP/Loop+detection

I do not know it this is a common usage problem, let’s ask @webtop_team.

1 Like
9

It is working partly. Contacts and e-mail seem to work fine
Calendar only syncs back til Oct. 4th 2020

I look into it later.

10

Well after checking my contacts data and calendar data it mostly works fine, however in the log still some warnings and also in gmail only appointments that go back till November 5th 2020.

./z-push/server_error.log

18/11/2020 18:09:48 [27067] [WARN] [guus@ijzereef.nl] BackendIMAP->parse_meeting_calendar() - No method header, please report it to the developers
18/11/2020 18:47:57 [27067] [WARN] [guus@ijzereef.nl] Message should be moved to WasteBasket, but the Backend did not return a destination ID. Message is hard deleted now!
18/11/2020 18:47:57 [27067] [WARN] [guus@ijzereef.nl] Message should be moved to WasteBasket, but the Backend did not return a destination ID. Message is hard deleted now!
18/11/2020 19:23:11 [27069] [WARN] [guus@ijzereef.nl] Searchtype ‘GAL’ is not supported.
18/11/2020 19:23:11 [30758] [WARN] [guus@ijzereef.nl] Searchtype ‘GAL’ is not supported.

and in the ./webtop-dav/dav-server.log

[2020-11-18 17:41:35] dav-server.ERROR: W\D\C\Backend - WT\Client\Contacts\ApiException: [500] Server error: GET http://localhost:58080/webtop/api/com.sonicle.webtop.contacts/v1/carddav/addressbooks/3i2NDaWmqGVd2U/cards?hrefs=7e41c96d-86bb-4ca0-9ecc-d20e17c9113c.vcf resulted in a 500 Internal Server Error response:
{“code”:500,“description”:“com.sonicle.webtop.core.sdk.WTRuntimeException: Owner not found [5]”}
in /usr/share/webtop/webdav/lib/webtop-contacts-client/Api/DavCardsApi.php:912
Stack trace:
#0 /usr/share/webtop/webdav/lib/webtop-contacts-client/Api/DavCardsApi.php(886): WT\Client\Contacts\Api\DavCardsApi->getCardsWithHttpInfo(‘3i2NDaWmqGVd2U’, Array)
#1 /usr/share/webtop/webdav/lib/webtop/DAV/CardDAV/Backend.php(227): WT\Client\Contacts\Api\DavCardsApi->getCards(‘3i2NDaWmqGVd2U’, Array)
#2 /usr/share/webtop/webdav/vendor/sabre/dav/lib/CardDAV/AddressBook.php(67): WT\DAV\CardDAV\Backend->getCard(‘3i2NDaWmqGVd2U’, ‘7e41c96d-86bb-4…’)
#3 /usr/share/webtop/webdav/vendor/sabre/dav/lib/DAV/Tree.php(76): Sabre\CardDAV\AddressBook->getChild(‘7e41c96d-86bb-4…’)
#4 /usr/share/webtop/webdav/vendor/sabre/dav/lib/DAV/CorePlugin.php(81): Sabre\DAV\Tree->getNodeForPath(‘addressbooks/gu…’)
#5 [internal function]: Sabre\DAV\CorePlugin->httpGet(Object(Sabre\HTTP\Request), Object(Sabre\HTTP\Response))
#6 /usr/share/webtop/webdav/vendor/sabre/event/lib/EventEmitterTrait.php(105): call_user_func_array(Array, Array)
#7 /usr/share/webtop/webdav/vendor/sabre/dav/lib/DAV/Server.php(479): Sabre\Event\EventEmitter->emit(‘method:GET’, Array)
#8 /usr/share/webtop/webdav/vendor/sabre/dav/lib/DAV/Server.php(254): Sabre\DAV\Server->invokeMethod(Object(Sabre\HTTP\Request), Object(Sabre\HTTP\Response))
#9 /usr/share/webtop/webdav/lib/webtop/DAV/Server.php(93): Sabre\DAV\Server->exec()
#10 /usr/share/webtop/webdav/server.php(21): WT\DAV\Server->exec()
#11 {main} [] []

11

Since my calendar is not syncing correct (google calendar) I tested with blue mail app.

There is somewhere a SOGo instance interfering, although completly deinstalled and config directory removed. Even a reboot didn’t change the behaviour:

Log z-push server:
19/11/2020 13:51:42 [27741] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command

log z-push/server_error
19/11/2020 08:23:32 [27069] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 09:32:46 [27070] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
19/11/2020 09:32:47 [30758] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
19/11/2020 09:47:44 [15524] [WARN] [guus@ijzereef.nl] BackendIMAP->parse_meeting_calendar() - No method header, please report it to the developers
19/11/2020 13:51:41 [27068] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
19/11/2020 13:51:42 [27741] [FATAL] [guus@ijzereef.nl] Exception: (ProvisioningRequiredException) - Retry after sending a PROVISION command
19/11/2020 13:51:46 [15524] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:47 [27070] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:47 [27068] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:48 [29788] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:49 [27741] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:49 [30758] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:50 [27067] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:51 [25193] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:51 [27069] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:52 [27065] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:53 [15524] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:53 [27070] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:54 [27068] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:55 [29788] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:55 [27741] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:56 [30758] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:56 [27067] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:57 [25193] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:58 [27069] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:51:58 [27065] [WARN] [guus@ijzereef.nl] Mobile loop detected! Messages sent to the mobile will be restricted to 1 items in order to identify the conflict
19/11/2020 13:57:29 [30758] [WARN] [guus@ijzereef.nl] BackendIMAP->parse_meeting_calendar() - No method header, please report it to the developers

system log
13:24 imap(guus@ijzereef.nl): Logged out in=305 out=18787 dovecot
13:24 imap-login: Login: user=guus@ijzereef.nl, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18412, secured, session=<+V/RzXS0TpJ/AAAB> dovecot
13:24 pam_sss(dovecot:auth): authentication success; logname= uid=0 euid=0 tty=dovecot ruser=guus@ijzereef.nl rhost=127.0.0.1 user=guus@ijzereef.nl auth
13:24 imap(guus@ijzereef.nl): Logged out in=3226 out=31679 dovecot
13:24 Removed slice User Slice of sogo. systemd
13:24 (sogo) CMD (/usr/sbin/sogo-ealarms-notify > /dev/null 2>&1) CROND
13:24 Started Session 1692 of user sogo. systemd
13:24 Created slice User Slice of sogo. systemd
13:23 imap(guus@ijzereef.nl): Logged out in=305 out=18787 dovecot
13:23 imap-login: Login: user=guus@ijzereef.nl, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=18318, secured, session=<li4jzHS0SJJ/AAAB> dovecot
13:23 pam_sss(dovecot:auth): authentication success; logname= uid=0 euid=0 tty=dovecot ruser=guus@ijzereef.nl rhost=127.0.0.1 user=guus@ijzereef.nl auth

Any suggestions how to investigate or resolve?

imap login is emclient

12

Hi @Guus

perhaps the sogo fragment remained in the apache configuration…
You can remove it like this:

rm -f /etc/httpd/conf.d/SOGo.conf
systemctl restart httpd

Let them know if it solves :wink:

1 Like
13

Also check for the presence of other sogo components:

rpm -qa sogo* sope* |sort
1 Like
14

Executed the command and start checking the log files

15

There are some instances still active

[root@yz1web ~]# rpm -qa sogo* sope* |sort
sogo-5.0.1-1.ns7.x86_64
sogo-activesync-5.0.1-1.ns7.x86_64
sogo-ealarms-notify-5.0.1-1.ns7.x86_64
sogo-tool-5.0.1-1.ns7.x86_64
sope49-appserver-4.9-5.0.1.1.ns7.x86_64
sope49-cards-5.0.1-1.ns7.x86_64
sope49-core-4.9-5.0.1.1.ns7.x86_64
sope49-gdl1-4.9-5.0.1.1.ns7.x86_64
sope49-gdl1-contentstore-5.0.1-1.ns7.x86_64
sope49-gdl1-mysql-4.9-5.0.1.1.ns7.x86_64
sope49-ldap-4.9-5.0.1.1.ns7.x86_64
sope49-mime-4.9-5.0.1.1.ns7.x86_64
sope49-sbjson-2.3.1-5.0.1.1.ns7.x86_64
sope49-xml-4.9-5.0.1.1.ns7.x86_64
[root@yz1web ~]#

The 4 sogo packages I already removed with yum. what is the packagename of sope49?

This actually means that when I remove the package from the dashboard these instances are not removed.

16

Well first tests implicate that the atctivesync is working. Only the imported calendar items are not displayed on my mobile (google calendar).
As soon as I make a new appointment on my handy it shows up, in android, in caldav (emclient) and in webapp webtop.

Also the error logs show no new entries since this afternoon. I follow up and keep you informed.

Thanks so far for the support.

1 Like
17

Don’t know what SOPE stands for, but it is a dependency of SOGo.
When removing modules from dashboard in most cases only the module is removed but not the underlying/related software. If you search the forum you’ll find past discussions about it.
Here is a more complete SOGo removal (but when removing things it’s always good to proceed with extra care):

AFAIK, the loop is done when there’s a sync problem, like a wrong entry (ex. starting date newer than ending date, etc.).

I guess a troubleshooting step would have been to identify/locate the message by the reported id and analyse it, but I do not know how it is done.

Glad it is (mostly) working.

18

So up till now e-mail and contacts sync as expected.

Calendar gives some troubles, possibly related to the oneplus 8 android phone I’am using.

Results so far:
I deleted all calendar items and put the important ones in the calendar using emclient on a win 10, connected over caldav for contacts and calendar. All calendar items are stored and also visible in both emclient calendar as well as in the webtop5 webbrowser client.

So now to the phone, first I installed again blue mail which syncs over eas without problem the e-mail and contacts. The calendar Items shown are only from this week and last week.
So second I installed DavX5. In the past I had good experience with it. I only sync the calendar items and it’s a bit better since now in Calendar I see the appointments of this week and the past 4 weeks.

Never the less my appointments reach back till August 2019 and I would like to see them all on my phone.

1 Like
19

@Guus

Hi

I don’t use WebTop, I use NextCloud for Calender and Adressbok sync.

But - just for your Information - The setting “past 4 weeks” for Calender is a very common setting i’ve seen in iOS and several Androids and has nothing to do with how you sync the server. The setting can / must be changed on your mobile device.

Maybe this helps…

My 2 cents
Andy

1 Like
20

Hi @Guss,

on DavX5 you can change the default settings of a single account by setting the synchronization time limit for ClaDAV for events that have already passed :wink:
To enter the settings you have to click on the gear icon at the top left:
Screenshot_DavX5

1 Like