See this part of the pg_dump
manpage:
-W, --password
Force pg_dump to prompt for a password before connecting to a database.
This option is never essential, since pg_dump will automatically prompt
for a password if the server demands password authentication.
Don't use -W
at all. In your case, it's just confusing.
Also, you need to know that the fact that the server asks for a password or not is not driven by the existence of this password.
It's driven by the server-side pg_hba.conf
file that you need to study and possibly modify according to your needs (don't forget to reload the server after modifying it).
EDIT: reviewing your pg_hba.conf. The relevant lines are:
# TYPE DATABASE USER ADDRESS METHOD
local all postgres peer
local all all peer
host all all 127.0.0.1/32 md5
host all all ::1/128 md5
The 1st line concerns the postgres
user. It's irrelevant for your pg_dump command since you're using the santa
user with -U santa
The 2nd line concerns any other connection through Unix domain sockets (TYPE column is local
). From the client, it means when you do not use -h localhost
. It says that if the OS user is the same name than the db user, he doesn't need a password.
The 3rd line says that if -h localhost
is used (IPv4 TCP connection), a password will always be asked to the client. The 4th line says the same with IPv6.
Based on this, this command run by the santa
OS user should not ask or need a password:
pg_dump --no-owner myapp_db > myapp_db_backup.sql
-U santa
is optional because the db username is taken as the OS user by default.
First of all when you run mongod as a normal user you need to make sure that the particular user has the following permissions:
- Access to network interface ( open socket ) in order to be able to listen to connections
- Access to the database folder. The default is accessible only by root or mongod user (/data/db)
- Access to logging folder /var/log/mongod
All of the above are automatically set and granted for the user mongodb (mongod in earlier versions). If you take a look at /etc/init.d/mongodb you will see that the service will be stared under the user mongodb DAEMONUSER=${DAEMONUSER:-mongodb} and not as root.
Best Answer
Launch Shell as User:
If all else fails, on Ubuntu 14.04 LTS running on AWS, try this...
OF COURSE, you'll add a much larger set of flags to the command. Note also that this assumes you're authenticated as
ubuntu
on an AWS EC2 instance. The first portion of each line to the left of the$
is the user@hostnameInvoke Command as User:
YMMV but this should work too...