Nick Howitt wrote:
Hi Patrick, since the upgrade process is still manual, I do not see Kopano automatically replacing Zarafa, and the document also indicates you'd need to purchase Kopano first.
The update was pushed to my server last night by ClearOS (with a problem on de LDAP server) and Zarafa is still working.
Still remains the question if ClearOS will supply a release like Home Edition with a Kopana license as we had with Zarafa (package deal)
Now i've a home edition with a paid license and need to buy a extra license for Kopano.
Gordon came into support and what we found was that a restore attempt earlier had made it so that our fix doesn't work because the restore killed all his LDAP database. Basically, if you have a compromised system and attempt to recover from a backup configuration it will try to restore with the failed slapd.conf file and will error out. Unfortunately, it will have already dropped your users from your LDAP database in the process so if you fix the slapd.conf file and start 'slapd' it will run but have no users in the database.
The process is a bit advanced to recover from this so if anyone has this particular nuance of attempting to recover from the backup config and failing, please hop into support for ClearCARE and let us help you fix it. Basically what you have to do is to create a merged recovery file in Remote Configuration Backup of a previous backup and the fixed slapd.conf.
You create a directory.
Copy the configuration backup file you want to restore from.
Extract it (tar xvcf filename) and move the archive tgz file away
Copy the correct slapd.conf file (with the Kopano fixes) into the right place in the archive
Validate the permissions (ldap:ldap)
Archive up the file (cd /place/you/extracted/the/file && tar /tmp/ldaprecovery.tgz -cvzf *)
Then move the ldap recovery file back to /var/clearos/configuration_backup
Then go back into Webconfig and restore it.
If you need us to do this for you, please open a ticket and we can get it resolved for you.
The password must already been set in the "old" slapd.conf.
Only replace the Schemes in to the slapd.conf with the Schemes Dave has posted.
I removed the folder as you said and put in the config file (slapd.conf) as you wrote in the other thread. I replaces the domain names and the ldap starts now, but samba, zarafa, ... do still now work ... .
You wrote in the other thread:
Password: Must have the valid password (for slapd.conf)
What does that mean? Where do I get that?
This worked out for me.
Dave Loper wrote:
Some systems were running a patch that originated from CentOS that borks their LDAP. The 3 steps to validate are:
1) Move the /etc/openldap/slapd.d folder out of the way. (The CentOS RPM creates this folder)
mv /etc/openldap/slapd.d /tmp/
2) Make sure ........................
Dave Loper wrote:
Kapano app (Zarafa Replacement) (https://www.clearos.com/resources/documentation/clearos/content:en_us:7_kb_zarafa_to_kopano_upgrade)
Do you what is going to happen with the Home essential subsciption.
This includes now a Zarafa package, but do need to pay extra for Kopano or will there be a package deal again.
Peter Baldwin wrote:
Certificate is not in use.
The Certificate Manager can detect when a certificate is in use via ClearOS apps (e.g. Web Server), but it cannot detect usage inside custom configuration files. Sorry!
Webconfig must had an update ;-)
Now it is saying :
When will the app run an update of the certificate ?
Is there a cronjob needed or is webconfig handling this ?