Re: postgresql log file not getting update
От | Chris |
---|---|
Тема | Re: postgresql log file not getting update |
Дата | |
Msg-id | 5592DBEE-A0FA-4387-B42D-A90F1A0B39F0@eisonline.co.za обсуждение исходный текст |
Ответ на | Re: postgresql log file not getting update (Anson Abraham <anson.abraham@gmail.com>) |
Ответы |
Re: postgresql log file not getting update
(Anson Abraham <anson.abraham@gmail.com>)
|
Список | pgsql-general |
On Feb 28, 2013, at 19:01, Anson Abraham <anson.abraham@gmail.com> wrote: > *Note when I change=20 > log_destination =3D 'syslog' >=20 > it does log to the syslog file. >=20 > When I changed to to log_destination =3D 'stderr' still nothing logged. >=20 > commenting out doesn't do much either. I initially thought it would be a p= erms thing, but when I deleted the file and did a reload, postgres created t= he log file. So not sure what is going on exactly. >=20 > Again, any help would be appreciated here to figure this out, where I don'= t need to restart the db. > Thanks >=20 > On Thu, Feb 28, 2013 at 11:19 AM, Anson Abraham <anson.abraham@gmail.com> w= rote: >> My postgresql-9.0-main.log file has suddenly stopped getting updated. I d= o not know why it stopped all of a sudden. We made a slight modification=20= >> where changed in the postgresql.conf param:=20 >> From >> log_connections =3D off >> log_disconnections =3D off >>=20 >> To >>=20 >> log_connections =3D on >> log_disconnections =3D on >>=20 >> I'm on a debian environment w/ version 9.0.7. It's a single instance w/ n= o cluster on here. It was done w/a simple apt-get install back when, when i= t was a fresh server (we'll call this db1) >>=20 >> I have an identical setup for another server (db4), and when I made the c= hange to the same paramers in conf, it's updating the postgresql-9.0-main.lo= g 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 l= og file is getting updated db1 nothing. I thought the file was locked or so= me 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 th= e new file, but still nothing getting written to it. >>=20 >> I know first thing people would say is to restart the instance, but resta= rting is not an option for me in this case. >>=20 >> I've changed >> ucommented out this param >> #log_destination =3D 'stderr' >>=20 >> to be stderr, and even syslog and did a reload and nothing. >>=20 >>=20 >> I know i should use log collector, but again, that also requires a restar= t as well, unless a reload will work? >>=20 >> The way I reload is /etc/init.d/postgresql reload >>=20 >> The distro for Debian is squeeze. Again, it works on my other server, th= is server it doesn't. Any one have any ideas, where I don't need to restart= the pg instance? =46rom the bin directory you can do: pg_ctl reload -D (followed by the data d= ierctory) >> Thanks in advance. >> -Anson >=20
В списке pgsql-general по дате отправления: