More 3.4 calendar woes

[Homer Dokes]

Hi Timotheus,

Thank you so much for your prompt reply.

I have enabled debugging from the initial installations (has been 
running for about 6 months now).  I actually monitor the log files in 
real time 24/7 for two configured kolab servers via ssh and tail 
configured in multiple windows through tmux.  This allows us to 'catch' 
some of the issues as they occur and address them right away.  
Unfortunately, I have been unable to determine why this particular users 
contacts and calendar events stopped showing in the roundcubemail web 
client.  As indicated before, any new entries do show... just not all 
the entries prior to it's hiccup.

I appreciate the sources of information you have provided.  We will 
spend some time and sift through them to know what is where and how to 
best utilize it.

What I really need right now is to know where the mysql tables 
'kolab_cache_contact' and 'kolab_cache_calendar' get their records 
from.  I had rebuilt them with the command below but that only brought 
back the newer entries after the hiccup.  The older entries do not show 
up in these tables even tho the actual 'files' exist in the users 
respective Calendar and Contacts directories.

Command used to rebuild tables
/⁠usr/⁠share/⁠roundcubemail/plugins/libkolab/bin/modcache.sh clear -⁠u 
<user at domain.org> -h localhost

Within these directories are binary files that are named cyrus_cache, 
cyrus.header, and cyrus.index.  For this particular users contact 
directory, the cyrus.cache file size is 1.6mb, the cyrus index is 155kb, 
and the cyrus.header are 208 bytes.  I am making the assumption that 
these files contain reference information to the user files within the 
directory but I can't be sure as the cache and index files are binary 
and not reviewable. Judging by the size of the files I have to also 
believe that they contain information related to all the user contact 
files within that directory as I doubt the cache file would be 1.6mb in 
size if it only contained information on 18 contacts.  Do the respective 
mysql table for contacts derive their content (records) from these cache 
files?  If so, can these cache files be rebuilt from the user contact 
files contained within the directory.  If not, how does one include all 
the contact files into the mysql kolab_cache_contact' table?  The 
command line above does not include them all... only the newer files 
that were added after the hiccup.  Should that command have included all 
the files from 1. to 1458. that exist within the contacts directory for 
that user?

For clarification.... definition of a 'hiccup': The point at which the 
user realized something was amiss...  not ALWAYS consistent with when 
the symptom actually manifested itself. :-)

I have tried to provide as much information here as I can think is 
pertinent.  If additional information would help please let me know what 
you would need to get a better understanding of the issues.

Again, Thanks Tim for your reply, and to anyone else that may be able to 
shed some light on this issue.  In the mean time, We'll keep plugging 
away for a viable solution.

hdokes