Re: [ADMIN] [GENERAL] postgresql Secure Mode
LOG Say: LOG: conexión recibida: host=192.168.0.100 port=1175 FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», usuario «vasa», base de datos «vasa», SSL inactivo LOG: conexión recibida: host=192.168.0.100 port=1226 FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», usuario «vasa», base de datos «vasa», SSL inactiv but SSl its active select * from pg_settings where name = 'ssl' ssl on Connections and Authentication / Security and Authentication Enables SSL connections. postmaster boolconfiguration file thank you 2005/8/8, Mario Soto Cordones - Venezuela <[EMAIL PROTECTED]>: > Hola Alvaro no po lostee en espanol porque pense que este problema > correspondia a la lista de admin, o me equivoco > > Saludos > > > 2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > > On Mon, Aug 08, 2005 at 11:06:22AM -0400, Mario Soto Cordones - Venezuela > > wrote: > > > 2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > > > > On Mon, Aug 08, 2005 at 10:24:54AM -0400, Mario Soto Cordones - > > > > Venezuela wrote: > > > > > > > but when I try to connect myself for example from an application EMS > > > > > postgresql manager by means of SSL, says that it cannot authenticate > > > > > in user > > > > > > > > Ok, so do you have the user created in Postgres by means of CREATE USER > > > > or createuser? Try changing the password. Also, please show us the > > > > relevant extract of the server log file. > > > > > > yes expample the user is vasa > > > > > > the log say > > > > > > LOG: no se pudo cargar el archivo del certificado raiz > > > /var/lib/pgsql/data/bd/root.crt > > > DETALLE: Los certificados de clientes no se verificaran > > > > This isn't the problem. Here it's only telling you that were the client > > to hand a certificate, they wouldn't be checked. There must be other > > message. > > > > > but I don't understand because it leaves that message > > > > It's because you don't have the root.crt file, or the file doesn't have > > the proper permissions. > > > > > > I don't understand why didn't you post this problem to pgsql-es-ayuda > > first ... > > > > -- > > Alvaro Herrera () > > Y dijo Dios: "Que sea Satanás, para que la gente no me culpe de todo a mí." > > "Y que hayan abogados, para que la gente no culpe de todo a Satanás" > > > > > -- > cordialmente, > > Ing. Mario Soto Cordones > -- cordialmente, Ing. Mario Soto Cordones ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [ADMIN] [GENERAL] postgresql Secure Mode
Mario Soto Cordones - Venezuela <[EMAIL PROTECTED]> writes: > LOG Say: > LOG: conexión recibida: host=192.168.0.100 port=1175 > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > usuario «vasa», base de datos «vasa», SSL inactivo > LOG: conexión recibida: host=192.168.0.100 port=1226 > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > usuario «vasa», base de datos «vasa», SSL inactiv > but SSl its active What that's showing is that the client isn't trying to use SSL. So either you have client-side code that's not SSL-aware at all, or the configuration problem is on the client side. regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [ADMIN] [GENERAL] postgresql Secure Mode
On Mon, Aug 08, 2005 at 11:41:24AM -0400, Mario Soto Cordones - Venezuela wrote: > LOG Say: > > LOG: conexión recibida: host=192.168.0.100 port=1175 > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > usuario «vasa», base de datos «vasa», SSL inactivo > LOG: conexión recibida: host=192.168.0.100 port=1226 > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > usuario «vasa», base de datos «vasa», SSL inactiv > > but SSl its active Yeah, the server thinks it's active, but the client doesn't know it. Did you try connecting with psql? Maybe your EMS client does not support SSL (it'd surprise me.) -- Alvaro Herrera () "Las cosas son buenas o malas segun las hace nuestra opinión" (Lisias) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [ADMIN] [GENERAL] postgresql Secure Mode
2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > On Mon, Aug 08, 2005 at 11:41:24AM -0400, Mario Soto Cordones - Venezuela > wrote: > > LOG Say: > > > > LOG: conexión recibida: host=192.168.0.100 port=1175 > > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > > usuario «vasa», base de datos «vasa», SSL inactivo > > LOG: conexión recibida: host=192.168.0.100 port=1226 > > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > > usuario «vasa», base de datos «vasa», SSL inactiv > > > > but SSl its active > > Yeah, the server thinks it's active, but the client doesn't know it. > Did you try connecting with psql? Maybe your EMS client does not > support SSL (it'd surprise me.) Yes EMS suport this but say unable to autenticate user thank > > -- > Alvaro Herrera () > "Las cosas son buenas o malas segun las hace nuestra opinión" (Lisias) > -- cordialmente, Ing. Mario Soto Cordones ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [ADMIN] [GENERAL] postgresql Secure Mode
On Mon, Aug 08, 2005 at 12:24:14PM -0400, Mario Soto Cordones - Venezuela wrote: > 2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > > On Mon, Aug 08, 2005 at 11:41:24AM -0400, Mario Soto Cordones - Venezuela > > wrote: > > > LOG Say: > > > > > > LOG: conexión recibida: host=192.168.0.100 port=1175 > > > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > > > usuario «vasa», base de datos «vasa», SSL inactivo > > > LOG: conexión recibida: host=192.168.0.100 port=1226 > > > FATAL: no hay una lÃnea en pg_hba.conf para «192.168.0.100», > > > usuario «vasa», base de datos «vasa», SSL inactiv > > > > > > but SSl its active > > > > Yeah, the server thinks it's active, but the client doesn't know it. > > Did you try connecting with psql? Maybe your EMS client does not > > support SSL (it'd surprise me.) > > Yes EMS suport this but say unable to autenticate user Maybe you have to enable it explicitly? Maybe it's not supported in the free (lite) version? Again, did you try with psql? -- Alvaro Herrera () "La felicidad no es mañana. La felicidad es ahora" ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [ADMIN] [GENERAL] postgresql Secure Mode
On Mon, Aug 08, 2005 at 01:03:03PM -0400, Mario Soto Cordones - Venezuela wrote: > from the server I connect with psql and makes it > > bash-3.00$ psql -U vasa -h 192.168.0.2 vasa > Contraseña: > Bienvenido a psql 8.0.3, el terminal interactivo de PostgreSQL. > > Digite: \copyright para ver los tÃ(c)rminos de distribución > \h para obtener ayuda sobre comandos SQL > \? para obtener ayuda sobre comandos internos > \g o punto y coma (;) para ejecutar consulta > \q para salir > > conexión SSL (cifrado: DHE-RSA-AES256-SHA, bits: 256) Ok, so it works with psql and the server is configured correctly. Congratulations! > 2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > > > Maybe you have to enable it explicitly? Maybe it's not supported in the > > free (lite) version? Again, did you try with psql? > > the EMS it's professional edition licenced Since you have a EMS license, you can complain to those guys, since obviously the problem is with their client software. -- Alvaro Herrera () "Es filósofo el que disfruta con los enigmas" (G. Coli) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] Restore from pg_dumpall
>From: Jeff Frost [mailto:[EMAIL PROTECTED] >What are you upgrading from/to? Can you share your dump and restore command line as well? I am upgrading from Gforge 3.0b1 to Gforge 4.5.0.1. Unfortunately, I don't have the dump and restore in my buffer, but I ran "pg_dumpall > backup.dump" and then I tried to upgrade Gforge and I got errors, so I freaked out and decided to restore before trying again. I then ran "pg_restore -c backup.dump" and it told me the file wasn't an archive so it wouldn't restore. >From: Tom Lane >Nothing ... in any PG version newer than 7.3 or so. Are you trying to back-port a dump into an older >server version, and if so why? I don't think I'm back-porting a dump. I don't even know what that means exactly. All I want to do is upgrade to Gforge 4.5.0.1. However, I *feel* I jacked up the DB in the process, so now I just want to restore from my dump and then try upgrading again. Thanks for all your help guys. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [ADMIN] Restore from pg_dumpall
On Mon, 8 Aug 2005, Buorn, Yoway wrote: Unfortunately, I don't have the dump and restore in my buffer, but I ran "pg_dumpall > backup.dump" and then I tried to upgrade Gforge and I got errors, so I freaked out and decided to restore before trying again. I then ran "pg_restore -c backup.dump" and it told me the file wasn't an archive so it wouldn't restore. There's your problem (or at least one of them). The pg_dumpall outputs straight SQL to stdout to recreate all DBs. To restore this, you would just do the following: psql template1 < backup.dump pg_restore is looking for one of the other output formats (tar or custom). -- Jeff Frost, Owner <[EMAIL PROTECTED]> Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 650-780-7908 FAX: 650-649-1954 ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[ADMIN] Trouble Getting Database Server Started
Trouble Getting Database Server Started I'm no longer able to connect to the database with psql. PostgreSQL 8.0.0 was included as part of a software package I'm using to collect environmental data. It is a very simple logging application - mostly a single simple table with timestamp and 6 integers in each record and on the order of 50K records over the past 3 weeks. I'm using version 8.0.0 on Windows XP Pro. The vendor install script for the application installs the database as a Win32 Serviceto be launched when Windows boots up. I don't have access to the details of theinstall procedure. It has been working fine for 3 weeks but one morning the computer(I'll refer to it as Computer A) was found powered down and since then I've no longer been able to connect to the database. I see from the Postgres archives that one can simply take a copy of the installed PostgreSQL directory folder and move it in place of the PostsgreSQL folder on a working system. I took another computer (Computer B) and ran the same installation script and tested to verify I could connect with psql. Window's Task Manager showed 6 postgres processes: postmaster.exe, pg_ctl.exe, and 4 postgres.exe. (Not sure what the 4 postgres.exe are for.) I next replaced the PostgreSQL folder with the one from my Computer A holding my collected data. After rebooting Computer B, Task Manager shows only postmaster.exe and pg_ctl.exe. I still can't connect with psql. Since I had a file system backup of Computer A from about a week prior when everything was working fine, I tried to see if I could get the archived PostgreSQL directory towork on Computer B. It also showed just postmaster.exe and pg_ctl.exe running and psqlcould not connect either. I don't know what caused Computer A to power down. It is in a lab and someone may have inadvertently cut the power. Would that corrupt the database to the point where I can't connect to it or its startup mechanism be disrupted? I don't know what role those 4postgres.exe processes fill - are they part of standard postgres startup? Secondly, Idon't know why sliding in the archived PostgreSQL folder on Computer B did not work. Please let me know if further details are required. Thanks in advance for any help,Dirk Kalp
Re: [ADMIN] Trouble Getting Database Server Started
Hi Dirk: I have been seeing similar problems if PC pwered down rather than using the Windows shut down facility. In my case the user which suppose to start the service loses "Logon as service" right therefore service can not be started. On your computer A, check to see if the database service was started or not. If not then give the user which suppose to start the service "logon as service" rigth again and try to re-start the service. The service should start. Once the service is started your front end programe should be able to connect to backend database. Hope this helps. Karim > Trouble Getting Database Server Started > > I'm no longer able to connect to the database with psql. PostgreSQL 8.0.0 > was included as part of a software package I'm using to collect > environmental > data. It is a very simple logging application - mostly a single simple > table > with timestamp and 6 integers in each record and on the order of 50K > records > over the past 3 weeks. I'm using version 8.0.0 on Windows XP Pro. > > The vendor install script for the application installs the database as a > Win32 Service > to be launched when Windows boots up. I don't have access to the details > of the > install procedure. It has been working fine for 3 weeks but one morning > the computer > (I'll refer to it as Computer A) was found powered down and since then > I've no > longer been able to connect to the database. > > I see from the Postgres archives that one can simply take a copy of the > installed > PostgreSQL directory folder and move it in place of the PostsgreSQL folder > on a > working system. I took another computer (Computer B) and ran the same > installation > script and tested to verify I could connect with psql. Window's Task > Manager showed > 6 postgres processes: postmaster.exe, pg_ctl.exe, and 4 postgres.exe. (Not > sure what > the 4 postgres.exe are for.) > > I next replaced the PostgreSQL folder with the one from my Computer A > holding my > collected data. After rebooting Computer B, Task Manager shows only > postmaster.exe > and pg_ctl.exe. I still can't connect with psql. > > Since I had a file system backup of Computer A from about a week prior > when everything > was working fine, I tried to see if I could get the archived PostgreSQL > directory to > work on Computer B. It also showed just postmaster.exe and pg_ctl.exe > running and psql > could not connect either. > > I don't know what caused Computer A to power down. It is in a lab and > someone may have > inadvertently cut the power. Would that corrupt the database to the point > where I can't > connect to it or its startup mechanism be disrupted? I don't know what > role those 4 > postgres.exe processes fill - are they part of standard postgres startup? > Secondly, I > don't know why sliding in the archived PostgreSQL folder on Computer B did > not work. > > Please let me know if further details are required. > > Thanks in advance for any help, > Dirk Kalp > Regards, Karim Mardhani ZeeCore Consulting ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [ADMIN] [GENERAL] postgresql Secure Mode
On Mon, Aug 08, 2005 at 12:40:24PM -0400, Alvaro Herrera wrote: > On Mon, Aug 08, 2005 at 12:24:14PM -0400, Mario Soto Cordones - Venezuela > wrote: > > 2005/8/8, Alvaro Herrera <[EMAIL PROTECTED]>: > > > > > Yeah, the server thinks it's active, but the client doesn't know it. > > > Did you try connecting with psql? Maybe your EMS client does not > > > support SSL (it'd surprise me.) > > > > Yes EMS suport this but say unable to autenticate user > > Maybe you have to enable it explicitly? Maybe it's not supported in the > free (lite) version? Again, did you try with psql? On private email exchange we found out that the culprit is pgOleDb, which doesn't support SSL connections. -- Alvaro Herrera () "There was no reply" (Kernel Traffic) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[ADMIN] REVOKE from all tables ...
Is there a way of REVOKEing privileges on all tables in a database? I've checked the REVOKE man page, and there doesn't appear to be, but I figured I'd double check to make sure ... ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [ADMIN] REVOKE from all tables ...
Marc G. Fournier wrote: Is there a way of REVOKEing privileges on all tables in a database? I've checked the REVOKE man page, and there doesn't appear to be, but I figured I'd double check to make sure ... No. This has actually been a requested feature on the grant side as well... Nothing a simple for loop can't do with perl though. ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [ADMIN] REVOKE from all tables ...
On Mon, 8 Aug 2005, Joshua D. Drake wrote: Marc G. Fournier wrote: Is there a way of REVOKEing privileges on all tables in a database? I've checked the REVOKE man page, and there doesn't appear to be, but I figured I'd double check to make sure ... No. This has actually been a requested feature on the grant side as well... Nothing a simple for loop can't do with perl though. Ya, that is what I did, it just seemed that there should be a much simplier way of doing it :( Ah well, at least I wasn't re-creating the wheel on this one :) Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
