maria-discuss team mailing list archive

[Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx>]

On 6/30/2014 3:48 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> solve problems at the root-cause

Absolutely agree...

> if a update of 3rd party software introduces problems it is very
> clear where the root-cause is

Not necessarily.

Have you never heard of a case where updating one software reveals a bug 
in some other related software that was not apparent before?

Happens all the time.

Of course, it is very likely that you are correct, but...

> - roll back that update or if that is not possible for whatever
> reason escalate the problem at the 3rd party which introduced it

> what other help do you expect

An answer to my very simple and specific GENERAL question that will help 
me to better troubleshoot this to ascertain precisely where the problem is.

> if nobody else has a similar problem and there is for days no
> repsonse it becomes even more clear that you seek at the wrong end of
> the chain

The questions I asked and re-asked for a response to were GENERAL 
questions, ie:

1. What should this (error message) be saying? Something like:

"... ERROR: could not open MySQL5 connection to database..." ?

In other words, should the mysql4 be mysql5 in the error message?

No amount of googling has answered this, and no amount of googling has 
revealed if there is even a 'mysql4' vs 'mysql5' 'connection protocol', 
or if this error message is purely created by the reporting (3rd party) 
software.

Then my other question about maybe getting a little more debug logging 
without going into full debug logging mode. I have little experience 
troubleshooting these kinds of problems, which is why I am asking (I 
thought that would be obvious).