Well, I’m out of idea ☹ Maybe test to change the username of SOGoProfileURL and look at the log to see if the name has changed as well, just to be sure the correct sogo.conf file is used. You could also send to my address only [email protected] <mailto:[email protected]> your sogo.conf file (censor your password) so I can see if anything shocks me.
From: [email protected] <[email protected]> On Behalf Of Richard Rosner Sent: vendredi 21 juillet 2023 13:27 To: qhivert ([email protected]) <[email protected]> Subject: Re: [SOGo] SOGo no longer talking to mysql Hi Quentin, thanks for this, but username is just sogo, password only consists of latin alphabet letters (no special letters like ê, ę or others), numbers and simple special characters like - or _, nothing that's not ASCII. Is there anything else that can/must be done? E.g. in mysql you have to denote usernames, passwords or host names in quotes. It's nothing sogo seems to need as it did work previously, but is there something similar I could try? Richard Am 21.07.2023 um 12:21 schrieb qhivert ([email protected] <mailto:[email protected]> ): Hello again Richard, Just in case, in your sogo.conf the username and password must be “url” encoded if you have any special characters -> https://www.w3schools.com/tags/ref_urlencode.ASP From: [email protected] <mailto:[email protected]> <mailto:[email protected]> <[email protected]> On Behalf Of Richard Rosner Sent: vendredi 21 juillet 2023 09:44 To: Kenren Taisho ([email protected] <mailto:[email protected]> ) <mailto:[email protected]> <[email protected]> Subject: Re: [SOGo] SOGo no longer talking to mysql Hi Kenren, skip-name-resolve is alraedy commented out. Richard Am 21.07.2023 um 02:13 schrieb Kenren Taisho ([email protected] <mailto:[email protected]> ): Hi Richard, ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Could you check if skip-name-resolve is enabled in your MySQL config? And if is, remove it, restart MySQL, and see if SOGo is communicating again with MySQL. Kind regards On Fri, Jul 21, 2023 at 12:03 AM Richard Rosner <[email protected] <mailto:[email protected]> > wrote: Hi Quentin, I didn't only not change the password, I even made double sure the user still had all permissions for the database in question. And like I said, I did try username and password manually, which did work. I enabled MySQL4DebugEnabled, but outout doesn't seem to have changed: Jul 20 17:41:15 sogod [79585]: <0x0x7f8a1a4b7340[WOWatchDogChild]> watchdog request timeout set to 10 minutes Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> preparing 3 children Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79586 Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79587 Jul 20 17:41:15 sogod [79585]: <0x0x55ce03e91c70[WOWatchDog]> child spawned with pid 79588 2023-07-20 17:41:16.020 sogod[79588:79588] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Jul 20 17:41:16 sogod [79588]: [ERROR] <0x0x55ce03f47520[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55ce03f707c0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 17:41:16 sogod [79588]: [WARN] <0x0x55ce03f47520[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 17:41:15 +0200 2023-07-20 17:41:16.026 sogod[79587:79587] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Jul 20 17:41:16 sogod [79587]: [ERROR] <0x0x55ce03e5a8c0[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55ce03f707c0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 17:41:16 sogod [79587]: [WARN] <0x0x55ce03e5a8c0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 17:41:15 +0200 2023-07-20 17:41:16.034 sogod[79586:79586] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Jul 20 17:41:16 sogod [79586]: [ERROR] <0x0x55ce03e56270[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55ce03f707c0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 17:41:16 sogod [79586]: [WARN] <0x0x55ce03e56270[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 17:41:15 +0200 Jul 20 17:41:16 sogod [79588]: <0x0x55ce04083130[WOHttpAdaptor]> notified the watchdog that we are ready Jul 20 17:41:16 sogod [79587]: <0x0x55ce040840a0[WOHttpAdaptor]> notified the watchdog that we are ready Jul 20 17:41:16 sogod [79586]: <0x0x55ce04087de0[WOHttpAdaptor]> notified the watchdog that we are ready Richard Am 20.07.2023 um 17:08 schrieb qhivert ([email protected] <mailto:[email protected]> ): Hello Richard, Strange indeed. I assume you didn’t change the sogo.conf nor the password between? Is this the log with the param MySQL4DebugEnabled = YES in your sogo.conf? If not could you add it and show us the logs? Regards, Quentin From: [email protected] <mailto:[email protected]> <mailto:[email protected]> <[email protected]> On Behalf Of Richard Rosner Sent: jeudi 20 juillet 2023 16:23 To: [email protected] <mailto:[email protected]> Subject: [SOGo] SOGo no longer talking to mysql Hi, I had to reinstall SOGo because for some strange reason it just refused to accept any changes to the config. Now for some reason it can't connect to mysql anymore. In the sogo.conf I have e.g. >> SOGoProfileURL = "mysql://sogo:[email protected]:3306/sogo/sogo_user_profile <http://127.0.0.1:3306/sogo/sogo_user_profile> "; << and I have verified that mariadb is actually listening to 127.0.0.1:3306 <http://127.0.0.1:3306> . But when I restart SOGo to activate the config, I get Jul 20 15:53:10 sogod [73521]: <0x0x7fb00f4b7340[WOWatchDogChild]> watchdog request timeout set to 10 minutes Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> preparing 3 children Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child spawned with pid 73522 Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child spawned with pid 73523 Jul 20 15:53:10 sogod [73521]: <0x0x55bdab397b90[WOWatchDog]> child spawned with pid 73524 2023-07-20 15:53:10.948 sogod[73523:73523] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Jul 20 15:53:10 sogod [73523]: [ERROR] <0x0x55bdab3912c0[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55bdab4766e0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 15:53:10 sogod [73523]: [WARN] <0x0x55bdab3912c0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 15:53:10 +0200 2023-07-20 15:53:10.948 sogod[73524:73524] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) 2023-07-20 15:53:10.948 sogod[73522:73522] ERROR: could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES) Jul 20 15:53:10 sogod [73522]: [ERROR] <0x0x55bdab390df0[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55bdab4766e0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 15:53:10 sogod [73524]: [ERROR] <0x0x55bdab373020[GCSChannelManager]> could not open channel <MySQL4Channel[0x0x55bdab4766e0] connection=0x(null)> for mysql://localhost/sogo/sogo_user_profile Jul 20 15:53:10 sogod [73522]: [WARN] <0x0x55bdab390df0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 15:53:10 +0200 Jul 20 15:53:10 sogod [73524]: [WARN] <0x0x55bdab373020[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2023-07-20 15:53:10 +0200 Jul 20 15:53:11 sogod [73522]: <0x0x55bdab1b0510[WOHttpAdaptor]> notified the watchdog that we are ready Jul 20 15:53:11 sogod [73523]: <0x0x55bdab589fc0[WOHttpAdaptor]> notified the watchdog that we are ready Jul 20 15:53:11 sogod [73524]: <0x0x55bdab589050[WOHttpAdaptor]> notified the watchdog that we are ready So of course I tried logging in manually to mysql, but this succedes without any complaints. Now what's the problem with it? I'm using mariadb-server 10.11.3.
