General discussion on installation and configuration of SOGo

Text archives Help


[SOGo] Be careful when choosing your database host name...


Chronological Thread 
  • From: Pascal Gienger < >
  • To:
  • Subject: [SOGo] Be careful when choosing your database host name...
  • Date: Thu, 16 Dec 2010 09:54:02 +0100

Just a little tip:

When deploying a SOGo installation where the database server will not reside on the same host as the SOGo instances, be careful to select a (virtual) hostname which will NOT change for the lifetime of your installation. Use an DNS alias and use entries in /etc/hosts. Do not use an IP address as database host name.

Why?

In case you want/have to change your database host (ip renumbering, infrastructure change, ...) just change the IP entry for that virtual database host name (either in /etc/hosts or DNS). Otherwise...

you're cooked.


In sogo_folder_info, SOGo stores the URL to the actual storage tables (data, index (quick) and ACL (acl)) for each calendar and contact ressource.

Example:

540 | /Users/testuser/Calendar/personal | Users | testuser | Calendar | personal | Persönlicher Kalender | postgresql://sogo: :5432/sogo/sogotestuser0013182468c | postgresql://sogo: :5432/sogo/sogotestuser0013182468c_quick | postgresql://sogo: :5432/sogo/sogotestuser0013182468c_acl | Appointment



As you can see, it stores links like

postgresql://sogo: :5432/sogo/sogopop211530013182468c_quick

So if you change


- the database host name
- the database user
- the database password
- the database server port number

then you'll have to ALTER ALL ENTRIES in sogo_folder_info.


Pascal



Archive powered by MHonArc 2.6.16.

Top of page