Page 3 of 3
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/15 14:20:30
by TrevorH
I suspect the issue is that you've added that directory to your PATH or to some LD_LIBRARY* variable so that it's being searched automatically and ahead of the /lib64. Yes, removing the whole package is likely to fix it but that's quite a big hammer.
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/17 06:09:25
by hemanthbitra
Now it's working fine after uninstalling Postgre Enterprise version
Thanks,
Hemanth BITRA.
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/17 06:10:35
by hemanthbitra
Is there is any way to prevent this issue before installing Postgres enterprise version.
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/17 06:17:48
by TrevorH
Yes. Don't add the /opt/postgresql directories to your PATH or any LD_LIBRARY* environment variables.
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/17 06:27:03
by hemanthbitra
TrevorH wrote:Yes. Don't add the /opt/postgresql directories to your PATH or any LD_LIBRARY* environment variables.
I didn't add path to environment variable but postgres enterprise application itself creating some profile like profile_sql.sh
while installing in /opt
Re: Automatic Bug reporting Tool Crashed
Posted: 2017/05/17 06:42:21
by TrevorH
Then it's broken and you should report it to the people that created it.
Re: Automatic Bug reporting Tool Crashed
Posted: 2018/05/26 18:18:10
by hemanthbitra
TrevorH wrote:Then it's broken and you should report it to the people that created it.
Hello TrevorH.
This issue is resolved after uninstalling postgres enterprise application.
Regards,
Hemanth.