Re: Why are there pg_dump errors in my Apache httpd error_log ? (Postgres 8.3.7 on CentOS 5)

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why are there pg_dump errors in my Apache httpd error_log ? (Postgres 8.3.7 on CentOS 5)
Date: 2009-11-03 21:17:11
Message-ID: d17c5b140911031317w5406878fqa43df13f296cfa7f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you for your replies. We don't have a CMS and none of our PHP
scripts call pg_dump so I am concerned about the security of our
system.

On Tue, Nov 3, 2009 at 1:00 PM, Russell Smith <mr-russ(at)pws(dot)com(dot)au> wrote:
> Aleksey Tsalolikhin wrote:
>>
>> # grep pg_dump /var/log/httpd/error_log
>> pg_dump: [archiver] could not open output file: Permission denied
>> pg_dump: [archiver] could not open output file: Permission denied
>> pg_dump: [archiver] could not open output file: Permission denied
>> pg_dump: [archiver] could not open output file: Permission denied
>> pg_dump: server version: X.X.X; pg_dump version: Y.Y.Y
>> pg_dump: aborting because of version mismatch  (Use the -i option to
>> proceed anyway.)
>>
> These are definitely outputs from phppgadmin.

How can you tell, please? It looks like output form pg_dump to me.

We don't have phppgadmin installed on this system.

# find / -print|grep -i phppgadmin
#

Anyway, "grep -r pg_dump $DOCROOT" turned up that one of our PHP
developers was trying to do a pg_dump in his code before making
changes "just in case, so he could roll back".

Sigh of relief. Wipes sweat off brow.

Thanks all. :)

Best,
-at

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Arnold, Sandra 2009-11-03 21:52:39 Re: Enabling Server Instrumentation on 8.4.1
Previous Message Russell Smith 2009-11-03 21:00:36 Re: Why are there pg_dump errors in my Apache httpd error_log ? (Postgres 8.3.7 on CentOS 5)