Search Postgresql Archives

Re: postgresql log file not getting update

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



how is that different from
/etc/init.d/postgres reload or for that matter select pg_reload_conf() ?

Which I execute both and they don't work either.

On Thu, Feb 28, 2013 at 12:43 PM, Chris <chris@xxxxxxxxxxxxxxx> wrote:


On Feb 28, 2013, at 19:01, Anson Abraham <anson.abraham@xxxxxxxxx> wrote:

*Note when I change 
log_destination = 'syslog'

it does log to the syslog file.

When I changed to to log_destination = 'stderr'  still nothing logged.

commenting out doesn't do much either. I initially thought it would be a perms thing, but when I deleted the file and did a reload, postgres created the log file.  So not sure what is going on exactly.

Again, any help would be appreciated here to figure this out, where I don't need to restart the db.
Thanks

On Thu, Feb 28, 2013 at 11:19 AM, Anson Abraham <anson.abraham@xxxxxxxxx> wrote:
My postgresql-9.0-main.log file has suddenly stopped getting updated.  I do not know why it stopped all of a sudden.  We made a slight modification 
where changed in the postgresql.conf param: 
From
log_connections = off
log_disconnections = off

To

log_connections = on
log_disconnections = on

I'm on a debian environment w/ version 9.0.7.  It's a single instance w/ no cluster on here.  It was done w/a simple apt-get install back when, when it was a fresh server (we'll call this db1)

I have an identical setup for another server (db4), and when I made the change to the same paramers in conf, it's updating the postgresql-9.0-main.log file.  I reverted the connections and discon from on back to off, and did a postgresql reload as well as pg_reload_conf().  For both servers.  db4 the log file is getting updated db1 nothing.  I thought the file was locked or some perms may have changed and I deleted the postgresql-9.0-main.log file. It didn't create a new log file until i did a postgresql reload. It created the new file, but still nothing getting written to it.

I know first thing people would say is to restart the instance, but restarting is not an option for me in this case.

I've changed
ucommented out this param
#log_destination = 'stderr'

to be stderr, and even syslog and did a reload and nothing.


I know i should use log collector, but again, that also requires a restart as well, unless a reload will work?

The way I reload is /etc/init.d/postgresql reload

The distro for Debian is squeeze.  Again, it works on my other server, this server it doesn't.  Any one have any ideas, where I don't need to restart the pg instance?

From the bin directory you can do: pg_ctl reload -D (followed by the data dierctory)
Thanks in advance.
-Anson



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux