Re: [SOGo] SOGo no longer talking to mysql
Glad you finally figured things out :-)
On Tue, Jul 25, 2023 at 5:11 PM Richard Rosner wrote:
> Good news, I finally was able to get SOGo back up and running (and using
> /etc/sogo/sogo.conf, like any sane progarm would do).
>
> But be honest people, who on earth should be able to have guessed that
> "~sogo/" refers to "/var/lib/sogo/"? I already thought I was crazy
> searching /usr for a .GNUstepDefaults, but this is actually peak
> insanity. ~ usually is read as /home/username. I think this needs to be
> clarified in the unmodified sogo.conf, or at least create a possibility
> to have sogo say where it actually reads the configuration from. I
> checked /var/lib/sogo/GNUstep/Defaults/ and can tell you SOGo did not
> read from .GNUstepDefaults as it basically didn't contain any config. It
> either read from .GNUstepDefaults.bck from 2013 or sogod.plist from
> 2015. And it does not help in the slightest when sogo-tool reads from
> /etc/sogo/sogo.conf, while it's not even read by sogod.
>
>
> Thanks anyways to all that came up with ways to find out what's going
> wrong with the setup. I'm still not really sure how strace would
> indicate that the mysql user in sogo.conf is being used when sogod
> clearly must have gotten its config from somewhere else, but that's
> something people can think about that know more about how sogo actually
> operates.
>
> Richard
>
> Am 25.07.2023 um 08:35 schrieb Markus Winkler (m...@irmawi.de):
> > Hi Richard,
> >
> > On Mon, 24 Jul 2023 at 01:40:52PM +0200, Richard Rosner wrote:
> >>
> >> My biggest problem with the old installation was (which was set up
> >> before I became admin and I can't tell if it has been upgraded somehow
> >> from SOGo 2.x, which we where using before 5.x, or if it was a fresh
> >> install) that when I took over, the whole config was commented out and
> >> everything was set to their default values. I have no idea how it even
> >> worked in the first place, already because the default database is
> >> postgresql, which isn't even installed on the system. And when I tried
> >> to edit things like page title or availability of forwarding, they
> >> simply didn't get applied. So I hoped with reinstalling I could solve
> >> the issue. I even did an apt purge to remove everything from that old
> >> installation (so only the mysql database survived), but obviously the
> >> problem seems to be somewhere it did survive.
> >
> > On Mon, 24 Jul 2023 at 03:27:49PM +0200, Richard Rosner wrote:
> >>
> >> The old installation was SOGo (up until 5.8.0) on Debian 11 from the
> >> official Nightly Repo. I now switched to Debians own packages after
> >> upgrading to Debian 12, so it's still SOGo 5.8.0. But as the problem
> >> was present during the whole 5.x cycle (at least since we switched
> >> from 2.x, maybe in 2018 or so) and I switched to the Debian packages
> >> just now, it must be a problem independent of the package source.
> >
> >
> > just another idea regarding this strange behaviour:
> >
> >
> > Within /usr/share/doc/sogo/README.Debian
> >
> > "The SOGo debian package differs from upstream in placing the
> > configuration file in /etc/sogo/sogo.conf instead of using the GNUstep
> > user defaults that are placed under the home directory of the user
> > used to run SOGo. This file is parsed as GNUstep defaults in the
> > "sogod" domain, which means you must not specify the sogod domain in
> > the configuration file (there shouldn't be a "sogod = {" in
> > /etc/sogo/sogo.conf)."
> >
> >
> > Within a non-Debian sogo.conf there's this hint:
> >
> > * ~sogo/GNUstep/Defaults/.GNUstepDefaults has precedence over this
> > file, *
> > * make sure to move it away to avoid unwanted parameter
> > overrides. *
> >
> >
> > --> Maybe you still have a mixture of old Debian and non-Debian and/or
> > 2.x vs. 5.x configuration files somewhere? Could you have a look at
> > /var/lib/sogo/GNUstep/Defaults/ if there are files which could provide
> > SOGo defaults even if you delete /etc/sogo/sogo.conf. Or somewhere
> > else, perhaps grepping for some relevant content shows a hit?
> >
> >
> > And just to be sure: in /etc/passwd is there an entry for the sogo
> > user like this one?:
> >
> > sogo:x:999:999:SOGo daemon:/var/lib/sogo:/usr/sbin/nologin
> >
> > The home directory would be the interesting part.
> >
> > Regards,
> > Markus
> >
>
Re: [SOGo] SOGo no longer talking to mysql
Good news, I finally was able to get SOGo back up and running (and using
/etc/sogo/sogo.conf, like any sane progarm would do).
But be honest people, who on earth should be able to have guessed that
"~sogo/" refers to "/var/lib/sogo/"? I already thought I was crazy
searching /usr for a .GNUstepDefaults, but this is actually peak
insanity. ~ usually is read as /home/username. I think this needs to be
clarified in the unmodified sogo.conf, or at least create a possibility
to have sogo say where it actually reads the configuration from. I
checked /var/lib/sogo/GNUstep/Defaults/ and can tell you SOGo did not
read from .GNUstepDefaults as it basically didn't contain any config. It
either read from .GNUstepDefaults.bck from 2013 or sogod.plist from
2015. And it does not help in the slightest when sogo-tool reads from
/etc/sogo/sogo.conf, while it's not even read by sogod.
Thanks anyways to all that came up with ways to find out what's going
wrong with the setup. I'm still not really sure how strace would
indicate that the mysql user in sogo.conf is being used when sogod
clearly must have gotten its config from somewhere else, but that's
something people can think about that know more about how sogo actually
operates.
Richard
Am 25.07.2023 um 08:35 schrieb Markus Winkler (m...@irmawi.de):
Hi Richard,
On Mon, 24 Jul 2023 at 01:40:52PM +0200, Richard Rosner wrote:
My biggest problem with the old installation was (which was set up
before I became admin and I can't tell if it has been upgraded somehow
from SOGo 2.x, which we where using before 5.x, or if it was a fresh
install) that when I took over, the whole config was commented out and
everything was set to their default values. I have no idea how it even
worked in the first place, already because the default database is
postgresql, which isn't even installed on the system. And when I tried
to edit things like page title or availability of forwarding, they
simply didn't get applied. So I hoped with reinstalling I could solve
the issue. I even did an apt purge to remove everything from that old
installation (so only the mysql database survived), but obviously the
problem seems to be somewhere it did survive.
On Mon, 24 Jul 2023 at 03:27:49PM +0200, Richard Rosner wrote:
The old installation was SOGo (up until 5.8.0) on Debian 11 from the
official Nightly Repo. I now switched to Debians own packages after
upgrading to Debian 12, so it's still SOGo 5.8.0. But as the problem
was present during the whole 5.x cycle (at least since we switched
from 2.x, maybe in 2018 or so) and I switched to the Debian packages
just now, it must be a problem independent of the package source.
just another idea regarding this strange behaviour:
Within /usr/share/doc/sogo/README.Debian
"The SOGo debian package differs from upstream in placing the
configuration file in /etc/sogo/sogo.conf instead of using the GNUstep
user defaults that are placed under the home directory of the user
used to run SOGo. This file is parsed as GNUstep defaults in the
"sogod" domain, which means you must not specify the sogod domain in
the configuration file (there shouldn't be a "sogod = {" in
/etc/sogo/sogo.conf)."
Within a non-Debian sogo.conf there's this hint:
* ~sogo/GNUstep/Defaults/.GNUstepDefaults has precedence over this
file, *
* make sure to move it away to avoid unwanted parameter
overrides. *
--> Maybe you still have a mixture of old Debian and non-Debian and/or
2.x vs. 5.x configuration files somewhere? Could you have a look at
/var/lib/sogo/GNUstep/Defaults/ if there are files which could provide
SOGo defaults even if you delete /etc/sogo/sogo.conf. Or somewhere
else, perhaps grepping for some relevant content shows a hit?
And just to be sure: in /etc/passwd is there an entry for the sogo
user like this one?:
sogo:x:999:999:SOGo daemon:/var/lib/sogo:/usr/sbin/nologin
The home directory would be the interesting part.
Regards,
Markus
Re: [SOGo] SOGo no longer talking to mysql
On Mon, Jul 24, 2023 at 3:51 PM Richard Rosner wrote: > It produces the exact same output. And yes, I completely emptied > /etc/sogo/: > > 2023-07-24 14:33:56.022 sogod[148688:148688] ERROR: *could not open > MySQL4 connection to database 'sogo': Access denied for user > 'sogo'@'localhost' (using password: YES)* > Jul 24 14:33:56 sogod [148688]: [ERROR] > <0x0x55d0b9b16cc0[GCSChannelManager]> could not open channel > for > mysql://localhost/sogo/sogo_user_profile > Jul 24 14:33:56 sogod [148688]: [WARN] > <0x0x55d0b9b16cc0[GCSChannelManager]> will prevent opening of this > channel 5 seconds after 2023-07-24 14:33:55 +0200 > Jul 24 14:33:56 sogod [148688]: <0x0x55d0b9d10410[WOHttpAdaptor]> notified > the watchdog that we are ready > 2023-07-24 14:33:56.024 sogod[148689:148689]* ERROR: could not open > MySQL4 connection to database 'sogo': Access denied for user > 'sogo'@'localhost' (using password: YES)* > Jul 24 14:33:56 sogod [148689]: [ERROR] > <0x0x55d0b9af8ce0[GCSChannelManager]> could not open channel > for > mysql://localhost/sogo/sogo_user_profile > Jul 24 14:33:56 sogod [148689]: [WARN] > <0x0x55d0b9af8ce0[GCSChannelManager]> will prevent opening of this > channel 5 seconds after 2023-07-24 14:33:55 +0200 > 2023-07-24 14:33:56.026 sogod[148687:148687] *ERROR: could not open > MySQL4 connection to database 'sogo': Access denied for user > 'sogo'@'localhost' (using password: YES)* > Jul 24 14:33:56 sogod [148687]: [ERROR] > <0x0x55d0b9b16cc0[GCSChannelManager]> could not open channel > for > mysql://localhost/sogo/sogo_user_profile > Jul 24 14:33:56 sogod [148687]: [WARN] > <0x0x55d0b9b16cc0[GCSChannelManager]> will prevent opening of this > channel 5 seconds after 2023-07-24 14:33:55 +0200 > Jul 24 14:33:56 sogod [148689]: <0x0x55d0b9d0e3b0[WOHttpAdaptor]> notified > the watchdog that we are ready > Jul 24 14:33:56 sogod [148687]: <0x0x55d0b9d14150[WOHttpAdaptor]> notified > the watchdog that we are ready > > The output if strace changes though, it's not containing any lines with > mysql anymore. > "could not open MySQL4 connection to database 'sogo': Access denied for user 'sogo'@'localhost' (using password: YES)" Those are lines with MySQL! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Re: [SOGo] SOGo no longer talking to mysql
Hi Richard,
On Mon, 24 Jul 2023 at 01:40:52PM +0200, Richard Rosner wrote:
My biggest problem with the old installation was (which was set up
before I became admin and I can't tell if it has been upgraded somehow
from SOGo 2.x, which we where using before 5.x, or if it was a fresh
install) that when I took over, the whole config was commented out and
everything was set to their default values. I have no idea how it even
worked in the first place, already because the default database is
postgresql, which isn't even installed on the system. And when I tried
to edit things like page title or availability of forwarding, they
simply didn't get applied. So I hoped with reinstalling I could solve
the issue. I even did an apt purge to remove everything from that old
installation (so only the mysql database survived), but obviously the
problem seems to be somewhere it did survive.
On Mon, 24 Jul 2023 at 03:27:49PM +0200, Richard Rosner wrote:
The old installation was SOGo (up until 5.8.0) on Debian 11 from the
official Nightly Repo. I now switched to Debians own packages after
upgrading to Debian 12, so it's still SOGo 5.8.0. But as the problem
was present during the whole 5.x cycle (at least since we switched
from 2.x, maybe in 2018 or so) and I switched to the Debian packages
just now, it must be a problem independent of the package source.
just another idea regarding this strange behaviour:
Within /usr/share/doc/sogo/README.Debian
"The SOGo debian package differs from upstream in placing the
configuration file in /etc/sogo/sogo.conf instead of using the GNUstep
user defaults that are placed under the home directory of the user
used to run SOGo. This file is parsed as GNUstep defaults in the
"sogod" domain, which means you must not specify the sogod domain in
the configuration file (there shouldn't be a "sogod = {" in
/etc/sogo/sogo.conf)."
Within a non-Debian sogo.conf there's this hint:
* ~sogo/GNUstep/Defaults/.GNUstepDefaults has precedence over this file, *
* make sure to move it away to avoid unwanted parameter overrides. *
--> Maybe you still have a mixture of old Debian and non-Debian and/or 2.x vs. 5.x configuration files somewhere? Could you have a look at
/var/lib/sogo/GNUstep/Defaults/ if there are files which could provide SOGo defaults even if you delete /etc/sogo/sogo.conf. Or somewhere else,
perhaps grepping for some relevant content shows a hit?
And just to be sure: in /etc/passwd is there an entry for the sogo user like
this one?:
sogo:x:999:999:SOGo daemon:/var/lib/sogo:/usr/sbin/nologin
The home directory would be the interesting part.
Regards,
Markus
Re: [SOGo] SOGo no longer talking to mysql
Hi Richard, On 21.07.23 13:27, Richard Rosner (rros...@fsmuw.rwth-aachen.de) wrote: 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. just to be sure: does the password contain characters like '&'? Is there anything else that can/must be done? Earlier you wrote: So of course I tried logging in manually to mysql, but this succedes without any complaints. How exactly did you do this test? Did you enter: (1) $ mysql -u sogo -ppassword -D sogo -h localhost or did you enter the password interactively: (2) $ mysql -u sogo -p -D sogo -h localhost If you did not use method (1): could you please try it and see if that works? Regards, Markus
Re: [SOGo] SOGo no longer talking to mysql
It doesn't change. Now the big question is: what is it that sogo is
loading? Because there's no other sogo.conf anywhere in the whole
system, except of the expected files like /etc/default/sogo.
Richard Rosner
Studierendenschaft der RWTH Aachen University
Fachschaft Materialwissenschaft und Werkstofftechnik
Intzestraße 1
52072 Aachen
Tel.: +49 241 80-95781
rros...@fsmuw.rwth-aachen.de
www.fsmuw.rwth-aachen.de <https://www.fsmuw.rwth-aachen.de>
Am 21.07.2023 um 15:22 schrieb qhivert (qhiv...@alinto.eu):
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
qhiv...@alinto.eu your sogo.conf file (censor your password) so I can
see if anything shocks me.
*From:*users-requ...@sogo.nu *On Behalf Of
*Richard Rosner
*Sent:* vendredi 21 juillet 2023 13:27
*To:* qhivert (qhiv...@alinto.eu)
*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 (qhiv...@alinto.eu):
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:*users-requ...@sogo.nu
<mailto:users-requ...@sogo.nu> *On Behalf Of *Richard Rosner
*Sent:* vendredi 21 juillet 2023 09:44
*To:* Kenren Taisho (toushin.tai...@gmail.com)
<mailto:users@sogo.nu>
*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
(toushin.tai...@gmail.com):
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
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 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 for
mysql://localhost/sogo/sogo_user_profile
Jul 20 17:41:16 sogod [79587]: [WARN]
<0x0x55ce03e5a8c0[
RE: [SOGo] SOGo no longer talking to mysql
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 qhiv...@alinto.eu <mailto:qhiv...@alinto.eu> your sogo.conf file (censor your password) so I can see if anything shocks me. From: users-requ...@sogo.nu On Behalf Of Richard Rosner Sent: vendredi 21 juillet 2023 13:27 To: qhivert (qhiv...@alinto.eu) 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 (qhiv...@alinto.eu <mailto:qhiv...@alinto.eu> ): 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: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> <mailto:users-requ...@sogo.nu> On Behalf Of Richard Rosner Sent: vendredi 21 juillet 2023 09:44 To: Kenren Taisho (toushin.tai...@gmail.com <mailto:toushin.tai...@gmail.com> ) <mailto:users@sogo.nu> 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 (toushin.tai...@gmail.com <mailto:toushin.tai...@gmail.com> ): 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 mailto:users@sogo.nu> > 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 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 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 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 (qhiv...@alinto.eu <mailto:qhiv...@alinto.eu> ): Hello Richard, Strang
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 (qhiv...@alinto.eu): 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:*users-requ...@sogo.nu *On Behalf Of *Richard Rosner *Sent:* vendredi 21 juillet 2023 09:44 *To:* Kenren Taisho (toushin.tai...@gmail.com) *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 (toushin.tai...@gmail.com): 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 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 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 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 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 (qhiv...@alinto.eu): Hello Richard, Strange indeed. I assume you didn’t change the sogo.conf nor the password between? Is this the log with t
RE: [SOGo] SOGo no longer talking to mysql
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: users-requ...@sogo.nu On Behalf Of Richard Rosner Sent: vendredi 21 juillet 2023 09:44 To: Kenren Taisho (toushin.tai...@gmail.com) 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 (toushin.tai...@gmail.com <mailto:toushin.tai...@gmail.com> ): 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 mailto:users@sogo.nu> > 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 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 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 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 (qhiv...@alinto.eu <mailto:qhiv...@alinto.eu> ): 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: users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> <mailto:users-requ...@sogo.nu> On Behalf Of Richard Rosner Sent: jeudi 20 juillet 2023 16:23 To: users@sogo.nu <mailto:users@sogo.nu> 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:password@127.0.0.1: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]: <0x0x55bd
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 (toushin.tai...@gmail.com): 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 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 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 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 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 (qhiv...@alinto.eu): 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:*users-requ...@sogo.nu <mailto:users-requ...@sogo.nu> *On Behalf Of *Richard Rosner *Sent:* jeudi 20 juillet 2023 16:23 *To:* users@sogo.nu *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:/password/@127.0.0.1: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
Re: [SOGo] SOGo no longer talking to mysql
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 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 > 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 > 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 > 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 (qhiv...@alinto.eu): > > 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:* users-requ...@sogo.nu > *On Behalf Of *Richard Rosner > *Sent:* jeudi 20 juillet 2023 16:23 > *To:* users@sogo.nu > *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:*password*@127.0.0.1:3306/sogo/sogo_user_profile"; << and I > have verified that mariadb is actually listening to 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'@'lo
Re: [SOGo] SOGo no longer talking to mysql
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 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 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 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 (qhiv...@alinto.eu): 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:*users-requ...@sogo.nu *On Behalf Of *Richard Rosner *Sent:* jeudi 20 juillet 2023 16:23 *To:* users@sogo.nu *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:/password/@127.0.0.1:3306/sogo/sogo_user_profile"; << and I have verified that mariadb is actually listening to 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 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 den
RE: [SOGo] SOGo no longer talking to mysql
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: users-requ...@sogo.nu On Behalf Of Richard Rosner Sent: jeudi 20 juillet 2023 16:23 To: users@sogo.nu 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:password@127.0.0.1:3306/sogo/sogo_user_profile"; << and I have verified that mariadb is actually listening to 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 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 for mysql://localhost/sogo/sogo_user_profile Jul 20 15:53:10 sogod [73524]: [ERROR] <0x0x55bdab373020[GCSChannelManager]> could not open channel 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.
[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:/password/@127.0.0.1:3306/sogo/sogo_user_profile"; << and I have verified that mariadb is actually listening to 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 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 for mysql://localhost/sogo/sogo_user_profile Jul 20 15:53:10 sogod [73524]: [ERROR] <0x0x55bdab373020[GCSChannelManager]> could not open channel 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. smime.p7s Description: S/MIME Cryptographic Signature
