I found this problem two weeks ago in a project,and then go to other
team.Environment and machine has been changed after.
so I cannot test now.Colleague told me this problem has been resolved by other
pepole.
I read the config of selinux.It changed as you said.
SELINUX=enforcing
changed to
SELINUX=disabled
Have no test,but I think this is the reason why I cannot execute DBI-connect in
my program.
Thank you very mach.
regards,
Li Hongbing
----- Original Message -----
From: "Craig Ringer" <cr...@postnewspapers.com.au>
To: "李紅兵" <lihongb...@intasect.com.cn>
Cc: "John R Pierce" <pie...@hogranch.com>; <pgsql-bugs@postgresql.org>
Sent: Wednesday, May 11, 2011 5:18 PM
Subject: Re: [BUGS] BUG #5994: Can't excute DBI->connect to oracle by client
site
On 05/11/2011 03:13 PM, 李紅兵 wrote:
yes,I am sure that I connect to the same database and same machine.
because I run my test code at the linux server with telnet.
As you said,it likes some security modules inhibit to make a new
connection.
My server is Redhat Linux Enterprice version with typical
installation.and I don't know about
SELinux/Apparmor/TOMOYO/SMACK
If you're running on RHEL, you're using SELinux.
For a test, you could set SELinux policy to audit mode (ie: not enforcing) and see if you still have the problem. If the problem
goes away that way, you know you need to tweak your SELinux policies or set an SELinux boolean.
See the SELinux documentation to learn more.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs