#2445 MySQL stuff does not work/is broken

All
closed
Jamie Cameron
9
2006-03-15
2006-03-13
kerplunk
No

There have been some other people with similiar
problems, but they have not replied to their bug
reports, so I have decided to make this.

Just like bug #1155246 ...

I am having the exact same problem. I'm using the
latest version of Webmin 1.260 and MySQL 4.1.18. I am
RACKING MY BRAIN trying to figure out what is wrong. I
have a hunch it has to do with MySQL itself. I never
had problems with MySQL 4.0 or older versions of MySQL
4.1, but ever since around 4.1.15 (I think), I have
been having the same problems.

The user/pass is fine and works. Things to help:

- CAN see the databases
- CAN see the tables
- CANNOT see tables after clicking a database
- CANNOT see User Permissions/Database Permissions/Host
Permissions/Table Permissions/Field Permissions/MySQL
Server Configuration

I have multiple servers running Webmin and this is the
case for all of them. PLEASE fix this.

Discussion

  • kerplunk
    kerplunk
    2006-03-13

    Examples of this bug

     
    Attachments
  • kerplunk
    kerplunk
    2006-03-13

    • priority: 5 --> 9
     
  • kerplunk
    kerplunk
    2006-03-13

    Logged In: YES
    user_id=1474694

    I have also added a screenshot of what it looks like...

     
  • Jamie Cameron
    Jamie Cameron
    2006-03-13

    Logged In: YES
    user_id=129364

    Does it help if you click on the Module Config link, and
    change the 'Use DBI to connect if available?' option to 'No' ?

     
  • kerplunk
    kerplunk
    2006-03-13

    Logged In: YES
    user_id=1474694

    IT WORKS! AMAZING!

    Thank you, thank you, thank you!

    BTW, I was using the latest version of DBD::mysql and DBI-perl.

     
  • Jamie Cameron
    Jamie Cameron
    2006-03-15

    • status: open --> closed
     
  • Jamie Cameron
    Jamie Cameron
    2006-03-15

    Logged In: YES
    user_id=129364

    If turning off DBI was the solution, that suggests that the
    bug is really in DBI.
    Make sure that if you have upgraded MySQL recently, you have
    also upgraded DBI .. if it was built against an older
    version of the MySQL libraries, problems like this can happen.