Обсуждение: Postgesql and SSL
Hello, I am trying to run PostgreSQL with SSL, so I compiled and linked with options: ./configure --prefix=/DB --with-openssl Configured and installed successfully. In postgresql.conf I have option "ssl = on" When starting Postgres I get error: LOG: SSL is not supported by this build FATAL: invalid value for parameter "ssl": 1 DEBUG: proc_exit(1) DEBUG: shmem_exit(1) DEBUG: exit(1) Where is the problem? Is here versions which does not support SSL, it would be strange.. Versions used: PostgreSQL 8.3.4 OpenSSL 0.9.8j -- Lukas UAB nSoft http://www.nsoft.lt Lukas at nsoft.lt +370 655 10 655 -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.
You defo have all the required openssl headers and libs and configure succeeds? It's a longshot, but I wonder if the prefixis somehow making configure read the string wrong? I've never really needed to use prefix, but what happend if youtry ./configure --prefix='/DB' --with-openssl or perhaps ./configure --with-openssl --prefix=/DB --- On Sat, 28/2/09, Lukas <Lukas@fmf.vtu.lt> wrote: > From: Lukas <Lukas@fmf.vtu.lt> > Subject: [ADMIN] Postgesql and SSL > To: pgsql-admin@postgresql.org > Date: Saturday, 28 February, 2009, 10:18 PM > Hello, > > I am trying to run PostgreSQL with SSL, so I compiled and > linked with > options: > > ./configure --prefix=/DB --with-openssl > > Configured and installed successfully. > In postgresql.conf I have option "ssl = on" > When starting Postgres I get error: > LOG: SSL is not supported by this build > FATAL: invalid value for parameter "ssl": 1 > DEBUG: proc_exit(1) > DEBUG: shmem_exit(1) > DEBUG: exit(1) > > Where is the problem? Is here versions which does not > support SSL, it > would be strange.. > > Versions used: > PostgreSQL 8.3.4 > OpenSSL 0.9.8j > > > > -- > Lukas > UAB nSoft > http://www.nsoft.lt > Lukas at nsoft.lt > +370 655 10 655 > > > > > -- > This message has been scanned for viruses and > dangerous content by > OpenProtect(http://www.openprotect.com), and is > believed to be clean. > > > -- > Sent via pgsql-admin mailing list > (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin
Hello again, nope, no use of it.. Situation stays the same.. Does any one have more ideas? -- Lukas UAB nSoft http://www.nsoft.lt Lukas at nsoft.lt +370 655 10 655 > You defo have all the required openssl headers and libs and configure > succeeds? It's a longshot, but I wonder if the prefix is somehow making > configure read the string wrong? I've never really needed to use prefix, > but what happend if you try > > ./configure --prefix='/DB' --with-openssl > > or perhaps > > ./configure --with-openssl --prefix=/DB > > > > --- On Sat, 28/2/09, Lukas <Lukas@fmf.vtu.lt> wrote: > >> From: Lukas <Lukas@fmf.vtu.lt> >> Subject: [ADMIN] Postgesql and SSL >> To: pgsql-admin@postgresql.org >> Date: Saturday, 28 February, 2009, 10:18 PM >> Hello, >> >> I am trying to run PostgreSQL with SSL, so I compiled and >> linked with >> options: >> >> ./configure --prefix=/DB --with-openssl >> >> Configured and installed successfully. >> In postgresql.conf I have option "ssl = on" >> When starting Postgres I get error: >> LOG: SSL is not supported by this build >> FATAL: invalid value for parameter "ssl": 1 >> DEBUG: proc_exit(1) >> DEBUG: shmem_exit(1) >> DEBUG: exit(1) >> >> Where is the problem? Is here versions which does not >> support SSL, it >> would be strange.. >> >> Versions used: >> PostgreSQL 8.3.4 >> OpenSSL 0.9.8j >> >> >> >> -- >> Lukas >> UAB nSoft >> http://www.nsoft.lt >> Lukas at nsoft.lt >> +370 655 10 655 >> >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by >> OpenProtect(http://www.openprotect.com), and is >> believed to be clean. >> >> >> -- >> Sent via pgsql-admin mailing list >> (pgsql-admin@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-admin > > > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > > -- > This message has been scanned for viruses and > dangerous content by OpenProtect(http://www.openprotect.com), and is > believed to be clean. > > -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.
have you generated the ssl certificates too? --- On Sun, 1/3/09, Lukas <Lukas@fmf.vtu.lt> wrote: > From: Lukas <Lukas@fmf.vtu.lt> > Subject: Re: [ADMIN] Postgesql and SSL > To: pgsql-admin@postgresql.org > Date: Sunday, 1 March, 2009, 8:37 AM > Hello again, > > nope, no use of it.. Situation stays the same.. Does any > one have more > ideas? > > > -- > Lukas > UAB nSoft > http://www.nsoft.lt > Lukas at nsoft.lt > +370 655 10 655 > > > > You defo have all the required openssl headers and > libs and configure > > succeeds? It's a longshot, but I wonder if the > prefix is somehow making > > configure read the string wrong? I've never really > needed to use prefix, > > but what happend if you try > > > > ./configure --prefix='/DB' --with-openssl > > > > or perhaps > > > > ./configure --with-openssl --prefix=/DB > > > > > > > > --- On Sat, 28/2/09, Lukas <Lukas@fmf.vtu.lt> > wrote: > > > >> From: Lukas <Lukas@fmf.vtu.lt> > >> Subject: [ADMIN] Postgesql and SSL > >> To: pgsql-admin@postgresql.org > >> Date: Saturday, 28 February, 2009, 10:18 PM > >> Hello, > >> > >> I am trying to run PostgreSQL with SSL, so I > compiled and > >> linked with > >> options: > >> > >> ./configure --prefix=/DB --with-openssl > >> > >> Configured and installed successfully. > >> In postgresql.conf I have option "ssl = > on" > >> When starting Postgres I get error: > >> LOG: SSL is not supported by this build > >> FATAL: invalid value for parameter > "ssl": 1 > >> DEBUG: proc_exit(1) > >> DEBUG: shmem_exit(1) > >> DEBUG: exit(1) > >> > >> Where is the problem? Is here versions which does > not > >> support SSL, it > >> would be strange.. > >> > >> Versions used: > >> PostgreSQL 8.3.4 > >> OpenSSL 0.9.8j > >> > >> > >> > >> -- > >> Lukas > >> UAB nSoft > >> http://www.nsoft.lt > >> Lukas at nsoft.lt > >> +370 655 10 655 > >> > >> > >> > >> > >> -- > >> This message has been scanned for viruses and > >> dangerous content by > >> OpenProtect(http://www.openprotect.com), and is > >> believed to be clean. > >> > >> > >> -- > >> Sent via pgsql-admin mailing list > >> (pgsql-admin@postgresql.org) > >> To make changes to your subscription: > >> http://www.postgresql.org/mailpref/pgsql-admin > > > > > > > > > > -- > > Sent via pgsql-admin mailing list > (pgsql-admin@postgresql.org) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-admin > > > > -- > > This message has been scanned for viruses and > > dangerous content by > OpenProtect(http://www.openprotect.com), and is > > believed to be clean. > > > > > > > > -- > This message has been scanned for viruses and > dangerous content by > OpenProtect(http://www.openprotect.com), and is > believed to be clean. > > > -- > Sent via pgsql-admin mailing list > (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin
Lukas schrieb: > nope, no use of it.. Situation stays the same.. Does any one have more > ideas? [...] >>> I am trying to run PostgreSQL with SSL, so I compiled and >>> linked with >>> options: >>> >>> ./configure --prefix=/DB --with-openssl >>> >>> Configured and installed successfully. >>> In postgresql.conf I have option "ssl = on" >>> When starting Postgres I get error: >>> LOG: SSL is not supported by this build >>> FATAL: invalid value for parameter "ssl": 1 >>> DEBUG: proc_exit(1) >>> DEBUG: shmem_exit(1) >>> DEBUG: exit(1) >>> >>> Where is the problem? Is here versions which does not >>> support SSL, it >>> would be strange.. >>> >>> Versions used: >>> PostgreSQL 8.3.4 >>> OpenSSL 0.9.8j well, probably; in a situation like this I'd first check for any errors from the configure step. Did it by any chance complain about not finding the SSL library? Next thing to check: is the postmaster linked against the SSL library? cd /your/postgres/install/path/bin ldd postgres|grep ssl should output something like libssl.so.0.9.7 => /usr/lib64/libssl.so.0.9.7 (0x0000002a95775000) if not, SSL is likely not compiled in; go back to checking the configure part. If you have positively confirmed, that SSL support is compiled in, you likely simply don't use your newly built postgres. Check paths and start scripts and make sure, it uses your new built binaries. If that's not it, I think you have to provide more information about your platform. Ciao, Thomas
Thomas Pundt <mlists@rp-online.de> writes: > Lukas schrieb: >>> I am trying to run PostgreSQL with SSL, so I compiled and >>> linked with >>> options: >>> ./configure --prefix=/DB --with-openssl > well, probably; in a situation like this I'd first check for any errors > from the configure step. Yeah. I would say this is pilot error somewhere along the line: either the configure/build process failed, or you forgot to "make install" afterwards, or the copy of the postmaster you're trying to start isn't the one you built. Given the nonstandard install location specified above, the last one seems particularly likely. regards, tom lane
Hi, i had the same problem building using latest cvs, it works fine on 64-bit ubuntu, but on 32-bit ubuntu (virtualbox) when i started the postgres it shows: # idir=/home/`whoami`/Software/PostgreSQL-9 # sudo su -p postgres -c "$idir/bin/postgres -D $idir/data" ; LOG: SSL is not supported by this build FATAL: invalid value for parameter "ssl": 1 * normally on my 64-bit, it shows: LOG: database system was shut down at 2010-03-19 12:02:00 WIT LOG: autovacuum launcher started LOG: database system is ready to accept connections ... query errors goes here ...^C LOG: received fast shutdown request LOG: aborting any active transactions LOG: autovacuum launcher shutting down LOG: shutting down LOG: database system is shut down * my configuration (32-bit and 64-bit differ only on shared_buffers value) # idir=/home/`whoami`/Software/PostgreSQL-9 # sudo cat $idir/data/postgresql.conf | egrep -v "^\s*(#|$)" listen_addresses = 'localhost' # what IP address(es) to listen on; port = 5432 # (change requires restart) max_connections = 100 # (change requires restart) unix_socket_directory = '/tmp' # (change requires restart) ssl = true # (change requires restart) password_encryption = on shared_buffers = 28MB # min 128kB datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' # locale for system error message lc_monetary = 'en_US.UTF-8' # locale for monetary formatting lc_numeric = 'en_US.UTF-8' # locale for number formatting lc_time = 'en_US.UTF-8' # locale for time formatting default_text_search_config = 'pg_catalog.english' * my build configuration: # idir=/home/`whoami`/Software/PostgreSQL-9 # ./configure --with-pam --with-openssl --with-libxml --with-libxslt --prefix=$idir && make && make install * installed libraries (dpkg -l | grep ssl): libssl-dev 0.9.8g-16ubuntu3.1 openssl 0.9.8g-16ubuntu3.1 libssl0.9.8 0.9.8g-16ubuntu3.1 * full script for download, compile and configuring http://pastebin.com/vmzryH82 -- Regards, Kiswono P GB
oh yeah i forgot to show you that it's linked successfully: # sudo ldd /home/`whoami`/Software/PostgreSQL-9/bin/* | grep ssl libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00cc4000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00214000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00e9b000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x0044f000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x0061b000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x004fb000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00b1a000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00284000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00135000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x004b6000) libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00603000) On Fri, Mar 19, 2010 at 1:33 PM, Kiswono Prayogo <kiswono@gmail.com> wrote: > Hi, i had the same problem building using latest cvs, it works fine on > 64-bit ubuntu, but on 32-bit ubuntu (virtualbox) when i started the > postgres it shows: > # idir=/home/`whoami`/Software/PostgreSQL-9 > # sudo su -p postgres -c "$idir/bin/postgres -D $idir/data" ; > LOG: SSL is not supported by this build > FATAL: invalid value for parameter "ssl": 1 > > * normally on my 64-bit, it shows: > LOG: database system was shut down at 2010-03-19 12:02:00 WIT > LOG: autovacuum launcher started > LOG: database system is ready to accept connections > ... query errors goes here ...^C > LOG: received fast shutdown request > LOG: aborting any active transactions > LOG: autovacuum launcher shutting down > LOG: shutting down > LOG: database system is shut down > > * my configuration (32-bit and 64-bit differ only on shared_buffers value) > # idir=/home/`whoami`/Software/PostgreSQL-9 > # sudo cat $idir/data/postgresql.conf | egrep -v "^\s*(#|$)" > listen_addresses = 'localhost' # what IP address(es) to listen on; > port = 5432 # (change requires restart) > max_connections = 100 # (change requires restart) > unix_socket_directory = '/tmp' # (change requires restart) > ssl = true # (change requires restart) > password_encryption = on > shared_buffers = 28MB # min 128kB > datestyle = 'iso, mdy' > lc_messages = 'en_US.UTF-8' # locale for system > error message > lc_monetary = 'en_US.UTF-8' # locale for monetary formatting > lc_numeric = 'en_US.UTF-8' # locale for number formatting > lc_time = 'en_US.UTF-8' # locale for time formatting > default_text_search_config = 'pg_catalog.english' > > * my build configuration: > # idir=/home/`whoami`/Software/PostgreSQL-9 > # ./configure --with-pam --with-openssl --with-libxml --with-libxslt > --prefix=$idir && make && make install > > * installed libraries (dpkg -l | grep ssl): > libssl-dev 0.9.8g-16ubuntu3.1 > openssl 0.9.8g-16ubuntu3.1 > libssl0.9.8 0.9.8g-16ubuntu3.1 > > * full script for download, compile and configuring > http://pastebin.com/vmzryH82 > > -- > Regards, > Kiswono P > GB > -- Regards, Kiswono P GB
for complete build log: http://pastebin.com/UfVFixQY and there are no errors T^T i didn't understand where is the possible cause of the problem.. any help, welcome ^^ thank you in advance.. On Fri, Mar 19, 2010 at 1:48 PM, Kiswono Prayogo <kiswono@gmail.com> wrote: > oh yeah i forgot to show you that it's linked successfully: > > # sudo ldd /home/`whoami`/Software/PostgreSQL-9/bin/* | grep ssl > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00cc4000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00214000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00e9b000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x0044f000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x0061b000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00110000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x004fb000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00b1a000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00284000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00135000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x004b6000) > libssl.so.0.9.8 => /lib/i686/cmov/libssl.so.0.9.8 (0x00603000) > -- Regards, Kiswono P GB
ok, please ignore this thread ^^ now i know that i shouldn't using code from cvs anyway.. On Fri, Mar 19, 2010 at 2:14 PM, Kiswono Prayogo <kiswono@gmail.com> wrote: > for complete build log: > http://pastebin.com/UfVFixQY > > and there are no errors T^T > i didn't understand where is the possible cause of the problem.. > any help, welcome ^^ thank you in advance.. > -- Regards, Kiswono P GB