What's my MySQL root password
I just installed mysql-server with the following command
$ sudo apt install mysql-server mysql-client mysql-common
Then when I call the command mysql_secure_installation MySQL asks to enter the root password:
I haven't set a password for mysql-server and is asking me for it.
How can I set the proper password? Is there a default password?
linux passwords mysql
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
add a comment |
I just installed mysql-server with the following command
$ sudo apt install mysql-server mysql-client mysql-common
Then when I call the command mysql_secure_installation MySQL asks to enter the root password:
I haven't set a password for mysql-server and is asking me for it.
How can I set the proper password? Is there a default password?
linux passwords mysql
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
I had not setup anything
– Hector
Nov 22 '18 at 23:12
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16
add a comment |
I just installed mysql-server with the following command
$ sudo apt install mysql-server mysql-client mysql-common
Then when I call the command mysql_secure_installation MySQL asks to enter the root password:
I haven't set a password for mysql-server and is asking me for it.
How can I set the proper password? Is there a default password?
linux passwords mysql
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
I just installed mysql-server with the following command
$ sudo apt install mysql-server mysql-client mysql-common
Then when I call the command mysql_secure_installation MySQL asks to enter the root password:
I haven't set a password for mysql-server and is asking me for it.
How can I set the proper password? Is there a default password?
linux passwords mysql
linux passwords mysql
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
edited Nov 23 '18 at 1:19
JakeGould
31k1093137
31k1093137
asked Nov 22 '18 at 22:46
Hector
63
asked Nov 22 '18 at 22:46
Hector
63
asked Nov 22 '18 at 22:46
Hector
63
63
I had not setup anything
– Hector
Nov 22 '18 at 23:12
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16
add a comment |
I had not setup anything
– Hector
Nov 22 '18 at 23:12
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16
I had not setup anything
– Hector
Nov 22 '18 at 23:12
I had not setup anything
– Hector
Nov 22 '18 at 23:12
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16
add a comment |
2 Answers
2
active
oldest
votes
While the original poster claims to have found a solution to this issue in this answer, it made no sense to me. But now I understand some Debian/Ubuntu distros use a socket-based authentication method. This method of authentication being enabled by default would naturally require one use sudo to get into MySQL as they describe.
But in general, there is no reason to run mysql_secure_installation via sudo. That makes no sense in most cases since MySQL doesn’t need sudo for a client transaction like this… Unless socket-based authentication is at play. And mysql_secure_installation is just a Bash script that runs a pile of commands in a nice, convenient package to allow updating of some MySQL related security items. Just look at the source code to see what I mean.
So if you are on a system that doesn’t use socket-based authentication and you are facing a similar issue, the solution is either the password is blank for older versions of MySQL. So you would just run this to get into MySQL:
mysql -uroot -p
Or in the case of mysql_secure_installation, just hit Return or Enter when prompted for a password.
Or for modern versions of MySQL—I believe MySQL 5.7 or higher—you need to check the error log for a message like this:
“2016-05-16T07:09:49.796912Z 1 [Note] A temporary password is generated for root@localhost: 8)13ftQG5OYl”
This is an example taken from the Persona blog entry on this topic. As to where this MySQL log entry is, it could be in /var/log/mysqld.log on a CentOS/RedHat server or it shows up as output from the package install on Ubuntu/Debian systems.
But simply checking the error log for the text “temporary password” will provide you with the initial root password MySQL sets when it is first installed.
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
This is the message on the error,log file2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
– Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had tosudomy way in onmysql. I restart the server, I checked the mysql login and I don't need tosudomy way in to MySQL from the terminal to the server.
– Hector
Nov 23 '18 at 6:07
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressedreturnand nothing happended. I'll tried again in other server. For now, I can log. thanks.
– Hector
Nov 23 '18 at 20:15
|
show 1 more comment
I found the solution. It needs to be execute as superuser
I had to execute $ sudo mysql_secure_installation
Also if I want to log in the mysql on the terminal I must sudo it
answered Nov 22 '18 at 23:58
Hector
63
Check my answer. There is no reason you need to runmysqlcommands viasudo.
– JakeGould
Nov 23 '18 at 1:31
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default formysqlclient) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.
– ivanivan
Nov 23 '18 at 23:19
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377691%2fwhats-my-mysql-root-password%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
While the original poster claims to have found a solution to this issue in this answer, it made no sense to me. But now I understand some Debian/Ubuntu distros use a socket-based authentication method. This method of authentication being enabled by default would naturally require one use sudo to get into MySQL as they describe.
But in general, there is no reason to run mysql_secure_installation via sudo. That makes no sense in most cases since MySQL doesn’t need sudo for a client transaction like this… Unless socket-based authentication is at play. And mysql_secure_installation is just a Bash script that runs a pile of commands in a nice, convenient package to allow updating of some MySQL related security items. Just look at the source code to see what I mean.
So if you are on a system that doesn’t use socket-based authentication and you are facing a similar issue, the solution is either the password is blank for older versions of MySQL. So you would just run this to get into MySQL:
mysql -uroot -p
Or in the case of mysql_secure_installation, just hit Return or Enter when prompted for a password.
Or for modern versions of MySQL—I believe MySQL 5.7 or higher—you need to check the error log for a message like this:
“2016-05-16T07:09:49.796912Z 1 [Note] A temporary password is generated for root@localhost: 8)13ftQG5OYl”
This is an example taken from the Persona blog entry on this topic. As to where this MySQL log entry is, it could be in /var/log/mysqld.log on a CentOS/RedHat server or it shows up as output from the package install on Ubuntu/Debian systems.
But simply checking the error log for the text “temporary password” will provide you with the initial root password MySQL sets when it is first installed.
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
This is the message on the error,log file2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
– Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had tosudomy way in onmysql. I restart the server, I checked the mysql login and I don't need tosudomy way in to MySQL from the terminal to the server.
– Hector
Nov 23 '18 at 6:07
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressedreturnand nothing happended. I'll tried again in other server. For now, I can log. thanks.
– Hector
Nov 23 '18 at 20:15
|
show 1 more comment
While the original poster claims to have found a solution to this issue in this answer, it made no sense to me. But now I understand some Debian/Ubuntu distros use a socket-based authentication method. This method of authentication being enabled by default would naturally require one use sudo to get into MySQL as they describe.
But in general, there is no reason to run mysql_secure_installation via sudo. That makes no sense in most cases since MySQL doesn’t need sudo for a client transaction like this… Unless socket-based authentication is at play. And mysql_secure_installation is just a Bash script that runs a pile of commands in a nice, convenient package to allow updating of some MySQL related security items. Just look at the source code to see what I mean.
So if you are on a system that doesn’t use socket-based authentication and you are facing a similar issue, the solution is either the password is blank for older versions of MySQL. So you would just run this to get into MySQL:
mysql -uroot -p
Or in the case of mysql_secure_installation, just hit Return or Enter when prompted for a password.
Or for modern versions of MySQL—I believe MySQL 5.7 or higher—you need to check the error log for a message like this:
“2016-05-16T07:09:49.796912Z 1 [Note] A temporary password is generated for root@localhost: 8)13ftQG5OYl”
This is an example taken from the Persona blog entry on this topic. As to where this MySQL log entry is, it could be in /var/log/mysqld.log on a CentOS/RedHat server or it shows up as output from the package install on Ubuntu/Debian systems.
But simply checking the error log for the text “temporary password” will provide you with the initial root password MySQL sets when it is first installed.
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
This is the message on the error,log file2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
– Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had tosudomy way in onmysql. I restart the server, I checked the mysql login and I don't need tosudomy way in to MySQL from the terminal to the server.
– Hector
Nov 23 '18 at 6:07
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressedreturnand nothing happended. I'll tried again in other server. For now, I can log. thanks.
– Hector
Nov 23 '18 at 20:15
|
show 1 more comment
While the original poster claims to have found a solution to this issue in this answer, it made no sense to me. But now I understand some Debian/Ubuntu distros use a socket-based authentication method. This method of authentication being enabled by default would naturally require one use sudo to get into MySQL as they describe.
But in general, there is no reason to run mysql_secure_installation via sudo. That makes no sense in most cases since MySQL doesn’t need sudo for a client transaction like this… Unless socket-based authentication is at play. And mysql_secure_installation is just a Bash script that runs a pile of commands in a nice, convenient package to allow updating of some MySQL related security items. Just look at the source code to see what I mean.
So if you are on a system that doesn’t use socket-based authentication and you are facing a similar issue, the solution is either the password is blank for older versions of MySQL. So you would just run this to get into MySQL:
mysql -uroot -p
Or in the case of mysql_secure_installation, just hit Return or Enter when prompted for a password.
Or for modern versions of MySQL—I believe MySQL 5.7 or higher—you need to check the error log for a message like this:
“2016-05-16T07:09:49.796912Z 1 [Note] A temporary password is generated for root@localhost: 8)13ftQG5OYl”
This is an example taken from the Persona blog entry on this topic. As to where this MySQL log entry is, it could be in /var/log/mysqld.log on a CentOS/RedHat server or it shows up as output from the package install on Ubuntu/Debian systems.
But simply checking the error log for the text “temporary password” will provide you with the initial root password MySQL sets when it is first installed.
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
While the original poster claims to have found a solution to this issue in this answer, it made no sense to me. But now I understand some Debian/Ubuntu distros use a socket-based authentication method. This method of authentication being enabled by default would naturally require one use sudo to get into MySQL as they describe.
But in general, there is no reason to run mysql_secure_installation via sudo. That makes no sense in most cases since MySQL doesn’t need sudo for a client transaction like this… Unless socket-based authentication is at play. And mysql_secure_installation is just a Bash script that runs a pile of commands in a nice, convenient package to allow updating of some MySQL related security items. Just look at the source code to see what I mean.
So if you are on a system that doesn’t use socket-based authentication and you are facing a similar issue, the solution is either the password is blank for older versions of MySQL. So you would just run this to get into MySQL:
mysql -uroot -p
Or in the case of mysql_secure_installation, just hit Return or Enter when prompted for a password.
Or for modern versions of MySQL—I believe MySQL 5.7 or higher—you need to check the error log for a message like this:
“2016-05-16T07:09:49.796912Z 1 [Note] A temporary password is generated for root@localhost: 8)13ftQG5OYl”
This is an example taken from the Persona blog entry on this topic. As to where this MySQL log entry is, it could be in /var/log/mysqld.log on a CentOS/RedHat server or it shows up as output from the package install on Ubuntu/Debian systems.
But simply checking the error log for the text “temporary password” will provide you with the initial root password MySQL sets when it is first installed.
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
edited Nov 25 '18 at 2:34
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
answered Nov 23 '18 at 1:30
JakeGould
31k1093137
31k1093137
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
This is the message on the error,log file2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
– Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had tosudomy way in onmysql. I restart the server, I checked the mysql login and I don't need tosudomy way in to MySQL from the terminal to the server.
– Hector
Nov 23 '18 at 6:07
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressedreturnand nothing happended. I'll tried again in other server. For now, I can log. thanks.
– Hector
Nov 23 '18 at 20:15
|
show 1 more comment
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
This is the message on the error,log file2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
– Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had tosudomy way in onmysql. I restart the server, I checked the mysql login and I don't need tosudomy way in to MySQL from the terminal to the server.
– Hector
Nov 23 '18 at 6:07
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressedreturnand nothing happended. I'll tried again in other server. For now, I can log. thanks.
– Hector
Nov 23 '18 at 20:15
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
Which version of mysql you got?
– Hector
Nov 23 '18 at 2:37
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
@Hector What does the version of MySQL matter? Look at my edit to understand what I mean.
– JakeGould
Nov 23 '18 at 2:49
1
1
This is the message on the error,log file
2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option. – Hector
Nov 23 '18 at 5:59
This is the message on the error,log file
2018-11-23T01:04:26.841276Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option. – Hector
Nov 23 '18 at 5:59
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had to
sudo my way in on mysql. I restart the server, I checked the mysql login and I don't need to sudo my way in to MySQL from the terminal to the server.– Hector
Nov 23 '18 at 6:07
Also I changed the password by doing the step 3 this Digital Ocean MySQL Install and Configuration digitalocean.com/community/tutorials/…. But I had to
sudo my way in on mysql. I restart the server, I checked the mysql login and I don't need to sudo my way in to MySQL from the terminal to the server.– Hector
Nov 23 '18 at 6:07
1
1
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressed
return and nothing happended. I'll tried again in other server. For now, I can log. thanks.– Hector
Nov 23 '18 at 20:15
Well I didn't know. I had setup local servers before on virtual box and this is the first time it happens. I did pressed
return and nothing happended. I'll tried again in other server. For now, I can log. thanks.– Hector
Nov 23 '18 at 20:15
|
show 1 more comment
I found the solution. It needs to be execute as superuser
I had to execute $ sudo mysql_secure_installation
Also if I want to log in the mysql on the terminal I must sudo it
answered Nov 22 '18 at 23:58
Hector
63
Check my answer. There is no reason you need to runmysqlcommands viasudo.
– JakeGould
Nov 23 '18 at 1:31
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default formysqlclient) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.
– ivanivan
Nov 23 '18 at 23:19
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
add a comment |
I found the solution. It needs to be execute as superuser
I had to execute $ sudo mysql_secure_installation
Also if I want to log in the mysql on the terminal I must sudo it
answered Nov 22 '18 at 23:58
Hector
63
Check my answer. There is no reason you need to runmysqlcommands viasudo.
– JakeGould
Nov 23 '18 at 1:31
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default formysqlclient) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.
– ivanivan
Nov 23 '18 at 23:19
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
add a comment |
I found the solution. It needs to be execute as superuser
I had to execute $ sudo mysql_secure_installation
Also if I want to log in the mysql on the terminal I must sudo it
answered Nov 22 '18 at 23:58
Hector
63
I found the solution. It needs to be execute as superuser
I had to execute $ sudo mysql_secure_installation
Also if I want to log in the mysql on the terminal I must sudo it
answered Nov 22 '18 at 23:58
Hector
63
answered Nov 22 '18 at 23:58
Hector
63
answered Nov 22 '18 at 23:58
Hector
63
answered Nov 22 '18 at 23:58
Hector
63
63
Check my answer. There is no reason you need to runmysqlcommands viasudo.
– JakeGould
Nov 23 '18 at 1:31
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default formysqlclient) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.
– ivanivan
Nov 23 '18 at 23:19
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
add a comment |
Check my answer. There is no reason you need to runmysqlcommands viasudo.
– JakeGould
Nov 23 '18 at 1:31
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default formysqlclient) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.
– ivanivan
Nov 23 '18 at 23:19
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
Check my answer. There is no reason you need to run
mysql commands via sudo.– JakeGould
Nov 23 '18 at 1:31
Check my answer. There is no reason you need to run
mysql commands via sudo.– JakeGould
Nov 23 '18 at 1:31
1
1
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default for
mysql client) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.– ivanivan
Nov 23 '18 at 23:19
@JakeGould actually.. recent installs (ubuntu, mint, maybe debian) have been using unix socket authentication. If hte connection is made via socket (default for
mysql client) then the *nix username is trusted and authentication is done automatically. Drove me nuts first time I ran into it a few months ago, since hte typical "restart w/o privs and set a new password for root" steps all work w/o error or other indication. there is another column that needs updating to use said set password vs. socket auth.– ivanivan
Nov 23 '18 at 23:19
1
1
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
@ivanivan Good to know. Read up on it and it seems that is exactly the scenario the original poster was facing. Updated my answer to reflect this new info.
– JakeGould
Nov 25 '18 at 2:35
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377691%2fwhats-my-mysql-root-password%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I had not setup anything
– Hector
Nov 22 '18 at 23:12
Please post text, no a link to an image.
– RalfFriedl
Nov 23 '18 at 0:16