osm2pgrouting conexión fallida

Question

Estoy importando datos de mi archivo OSM a una base de datos postgresql usando osm2pgrouting. He seguido todo lo de aquí y fue sin problemas, hasta que intente usar osm2pgrouting. Esto es lo que sucede:

root@niceroute:/opt/osm2pgrouting# ./osm2pgrouting -file ncr.osm -conf mapconfig.xml -dbname niceroute -user postgres -host localhost
host=localhost user=postgres dbname=niceroute port=5432
connection failed

He mirado en muchos foros pero sigo sin tener la respuesta que busco. Por favor, ayúdenme. Gracias.

ACTUALIZACIÓN: Mi archivo pg_hba.conf:

\# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the
# PostgreSQL documentation for a complete description
# of this file.  A short synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  \[OPTION\]
# host       DATABASE  USER  CIDR-ADDRESS  METHOD  \[OPTION\]
# hostssl    DATABASE  USER  CIDR-ADDRESS  METHOD  \[OPTION\]
# hostnossl  DATABASE  USER  CIDR-ADDRESS  METHOD  \[OPTION\]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", a database name, or
# a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or
# a comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names from
# a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
# the number of significant bits in the mask.  Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
# "krb5", "ident", "pam" or "ldap".  Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
# OPTION is the ident map or the name of the PAM service, depending on METHOD.
#
# Database and user names containing spaces, commas, quotes and other special
# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
# "samerole" makes the name lose its special character, and just match a
# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can use
# "pg\_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# on a non-local interface via the listen\_addresses configuration parameter,
# or via the -i or -h command line switches.
#

# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (custom daily cronjobs, replication, and similar tasks).
#
# Database administrative login by UNIX sockets

# JA: Set local database connections to "trust" in "pg\_hba.conf" to be able to work with PostgreSQL as user "postgres". 
#local   all         postgres                          ident sameuser
local   all postgres    trust

# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD

# "local" is for Unix domain socket connections only
# JA: change to solve isssue on osm2pgrouting 
#local   all         all                               ident sameuser
local   all         all                               trust
# IPv4 local connections:
host    all         all         127.0.0.1/32          md5
# IPv6 local connections:
host    all         all         ::1/128               md5

Espero que esto aclare las cosas :D

Answer 1

Es un problema con postgresql. Puede solucionarlo editando pg_hba.conf con

sudo nano /etc/postgresql/8.x/main/pg_hba.conf

donde 8.x depende de su versión de postgresql (8.4 en Lucid Lynx)

Se cambia en la columna MÉTODO del fichero la palabra ident por trust y se guarda el fichero.

Después de hacer un

sudo /etc/init.d/postgresql-8.x restart

Su comando pgrouting ahora funciona.

Tenga cuidado, el consejo que te doy abrir un problema de seguridad : Ok sólo en un servidor de desarrollo en la oficina

Answer 2

Esta noche me he encontrado con un problema similar. En mi caso la solución era que mi base de datos tenía una contraseña y osm2pgrouting necesitando el parámetro -passwd.