On 6/14/2014 3:35 PM, Ludovic Marcotte <[email protected]> wrote:
On 2014-06-14, 2:32 PM, Charles Marcus wrote:
2014-06-14 14:32:01.639 sogo-tool[19240] ERROR: could not open MySQL4
connection to database 'sogo': Host 'webmail.media-brokers.com' is
not allowed to connect to this MariaDB server
<0x0x177b140[GCSChannelManager]> could not open channel
<MySQL4Channel[0x0x16331b0] connection=0x(null)> for
URL:mysql://sogo_admin:[email protected]:3306/sogo/sogo_sessions_folder
Check your ACL on mysql.media-brokers.com.
The host 'webmail.media-brokers.com' should be allowed to connect
using the 'sogo_admin' user and access the 'sogo' database.
See: https://mariadb.com/kb/en/grant/
I guess during your upgrade the access lists were messed up.
Ok, well, it is no longer an emergency...
Once I noticed the wrong hostname, I was able to fix this temporarily by
granting the same rights that the sogo user has on the sogo DB, to
[email protected] user.
Now, the question is, why did the DB start seeing these connections as
coming from the webmail.media-brokers.com hostname?
I did have that pointer set up in DNS as an alternate hostname
associated with the sogo host IP, but it has been working for months
like that. I tried deleting this entry, clearing the DNS cache on the
DNS server and restarting it, and even restarting the SOGo server
The hostname is set to sogo:
root@sogo:~# hostname
sogo
root@sogo:~#
Is there a way to tell sogo to connect with a specific hostname, ie:
sogo.media-brokers.com?
Best regards,
Charles
--
[email protected]
https://inverse.ca/sogo/lists
