Piotras wrote:
Vincent <[EMAIL PROTECTED]> wrote:


Hello,
Is everyone using midgard in Europe now, because it seems like the list hits a quiet 
spot
this time of day in EST (gmt -5) . Anyway, i just wanted to get on my old soapbox in
regard to repligard. Repligard is a cool tool with an awful flaw. It does not return
helpful error message on failure -even when you use the -d  switch.


Repligard will return error message when can not connect to MySQL database.
If You really want to make some error reporting better ,
You should look at mgd_log_debug_default function.

Piotras



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Actually the only error I was getting before the patch was this:


repligard -a -i AegirCMS.xml.gz

repligard-CRITICAL **: Error in DB connection

which is very vague error message  and difficult to troubleshoot without shooting off a
mail to this list.


_after_ the patch I got:


ERROR 2002: Can't connect to local MySQL server through socket 
'/var/lib/mysql/mysql.sock'
repligard-CRITICAL **: Error in DB connection

which took me 5 seconds to fix.*   My point being that a lot of people get stuck in
the midgard installation because not enough info is proided for developers to fix
the problem. Not every new Midgardian joins this mailing list.


* the quick fix was to specify the [mysqld] and [client] to use the same socket location in the my.cnf file. The problem was that repligard was looking for it for it in /tmp instead of /var/lib/mysql/

Vincent





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to