Repeated hierarchy changes in a new 2.3.8 installation with IMAP backend
-
I am getting the following repeated info message in the logs:
ExportChangesDiff->InitializeExporter(): Found ‘11’ changes for ‘hierarchy’The IMAP mailbox in question has 11 folders total, but there are no changes happening and I am getting this message even when there are no new messages.
Is it a cause for concern? Push is working intermittently with an iOS client and I am looking for possible causes.
-
Hi elodg,
could you provide more information on what’s happening?
How often is this entry in the log? It alone doesn’t indicate any issues.
Manfred
-
With every Sync or Ping command, pretty much all the time.
25/12/2017 05:51:44 [ 6207] [ INFO] [<EMAIL>] cmd='Ping' memory='2.81 MiB/3.25 MiB' time='599.92s' devType='iPhone' devId='l6ks0va0ip4d7eq44vk20f3688' getUser='<EMAIL>' from='109.166.137.72' idle='600s' version='2.3.8' method='POST' httpcode='200' 25/12/2017 05:56:06 [ 6159] [ INFO] [<EMAIL>] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 600 seconds) 25/12/2017 05:56:06 [ 6159] [ INFO] [<EMAIL>] ExportChangesDiff->InitializeExporter(): Found '11' changes for 'hierarchy' 25/12/2017 06:06:06 [ 6159] [ INFO] [<EMAIL>] cmd='Ping' memory='2.84 MiB/3.25 MiB' time='599.05s' devType='iPhone' devId='l6ks0va0ip4d7eq44vk20f3688' getUser='<EMAIL>' from='109.166.137.72' idle='600s' version='2.3.8' method='POST' httpcode='200' 25/12/2017 06:24:54 [ 6214] [ INFO] [<EMAIL>] SyncCollections->CheckForChanges(): Waiting for store changes... (lifetime 600 seconds) 25/12/2017 06:24:54 [ 6214] [ INFO] [<EMAIL>] ExportChangesDiff->InitializeExporter(): Found '11' changes for 'hierarchy'
When there is new e-mail I am getting an additional
24/12/2017 18:14:02 [27256] [ INFO] [<EMAIL>] ExportChangesDiff->InitializeExporter(): Found '1' changes for 'fa950af3'
which is expected.
Why aren’t ‘hierarchy’ changes counted only when there is actual change? -
Hi elodg,
hierarchy changes are counted when there’s a change. There is a comparison between saved and current hierarchy. Why it finds change every time is another question. The INFO loglevel doesn’t provide much information. At least DEBUG would be necessary.
Manfred
-
I believe the log excerpt below is relevant. It repeats for each folder. What changes deemed not relevant could be there to folders?
29/12/2017 15:20:03 [ 9504] [ INFO] [<EMAIL>] ExportChangesDiff->InitializeExporter(): Found '12' changes for 'hierarchy' 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] ExportChangesCombined->InitializeExporter(...) success 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] ExportChangesCombined->Synchronize() 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] BackendIMAP->getImapIdFromFolderId('340e6f4a') = INBOX 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] BackendIMAP->GetFolder('340e6f4a'): 'SyncFolder ( (S) serverid => 340e6f4a (S) parentid => 0 (S) displayname => Inbox (S) type => 2 (S) Store => null (S) NoBackendFolder => null (S) BackendId => null (S) Flags => null (S) TypeReal => null unsetVars(Array) size: 0 supportsPrivateStripping => false flags => false content => null )' 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] BackendIMAP->getImapIdFromFolderId('340e6f4a') = INBOX 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] BackendIMAP->GetFolder('340e6f4a'): 'SyncFolder ( (S) serverid => 340e6f4a (S) parentid => 0 (S) displayname => Inbox (S) type => 2 (S) Store => null (S) NoBackendFolder => null (S) BackendId => null (S) Flags => null (S) TypeReal => null unsetVars(Array) size: 0 supportsPrivateStripping => false flags => false content => null )' 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] ImportHierarchyChangesCombinedWrap->ImportFolderChange('340e6f4a') 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] ImportHierarchyChangesCombinedWrap->ImportFolderChange() success 29/12/2017 15:20:03 [ 9504] [DEBUG] [<EMAIL>] ChangesMemoryWrapper->ImportFolderChange(): Change for folder 'Inbox' will not be sent as modification is not relevant.
-
Hi elodg,
for the hierarchy the relevant changes are the folder name and folder’s parent. If some folder flags change (e.g. count of read/unread/deleted messages), it is not relevant for the hierarchy. The count and log output of changes happens before the check if these changes are relevant. If this log output is your only issue, you don’t have to worry.
Manfred
-
I don’t have any issues that can be attributed to this log, and it is good to know there is no need to worry. It does make curious though what those flag changes could be if there are absolutely no changes in the mailbox.