Re: [GENERAL] Weird periodical pg log

2017-05-19 Thread cen
Hmm indeed that seems to be the case. Thanks for the tip! On 05/19/2017 04:10 PM, John R Pierce wrote: On 5/19/2017 1:25 AM, cen wrote: < 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command" changed to ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup" I believe /opt/omni is the

Re: [GENERAL] Weird periodical pg log

2017-05-19 Thread John R Pierce
On 5/19/2017 1:25 AM, cen wrote: < 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command" changed to ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup" I believe /opt/omni is the default installation path for HP Data Protector, formerly known as OmniBack. That comprehensive

Re: [GENERAL] Weird periodical pg log

2017-05-19 Thread Adrian Klaver
On 05/19/2017 01:25 AM, cen wrote: Every single day at exactly the same hour I get this in my pg_log: < 2017-05-15 17:00:29.517 CEST >FATAL: pg_hba.conf rejects connection for host "...", user "postgres", database "template1", SSL off < 2017-05-15 17:00:29.571 CEST >WARNING: archive_mode

Re: [GENERAL] Weird periodical pg log

2017-05-19 Thread Karsten Hilbert
On Fri, May 19, 2017 at 10:25:13AM +0200, cen wrote: > < 2017-05-15 17:00:41.861 CEST >LOG: parameter "archive_command" changed to > ""/opt/omni/lbin/pgsqlbar.exe" -stage %p -backup" This is the line that you'll have to base your research on. Also, you might want to check for a keylogger in

[GENERAL] Weird periodical pg log

2017-05-19 Thread cen
Every single day at exactly the same hour I get this in my pg_log: < 2017-05-15 17:00:29.517 CEST >FATAL: pg_hba.conf rejects connection for host "...", user "postgres", database "template1", SSL off < 2017-05-15 17:00:29.571 CEST >WARNING: archive_mode enabled, yet archive_command is not