Обсуждение: Re: [ADMIN] postmaster failure
I should have read more messages in the archives. Right after I sent my
message, I read that the following is typical:
set shmsys:shminfo_shmmax=16777216
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=51
postmaster now starts. Thanks for your help.
One more thing - is there a password access facility for users in the
postgres system?
>
>what does an 'ipcs' show? did you reboot after editing /etc/system? if
>you can't reboot, use the -B option to reduce the number of segments used
>until you can reboot with the new /etc/system in place ...
>
>On Thu, 3 Feb 2000, Christopher R. Jones wrote:
>
>> I installed postgres-6.5 on Solaris 7, Intel - Pentium Pro, 128 MByte Ram.
>> I used gcc-2.95.1 and gnu make. The program compiled installed fine but
>> postmaster failed:
>>
>> cr-jay.com% initdb
>>
>> We are initializing the database system with username postgres (uid=1003).
>> This user will own all the files and must also own the server process.
>>
>> Creating Postgres database system directory /usr/local/pgsql/data
>>
>> Creating Postgres database system directory /usr/local/pgsql/data/base
>>
>> Creating template database in /usr/local/pgsql/data/base/template1
>>
>> Creating global classes in /usr/local/pgsql/data/base
>>
>> Adding template1 database to pg_database...
>>
>> Vacuuming template1
>> Creating public pg_user view
>> Creating view pg_rules
>> Creating view pg_views
>> Creating view pg_tables
>> Creating view pg_indexes
>> Loading pg_description
>>
>> cr-jay.com% postmaster -i
>> IpcMemoryCreate: shmget failed (Invalid argument) key=5432001,
>> size=1063936, permission=600
>> FATAL 1: ShmemCreate: cannot create region
>>
>> So then, after reading in the faq, I edited the /etc/system file to add:
>> set shmsys:shminfo_shmmax=1048567
>> set shmsys:shminfo_shmmin=200
>> set shmsys:shminfo_shmmni=200
>> set shmsys:shminfo_shmseg=200
>> set semsys:seminfo_semmap=250
>> set semsys:seminfo_semmni=500
>> set semsys:seminfo_semmns=500
>> set semsys:seminfo_semmsl=500
>> set semsys:seminfo_semmnu=500
>> set semsys:seminfo_semume=100
>>
>> I now get:
>> cr-jay.com% postmaster -i
>> IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=120,
>> permission=700
>> IpcMemoryIdGet: shmget failed (No such file or directory) key=5432010,
>> size=120, permission=0
>> IpcMemoryAttach: shmat failed (Invalid argument) id=-2
>> FATAL 1: AttachSLockMemory: could not attach segment
>>
>> I played with the segment max size to no avail.
>>
>> Any ideas?
>>
>>
>> Christopher R. Jones, P.Eng.
>> 14 Oneida Avenue
>> Toronto, Ontario M5J 2E3
>> Tel. 416 203-7465
>> Fax. 416 203-3044
>> Email cj@interlog.com
>>
>>
>>
>> ************
>>
>
>Marc G. Fournier ICQ#7615664 IRC Nick:
Scrappy
>Systems Administrator @ hub.org
>primary: scrappy@hub.org secondary:
scrappy@{freebsd|postgresql}.org
>
>
>
Christopher R. Jones, P.Eng.
14 Oneida Avenue
Toronto, Ontario M5J 2E3
Tel. 416 203-7465
Fax. 416 203-3044
Email cj@interlog.com
On Thu, 3 Feb 2000, Christopher R. Jones wrote:
> I should have read more messages in the archives. Right after I sent my
> message, I read that the following is typical:
> set shmsys:shminfo_shmmax=16777216
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmmni=100
> set shmsys:shminfo_shmseg=51
>
> postmaster now starts. Thanks for your help.
> One more thing - is there a password access facility for users in the
> postgres system?
password access facility? purely a guess, but I think you are referring
to the 'pg_hba.conf' file that is found in the data directory, whre you
can set various 'authentication' method on a database by database basis
...
> > >
> >what does an 'ipcs' show? did you reboot after editing /etc/system? if
> >you can't reboot, use the -B option to reduce the number of segments used
> >until you can reboot with the new /etc/system in place ...
> >
> >On Thu, 3 Feb 2000, Christopher R. Jones wrote:
> >
> >> I installed postgres-6.5 on Solaris 7, Intel - Pentium Pro, 128 MByte Ram.
> >> I used gcc-2.95.1 and gnu make. The program compiled installed fine but
> >> postmaster failed:
> >>
> >> cr-jay.com% initdb
> >>
> >> We are initializing the database system with username postgres (uid=1003).
> >> This user will own all the files and must also own the server process.
> >>
> >> Creating Postgres database system directory /usr/local/pgsql/data
> >>
> >> Creating Postgres database system directory /usr/local/pgsql/data/base
> >>
> >> Creating template database in /usr/local/pgsql/data/base/template1
> >>
> >> Creating global classes in /usr/local/pgsql/data/base
> >>
> >> Adding template1 database to pg_database...
> >>
> >> Vacuuming template1
> >> Creating public pg_user view
> >> Creating view pg_rules
> >> Creating view pg_views
> >> Creating view pg_tables
> >> Creating view pg_indexes
> >> Loading pg_description
> >>
> >> cr-jay.com% postmaster -i
> >> IpcMemoryCreate: shmget failed (Invalid argument) key=5432001,
> >> size=1063936, permission=600
> >> FATAL 1: ShmemCreate: cannot create region
> >>
> >> So then, after reading in the faq, I edited the /etc/system file to add:
> >> set shmsys:shminfo_shmmax=1048567
> >> set shmsys:shminfo_shmmin=200
> >> set shmsys:shminfo_shmmni=200
> >> set shmsys:shminfo_shmseg=200
> >> set semsys:seminfo_semmap=250
> >> set semsys:seminfo_semmni=500
> >> set semsys:seminfo_semmns=500
> >> set semsys:seminfo_semmsl=500
> >> set semsys:seminfo_semmnu=500
> >> set semsys:seminfo_semume=100
> >>
> >> I now get:
> >> cr-jay.com% postmaster -i
> >> IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=120,
> >> permission=700
> >> IpcMemoryIdGet: shmget failed (No such file or directory) key=5432010,
> >> size=120, permission=0
> >> IpcMemoryAttach: shmat failed (Invalid argument) id=-2
> >> FATAL 1: AttachSLockMemory: could not attach segment
> >>
> >> I played with the segment max size to no avail.
> >>
> >> Any ideas?
> >>
> >>
> >> Christopher R. Jones, P.Eng.
> >> 14 Oneida Avenue
> >> Toronto, Ontario M5J 2E3
> >> Tel. 416 203-7465
> >> Fax. 416 203-3044
> >> Email cj@interlog.com
> >>
> >>
> >>
> >> ************
> >>
> >
> >Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> >Systems Administrator @ hub.org
> >primary: scrappy@hub.org secondary:
> scrappy@{freebsd|postgresql}.org
> >
> >
> >
> Christopher R. Jones, P.Eng.
> 14 Oneida Avenue
> Toronto, Ontario M5J 2E3
> Tel. 416 203-7465
> Fax. 416 203-3044
> Email cj@interlog.com
>
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
I know it's not suggested that you backup a live/active database. I believe that the suggested procedure is to take a snapshot of the database by dumping it and then backing up the dump. However I have an app that is used only by a single deptartment here. Data is not changing 24/7, there is no way that anybody is working on this at 3am. Is there any harm in backing up this live database w/o dumping it? Because of it's small audience, if I needed to restore the data, I could shutdown the postgres daemon, restore the data, and then fire it back up. Not a huge deal, just being a bit lazy w/ backup procedures. I mean it's not really hard to have my backup script dump the db before the tape fires up and then skip backing up the live db. --------------------------------------------------------------- Edward F. Chase III | echase@providence.edu Providence College | http://www.providence.edu Computer Services | http://studentweb.providence.edu Providence, RI 02918 |