Thread: BUG #6404: postgres account not created during unattended install
BUG #6404: postgres account not created during unattended install
From
mark.phillips@mophilly.com
Date:
The following bug has been logged on the website: 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=20=20=20=20=20=20=20 for a stand alone app that uses postgres, the app installer invokes the shell script installbuilder.sh for the "unattended" install of postgres. The pg installer creates a user "PostgreSQL" that is not hidden, but does not create a hidden account "postgres". As a result, the invocation of pg_ctl fails. Error is "unknown login: postgres".=20
On Sat, Jan 21, 2012 at 3:01 AM, <mark.phillips@mophilly.com> wrote: > The following bug has been logged on the website: > > 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: > > for a stand alone app that uses postgres, the app installer invokes the > shell script installbuilder.sh for the "unattended" install of postgres. > > The pg installer creates a user "PostgreSQL" that is not hidden, but does > 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 under /tmp/install-postgresql.log. Also if you can run installation_path/installer/server/createuser.sh script manually and check the output, it can be helpful. Thanks, -- Dharmendra Goyal Senior Software Engineer EnterpriseDB Corporation The Enterprise Postgres Company Phone: +91-20-30589493 Mobile: +91-9552103323 Website: http://www.enterprisedb.com EnterpriseDB Blog: http://blogs.enterprisedb.com/ Follow us on Twitter: http://www.twitter.com/enterprisedb 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 information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
Hi Mark,
Install log shows that your db installation is successful. The error which
you had sent is coming because your earlier installation failed to create
'postgres' user and when you ran the installer again, installer read
/etc/postgres-reg.ini file to check any previous installation and found
that previous installation was done. Hence installer tries to stop the db
server in case it is running using postgres user. This command fails as
postgres user was not created in your first installation because of some
reason. But in latest installation (for which you have sent the log),
postgres user has been created successfully and installation went
successfully. You need to check why postgres user was not created in first
go by checking logs of that installation.
You are checking return status of the installbuilder.sh command run which
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
installbuilder.sh.
Regards,
On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips
<mark.phillips@mophilly.com>wrote:
>
> On Jan 29, 2012, at 11:07 PM, Dharmendra Goyal wrote:
>
> On Sat, Jan 21, 2012 at 3:01 AM, <mark.phillips@mophilly.com> wrote:
>
>> The following bug has been logged on the website:
>>
>> 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:
>>
>> for a stand alone app that uses postgres, the app installer invokes the
>> shell script installbuilder.sh for the "unattended" install of postgres.
>>
>> The pg installer creates a user "PostgreSQL" that is not hidden, but does
>> 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 under
> /tmp/install-postgresql.log. Also if you can run
> installation_path/installer/server/createuser.sh script manually and check
> the output, it can be helpful.
>
> Thanks,
> --
> Dharmendra Goyal
>
>
> Thank you for the reply. I apologize for the delay in responding.
>
> File install-postgresql.log attached.
>
> Please review the link below to a post in the postgresql forum for a bit
> more detail about this issue:
>
> http://forums.enterprisedb.com/posts/list/3042.page
>
> 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.
>
> Beginning anew with a clean os install, I ran the app installer that
> invokes the postgresql installer.
>
> Here is a snippet of the installer script that relates to installing
> postgres:
>
> # 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=1610612736
> sysctl -w kern.sysv.shmall=393216
> sysctl -w kern.sysv.shmmin=1
> sysctl -w kern.sysv.shmmni=32
> sysctl -w kern.sysv.shmseg=8
> sysctl -w kern.maxprocperuid=512
> sysctl -w kern.maxproc=2048
>
> # install postgres
>
> cd "${BASE}"
> log "change directory to ${BASE}"
>
> log "=== install DBMS engine ==="
> postgresql-9.1.2-1-osx.app/Contents/MacOS/installbuilder.sh --mode
> unattended --superaccount PostgresSQL --superpassword Omnis1
> if [ $? != 0 ]; then
> log "install of DBMS failed: ${?}"
> exit 1
> fi
>
> It appears execution stops there. The following is in the system log:
>
> 1/30/12 3:41:26.784 PM markphillips: PRM Installer: === install DBMS
> engine ===
> 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.app/Contents/MacOS/osx-intel
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorInvalidConnection:
> CGSGetWindowTags: Invalid connection
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorFailure: Set a breakpoint @
> CGErrorBreakpoint() to catch errors as they are logged.
>
> 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.
>
> Thank you,
>
> - Mark
>
>
>
>
>
--
Dharmendra Goyal
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise Postgres Company
Phone: +91-20-30589493
Mobile: +91-9552103323
Website: http://www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb
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
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
Thank you for the reply. I have spent the better part of this week on this =
and related issues.=20
My test procedure is as follows: create VM using Fusion 4.x with a fresh in=
stall of OS X 10.7. The VM is hosted on a Mac also running 10.7. I create a=
snapshot of this clean image. The first step of each test run is to restor=
e the snapshot image.=20
With this in mind, the comment about the previous installation does not see=
m to apply to my report.=20
After considering your remarks and modifying the app install script, the ap=
p installation completes normally with a functioning PostgreSQL installatio=
n. However, the errors reported previous still appear in the logs.=20
The unattended mode results in the appearance of a user "PostgreSQL" in the=
User Accounts preferences panel as well as the login window. It is interes=
ting to note that a user named "postgres" in any variant does not appear in=
/Users/ directory, nor in the file /etc/passwd/, with the exception of the=
os x standard postgres account.
$ cat /etc/passwd | grep "Postgre"
_postgres:*:216:216:PostgreSQL Server:/var/empty:/usr/bin/false
The "one click" installer does not result in the appearance of the "Postgre=
SQL" user account in the os x GUI.
To recap the questions:
1. are the errors reported in the postgres install log of a type to cause a=
malfunction for end users?
2. how can I suppress the appearance of the user account "PostgreSQL" in th=
e os x login window?
Many thanks,
- Mark
On Jan 30, 2012, at 11:34 PM, Dharmendra Goyal wrote:
> Hi Mark,
>=20
> Install log shows that your db installation is successful. The error whic=
h you had sent is coming because your earlier installation failed to create=
'postgres' user and when you ran the installer again, installer read /etc/=
postgres-reg.ini file to check any previous installation and found that pre=
vious installation was done. Hence installer tries to stop the db server in=
case it is running using postgres user. This command fails as postgres use=
r was not created in your first installation because of some reason. But in=
latest installation (for which you have sent the log), postgres user has b=
een created successfully and installation went successfully. You need to ch=
eck 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 which=
is not 0 hence you are getting error ("install of DBMS failed".) in your s=
cript. Can yu please check what is the return value in your script of insta=
llbuilder.sh.
>=20
> Regards,
>=20
> On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips <mark.phillips@mophilly.co=
m> 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 does
>> 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 a=
t your machine. Can you please send installation log which can be found und=
er /tmp/install-postgresql.log. Also if you can run installation_path/insta=
ller/server/createuser.sh script manually and check the output, it can be h=
elpful.
>>=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 invo=
kes the postgresql installer.
>=20
> Here is a snippet of the installer script that relates to installing post=
gres:
>=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-r=
esources.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 unat=
tended --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 DBM=
S 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.app=
/Contents/MacOS/osx-intel
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorInvalidConnection: CGSGetWindow=
Tags: Invalid connection
> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorFailure: Set a breakpoint @ CGE=
rrorBreakpoint() 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 t=
he script progressed further. None were logged so I assume the script was a=
borted 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 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
On Fri, Feb 3, 2012 at 10:37 PM, Mark Phillips
<mark.phillips@mophilly.com>wrote:
> Thank you for the reply. I have spent the better part of this week on this
> and related issues.
>
> My test procedure is as follows: create VM using Fusion 4.x with a fresh
> install of OS X 10.7. The VM is hosted on a Mac also running 10.7. I create
> a snapshot of this clean image. The first step of each test run is
> to restore the snapshot image.
>
> With this in mind, the comment about the previous installation does not
> seem to apply to my report.
>
> After considering your remarks and modifying the app install script, the
> app installation completes normally with a functioning PostgreSQL
> installation. However, the errors reported previous still appear in the
> logs.
>
If erros which you sent last tim appear even when you run the installation
first time, it means that there was an existing installation of postgres.
You can confirm same by checking /etc/postgres-reg.ini file.
>
> The unattended mode results in the appearance of a user "PostgreSQL" in
> the User Accounts preferences panel as well as the login window. It is
> interesting to note that a user named "postgres" in any variant does not
> appear in /Users/ directory, nor in the file /etc/passwd/, with the
> exception of the os x standard postgres account.
> $ cat /etc/passwd | grep "Postgre"
> _postgres:*:216:216:PostgreSQL Server:/var/empty:/usr/bin/false
>
I agree that _postgres exists because of the inbuilt pg which is bundled
with OS. But not sure why PostgreSQL user is there.
>
> The "one click" installer does not result in the appearance of the
> "PostgreSQL" user account in the os x GUI.
>
> 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
finds a previous installation of PG hence tries to stop the existing pg
server 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.
> 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.
>
> Many thanks,
>
> - Mark
>
> On Jan 30, 2012, at 11:34 PM, Dharmendra Goyal wrote:
>
> Hi Mark,
>
> Install log shows that your db installation is successful. The error which
> you had sent is coming because your earlier installation failed to create
> 'postgres' user and when you ran the installer again, installer read
> /etc/postgres-reg.ini file to check any previous installation and found
> that previous installation was done. Hence installer tries to stop the db
> server in case it is running using postgres user. This command fails as
> postgres user was not created in your first installation because of some
> reason. But in latest installation (for which you have sent the log),
> postgres user has been created successfully and installation went
> successfully. You need to check why postgres user was not created in first
> go by checking logs of that installation.
>
> You are checking return status of the installbuilder.sh command run which
> 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
> installbuilder.sh.
>
> Regards,
>
> On Tue, Jan 31, 2012 at 5:37 AM, Mark Phillips <mark.phillips@mophilly.com
> > wrote:
>
>>
>> On Jan 29, 2012, at 11:07 PM, Dharmendra Goyal wrote:
>>
>> On Sat, Jan 21, 2012 at 3:01 AM, <mark.phillips@mophilly.com> wrote:
>>
>>> The following bug has been logged on the website:
>>>
>>> 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:
>>>
>>> for a stand alone app that uses postgres, the app installer invokes the
>>> shell script installbuilder.sh for the "unattended" install of postgres.
>>>
>>> The pg installer creates a user "PostgreSQL" that is not hidden, but does
>>> 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 under
>> /tmp/install-postgresql.log. Also if you can run
>> installation_path/installer/server/createuser.sh script manually and check
>> the output, it can be helpful.
>>
>> Thanks,
>> --
>> Dharmendra Goyal
>>
>>
>> Thank you for the reply. I apologize for the delay in responding.
>>
>> File install-postgresql.log attached.
>>
>> Please review the link below to a post in the postgresql forum for a bit
>> more detail about this issue:
>>
>> http://forums.enterprisedb.com/posts/list/3042.page
>>
>> 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.
>>
>> Beginning anew with a clean os install, I ran the app installer that
>> invokes the postgresql installer.
>>
>> Here is a snippet of the installer script that relates to installing
>> postgres:
>>
>> # 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=1610612736
>> sysctl -w kern.sysv.shmall=393216
>> sysctl -w kern.sysv.shmmin=1
>> sysctl -w kern.sysv.shmmni=32
>> sysctl -w kern.sysv.shmseg=8
>> sysctl -w kern.maxprocperuid=512
>> sysctl -w kern.maxproc=2048
>>
>> # install postgres
>>
>> cd "${BASE}"
>> log "change directory to ${BASE}"
>>
>> log "=== install DBMS engine ==="
>> postgresql-9.1.2-1-osx.app/Contents/MacOS/installbuilder.sh --mode
>> unattended --superaccount PostgresSQL --superpassword Omnis1
>> if [ $? != 0 ]; then
>> log "install of DBMS failed: ${?}"
>> exit 1
>> fi
>>
>> It appears execution stops there. The following is in the system log:
>>
>> 1/30/12 3:41:26.784 PM markphillips: PRM Installer: === install DBMS
>> engine ===
>> 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.app/Contents/MacOS/osx-intel
>> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorInvalidConnection:
>> CGSGetWindowTags: Invalid connection
>> 1/30/12 3:41:49.097 PM osx-intel: kCGErrorFailure: Set a breakpoint @
>> CGErrorBreakpoint() to catch errors as they are logged.
>>
>> 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.
>>
>> Thank you,
>>
>> - Mark
>>
>>
>>
>>
>>
>
>
> --
> Dharmendra Goyal
> Senior Software Engineer
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>
> Phone: +91-20-30589493
> Mobile: +91-9552103323
>
> Website: http://www.enterprisedb.com
> EnterpriseDB Blog: http://blogs.enterprisedb.com/
> Follow us on Twitter: http://www.twitter.com/enterprisedb
>
> 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
> information from EnterpriseDB Corporation that may be privileged,
> confidential, or exempt from disclosure under applicable law. If you are
> not the intended recipient or authorized to receive this for the intended
> recipient, any use, dissemination, distribution, retention, archiving, or
> copying of this communication is strictly prohibited. If you have received
> this e-mail in error, please notify the sender immediately by reply e-mail
> and delete this message.
>
>
>
--
Dharmendra Goyal
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise Postgres Company
Phone: +91-20-30589493
Mobile: +91-9552103323
Website: http://www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb
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
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
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