Thread: still having pg_user error
Well I re-installed Fedora 3 and updated my postgres and started the service (no command line stuff).
When I connected using pgadmin I still got the sp_user error.
I am brand new to both linux and postgres and am a bit frustrated as I have spent the entire day getting no where.
Is there a step by step instruction for using postgres on fedora 3 anywhere?
What I did seemed simple enough using the graphical interface I added the postgres components and put in CD3 then I used the up2date thing, then I started the service.
Obviously I am missing a important step (I realize I have to edit the ph_hba.conf file, but it was not there until after I started the service. I stopped the service and added a host line and edited postgres.conf to allow tcpip sockets.
I hate to not get further tonight as it takes all night to move the data and I wanted to be moving views tomorrow, but I guess I will just have to try again tomorrow.
Joel Fradkin
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
© 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
This email message is for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message, including attachments.
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Well I re-installed Fedora 3 and updated my postgres and started the =
> service
> (no command line stuff).
> When I connected using pgadmin I still got the sp_user error.
Fedora 3? You should've mentioned that before. I'll bet you've got
SELinux enabled in enforcement mode. SELinux interferes with initdb
and I believe a missing pg_user view is one of the symptoms.
This is fixed in the very latest postgresql and selinux-policy-targeted
RPMs (u need both), but the path of least resistance is often to dial
SELinux down to permissive mode (sudo /usr/sbin/setenforce 0) for long
enough to do the initdb.
If you're running SELinux in strict rather than targeted policy, good
luck ... I honestly haven't tried that one at all ...
regards, tom lane
Tom thank you for the reply.
I believe I turned all that off during the install (no firewall).
But I can try again.
Is there an action I can take now since it is installed and in theory the
RPM's are up2date. Sorry I have a few books on postgres Oreily and Sams, but
it seems a bit deep on install.
At the very least I guess I can do a backup of the database, wipe everything
/var/lib/pgsql/data and try the initd thing (verify SELinux is off; not sure
how I do that, but I will look at the command you mentioned).
I am very happy with my progress thus far (have most of my data coming
over), but I am frustrated on my lack of knowledge. I have administered
Linux before but its been several years and I don't remember much.
I am very impressed with the progress with admin tools and such, I just wish
I had a clear idea of the path to get a development postgres box up on
fedora and am more then a little worried about administering the production
(we ordered a 4 processor Dell with Red HAT, I believe I will also need to
install it).
Again thank you for that piece of advice, I can always re-install Linux and
verify the SELinux option is off, maybe I messed up again.
Joel Fradkin
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, IncThis email message is for the use of the intended recipient(s)
andmay
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, January 21, 2005 12:48 AM
To: Joel Fradkin
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] still having pg_user error
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Well I re-installed Fedora 3 and updated my postgres and started the =
> service
> (no command line stuff).
> When I connected using pgadmin I still got the sp_user error.
Fedora 3? You should've mentioned that before. I'll bet you've got
SELinux enabled in enforcement mode. SELinux interferes with initdb
and I believe a missing pg_user view is one of the symptoms.
This is fixed in the very latest postgresql and selinux-policy-targeted
RPMs (u need both), but the path of least resistance is often to dial
SELinux down to permissive mode (sudo /usr/sbin/setenforce 0) for long
enough to do the initdb.
If you're running SELinux in strict rather than targeted policy, good
luck ... I honestly haven't tried that one at all ...
regards, tom lane
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Is there an action I can take now since it is installed and in theory the
> RPM's are up2date. Sorry I have a few books on postgres Oreily and Sams, but
> it seems a bit deep on install.
Sure, you can use the RPMs you have. You want something like (as root)
service postgresql stoprm -rf /var/lib/pgsql/datasetenforce 0service postgresql start
The start script will observe that there's no database directory and
proceed to run initdb for you.
regards, tom lane
Finally I think that did the trick.
I did see the GUI editor for security and set SELinux to off and re-booted.
I ran the rpm text you gave me
I can use pgadmin with no errors, now for another 12 hours of transferring
data :( so I can work on the views and stored procedures.
This list is a great resource and I appreciate all the ideas comments and
help it has made the difference for me.
Joel Fradkin
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, IncThis email message is for the use of the intended recipient(s)
andmay
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, January 21, 2005 9:17 AM
To: Joel Fradkin
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] still having pg_user error
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Is there an action I can take now since it is installed and in theory the
> RPM's are up2date. Sorry I have a few books on postgres Oreily and Sams,
but
> it seems a bit deep on install.
Sure, you can use the RPMs you have. You want something like (as root)
service postgresql stoprm -rf /var/lib/pgsql/datasetenforce 0service postgresql start
The start script will observe that there's no database directory and
proceed to run initdb for you.
regards, tom lane