mysql:- can be accessed from shell but not from myphpadmin
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
MyPHP admin is configured correctly and can be
used to access other users databases using
respective login names. But one particular user
can not log in using his a/c. I have tried changing
the password for the user from the console using mysqladmin and a plesk also.(I forgot to tell you that
this had happened on a production server!) One more thing, that username can be used to log in and access the
databases using myphpadmin (dbwebadmin called in plesk) but not through the myphpadmin which is installed on separately on the server.(This myphpadmin is and was working properly for other users too.) No config play around have been done before it stopped working.
Secondly, try logging into the information_schema database as admin and
look for anything (ie access privileges) that is configured differently for the user
in question. However, from your explanation, it seems that the problem may not be caused by
the database (as MySql probably doesn't really care how you connect to it, just as long as you
give it the right database name and login credentials).
Thirdly, you may want to take a closer look at security measures (ie PAM rules) and environment settings for the myphpadmin (non-plesk).
Can you show us how you attempt to login to myphpadmin and dbwebadmin with a user that works and
with the user that doesn't?
Thanks for your support but I just could not wait to find where the problem is as I told you earlier it was a production server.
I just had to make it work immedietly and I did..
I don't like this approach but its ok when you are in nick of time.
I would argue that especially production servers need to have stable, reliable configurations, certainly
no "quick hacks".
Can't you copy the configuration to a test machine now so that you can do some extensive testing?
I agree with you that those production servers do not need to be paid
extra attention once installed and configured especially when these are LINUX But I have to also mention that tweaks are to be done
always with test boxes and then to be used as customization(As they are no tweaks anymore). Anyway I will do some tests with those configs.
I will let you know what and how did I try with those config files.