Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was having trouble resetting the root password in 4.1.9, so I upgraded to 5.0.22, since I recalled there being an explicit step in which the root password was set. However, when I got to that step, the command didn't work. That is: I started the server, and checked that it was running, and then here's what happened:
# mysqladmin -u root password 'blahblah'
mysqladmin: connect to server at 'puma' failed
error: 'Can't connect to MySQL server on 'puma' (4)'
Check that mysqld is running on puma and that the port is 3306.
You can check this by doing 'telnet puma 3306'
I did check that the server was running (using "ps"), and according to "nmap", it's running on port 3306, but the telnet command hangs and eventually (several minutes) times out.
Any ideas why I can't connect to the server? I was able to connect to the server in 4.1.9 (I just couldn't reset the password), so it seems like it's related to the upgrade. I haven't changed the firewall or anything else.
When I tried "telnet localhost 3306" as well as "telnet puma 3306" and the first worked while the second failed, I realized that the problem was with DNS. It turned out there was a mistaken IP address for Puma in /etc/hosts. So, the connection problem is solved. I now need to solve the password problem. :-)