Обсуждение: starting posgresql for the first time and most probably last :)

Поиск
Список
Период
Сортировка

starting posgresql for the first time and most probably last :)

От
Robert Morgan
Дата:
I posted this 3 hours ago but haven't seen it in the messages so am
reposting( in case other post shows up)

Thankyou to all the people who have taken the time to reply my posts,
unfortunately nothing has worked.
I have removed postgresql and reinstalled from source following the
directions from:

http://www.postgresql.org/docs/current/static/install-post.htm

this is the end result...

gmake[2]: Leaving directory `/usr/local/src/postgresql-7.4.2/src/pl'
gmake[1]: Leaving directory `/usr/local/src/postgresql-7.4.2/src'

postgreSQL installation complete.

GMAKE INSTALL FINISHES SUCCESSFULLY

[root@localhost postgresql-7.4.2]# LD_LIBRARY_PATH=/usr/local/pgsql/lib
[root@localhost postgresql-7.4.2]# export LD_LIBRARY_PATH
[root@localhost postgresql-7.4.2]# su postgres
bash-2.05b$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user
"postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_NZ.UTF-8.

creating directory /usr/local/pgsql/data... ok
creating directory /usr/local/pgsql/data/base... ok
creating directory /usr/local/pgsql/data/global... ok
creating directory /usr/local/pgsql/data/pg_xlog... ok
creating directory /usr/local/pgsql/data/pg_clog... ok
selecting default max_connections... 100
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in /usr/local/pgsql/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ok
creating information schema... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
or
/usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l logfile start

INITIALISATION IS SUCCESSFUL

bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
LOG: could not create IPv6 socket: Address family not supported by protocol
LOG: database system was shut down at 2004-04-29 10:51:19 NZST
LOG: checkpoint record is at 0/9B1058
LOG: redo record is at 0/9B1058; undo record is at 0/0; shutdown TRUE
LOG: next transaction ID: 536; next OID: 17142
LOG: database system is ready

AT THIS POINT I DID CTRL+Z AS NOTHING ELSE HAPPENED

[1]+ Stopped /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data

POSMASTER HAS STOPPED

bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
FATAL: lock file "/usr/local/pgsql/data/postmaster.pid" already exists
HINT: Is another postmaster (PID 19495) running in data directory
"/usr/local/pgsql/data"?
bash-2.05b$

UNABLE TO RESTART? ANOTHER INSTANCE OF POSTMASTER RUNNING? NO!!

If someone could explain to me what is going on I would appreciate it.

Without a doubt one of the more user unfriendly programmes I have come
across!

Bob

Whats that other dbms my…my something……


Re: starting posgresql for the first time and most probably last :)

От
daq
Дата:
RM> bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
RM> LOG: could not create IPv6 socket: Address family not supported by protocol
RM> LOG: database system was shut down at 2004-04-29 10:51:19 NZST
RM> LOG: checkpoint record is at 0/9B1058
RM> LOG: redo record is at 0/9B1058; undo record is at 0/0; shutdown TRUE
RM> LOG: next transaction ID: 536; next OID: 17142
RM> LOG: database system is ready

RM> AT THIS POINT I DID CTRL+Z AS NOTHING ELSE HAPPENED

RM> [1]+ Stopped /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data

RM> POSMASTER HAS STOPPED

RM> bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
RM> FATAL: lock file "/usr/local/pgsql/data/postmaster.pid" already exists
RM> HINT: Is another postmaster (PID 19495) running in data directory
RM> "/usr/local/pgsql/data"?
RM> bash-2.05b$

RM> UNABLE TO RESTART? ANOTHER INSTANCE OF POSTMASTER RUNNING? NO!!

I think your Postgres server is runing. After CTRL+Z write bg into the
console to run the postmaster process in background. And now you can
connect to the server.

DAQ


Re: starting posgresql for the first time and most probably

От
David Filion
Дата:
Robert Morgan wrote:
> I posted this 3 hours ago but haven't seen it in the messages so am
> reposting( in case other post shows up)
>
> Thankyou to all the people who have taken the time to reply my posts,
> unfortunately nothing has worked.
> I have removed postgresql and reinstalled from source following the
> directions from:
>
> http://www.postgresql.org/docs/current/static/install-post.htm
>
> this is the end result...
>
> gmake[2]: Leaving directory `/usr/local/src/postgresql-7.4.2/src/pl'
> gmake[1]: Leaving directory `/usr/local/src/postgresql-7.4.2/src'
>
> postgreSQL installation complete.
>
> GMAKE INSTALL FINISHES SUCCESSFULLY
>
> [root@localhost postgresql-7.4.2]# LD_LIBRARY_PATH=/usr/local/pgsql/lib
> [root@localhost postgresql-7.4.2]# export LD_LIBRARY_PATH
> [root@localhost postgresql-7.4.2]# su postgres
> bash-2.05b$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
> The files belonging to this database system will be owned by user
> "postgres".
> This user must also own the server process.
>
> The database cluster will be initialized with locale en_NZ.UTF-8.
>
> creating directory /usr/local/pgsql/data... ok
> creating directory /usr/local/pgsql/data/base... ok
> creating directory /usr/local/pgsql/data/global... ok
> creating directory /usr/local/pgsql/data/pg_xlog... ok
> creating directory /usr/local/pgsql/data/pg_clog... ok
> selecting default max_connections... 100
> selecting default shared_buffers... 1000
> creating configuration files... ok
> creating template1 database in /usr/local/pgsql/data/base/1... ok
> initializing pg_shadow... ok
> enabling unlimited row size for system tables... ok
> initializing pg_depend... ok
> creating system views... ok
> loading pg_description... ok
> creating conversions... ok
> setting privileges on built-in objects... ok
> creating information schema... ok
> vacuuming database template1... ok
> copying template1 to template0... ok
>
> Success. You can now start the database server using:
>
> /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
> or
> /usr/local/pgsql/bin/pg_ctl -D /usr/local/pgsql/data -l logfile start
>
> INITIALISATION IS SUCCESSFUL
>
> bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
> LOG: could not create IPv6 socket: Address family not supported by protocol
> LOG: database system was shut down at 2004-04-29 10:51:19 NZST
> LOG: checkpoint record is at 0/9B1058
> LOG: redo record is at 0/9B1058; undo record is at 0/0; shutdown TRUE
> LOG: next transaction ID: 536; next OID: 17142
> LOG: database system is ready
>
> AT THIS POINT I DID CTRL+Z AS NOTHING ELSE HAPPENED
>
> [1]+ Stopped /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
>
> POSMASTER HAS STOPPED
>
> bash-2.05b$ /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
> FATAL: lock file "/usr/local/pgsql/data/postmaster.pid" already exists
> HINT: Is another postmaster (PID 19495) running in data directory
> "/usr/local/pgsql/data"?
> bash-2.05b$
>
> UNABLE TO RESTART? ANOTHER INSTANCE OF POSTMASTER RUNNING? NO!!
>
> If someone could explain to me what is going on I would appreciate it.
>
> Without a doubt one of the more user unfriendly programmes I have come
> across!
>
> Bob
>
> Whats that other dbms my…my something……
>
>

You may want to reread the section on jobs in the shell manual.  ctrl-z
puts the process to sleep, it doesn't kill it.  So, doing a ctrl-z just
put the postmaster to sleep in the background.  A ps -ef would have
shown you that it was in fact still there waiting for you to tell it
what to do next.  To get it to run in the background to needed to do a
bg command after your ctrl-z.

As for the IPv6, it could be the kernel doesn't have IPv6 loaded. Maybe
kernel module needed to be loaded?

Sorry if you've heard all this before but I just wanted  to cover the
basics first.

David