On 15 Jun 2001, at 15:02, Emiliano wrote:
> Richard Merryweather wrote:
>
> > I have midgard 1.4.1 set up with apache 1.3.20 under debian 2.2.17
> > Hitting http://richdev:9000/ or http://richdev:9000/admin gives me (httpd
> > error logs, loglevel debug)
> > [Thu Jun 14 14:54:14 2001] [debug] mod_midgard.c(1195): [client
> > 172.27.252.111] midgard_translate_handler(latin1,
> > http://richdev:9000/admin/)
> > [Thu Jun 14 14:54:14 2001] [warn] [client 172.27.252.111] Midgard: failed to
> > open midgard for midgard
>
> Try a recent CVS, which will be more verbose about the actual failure
> reason. David and I had a problem with Debian a while ago where
> midgard would, through libmysqlclient, attempt to open the wrong
> socket file.
I reinstalled (checking installs with a toothcomb :( ). The only thing
changed was source compile of mysql (previous was a binary). It
works now so I'm guessing that was indeed the problem as the
new mysql.sock is living in /tmp as opposed to /var/run/mysqld/
Cheers,
Richard
>
> > Which is a bit wierd. I can connect to the created midgard database fine
> > with the midgard user/pass as specified when loading the midgard data
> > from mysql/php and connecting directly to /var/run/mysqld/mysqld.sock
> > --with-db-user=midgard --with-db-user-password=fishf00d
> > (mysql user/pass from midgard configure)
>
> Also done as the user that apache runs as?
>
> Emile
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
