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 [email protected]: >>>>>> 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 <MySQL4Channel[0x0x7f45298f63e0] >>>>>> 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 >>>>>>>> <MySQL4Channel[0x0x7f3a2ce4e490] connection=0x(null)> 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 >>>>>>> -- >>>>>>> [email protected] >>>>>>> https://inverse.ca/sogo/lists >>>>>>> >
signature.asc
Description: OpenPGP digital signature
