Re: Unattended Installation

Many thanks to Igor

The hint with the "bitrock" installer log helped me to find the problem.
It was an incorrect path setting (double backslash). The UI-Installer
might correct these settings.

Regards, Peter.

Quoting Igor Neyman <ineyman@perceptron.com>:

>> -----Original Message-----
>> From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-
>> owner@postgresql.org] On Behalf Of shetty65
>> Sent: Tuesday, April 01, 2014 3:13 AM
>> To: pgsql-general@postgresql.org
>> Subject: [GENERAL] Unattended Installation
>>
>> Hello
>>
>> I am using Postgres 9.3.3.1 on Windows (32-Bit Windows 7 Professional).
>> I use the installer executable postgresql-9.3.3-1-windows.exe with the
>> option "--optionfile <file>"
>>
>> The option file has the following content (the ${..} are replaced
>> with correct
>> values before execution):
>>  #mode=unattended
>>  datadir=${program.base}data
>>  prefix=${program.base}
>>  serverport=${postgres.port}
>>  superaccount=postgres
>>  superpassword=${postgres.passwd}
>>  unattendedmodeui=minimalWithDialogs
>>  servicename=${postgres.service.name}
>>
>> 1) If the "mode" property is enabled to mode=unattended, the installation
>> works silent but the whole 'data' folder is missing after
>> installation (the first
>> error message will occur when the server-startup failes after installation).
>>
>> 2) If the "mode" property is disabled, the Installer interface appears.
>> Everything is correctly set, I need only to press the <next> button. The
>> Installation completes correctly.
>>
>> Why does my unattended installation as described in 1) fail, but 2)
>> succeeds?
>>
>> Thank you in advance for the help
>> Peter.
>>
>
> Here are options that I use for unattended install (and it creates
> cluster with Postgres, template0, and template1 databases, which
> means data directory and all its subdirectories are created too):
>
> SET INSTALLOPTIONS=--unattendedmodeui none
> SET INSTALLOPTIONS=%INSTALLOPTIONS% --mode unattended
>
> Also, you are missing settings for servicesaccount, servicepassword,
> and locale, e.g.:
> SET INSTALLOPTIONS=%INSTALLOPTIONS% --locale C
> SET INSTALLOPTIONS=%INSTALLOPTIONS% --serviceaccount postgres
> SET INSTALLOPTIONS=%INSTALLOPTIONS% --servicepassword pg_password123
>
> In general, to diagnose (silent or not) installation problems find
> "bitrock" installer log somewhere under DocumentsandSettings for OS
> user that runs installation.
>
> Regards,
> Igor Neyman
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general