Hi, I've just installed postgres on the Linux server. It is supposed
to start automatically which I think it does since I can run an sql
stmt right away. When I'm trying to connect from a remote machine I
get a message that the remote machine IP address is not specified in
pg_hba.conf, that there is no record of that machine there.
ph_hba.conf is set up correctly, because when I run the following:
postmaster -i -D /var/lib/pgsql/data
from the command line, I'm able to easily connect to postgre from the
remote machine.
What's the deal here? It's probably how postgres is started.
here is my startup script:
#! /bin/sh
# postgresql This is the init script for starting up the PostgreSQL
# server
#
# chkconfig: - 85 15
# description: Starts and stops the PostgreSQL backend daemon that
handles \
# all database requests.
# processname: postmaster
# pidfile: /var/run/postmaster.pid
# Version 6.5.3-2 Lamar Owen
# Added code to determine if PGDATA exists, whether it is current
version
# or not, and initdb if no PGDATA (initdb will not overwrite a
database).
# Version 7.0 Lamar Owen
# Added logging code
# Changed PGDATA.
#
# Version 7.0.2 Trond Eivind Glomsrød <te*@redhat.com>
# use functions, add conditional restart
# Version 7.0.3 Lamar Owen <la***@postgresql.org>
# Check for the existence of functions before blindly using them
# in particular -- check for success () and failure () before using.
# More Cross-distribution support -- PGVERSION variable, and docdir
checks.
# Version 7.1 Release Candidate Lamar Owen <la***@postgresql.org>
# initdb parameters have changed.
# Version 7.1.2 Trond Eivind Glomsrød <te*@redhat.com>
# Specify shell for su
# Handle stop better - kill unwanted output, make it wait until the
database is ready
# Handle locales slightly differently - always using "C" isn't a valid
option
# Kill output from database initialization
# Mark messages for translation
# Version 7.1.2-2.PGDG Lamar Owen <la********@wgcr.org>
# sync up.
# Karl's fixes for some quoting issues.
# Version 7.2b2 Lamar Owen <la********@wgcr.org>
# version change.
# Version 7.2 final. Lamar Owen <la********@wgcr.org>
# reload from Peter E.
# Eliminate the pidof postmaster test in stop -- we're using pg_ctl so
we don't need pidof.
# Tested the $? return for the stop script -- it does in fact
propagate.
# TODO: multiple postmasters.
# PGVERSION is:
PGVERSION=7.2
# Source function library.
INITD=/etc/rc.d/init.d
.. $INITD/functions
# Get function listing for cross-distribution logic.
TYPESET=`typeset -f|grep "declare"`
# Get config.
.. /etc/sysconfig/network
# Check that networking is up.
# Pretty much need it for postmaster.
[ "${NETWORKING}" = "no" ] && exit 0
[ -f /usr/bin/postmaster ] || exit 0
start(){
PSQL_START=$"Starting postgresql service: "
# Check for older PGDATA location.
if [ -f /var/lib/pgsql/PG_VERSION ] && [ -d
/var/lib/pgsql/base/template1 ]
then
export PGDATA=/var/lib/pgsql
else
export PGDATA=/var/lib/pgsql/data
fi
# Check for the PGDATA structure
if [ -f $PGDATA/PG_VERSION ] && [ -d $PGDATA/base ]
then
# Check version of existing PGDATA
if [ `cat $PGDATA/PG_VERSION` != '7.2' ]
then
SYSDOCDIR="(Your System's documentation directory)"
if [ -d /usr/doc/postgresql-$PGVERSION ]
then
SYSDOCDIR=/usr/doc
fi
if [ -d /usr/share/doc/postgresql-$PGVERSION ]
then
SYSDOCDIR=/usr/share/doc
fi
if [ -d /usr/doc/packages/postgresql-$PGVERSION ]
then
SYSDOCDIR=/usr/doc/packages
fi
if [ -d /usr/share/doc/packages/postgresql-$PGVERSION ]
then
SYSDOCDIR=/usr/share/doc/packages
fi
echo
echo -e $"An old version of the database format was found.\nYou
need to upgrade the data format before using PostgreSQL.\nSee
$SYSDOCDIR/postgresql-$PGVERSION/README.rpm-dist for more
information."
exit 1
# This doesn't seem to do anything useful...
# else
# if echo "$TYPESET"|grep "declare -f success ()" >/dev/null
# then
# success "$PSQL_CHECK"
# else
# echo " [ OK ]"
# fi
# echo
fi
# No existing PGDATA! Initdb it.
else
echo -n $"Initializing database: "
if [ ! -d $PGDATA ]
then
mkdir -p $PGDATA
chown postgres.postgres $PGDATA
fi
# Make sure the locale from the initdb is preserved for later
startups...
[ -f /etc/sysconfig/i18n ] && cp /etc/sysconfig/i18n
$PGDATA/../initdb.i18n
# Just in case no locale was set, use en_US
[ ! -f /etc/sysconfig/i18n ] && echo "LANG=en_US" >
$PGDATA/../initdb.i18n
# Is expanded this early to be used in the command su runs
echo "export LANG LC_ALL LC_CTYPE LC_COLLATE LC_NUMERIC LC_CTYPE
LC_TIME" >> $PGDATA/../initdb.i18n
# Initialize the database
su -l postgres -s /bin/sh -c "/usr/bin/initdb
--pgdata=/var/lib/pgsql/data > /dev/null 2>&1" < /dev/null
[ -f $PGDATA/PG_VERSION ] && echo_success
[ ! -f $PGDATA/PG_VERSION ] && echo_failure
echo
fi
# Check for postmaster already running...
pid=`pidof -s postmaster`
if [ $pid ]
then
echo $"Postmaster already running."
else
#all systems go -- remove any stale lock files
rm -f /tmp/.s.PGSQL.* > /dev/null
echo -n "$PSQL_START"
su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -o '-i' -p
/usr/bin/postmaster start > /dev/null 2>&1" < /dev/null
sleep 1
pid=`pidof -s postmaster`
if [ $pid ]
then
if echo "$TYPESET"|grep "declare -f success ()" >/dev/null
then
success "$PSQL_START"
else
echo " [ OK ]"
fi
touch /var/lock/subsys/postgresql
echo $pid > /var/run/postmaster.pid
echo
else
if echo "$TYPESET"|grep "declare -f failure ()" >/dev/null
then
failure "$PSQL_START"
else
echo " [ FAILED ]"
fi
echo
fi
fi
}
stop(){
echo -n $"Stopping postgresql service: "
# Check for older PGDATA location.
if [ -f /var/lib/pgsql/PG_VERSION ] && [ -d
/var/lib/pgsql/base/template1 ]
then
export PGDATA=/var/lib/pgsql
else
export PGDATA=/var/lib/pgsql/data
fi
su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl stop -D $PGDATA -s -m
fast" > /dev/null 2>&1
ret=$?
if [ $ret -eq 0 ]; then
echo_success
else
echo_failure
fi
echo
rm -f /var/run/postmaster.pid
rm -f /var/lock/subsys/postgresql
}
restart(){
stop
start
}
condrestart(){
[ -e /var/lock/subsys/postgresql ] && restart || :
}
reload(){
su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl reload -D $PGDATA
-s" > /dev/null 2>&1
}
# This script is slightly unusual in that the name of the daemon
(postmaster)
# is not the same as the name of the subsystem (postgresql)
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status postmaster
;;
restart)
restart
;;
condrestart)
condrestart
;;
reload|force-reload)
reload
;;
*)
echo $"Usage: $0 {start|stop|status|restart|condrestart|reload|forc e-reload}"
exit 1
esac
exit 0
Please, let me know what should I do.
N.K. 3 4157
On Thursday 11 September 2003 21:42, N.K. wrote: Hi, I've just installed postgres on the Linux server. It is supposed to start automatically which I think it does since I can run an sql stmt right away. When I'm trying to connect from a remote machine I get a message that the remote machine IP address is not specified in pg_hba.conf, that there is no record of that machine there. ph_hba.conf is set up correctly, because when I run the following: postmaster -i -D /var/lib/pgsql/data from the command line, I'm able to easily connect to postgre from the remote machine. What's the deal here? It's probably how postgres is started.
here is my startup script:
Assuming this is the startup script that ships with PG, you probably want to
look in your postgresql.conf file and check the tcp_ip setting is on.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
On Thursday 11 September 2003 21:42, N.K. wrote: Hi, I've just installed postgres on the Linux server. It is supposed to start automatically which I think it does since I can run an sql stmt right away. When I'm trying to connect from a remote machine I get a message that the remote machine IP address is not specified in pg_hba.conf, that there is no record of that machine there. ph_hba.conf is set up correctly, because when I run the following: postmaster -i -D /var/lib/pgsql/data from the command line, I'm able to easily connect to postgre from the remote machine. What's the deal here? It's probably how postgres is started.
here is my startup script:
Assuming this is the startup script that ships with PG, you probably want to
look in your postgresql.conf file and check the tcp_ip setting is on.
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives? http://archives.postgresql.org
Thank you so much for your help.
It worked.
Thanks again.
N.K. na****@parkerglobal.com (N.K.) wrote in message news:<2d**************************@posting.google. com>... Hi, I've just installed postgres on the Linux server. It is supposed to start automatically which I think it does since I can run an sql stmt right away. When I'm trying to connect from a remote machine I get a message that the remote machine IP address is not specified in pg_hba.conf, that there is no record of that machine there. ph_hba.conf is set up correctly, because when I run the following: postmaster -i -D /var/lib/pgsql/data from the command line, I'm able to easily connect to postgre from the remote machine. What's the deal here? It's probably how postgres is started.
here is my startup script:
#! /bin/sh # postgresql This is the init script for starting up the PostgreSQL # server # # chkconfig: - 85 15 # description: Starts and stops the PostgreSQL backend daemon that handles \ # all database requests. # processname: postmaster # pidfile: /var/run/postmaster.pid
# Version 6.5.3-2 Lamar Owen # Added code to determine if PGDATA exists, whether it is current version # or not, and initdb if no PGDATA (initdb will not overwrite a database).
# Version 7.0 Lamar Owen # Added logging code # Changed PGDATA. #
# Version 7.0.2 Trond Eivind Glomsrød <te*@redhat.com> # use functions, add conditional restart
# Version 7.0.3 Lamar Owen <la***@postgresql.org> # Check for the existence of functions before blindly using them # in particular -- check for success () and failure () before using. # More Cross-distribution support -- PGVERSION variable, and docdir checks.
# Version 7.1 Release Candidate Lamar Owen <la***@postgresql.org> # initdb parameters have changed.
# Version 7.1.2 Trond Eivind Glomsrød <te*@redhat.com> # Specify shell for su # Handle stop better - kill unwanted output, make it wait until the database is ready # Handle locales slightly differently - always using "C" isn't a valid option # Kill output from database initialization # Mark messages for translation
# Version 7.1.2-2.PGDG Lamar Owen <la********@wgcr.org> # sync up. # Karl's fixes for some quoting issues.
# Version 7.2b2 Lamar Owen <la********@wgcr.org> # version change.
# Version 7.2 final. Lamar Owen <la********@wgcr.org> # reload from Peter E. # Eliminate the pidof postmaster test in stop -- we're using pg_ctl so we don't need pidof. # Tested the $? return for the stop script -- it does in fact propagate. # TODO: multiple postmasters.
# PGVERSION is: PGVERSION=7.2
# Source function library. INITD=/etc/rc.d/init.d . $INITD/functions
# Get function listing for cross-distribution logic. TYPESET=`typeset -f|grep "declare"`
# Get config. . /etc/sysconfig/network
# Check that networking is up. # Pretty much need it for postmaster. [ "${NETWORKING}" = "no" ] && exit 0
[ -f /usr/bin/postmaster ] || exit 0
start(){ PSQL_START=$"Starting postgresql service: "
# Check for older PGDATA location. if [ -f /var/lib/pgsql/PG_VERSION ] && [ -d /var/lib/pgsql/base/template1 ] then export PGDATA=/var/lib/pgsql else export PGDATA=/var/lib/pgsql/data fi
# Check for the PGDATA structure if [ -f $PGDATA/PG_VERSION ] && [ -d $PGDATA/base ] then # Check version of existing PGDATA
if [ `cat $PGDATA/PG_VERSION` != '7.2' ] then SYSDOCDIR="(Your System's documentation directory)" if [ -d /usr/doc/postgresql-$PGVERSION ] then SYSDOCDIR=/usr/doc fi if [ -d /usr/share/doc/postgresql-$PGVERSION ] then SYSDOCDIR=/usr/share/doc fi if [ -d /usr/doc/packages/postgresql-$PGVERSION ] then SYSDOCDIR=/usr/doc/packages fi if [ -d /usr/share/doc/packages/postgresql-$PGVERSION ] then SYSDOCDIR=/usr/share/doc/packages fi echo echo -e $"An old version of the database format was found.\nYou need to upgrade the data format before using PostgreSQL.\nSee $SYSDOCDIR/postgresql-$PGVERSION/README.rpm-dist for more information." exit 1 # This doesn't seem to do anything useful... # else # if echo "$TYPESET"|grep "declare -f success ()" >/dev/null # then # success "$PSQL_CHECK" # else # echo " [ OK ]" # fi # echo fi
# No existing PGDATA! Initdb it.
else echo -n $"Initializing database: " if [ ! -d $PGDATA ] then mkdir -p $PGDATA chown postgres.postgres $PGDATA fi # Make sure the locale from the initdb is preserved for later startups... [ -f /etc/sysconfig/i18n ] && cp /etc/sysconfig/i18n $PGDATA/../initdb.i18n # Just in case no locale was set, use en_US [ ! -f /etc/sysconfig/i18n ] && echo "LANG=en_US" > $PGDATA/../initdb.i18n # Is expanded this early to be used in the command su runs echo "export LANG LC_ALL LC_CTYPE LC_COLLATE LC_NUMERIC LC_CTYPE LC_TIME" >> $PGDATA/../initdb.i18n # Initialize the database su -l postgres -s /bin/sh -c "/usr/bin/initdb --pgdata=/var/lib/pgsql/data > /dev/null 2>&1" < /dev/null [ -f $PGDATA/PG_VERSION ] && echo_success [ ! -f $PGDATA/PG_VERSION ] && echo_failure echo fi
# Check for postmaster already running... pid=`pidof -s postmaster` if [ $pid ] then echo $"Postmaster already running." else #all systems go -- remove any stale lock files rm -f /tmp/.s.PGSQL.* > /dev/null echo -n "$PSQL_START" su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl -D $PGDATA -o '-i' -p /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null sleep 1 pid=`pidof -s postmaster` if [ $pid ] then if echo "$TYPESET"|grep "declare -f success ()" >/dev/null then success "$PSQL_START" else echo " [ OK ]" fi touch /var/lock/subsys/postgresql echo $pid > /var/run/postmaster.pid echo else if echo "$TYPESET"|grep "declare -f failure ()" >/dev/null then failure "$PSQL_START" else echo " [ FAILED ]" fi echo fi fi }
stop(){ echo -n $"Stopping postgresql service: " # Check for older PGDATA location. if [ -f /var/lib/pgsql/PG_VERSION ] && [ -d /var/lib/pgsql/base/template1 ] then export PGDATA=/var/lib/pgsql else export PGDATA=/var/lib/pgsql/data fi su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl stop -D $PGDATA -s -m fast" > /dev/null 2>&1 ret=$? if [ $ret -eq 0 ]; then echo_success else echo_failure fi echo rm -f /var/run/postmaster.pid rm -f /var/lock/subsys/postgresql }
restart(){ stop start }
condrestart(){ [ -e /var/lock/subsys/postgresql ] && restart || : }
reload(){ su -l postgres -s /bin/sh -c "/usr/bin/pg_ctl reload -D $PGDATA -s" > /dev/null 2>&1 }
# This script is slightly unusual in that the name of the daemon (postmaster) # is not the same as the name of the subsystem (postgresql)
# See how we were called. case "$1" in start) start ;; stop) stop ;; status) status postmaster ;; restart) restart ;; condrestart) condrestart ;; reload|force-reload) reload ;; *) echo $"Usage: $0 {start|stop|status|restart|condrestart|reload|forc e-reload}" exit 1 esac
exit 0
Please, let me know what should I do. N.K. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Lance Hoffmeyer |
last post by:
Hello,
I am trying to learn some basics of python. One of the things
I want to do is write a script to access a postgresql database
DB as user USER with password PW and
SELECT first_name,...
|
by: Donna |
last post by:
Hi,
I've set up remote debugging following every step in the manu from
microsoft. However, I can't see mtx.exe process in romote machine,
instead I only see inetinfo.exe. I attached to it and it...
|
by: N.K. |
last post by:
Hi, I've just installed postgres on the Linux server. It is supposed
to start automatically which I think it does since I can run an sql
stmt right away. When I'm trying to connect from a remote...
|
by: Martin_Hurst |
last post by:
Is it possible to establish a connection from within a postgres database to
another external database on the network, i.e., not a java or scripting
connection, BUT by some type of table definition...
|
by: tim |
last post by:
I have problems to connect my postgres db in Openoffice 1.1 via jdbc.
I can open the tables and run queries. But when try to create or alter
tables OpenOffice crashes.
My Settings
ClassPath...
|
by: Joe Lester |
last post by:
This thread was renamed. It used to be: "shared_buffers Question". The
old thread kind of died out. I'm hoping to get some more direction by
rephrasing the problem, along with some extra...
|
by: Alexander Cohen |
last post by:
Im trying to connect locally to a database on a running postgres
cluster. If i connect with psql, everything is fine and i can transact.
I i try and connect in my own app, i get this error:
...
|
by: Goutam Paruchuri |
last post by:
Hello,
I get an error in my log when connecting to postgres server on Windows.
Postgres version : 8.0.0-beta4
LOG TEXT
2004-11-10 11:22:47 LOG: invalid entry in file "C:/Program...
|
by: SYT |
last post by:
Hello,
I wrote C program for connecting to postgresSQL server to retrieve data from the postgres database. The program is:
#include <stdio.h>
#include <stdlib.h>
#include "libpq-fe.h"
int...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |