Re: [SOGo] Sogo and MySQL problem
I first had issues with postgresql as well but realized it was caused by the different user authentication. Fortunately there were entries in the postgresql log and the root cause was that postgresql may / can use "ident" as authentication. For sogo it looks like the DB access is done by user "apache" from the WEB interface. In this case the configuration of /var/lib/pgsql/data/pg_hba.conf is crucial. For me it works if the first entry (line) are: hostsogosogo127.0.0.1/32md5 local sogosogomd5 If I get it right the authentication depends on the order of the lines inside the file. And if the default entry (pgl 9.2.10 / CentOS 7_1503) hostall all 127.0.0.1/32ident comes first SOGo from teh WEB UI will fail since system user "apache" is by default not authorized to access the SOGo database. In this respect PostgreSQL is a bit more tricky then mysql... The SOGo log messages look very similar to the mysql problem since it's DB access problem as well. Mfg UlI Maurus On 09/04/15 03:06 AM, Jeroen Beerstra wrote: > Not sure, I also tried switching from mariadb to postgresql. Same errors :( > > From the looks of it this is what happens: > - sogo tries to connect to the db without the sogo user/pwd and ofcourse > this doesn't work > - sogo suspends the db connection for 5 seconds > - result = access denied or object not found > > mvg, > > Jeroen Beerstra > > Op 09-04-15 om 02:27 schreef Ulrich Maurus: >> I run into the same problem last week when upgrading from CentOS 7 to >> CentOS 7.1, which I found a bit "stealthy", since the repo links stay >> the same. But a lot of base as well as epel packages are having a major >> upgrades. I am using IPA for authentication with SOGO / Dovecot and that >> went from 3.2 to 4.1, fortunately without a major glitch (up to now :-). >> >> But the SOGO / SOPE49 interface to mariadb / mysql seems to have at >> least intermittent connection problems after the upgrade. It tried to >> backout - go to the older version - for gnustep-base/-make/-filesystem >> from the jaille-sogo repository without luck. >> >> My final solution was to switch the DB from mysql/mariadb to postgreql. >> The combination sogo / sope49 / gnustep from the pre-packaged jaile-sogo >> repo, CentOS & postresql (9.2.10) from the most recent update repo works >> stable since last week. >> >> I found a hint on google that the mysql"4" calls / interface are no >> longer fully supported with MySQL / mariadb 5. At least the problem on >> my server were intermittent so I could access one account via the WEB >> interface after each sogo restart and export teh calendar / contacts >> into text files. As soon as I tried to switch the user account or access >> via the Thunderbird connector things went south... For larger databases >> (I have 14 accounts) a mysql export -> postgresql import might be >> feasible. (A short test using phpmysqadmin / phppgadmin did not work...) >> >> Fortunately I use the DB only for the SOGO calendar / contact >> information. The user authentication as well as mail accounts are >> administrated by (Free)IPA bundled with CentOS which provides a LDAP >> (via ldapsearch) as well as pam.d (via sssd) interface. >> >> Kind regards >> >> Uli Maurus >> >> >> On 08/04/15 04:43 PM, Jeroen Beerstra wrote: >>> Yes CentOS 7.1, I used to just use newer gnustep-make and gnustep-base >>> from either fedora or epel, but guess this doens't work anymore. >>> >>> Bad news is I can't get the sogu.nu provided srpms counterparts to >>> compile, guess they are just too old for 7 :( >>> >>> mvg, >>> >>> Jeroen Beerstra >>> >>> Op 09-04-15 om 00:19 schreef Schifano Alexandre: On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! > Same issue here. Are you still running your sogo install on centos 7 by any chance ? > On my side the only significant change I did is to yum update, which upgraded my box to the recently released centos 7.1, which among other things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too before restarting your server ... > I tried to rebuild everything in case there is some binary compatibility issue, but to no avail. > Gilles > Hi, I used CentOS 7. After my server reboot I did a yum update and I'm now with a CentOS 7.1. I tried the new binaries available in the SOGo repository, with the same result. On 08/04/2015 22:26, Steve Ankeny wrote: > (1) What version of MariaDB are you using? > > (2) Are you using anything else such as Samba 4 LDAP with MariaDB? > > (3) What are you using for SOGoUserSources? > > I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. > > I rebooted over the weekend for a kernel upgrade, and I've had no > problems. > > My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially
Re: [SOGo] Sogo and MySQL problem
What about MariaDB 10.0? I don't see a "libs" package. On 04/09/2015 11:54 AM, Gilles Gagniard wrote: Hello, I think this is actually linked to the recent mariadb upgrade, not because of mariadb-server, but because of mariadb-libs ie the client side. Here is where it fails (there is a "could not allocate MySQL4 connection" error in the logs) : https://github.com/inverse-inc/sope/blob/6452ca58fbd7ee4850ae06bd7228a4feeb21441b/sope-gdl1/MySQL/MySQL4Channel.m#L143 mysql_init() is just doing some client-side initialization (such as setting up threads on so on), which fails. No actual connection attempt has been done yet ! This is done at a later stage by mysql_real_connect(). So here is the list of workarounds that can be ruled out : - This is not related to credentials or privileges or actual database content (we have not even tried to connect to the mysql server at this stage) - Changing the server to older/newer mariadb or even mysql cannot help with this issue (same reason than above) The only thing that could actually be tried is to downgrade mariadb-libs to 5.5.35 which is the client sogo uses. Gilles Le Jeudi 9 Avril 2015 16:28 CEST, Alessandro Briosi a écrit: Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: The only thing I haven't tried is mysql, postgresql and mariadb both have the same problem. So I don't think it's related to changes in recent mariadb Just a wild guess here (or a long shot if you prefere :P ). Could it be that the name resolution is not pointing to the correct host, or that the daemons for some reason are listening only on localhost (127.0.0.1) so the connection fails? Have you tried with the host IP? Ciao. Alessandro -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
As said, same problem when I use the local Lan hostname. The host file hasn't changed. My guess is a software version problem somewhere since multiple users report having updated to centos 7.1, as have I Op 9 apr. 2015 18:59 schreef Steve Ankeny : > > actually, I'd agree . . . > > You use 'localhost' What about using 127.0.0.1? And, since it worked > once, has hosts file changed? > > On 04/09/2015 10:28 AM, Alessandro Briosi wrote: > > > > Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: > >> The only thing I haven't tried is mysql, postgresql and mariadb both have > >> the same problem. So I don't think it's related to changes in recent > >> mariadb > > Just a wild guess here (or a long shot if you prefere :P ). > > Could it be that the name resolution is not pointing to the correct > > host, or that the daemons for some reason are listening only on > > localhost (127.0.0.1) so the connection fails? > > Have you tried with the host IP? > > > > Ciao. > > Alessandro > > > > > > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
Hello, I think this is actually linked to the recent mariadb upgrade, not because of mariadb-server, but because of mariadb-libs ie the client side. Here is where it fails (there is a "could not allocate MySQL4 connection" error in the logs) : https://github.com/inverse-inc/sope/blob/6452ca58fbd7ee4850ae06bd7228a4feeb21441b/sope-gdl1/MySQL/MySQL4Channel.m#L143 mysql_init() is just doing some client-side initialization (such as setting up threads on so on), which fails. No actual connection attempt has been done yet ! This is done at a later stage by mysql_real_connect(). So here is the list of workarounds that can be ruled out : - This is not related to credentials or privileges or actual database content (we have not even tried to connect to the mysql server at this stage) - Changing the server to older/newer mariadb or even mysql cannot help with this issue (same reason than above) The only thing that could actually be tried is to downgrade mariadb-libs to 5.5.35 which is the client sogo uses. Gilles Le Jeudi 9 Avril 2015 16:28 CEST, Alessandro Briosi a écrit: > > > Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: > > The only thing I haven't tried is mysql, postgresql and mariadb both have > > the same problem. So I don't think it's related to changes in recent mariadb > > Just a wild guess here (or a long shot if you prefere :P ). > Could it be that the name resolution is not pointing to the correct > host, or that the daemons for some reason are listening only on > localhost (127.0.0.1) so the connection fails? > Have you tried with the host IP? > > Ciao. > Alessandro > > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
actually, I'd agree . . . You use 'localhost' What about using 127.0.0.1? And, since it worked once, has hosts file changed? On 04/09/2015 10:28 AM, Alessandro Briosi wrote: Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: The only thing I haven't tried is mysql, postgresql and mariadb both have the same problem. So I don't think it's related to changes in recent mariadb Just a wild guess here (or a long shot if you prefere :P ). Could it be that the name resolution is not pointing to the correct host, or that the daemons for some reason are listening only on localhost (127.0.0.1) so the connection fails? Have you tried with the host IP? Ciao. Alessandro -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
Yes I did, also with the local network name, same problem. Also verified ipv6 is disabled. It seems the first connection succeeds (selecting jeroen from the user table) but the second connection (without user or pwd) fails and triggers a db connection suspend so everything else (with user / pwd) also fails. The result is either user / pwd combo is wrong or object not found, it varies. mvg, Jeroen Beerstra Op 09-04-15 om 16:28 schreef Alessandro Briosi: > > > Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: >> The only thing I haven't tried is mysql, postgresql and mariadb both have >> the same problem. So I don't think it's related to changes in recent mariadb > > Just a wild guess here (or a long shot if you prefere :P ). > Could it be that the name resolution is not pointing to the correct > host, or that the daemons for some reason are listening only on > localhost (127.0.0.1) so the connection fails? > Have you tried with the host IP? > > Ciao. > Alessandro > > > signature.asc Description: OpenPGP digital signature
Re: [SOGo] Sogo and MySQL problem
Il 09/04/2015 15:03, Jeroen Beerstra ha scritto: > The only thing I haven't tried is mysql, postgresql and mariadb both have the > same problem. So I don't think it's related to changes in recent mariadb Just a wild guess here (or a long shot if you prefere :P ). Could it be that the name resolution is not pointing to the correct host, or that the daemons for some reason are listening only on localhost (127.0.0.1) so the connection fails? Have you tried with the host IP? Ciao. Alessandro -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
The only thing I haven't tried is mysql, postgresql and mariadb both have the same problem. So I don't think it's related to changes in recent mariadb Op 9 apr. 2015 14:32 schreef Steve Ankeny : > > (1) try MariaDB 10.x > > (2) move back to MySQL > > (3) try PostgreSQL > > > On 04/09/2015 07:30 AM, schif...@polytech.unice.fr wrote: > > I made this new user with no more results. The only changes are the url in > > my logs, like : > > [ERROR] <0x0x7f2dcac33220[GCSChannelManager]> could not open channel > > for > > mysql://host.org/sogo/sogo_sessions_folder > > > > So as you can see, the problem is still the same : for joining the > > sessions_folder table, SOGo seems to not use the login/password and the > > port. > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
(1) try MariaDB 10.x (2) move back to MySQL (3) try PostgreSQL On 04/09/2015 07:30 AM, schif...@polytech.unice.fr wrote: I made this new user with no more results. The only changes are the url in my logs, like : [ERROR] <0x0x7f2dcac33220[GCSChannelManager]> could not open channel for mysql://host.org/sogo/sogo_sessions_folder So as you can see, the problem is still the same : for joining the sessions_folder table, SOGo seems to not use the login/password and the port. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
I made this new user with no more results. The only changes are the url in my logs, like : [ERROR] <0x0x7f2dcac33220[GCSChannelManager]> could not open channel for mysql://host.org/sogo/sogo_sessions_folder So as you can see, the problem is still the same : for joining the sessions_folder table, SOGo seems to not use the login/password and the port. > . . . answer below . . . > > On 04/08/2015 06:19 PM, Schifano Alexandre wrote: >> On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! >>> Same issue here. Are you still running your sogo install on centos 7 >> by any chance ? >>> On my side the only significant change I did is to yum update, which >> upgraded my box to the recently released centos 7.1, which among other >> things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too >> before restarting your server ... >>> I tried to rebuild everything in case there is some binary >> compatibility issue, but to no avail. >>> Gilles >>> >> Hi, >> >> I used CentOS 7. After my server reboot I did a yum update and I'm now >> with a CentOS 7.1. >> I tried the new binaries available in the SOGo repository, with the same >> result. >> >> On 08/04/2015 22:26, Steve Ankeny wrote: >>> (1) What version of MariaDB are you using? >>> >>> (2) Are you using anything else such as Samba 4 LDAP with MariaDB? >>> >>> (3) What are you using for SOGoUserSources? >>> >>> I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. >>> >>> I rebooted over the weekend for a kernel upgrade, and I've had no >>> problems. >>> >>> My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as >>> yours. >>> >>> I had an issue creating the OpenChange MySQL user as >>> 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did >>> not like the single quotes. Once I removed those, everything worked >>> fine. >>> >>> I had thought that was the case with the SOGo MySQL user, but it was >>> created without single quotes. >>> >>> I wonder if it has to do with the MariaDB version? >>> >> Hi, >> >> I have MariaDB 5.5.41, with no LDAP and no Samba. My user >> authentification is done throught the SQL backend. > > IF it's not too difficult, you might try deleting the 'sogo' user and > recreating it. > > MariaDB prefers creating the user without @localhost but using @% > instead. Look at documentation. > > How it looks in MySQL > > > > > > > > Somehow or other, I ended up with sogo and 'openchange-user' (but it > works fine) > > I'm just trying to think of things you can consider. Maybe someone will > know more about MariaDB > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
Not sure, I also tried switching from mariadb to postgresql. Same errors :( From the looks of it this is what happens: - sogo tries to connect to the db without the sogo user/pwd and ofcourse this doesn't work - sogo suspends the db connection for 5 seconds - result = access denied or object not found mvg, Jeroen Beerstra Op 09-04-15 om 02:27 schreef Ulrich Maurus: > I run into the same problem last week when upgrading from CentOS 7 to > CentOS 7.1, which I found a bit "stealthy", since the repo links stay > the same. But a lot of base as well as epel packages are having a major > upgrades. I am using IPA for authentication with SOGO / Dovecot and that > went from 3.2 to 4.1, fortunately without a major glitch (up to now :-). > > But the SOGO / SOPE49 interface to mariadb / mysql seems to have at > least intermittent connection problems after the upgrade. It tried to > backout - go to the older version - for gnustep-base/-make/-filesystem > from the jaille-sogo repository without luck. > > My final solution was to switch the DB from mysql/mariadb to postgreql. > The combination sogo / sope49 / gnustep from the pre-packaged jaile-sogo > repo, CentOS & postresql (9.2.10) from the most recent update repo works > stable since last week. > > I found a hint on google that the mysql"4" calls / interface are no > longer fully supported with MySQL / mariadb 5. At least the problem on > my server were intermittent so I could access one account via the WEB > interface after each sogo restart and export teh calendar / contacts > into text files. As soon as I tried to switch the user account or access > via the Thunderbird connector things went south... For larger databases > (I have 14 accounts) a mysql export -> postgresql import might be > feasible. (A short test using phpmysqadmin / phppgadmin did not work...) > > Fortunately I use the DB only for the SOGO calendar / contact > information. The user authentication as well as mail accounts are > administrated by (Free)IPA bundled with CentOS which provides a LDAP > (via ldapsearch) as well as pam.d (via sssd) interface. > > Kind regards > > Uli Maurus > > > On 08/04/15 04:43 PM, Jeroen Beerstra wrote: >> Yes CentOS 7.1, I used to just use newer gnustep-make and gnustep-base >> from either fedora or epel, but guess this doens't work anymore. >> >> Bad news is I can't get the sogu.nu provided srpms counterparts to >> compile, guess they are just too old for 7 :( >> >> mvg, >> >> Jeroen Beerstra >> >> Op 09-04-15 om 00:19 schreef Schifano Alexandre: >>> On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! Same issue here. Are you still running your sogo install on centos 7 >>> by any chance ? On my side the only significant change I did is to yum update, which >>> upgraded my box to the recently released centos 7.1, which among other >>> things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too >>> before restarting your server ... I tried to rebuild everything in case there is some binary >>> compatibility issue, but to no avail. Gilles >>> Hi, >>> >>> I used CentOS 7. After my server reboot I did a yum update and I'm now >>> with a CentOS 7.1. >>> I tried the new binaries available in the SOGo repository, with the same >>> result. >>> >>> On 08/04/2015 22:26, Steve Ankeny wrote: (1) What version of MariaDB are you using? (2) Are you using anything else such as Samba 4 LDAP with MariaDB? (3) What are you using for SOGoUserSources? I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. I rebooted over the weekend for a kernel upgrade, and I've had no problems. My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as yours. I had an issue creating the OpenChange MySQL user as 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did not like the single quotes. Once I removed those, everything worked fine. I had thought that was the case with the SOGo MySQL user, but it was created without single quotes. I wonder if it has to do with the MariaDB version? >>> Hi, >>> >>> I have MariaDB 5.5.41, with no LDAP and no Samba. My user >>> authentification is done throught the SQL backend. >>> On 04/08/2015 03:55 PM, Jeroen Beerstra wrote: > Exact same problem here, SOGo used to work just fine and now it doesn't. > Tried everything I could think of, including altering db host user pwd > and even recompiling since I´d seen some OS updates. > > also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, > while this is defined and used to work as > mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder > > This is driving me nuts :( Something is clearly broken, if only the log > would provide some more clou... > > mvg, > > Jeroen Beerstra > > Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: >
Re: [SOGo] Sogo and MySQL problem
. . . answer below . . . On 04/08/2015 06:19 PM, Schifano Alexandre wrote: On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! Same issue here. Are you still running your sogo install on centos 7 by any chance ? On my side the only significant change I did is to yum update, which upgraded my box to the recently released centos 7.1, which among other things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too before restarting your server ... I tried to rebuild everything in case there is some binary compatibility issue, but to no avail. Gilles Hi, I used CentOS 7. After my server reboot I did a yum update and I'm now with a CentOS 7.1. I tried the new binaries available in the SOGo repository, with the same result. On 08/04/2015 22:26, Steve Ankeny wrote: (1) What version of MariaDB are you using? (2) Are you using anything else such as Samba 4 LDAP with MariaDB? (3) What are you using for SOGoUserSources? I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. I rebooted over the weekend for a kernel upgrade, and I've had no problems. My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as yours. I had an issue creating the OpenChange MySQL user as 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did not like the single quotes. Once I removed those, everything worked fine. I had thought that was the case with the SOGo MySQL user, but it was created without single quotes. I wonder if it has to do with the MariaDB version? Hi, I have MariaDB 5.5.41, with no LDAP and no Samba. My user authentification is done throught the SQL backend. IF it's not too difficult, you might try deleting the 'sogo' user and recreating it. MariaDB prefers creating the user without @localhost but using @% instead. Look at documentation. How it looks in MySQL Somehow or other, I ended up with sogo and 'openchange-user' (but it works fine) I'm just trying to think of things you can consider. Maybe someone will know more about MariaDB -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
I run into the same problem last week when upgrading from CentOS 7 to CentOS 7.1, which I found a bit "stealthy", since the repo links stay the same. But a lot of base as well as epel packages are having a major upgrades. I am using IPA for authentication with SOGO / Dovecot and that went from 3.2 to 4.1, fortunately without a major glitch (up to now :-). But the SOGO / SOPE49 interface to mariadb / mysql seems to have at least intermittent connection problems after the upgrade. It tried to backout - go to the older version - for gnustep-base/-make/-filesystem from the jaille-sogo repository without luck. My final solution was to switch the DB from mysql/mariadb to postgreql. The combination sogo / sope49 / gnustep from the pre-packaged jaile-sogo repo, CentOS & postresql (9.2.10) from the most recent update repo works stable since last week. I found a hint on google that the mysql"4" calls / interface are no longer fully supported with MySQL / mariadb 5. At least the problem on my server were intermittent so I could access one account via the WEB interface after each sogo restart and export teh calendar / contacts into text files. As soon as I tried to switch the user account or access via the Thunderbird connector things went south... For larger databases (I have 14 accounts) a mysql export -> postgresql import might be feasible. (A short test using phpmysqadmin / phppgadmin did not work...) Fortunately I use the DB only for the SOGO calendar / contact information. The user authentication as well as mail accounts are administrated by (Free)IPA bundled with CentOS which provides a LDAP (via ldapsearch) as well as pam.d (via sssd) interface. Kind regards Uli Maurus On 08/04/15 04:43 PM, Jeroen Beerstra wrote: > Yes CentOS 7.1, I used to just use newer gnustep-make and gnustep-base > from either fedora or epel, but guess this doens't work anymore. > > Bad news is I can't get the sogu.nu provided srpms counterparts to > compile, guess they are just too old for 7 :( > > mvg, > > Jeroen Beerstra > > Op 09-04-15 om 00:19 schreef Schifano Alexandre: >> On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! >>> Same issue here. Are you still running your sogo install on centos 7 >> by any chance ? >>> On my side the only significant change I did is to yum update, which >> upgraded my box to the recently released centos 7.1, which among other >> things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too >> before restarting your server ... >>> I tried to rebuild everything in case there is some binary >> compatibility issue, but to no avail. >>> Gilles >>> >> Hi, >> >> I used CentOS 7. After my server reboot I did a yum update and I'm now >> with a CentOS 7.1. >> I tried the new binaries available in the SOGo repository, with the same >> result. >> >> On 08/04/2015 22:26, Steve Ankeny wrote: >>> (1) What version of MariaDB are you using? >>> >>> (2) Are you using anything else such as Samba 4 LDAP with MariaDB? >>> >>> (3) What are you using for SOGoUserSources? >>> >>> I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. >>> >>> I rebooted over the weekend for a kernel upgrade, and I've had no problems. >>> >>> My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as >>> yours. >>> >>> I had an issue creating the OpenChange MySQL user as >>> 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did >>> not like the single quotes. Once I removed those, everything worked fine. >>> >>> I had thought that was the case with the SOGo MySQL user, but it was >>> created without single quotes. >>> >>> I wonder if it has to do with the MariaDB version? >>> >> Hi, >> >> I have MariaDB 5.5.41, with no LDAP and no Samba. My user >> authentification is done throught the SQL backend. >> >>> On 04/08/2015 03:55 PM, Jeroen Beerstra wrote: Exact same problem here, SOGo used to work just fine and now it doesn't. Tried everything I could think of, including altering db host user pwd and even recompiling since I´d seen some OS updates. also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, while this is defined and used to work as mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder This is driving me nuts :( Something is clearly broken, if only the log would provide some more clou... mvg, Jeroen Beerstra Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: > I tried this and it changed nothing. > > I read more carefully my logd and I saw this before the error previously > quoted : > Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from > '127.0.0.1' for user 'USER' - expire = -1 grace = -1 > 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate > MySQL4 connection! > Apr 08 15:12:52 sogod [992]: [ERROR] > <0x0x7f4529584700[GCSChannelManager]> > could not open channel connection=0x(null)> for
Re: [SOGo] Sogo and MySQL problem
Yes CentOS 7.1, I used to just use newer gnustep-make and gnustep-base from either fedora or epel, but guess this doens't work anymore. Bad news is I can't get the sogu.nu provided srpms counterparts to compile, guess they are just too old for 7 :( mvg, Jeroen Beerstra Op 09-04-15 om 00:19 schreef Schifano Alexandre: > On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! >> >> Same issue here. Are you still running your sogo install on centos 7 > by any chance ? >> >> On my side the only significant change I did is to yum update, which > upgraded my box to the recently released centos 7.1, which among other > things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too > before restarting your server ... >> >> I tried to rebuild everything in case there is some binary > compatibility issue, but to no avail. >> >> Gilles >> > > Hi, > > I used CentOS 7. After my server reboot I did a yum update and I'm now > with a CentOS 7.1. > I tried the new binaries available in the SOGo repository, with the same > result. > > On 08/04/2015 22:26, Steve Ankeny wrote: >> (1) What version of MariaDB are you using? >> >> (2) Are you using anything else such as Samba 4 LDAP with MariaDB? >> >> (3) What are you using for SOGoUserSources? >> >> I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. >> >> I rebooted over the weekend for a kernel upgrade, and I've had no problems. >> >> My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as >> yours. >> >> I had an issue creating the OpenChange MySQL user as >> 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did >> not like the single quotes. Once I removed those, everything worked fine. >> >> I had thought that was the case with the SOGo MySQL user, but it was >> created without single quotes. >> >> I wonder if it has to do with the MariaDB version? >> > > Hi, > > I have MariaDB 5.5.41, with no LDAP and no Samba. My user > authentification is done throught the SQL backend. > >> On 04/08/2015 03:55 PM, Jeroen Beerstra wrote: >>> Exact same problem here, SOGo used to work just fine and now it doesn't. >>> Tried everything I could think of, including altering db host user pwd >>> and even recompiling since I´d seen some OS updates. >>> >>> also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, >>> while this is defined and used to work as >>> mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder >>> >>> This is driving me nuts :( Something is clearly broken, if only the log >>> would provide some more clou... >>> >>> mvg, >>> >>> Jeroen Beerstra >>> >>> Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: I tried this and it changed nothing. I read more carefully my logd and I saw this before the error previously quoted : Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from '127.0.0.1' for user 'USER' - expire = -1 grace = -1 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate MySQL4 connection! Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> could not open channel >>> connection=0x(null)> for mysql://localhost/sogo/sogo_sessions_folder Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 +0200 I have my "OCSSessionsFolderURL" well defined with username, password, and DB port, but it looks like this is not well setted in the running SOGo. Is there a way to get the config of the running SOGo ? And how can I correct this problem ? Best regards > Hi, > > imho when you set IMAPLoginFieldName (see documentation for more > explanation) to your field which only returns the Given Name it would > work. > > best regards > > Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: >> Hi, >> >> I'm facing to a very weird problem about SOGo and MySQL. >> I had a SOGo server working correctly with no problem, but I had to >> reboot the server. After that I restarted Sogod, MariaDB, memcache, >> Apache, and the other services, but now sogo is unable to use >> MySQL/MariaDB. I have this kind of error in my logs messages : >> >> 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate >> MySQL4 connection! >> Apr 08 8:18:58 sogod [8174]: [ERROR] >> <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel >> for >> mysql://localhost/sogo/sogo_custom_users >> Apr 08 8:18:58 sogod [8174]: [WARN] >> <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this >> channel 5 seconds after 2015-04-08 8:18:58 +0200 >> Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> >> failed to acquire channel for URL: >> mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_u
Re: [SOGo] Sogo and MySQL problem
On 08/04/2015 22:45, Gilles Gagniard wrote:> Hello ! > > Same issue here. Are you still running your sogo install on centos 7 by any chance ? > > On my side the only significant change I did is to yum update, which upgraded my box to the recently released centos 7.1, which among other things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too before restarting your server ... > > I tried to rebuild everything in case there is some binary compatibility issue, but to no avail. > > Gilles > Hi, I used CentOS 7. After my server reboot I did a yum update and I'm now with a CentOS 7.1. I tried the new binaries available in the SOGo repository, with the same result. On 08/04/2015 22:26, Steve Ankeny wrote: > (1) What version of MariaDB are you using? > > (2) Are you using anything else such as Samba 4 LDAP with MariaDB? > > (3) What are you using for SOGoUserSources? > > I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. > > I rebooted over the weekend for a kernel upgrade, and I've had no problems. > > My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as > yours. > > I had an issue creating the OpenChange MySQL user as > 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did > not like the single quotes. Once I removed those, everything worked fine. > > I had thought that was the case with the SOGo MySQL user, but it was > created without single quotes. > > I wonder if it has to do with the MariaDB version? > Hi, I have MariaDB 5.5.41, with no LDAP and no Samba. My user authentification is done throught the SQL backend. > On 04/08/2015 03:55 PM, Jeroen Beerstra wrote: >> Exact same problem here, SOGo used to work just fine and now it doesn't. >> Tried everything I could think of, including altering db host user pwd >> and even recompiling since I´d seen some OS updates. >> >> also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, >> while this is defined and used to work as >> mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder >> >> This is driving me nuts :( Something is clearly broken, if only the log >> would provide some more clou... >> >> mvg, >> >> Jeroen Beerstra >> >> Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: >>> I tried this and it changed nothing. >>> >>> I read more carefully my logd and I saw this before the error previously >>> quoted : >>> Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from >>> '127.0.0.1' for user 'USER' - expire = -1 grace = -1 >>> 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate >>> MySQL4 connection! >>> Apr 08 15:12:52 sogod [992]: [ERROR] >>> <0x0x7f4529584700[GCSChannelManager]> >>> could not open channel >> connection=0x(null)> for mysql://localhost/sogo/sogo_sessions_folder >>> Apr 08 15:12:52 sogod [992]: [WARN] >>> <0x0x7f4529584700[GCSChannelManager]> >>> will prevent opening of this channel 5 seconds after 2015-04-08 >>> 17:12:52 >>> +0200 >>> >>> I have my "OCSSessionsFolderURL" well defined with username, >>> password, and >>> DB port, but it looks like this is not well setted in the running >>> SOGo. Is >>> there a way to get the config of the running SOGo ? And how can I >>> correct >>> this problem ? >>> >>> Best regards >>> Hi, imho when you set IMAPLoginFieldName (see documentation for more explanation) to your field which only returns the Given Name it would work. best regards Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: > Hi, > > I'm facing to a very weird problem about SOGo and MySQL. > I had a SOGo server working correctly with no problem, but I had to > reboot the server. After that I restarted Sogod, MariaDB, memcache, > Apache, and the other services, but now sogo is unable to use > MySQL/MariaDB. I have this kind of error in my logs messages : > > 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate > MySQL4 connection! > Apr 08 8:18:58 sogod [8174]: [ERROR] > <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel > for > mysql://localhost/sogo/sogo_custom_users > Apr 08 8:18:58 sogod [8174]: [WARN] > <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this > channel 5 seconds after 2015-04-08 8:18:58 +0200 > Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> > failed to acquire channel for URL: > mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users > > However : > * it worked well before the reboot, > * I am able to be connected to my db with "mysql -h localhost -u sogo > -p", > * when I do "telnet localhost 3306" I have a opened connection to > MariaDB (the connection is accepted and there is a kind of welcome > message) > * the port used by MariaDB is still the same, > * and I even configured iptable for having the 3306 port open to > everybody. >
Re: [SOGo] Sogo and MySQL problem
Hello ! Same issue here. Are you still running your sogo install on centos 7 by any chance ? On my side the only significant change I did is to yum update, which upgraded my box to the recently released centos 7.1, which among other things updates mariadb from 5.5.35 to 5.5.41. Maybe you did that too before restarting your server ... I tried to rebuild everything in case there is some binary compatibility issue, but to no avail. Gilles Le Mercredi 8 Avril 2015 15:35 CEST, schif...@polytech.unice.fr a écrit: > I tried this and it changed nothing. > > I read more carefully my logd and I saw this before the error previously > quoted : > Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from > '127.0.0.1' for user 'USER' - expire = -1 grace = -1 > 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate > MySQL4 connection! > Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> > could not open channel connection=0x(null)> for mysql://localhost/sogo/sogo_sessions_folder > Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> > will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 > +0200 > > I have my "OCSSessionsFolderURL" well defined with username, password, and > DB port, but it looks like this is not well setted in the running SOGo. Is > there a way to get the config of the running SOGo ? And how can I correct > this problem ? > > Best regards > > > Hi, > > > > imho when you set IMAPLoginFieldName (see documentation for more > > explanation) to your field which only returns the Given Name it would > > work. > > > > best regards > > > > Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: > >> Hi, > >> > >> I'm facing to a very weird problem about SOGo and MySQL. > >> I had a SOGo server working correctly with no problem, but I had to > >> reboot the server. After that I restarted Sogod, MariaDB, memcache, > >> Apache, and the other services, but now sogo is unable to use > >> MySQL/MariaDB. I have this kind of error in my logs messages : > >> > >> 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate > >> MySQL4 connection! > >> Apr 08 8:18:58 sogod [8174]: [ERROR] > >> <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel > >> for > >> mysql://localhost/sogo/sogo_custom_users > >> Apr 08 8:18:58 sogod [8174]: [WARN] > >> <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this > >> channel 5 seconds after 2015-04-08 8:18:58 +0200 > >> Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> > >> failed to acquire channel for URL: > >> mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users > >> > >> However : > >> * it worked well before the reboot, > >> * I am able to be connected to my db with "mysql -h localhost -u sogo > >> -p", > >> * when I do "telnet localhost 3306" I have a opened connection to > >> MariaDB (the connection is accepted and there is a kind of welcome > >> message) > >> * the port used by MariaDB is still the same, > >> * and I even configured iptable for having the 3306 port open to > >> everybody. > >> What did I forget ? > >> > >> Best regards > > > > > > -- > > users@sogo.nu > > https://inverse.ca/sogo/lists > > > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
(1) What version of MariaDB are you using? (2) Are you using anything else such as Samba 4 LDAP with MariaDB? (3) What are you using for SOGoUserSources? I am using LDAP AD/Samba4 with MariaDB 10.0.17, and it's working fine. I rebooted over the weekend for a kernel upgrade, and I've had no problems. My SOGoProfileURL, OCSSessionsFolderURL etc. is essentially the same as yours. I had an issue creating the OpenChange MySQL user as 'openchange-user'@'localhost' (as in the Outlook manual) as MariaDB did not like the single quotes. Once I removed those, everything worked fine. I had thought that was the case with the SOGo MySQL user, but it was created without single quotes. I wonder if it has to do with the MariaDB version? On 04/08/2015 03:55 PM, Jeroen Beerstra wrote: Exact same problem here, SOGo used to work just fine and now it doesn't. Tried everything I could think of, including altering db host user pwd and even recompiling since I´d seen some OS updates. also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, while this is defined and used to work as mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder This is driving me nuts :( Something is clearly broken, if only the log would provide some more clou... mvg, Jeroen Beerstra Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: I tried this and it changed nothing. I read more carefully my logd and I saw this before the error previously quoted : Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from '127.0.0.1' for user 'USER' - expire = -1 grace = -1 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate MySQL4 connection! Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> could not open channel for mysql://localhost/sogo/sogo_sessions_folder Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 +0200 I have my "OCSSessionsFolderURL" well defined with username, password, and DB port, but it looks like this is not well setted in the running SOGo. Is there a way to get the config of the running SOGo ? And how can I correct this problem ? Best regards Hi, imho when you set IMAPLoginFieldName (see documentation for more explanation) to your field which only returns the Given Name it would work. best regards Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: Hi, I'm facing to a very weird problem about SOGo and MySQL. I had a SOGo server working correctly with no problem, but I had to reboot the server. After that I restarted Sogod, MariaDB, memcache, Apache, and the other services, but now sogo is unable to use MySQL/MariaDB. I have this kind of error in my logs messages : 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate MySQL4 connection! Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel for mysql://localhost/sogo/sogo_custom_users Apr 08 8:18:58 sogod [8174]: [WARN] <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 8:18:58 +0200 Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> failed to acquire channel for URL: mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users However : * it worked well before the reboot, * I am able to be connected to my db with "mysql -h localhost -u sogo -p", * when I do "telnet localhost 3306" I have a opened connection to MariaDB (the connection is accepted and there is a kind of welcome message) * the port used by MariaDB is still the same, * and I even configured iptable for having the 3306 port open to everybody. What did I forget ? Best regards -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
hi all, i had this issue today on a cetnos 7 installation with rpms from redhat [jaile-sogo] name=Copr repo for sogo owned by jaile baseurl=https://copr-be.cloud.fedoraproject.org/results/jaile/sogo/epel-7-$basearch/ SOGO was throwing 1000s of msql errors -- I finally saw the segfault messages on the console. I decommissioned the server and replaced it with centos 6 -- works perfectly. I will not be using centos 7 again until rpms are available here Apr 8 13:31:44 alt kernel: sogod[6962]: segfault at 0 ip 7f1e2a40b053 sp 7fff86af5890 error 6 in libmysqlclient.so.18.0.0[7f1e2a3af000+28c000] Apr 8 13:31:44 alt kernel: sogod[6963]: segfault at 0 ip 7f1e2a40b053 sp 7fff86af5890 error 6 in libmysqlclient.so.18.0.0[7f1e2a3af000+28c000] Apr 8 13:31:44 alt kernel: sogod[6964]: segfault at 0 ip 7f1e2a40b053 sp 7fff86af5890 error 6 in libmysqlclient.so.18.0.0[7f1e2a3af000+28c000] Apr 8 13:31:44 alt kernel: sogod[6965]: segfault at 0 ip 7f1e2a40b053 sp 7fff86af5890 error 6 in libmysqlclient.so.18.0.0[7f1e2a3af000+28c000] ... Cheers M On 04/08/2015 09:55 PM, Jeroen Beerstra wrote: Exact same problem here, SOGo used to work just fine and now it doesn't. Tried everything I could think of, including altering db host user pwd and even recompiling since I´d seen some OS updates. also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, while this is defined and used to work as mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder This is driving me nuts :( Something is clearly broken, if only the log would provide some more clou... mvg, Jeroen Beerstra Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: I tried this and it changed nothing. I read more carefully my logd and I saw this before the error previously quoted : Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from '127.0.0.1' for user 'USER' - expire = -1 grace = -1 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate MySQL4 connection! Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> could not open channel for mysql://localhost/sogo/sogo_sessions_folder Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 +0200 I have my "OCSSessionsFolderURL" well defined with username, password, and DB port, but it looks like this is not well setted in the running SOGo. Is there a way to get the config of the running SOGo ? And how can I correct this problem ? Best regards Hi, imho when you set IMAPLoginFieldName (see documentation for more explanation) to your field which only returns the Given Name it would work. best regards Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: Hi, I'm facing to a very weird problem about SOGo and MySQL. I had a SOGo server working correctly with no problem, but I had to reboot the server. After that I restarted Sogod, MariaDB, memcache, Apache, and the other services, but now sogo is unable to use MySQL/MariaDB. I have this kind of error in my logs messages : 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate MySQL4 connection! Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel for mysql://localhost/sogo/sogo_custom_users Apr 08 8:18:58 sogod [8174]: [WARN] <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 8:18:58 +0200 Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> failed to acquire channel for URL: mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users However : * it worked well before the reboot, * I am able to be connected to my db with "mysql -h localhost -u sogo -p", * when I do "telnet localhost 3306" I have a opened connection to MariaDB (the connection is accepted and there is a kind of welcome message) * the port used by MariaDB is still the same, * and I even configured iptable for having the 3306 port open to everybody. What did I forget ? Best regards -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
Exact same problem here, SOGo used to work just fine and now it doesn't. Tried everything I could think of, including altering db host user pwd and even recompiling since I´d seen some OS updates. also see mysql://localhost/sogo/sogo_sessions_folder in the sogo log, while this is defined and used to work as mysql://sogo:sogo@localhost:3306/sogo/sogo_sessions_folder This is driving me nuts :( Something is clearly broken, if only the log would provide some more clou... mvg, Jeroen Beerstra Op 08-04-15 om 15:35 schreef schif...@polytech.unice.fr: > I tried this and it changed nothing. > > I read more carefully my logd and I saw this before the error previously > quoted : > Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from > '127.0.0.1' for user 'USER' - expire = -1 grace = -1 > 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate > MySQL4 connection! > Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> > could not open channel connection=0x(null)> for mysql://localhost/sogo/sogo_sessions_folder > Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> > will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 > +0200 > > I have my "OCSSessionsFolderURL" well defined with username, password, and > DB port, but it looks like this is not well setted in the running SOGo. Is > there a way to get the config of the running SOGo ? And how can I correct > this problem ? > > Best regards > >> Hi, >> >> imho when you set IMAPLoginFieldName (see documentation for more >> explanation) to your field which only returns the Given Name it would >> work. >> >> best regards >> >> Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: >>> Hi, >>> >>> I'm facing to a very weird problem about SOGo and MySQL. >>> I had a SOGo server working correctly with no problem, but I had to >>> reboot the server. After that I restarted Sogod, MariaDB, memcache, >>> Apache, and the other services, but now sogo is unable to use >>> MySQL/MariaDB. I have this kind of error in my logs messages : >>> >>> 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate >>> MySQL4 connection! >>> Apr 08 8:18:58 sogod [8174]: [ERROR] >>> <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel >>> for >>> mysql://localhost/sogo/sogo_custom_users >>> Apr 08 8:18:58 sogod [8174]: [WARN] >>> <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this >>> channel 5 seconds after 2015-04-08 8:18:58 +0200 >>> Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> >>> failed to acquire channel for URL: >>> mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users >>> >>> However : >>> * it worked well before the reboot, >>> * I am able to be connected to my db with "mysql -h localhost -u sogo >>> -p", >>> * when I do "telnet localhost 3306" I have a opened connection to >>> MariaDB (the connection is accepted and there is a kind of welcome >>> message) >>> * the port used by MariaDB is still the same, >>> * and I even configured iptable for having the 3306 port open to >>> everybody. >>> What did I forget ? >>> >>> Best regards >> >> >> -- >> users@sogo.nu >> https://inverse.ca/sogo/lists >> > > signature.asc Description: OpenPGP digital signature
Re: [SOGo] Sogo and MySQL problem
I tried this and it changed nothing. I read more carefully my logd and I saw this before the error previously quoted : Apr 08 17:12:52 sogod [992]: SOGoRootPage successful login from '127.0.0.1' for user 'USER' - expire = -1 grace = -1 2015-04-08 15:12:52.871 sogod[992] ERROR((null)): could not allocate MySQL4 connection! Apr 08 15:12:52 sogod [992]: [ERROR] <0x0x7f4529584700[GCSChannelManager]> could not open channel for mysql://localhost/sogo/sogo_sessions_folder Apr 08 15:12:52 sogod [992]: [WARN] <0x0x7f4529584700[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2015-04-08 17:12:52 +0200 I have my "OCSSessionsFolderURL" well defined with username, password, and DB port, but it looks like this is not well setted in the running SOGo. Is there a way to get the config of the running SOGo ? And how can I correct this problem ? Best regards > Hi, > > imho when you set IMAPLoginFieldName (see documentation for more > explanation) to your field which only returns the Given Name it would > work. > > best regards > > Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: >> Hi, >> >> I'm facing to a very weird problem about SOGo and MySQL. >> I had a SOGo server working correctly with no problem, but I had to >> reboot the server. After that I restarted Sogod, MariaDB, memcache, >> Apache, and the other services, but now sogo is unable to use >> MySQL/MariaDB. I have this kind of error in my logs messages : >> >> 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate >> MySQL4 connection! >> Apr 08 8:18:58 sogod [8174]: [ERROR] >> <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel >> for >> mysql://localhost/sogo/sogo_custom_users >> Apr 08 8:18:58 sogod [8174]: [WARN] >> <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this >> channel 5 seconds after 2015-04-08 8:18:58 +0200 >> Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> >> failed to acquire channel for URL: >> mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users >> >> However : >> * it worked well before the reboot, >> * I am able to be connected to my db with "mysql -h localhost -u sogo >> -p", >> * when I do "telnet localhost 3306" I have a opened connection to >> MariaDB (the connection is accepted and there is a kind of welcome >> message) >> * the port used by MariaDB is still the same, >> * and I even configured iptable for having the 3306 port open to >> everybody. >> What did I forget ? >> >> Best regards > > > -- > users@sogo.nu > https://inverse.ca/sogo/lists > -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo and MySQL problem
Hi, imho when you set IMAPLoginFieldName (see documentation for more explanation) to your field which only returns the Given Name it would work. best regards Am Mittwoch, den 08.04.2015, 08:35 +0200 schrieb Schifano Alexandre: > Hi, > > I'm facing to a very weird problem about SOGo and MySQL. > I had a SOGo server working correctly with no problem, but I had to > reboot the server. After that I restarted Sogod, MariaDB, memcache, > Apache, and the other services, but now sogo is unable to use > MySQL/MariaDB. I have this kind of error in my logs messages : > > 2015-04-08 8:18:58.708 sogod[8174] ERROR((null)): could not allocate > MySQL4 connection! > Apr 08 8:18:58 sogod [8174]: [ERROR] > <0x0x7f3a2c9564f0[GCSChannelManager]> could not open channel > for > mysql://localhost/sogo/sogo_custom_users > Apr 08 8:18:58 sogod [8174]: [WARN] > <0x0x7f3a2c9564f0[GCSChannelManager]> will prevent opening of this > channel 5 seconds after 2015-04-08 8:18:58 +0200 > Apr 08 8:18:58 sogod [8174]: [ERROR] <0x0x7f3a2c8fb050[SQLSource]> > failed to acquire channel for URL: > mysql://sogo:PASSWORD@localhost:3306/sogo/sogo_custom_users > > However : > * it worked well before the reboot, > * I am able to be connected to my db with "mysql -h localhost -u sogo -p", > * when I do "telnet localhost 3306" I have a opened connection to > MariaDB (the connection is accepted and there is a kind of welcome message) > * the port used by MariaDB is still the same, > * and I even configured iptable for having the 3306 port open to everybody. > What did I forget ? > > Best regards -- users@sogo.nu https://inverse.ca/sogo/lists
