Re: BUG #6404: postgres account not created during unattended install

Поиск
Список
Период
Сортировка
От Mark Phillips
Тема Re: BUG #6404: postgres account not created during unattended install
Дата
Msg-id 08B787D6-E483-444D-B0D3-BD9EAB06E80D@mophilly.com
обсуждение исходный текст
Ответ на Re: BUG #6404: postgres account not created during unattended install  (Dharmendra Goyal <dharmendra.goyal@enterprisedb.com>)
Список pgsql-bugs
Thank you for your reply.

On Feb 3, 2012, at 9:31 AM, Dharmendra Goyal wrote:

> On Fri, Feb 3, 2012 at 10:37 PM, Mark Phillips <mark.phillips@mophilly.co=
m> wrote:
> After considering your remarks and modifying the app install script, the =
app installation completes normally with a functioning PostgreSQL installat=
ion. However, the errors reported previous still appear in the logs.=20
> If erros which you sent last tim appear  even when you run the installati=
on first time, it means that there was an existing installation of postgres=
. You can confirm same by checking /etc/postgres-reg.ini file.

Immediately after restoration of the vm image, there is no file /etc/postgr=
es-reg.ini. Perhaps it is placed elsewhere by the OS X designers. I cannot =
find it with locate enabled and run as root.=20

The file is present after I run the postgres installer.=20


> To recap the questions:
> 1. are the errors reported in the postgres install log of a type to cause=
 a malfunction for end users?
> Even if the error (postgres user not found) is there in the log, it will =
not cause any problem to the end user. Error is coming because installer fi=
nds a previous installation of PG hence tries to stop the existing pg serve=
r if it is running. So even if it is not able to stop any, it is not going =
to cause any issue as subsequent installation of pg goes fine.=20

This is good news. :-)

> 2. how can I suppress the appearance of the user account "PostgreSQL" in =
the os x login window?
> Please check /etc/postgres-reg.ini file for bindled pg installation.=20=
=20

Forgive me for being redundant, but I cannot locate a file named "postgres-=
reg.ini" prior to running the installer.

Here is the content from the file /etc/postgres-reg.ini written by the post=
gres installer:

$ cat etc/postgres-reg.ini=20
[PostgreSQL/9.1]
Branding=3DPostgreSQL 9.1
DataDirectory=3D/Library/PostgreSQL/9.1/data
Description=3DPostgreSQL 9.1
DisableStackBuilder=3D0
InstallationDirectory=3D/Library/PostgreSQL/9.1
Locale=3DC
Port=3D5432
Serviceaccount=3Dpostgres
ServiceID=3Dpostgresql-9.1
Shortcuts=3D1
Superuser=3Dpostgres
Version=3D9.1.2.1

You thoughts are most welcome.

 - Mark


>=20
> Many thanks,
>=20
>  - Mark
>=20
> On Jan 30, 2012, at 11:34 PM, Dharmendra Goyal wrote:
>=20
>> Hi Mark,
>>=20
>> Install log shows that your db installation is successful. The error whi=
ch you had sent is coming because your earlier installation failed to creat=
e 'postgres' user and when you ran the installer again, installer read /etc=
/postgres-reg.ini file to check any previous installation and found that pr=
evious installation was done. Hence installer tries to stop the db server i=
n case it is running using postgres user. This command fails as postgres us=
er was not created in your first installation because of some reason. But i=
n latest installation (for which you have sent the log), postgres user has =
been created successfully and installation went successfully. You need to c=
heck why postgres user was not created in first go by checking logs of that=
 installation.
>>=20
>> You are checking return status of the installbuilder.sh command run whic=
h is not 0 hence you are getting error ("install of DBMS failed".) in your =
script. Can yu please check what is the return value in your script of inst=
allbuilder.sh.
>>=20
>> Regards,
>>=20
>> On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips <mark.phillips@mophilly.c=
om> wrote:
>>=20
>> On Jan 29, 2012, at 11:07 PM, Dharmendra Goyal wrote:
>>=20
>>> On Sat, Jan 21, 2012 at 3:01 AM, <mark.phillips@mophilly.com> wrote:
>>> The following bug has been logged on the website:
>>>=20
>>> Bug reference:      6404
>>> Logged by:          Mark Phillips
>>> Email address:      mark.phillips@mophilly.com
>>> PostgreSQL version: 9.1.2
>>> Operating system:   Mac OS X 10.7
>>> Description:
>>>=20
>>> for a stand alone app that uses postgres, the app installer invokes the
>>> shell script installbuilder.sh for the "unattended" install of postgres.
>>>=20
>>> The pg installer creates a user "PostgreSQL" that is not hidden, but do=
es
>>> not create a hidden account "postgres". As a result, the invocation of
>>> pg_ctl fails. Error is "unknown login: postgres".
>>> pg installer creates "postgres" user which somehow seems to be failing =
at your machine. Can you please send installation log which can be found un=
der /tmp/install-postgresql.log. Also if you can run installation_path/inst=
aller/server/createuser.sh script manually and check the output, it can be =
helpful.
>>>=20
>>> Thanks,
>>> --=20
>>> Dharmendra Goyal
>>=20
>> Thank you for the reply. I apologize for the delay in responding.
>>=20
>> File install-postgresql.log attached.
>>=20
>> Please review the link below to a post in the postgresql forum for a bit=
 more detail about this issue:
>>=20
>>   http://forums.enterprisedb.com/posts/list/3042.page
>>=20
>> I looked into running the createuser.sh script. However, I encountered a=
 bit of new information before I could get that far so I include it here in=
 case it is relevant.=20
>>=20
>> Beginning anew with a clean os install, I ran the app installer that inv=
okes the postgresql installer.
>>=20
>> Here is a snippet of the installer script that relates to installing pos=
tgres:
>>=20
>>   # adjust current settings to allow the install to execute properly
>>   log "adjust current shared memory settings"
>>   log "..refer to http://www.postgresql.org/docs/9.1/interactive/kernel-=
resources.html#SYSVIPC"
>>   sysctl -w kern.sysv.shmmax=3D1610612736
>>   sysctl -w kern.sysv.shmall=3D393216
>>   sysctl -w kern.sysv.shmmin=3D1
>>   sysctl -w kern.sysv.shmmni=3D32
>>   sysctl -w kern.sysv.shmseg=3D8
>>   sysctl -w kern.maxprocperuid=3D512
>>   sysctl -w kern.maxproc=3D2048
>>=20
>>   # install postgres
>>=20
>>   cd "${BASE}"
>>   log "change directory to ${BASE}"
>>=20
>>   log "=3D=3D=3D install DBMS engine  =3D=3D=3D"
>>   postgresql-9.1.2-1-osx.app/Contents/MacOS/installbuilder.sh --mode una=
ttended --superaccount PostgresSQL --superpassword Omnis1
>>   if [ $? !=3D 0 ]; then
>>       log "install of DBMS failed: ${?}"
>>       exit 1
>>   fi
>>=20
>> It appears execution stops there. The following is in the system log:
>>=20
>> 1/30/12 3:41:26.784 PM markphillips: PRM Installer: =3D=3D=3D install DB=
MS engine  =3D=3D=3D
>> 1/30/12 3:41:26.819 PM authexec: executing /Users/markphillips/Downloads=
/PRM Installer/Install PRM.app/Contents/Resources/postgresql-9.1.2-1-osx.ap=
p/Contents/MacOS/osx-intel
>> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorInvalidConnection: CGSGetWindo=
wTags: Invalid connection
>> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorFailure: Set a breakpoint @ CG=
ErrorBreakpoint() to catch errors as they are logged.
>>=20
>> Please note the lack of the terminating message "install of DBMS failed"=
. There are other termination log messages that might have been written if =
the script progressed further. None were logged so I assume the script was =
aborted while running the postgresql install script.
>>=20
>> Thank you,
>>=20
>>  - Mark
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Dharmendra Goyal
>> Senior Software Engineer
>> EnterpriseDB Corporation
>> The Enterprise Postgres Company
>>=20
>> Phone: +91-20-30589493
>> Mobile: +91-9552103323
>>=20
>> Website: http://www.enterprisedb.com
>> EnterpriseDB Blog: http://blogs.enterprisedb.com/
>> Follow us on Twitter: http://www.twitter.com/enterprisedb
>>=20
>> This e-mail message (and any attachment) is intended for the use of the =
individual or entity to whom it is addressed. This message contains informa=
tion from EnterpriseDB Corporation that may be privileged, confidential, or=
 exempt from disclosure under applicable law. If you are not the intended r=
ecipient or authorized to receive this for the intended recipient, any use,=
 dissemination, distribution, retention, archiving, or copying of this comm=
unication is strictly prohibited. If you have received this e-mail in error=
, please notify the sender immediately by reply e-mail and delete this mess=
age.
>>=20
>=20
>=20
>=20
>=20
> --=20
> Dharmendra Goyal
> Senior Software Engineer
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>=20
> Phone: +91-20-30589493
> Mobile: +91-9552103323
>=20
> Website: http://www.enterprisedb.com
> EnterpriseDB Blog: http://blogs.enterprisedb.com/
> Follow us on Twitter: http://www.twitter.com/enterprisedb
>=20
> This e-mail message (and any attachment) is intended for the use of the i=
ndividual or entity to whom it is addressed. This message contains informat=
ion from EnterpriseDB Corporation that may be privileged, confidential, or =
exempt from disclosure under applicable law. If you are not the intended re=
cipient or authorized to receive this for the intended recipient, any use, =
dissemination, distribution, retention, archiving, or copying of this commu=
nication is strictly prohibited. If you have received this e-mail in error,=
 please notify the sender immediately by reply e-mail and delete this messa=
ge.
>=20

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Bridget Frey
Дата:
Сообщение: Re: BUG #6425: Bus error in slot_deform_tuple
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: converting between infinity timestamp and float8 (epoch)