Re: BUG #5008: Server Startup Problem - When server is configured for SSL

On Tue, Aug 25, 2009 at 08:11, Jalaj Negi<jalajsinghnegi@gmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05008
> Logged by: =A0 =A0 =A0 =A0 =A0Jalaj Negi
> Email address: =A0 =A0 =A0jalajsinghnegi@gmail.com
> PostgreSQL version: 8.4.0
> Operating system: =A0 Windows XP with SP3
> Description: =A0 =A0 =A0 =A0Server Startup Problem - When server is confi=
gured for
> SSL
> Details:
>
> I am running PostgreSQL version 8.4.0 on Windows XP machine with SP3. I
> installed using Win32 Installer Package and the server runs as a service =
and
> a service account was automatically created by the Win32 installer package
> during server installation.
>
> With default configuration the server was running fine and took minimal t=
ime
> to start up (2-3 seconds). But when I configured server for SSL and
> restarted server it took long time to start up (3-4 minutes) and displayed
> the following startup message.
>
>
> Startup Message
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> The PostgreSQL Server 8.4 service is
> starting...................................
> ..
> The PostgreSQL Server 8.4 service could not be started.
>
> The service did not report an error.
>
> More help is available by typing NET HELPMSG 3534.
>
> The start command returned an error (2)
>
> Press <return> to continue...
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
>
> Exact Steps
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> 1) Stopped the server.
>
> 2) Made following changes in configuration files for enabling SSL support.
>
> In pg_hba.conf I have only following one entry -
> hostssl all =A0all =A0127.0.0.1/32 =A0md5 clientcert=3D1
>
> In postgresql.conf I made following changes -
> ssl =3D on
> ssl_ciphers =3D 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH'
>
> Added server.crt, server.key, root.crt, root.crl in servers data director=
y.
>
> 3) Started the server.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
>
> Few Observations
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> 1) When server starts with default configuration (without SSL configurati=
on
> changes) following process are created and running in system - pg_ctl.exe=
 (1
> instance), postgres.exe (6 instances).
>
> 2) When server starts with SSL configuration changes following process are
> created and running in system - postgres.exe (6 instances). This time
> pg_ctl.exe process is absent.
>
> 3) Server starts properly when "clientcert=3D1" is removed from pg_hba.co=
nf
> file. But if we want server to request client certificates we cant remove
> clientcert parameter from pg_hba.conf file.

What's in the log? Check both the PostgreSQL logfile and the Windows eventl=
og.

--=20
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/