On 05/31/2010 10:37 AM, Dominique Dominique wrote:
My two cents. I have the same problem with a MySQL install. I'm still trying to configure the MySQL connection correctly, but the error message in Firefox is the same "the called object returned no result". Althoug this can be a database connection problem it is definitively not Postgre specific. Postgre is not installed on my system. Look forward to finding a solution though. Dom.> Date: Mon, 31 May 2010 19:22:51 +0200 > From: rpesc...@peschke-it.de > To: users@sogo.nu > Subject: Re: [SOGo] SOGo installation on Ubuntu Lucid > > > Wolfgang Sourdeau schrieb: > > rpesc...@peschke-it.de wrote: > >> Hi, > >> thank you, Roberto for your hints. I experimented with them, but nothing > >> changed. > >> On the psql-commandline there is no problem with the given credentials > >> to log in, create some tables and access them in the database named sogo. > >> I think I'll try to use another daily build, but ... > >> > >> Ralf > > > > Hi Ralf, > > > > > > You probably also need to enable identification via tcp in your > > postgres, which is disabled by default on new installations... > > > > Here is what I have in my own pg_hba.conf: > > > > host all all 127.0.0.1/32 md5 > > > This line is also in my pg_hba.conf. > > Are you shure that it is a postgre-problem? > Maybe SOGo reports the error because the database is still empty? > The next error in the log is this: > > May 27 17:59:21 sogod: SOGo watchdog [3920]: [ERROR] [object-handler] > > did not find dispatcher class ''SoObjectMethodDispatcher'; fallback' > > 127.0.0.1 - - [27/May/2010:17:59:21 GMT] "GET /SOGo HTTP/1.1" 500 36/0 > > 0.018 - - 312K > > May 27 17:59:23 sogod: SOGo watchdog [3920]: [ERROR] [object-handler] > > did not find dispatcher class ''SoObjectMethodDispatcher'; fallback' > > 127.0.0.1 - - [27/May/2010:17:59:23 GMT] "GET /SOGo HTTP/1.1" 500 36/0 > > 0.006 - - 0 > > > > When do SOGo try to install the database? > > Thanks > Ralf
I just hit this problem, upgrading Ubuntu to 10.04. In the postgres logs, I was seeing this:
2010-06-17 10:28:29 MST FATAL: database "sogo/sogo_user_profile" does not exist
And at the same time, the sogo log shows:2010-06-17 10:28:29.969 sogod[1377] could not open channel to sogo/sogo_user_prof...@localhost Jun 17 10:28:29 sogod: SOGo watchdog [1377]: [ERROR] <0x0x1f7a4e0[GCSChannelManager]> could not open channel <0x0x2168900[PostgreSQL72Channel]: not-connected> for URL: postgresql://sogo:opensesam...@localhost:5432/sogo/sogo_user_profile Jun 17 10:28:29 sogod: SOGo watchdog [1377]: [WARN] <0x0x1f7a4e0[GCSChannelManager]> will prevent opening of this channel 5 seconds after 2010-06-17 10:28:29 -0700
Ouch. Isn't SOGo supposed to create the "sogo_user_profile" stuff?
<<attachment: jason_oster.vcf>>
-- users@sogo.nu https://inverse.ca/sogo/lists
