New answers tagged ubuntu
OK, I found the issue. I hadn't properly configured passwordless ssh login between my master and slave. So despite being able to login into my master from my slave the issue was it couldn't copy files because ssh wold require a password. My only issue is error reporting is horrible for repmgr. Following this guide I missed a very small step. Always make ...
I accidentally deleted my passwd file under /etc directory and after that postgresql service could start, when I run command systemctl status postgresql.myversion. the error was no passwd entry found for user postgres I decided to reinstall postgresql. Because I used enterpricedb installer sudo apt-get --purge remove postgresql* did not work for me. ...
There was a bug in galera_recovery.sh script. https://jira.mariadb.org/browse/MDEV-10396
I've been able to temporarily alleviate my problems by downgrading to 10.1.14: wget https://downloads.mariadb.com/files/MariaDB/mariadb-10.1.14/repo/ubuntu/pool/main/m/mariadb-10.1/mariadb-server-10.1_10.1.14+maria-1~xenial_amd64.deb wget https://downloads.mariadb.com/files/MariaDB/mariadb-10.1.14/repo/ubuntu/pool/main/m/mariadb-10.1/libmariadbclient18_10.1....
It is possible if you add default username and Password to my.cnf [client] user = root password = yourpass Then, you will be able to login as shell> mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 24 Server version: 5.7.13 MySQL Community Server (GPL) Copyright (c) 2000, 2016, ...
There is the utility mysql_config_editor, which will help create the file .myLogin.cnf for you, which will be able to store login credentials. What you'll then be doing is to store the encrypted password for the root user in that file. See http://dev.mysql.com/doc/refman/5.7/en/mysql-config-editor.html for details.
Can you please specify, why do you have to do so? You want to use it in shell script or command line Check this out http://serverfault.com/questions/563714/allow-linux-root-user-mysql-root-access-without-password
Figured it out. This was a long shot, but it may help someone who has exhausted the normal avenues or is not used to postgres. The server I was working on had another instance running through puppet, and so the config I was modifying was not for the instance I was connecting to. run find / -name 'postgresql.conf' to see if there are any other locations ...
Quite simply, the message is there plain to see: psql: FATAL: password authentication failed for user "posgres" Typo!
As dezso mentioned in the question comments, this did seem to be an issue with (possibly more recent versions of the) 3.13 kernel in Ubuntu Trusty - we switched to the Xenial HWE 4.4 kernel in Trusty and the problem seems to have gone away and compaction stalls are now very small and don't interfere.
Top 50 recent answers are included