Re: SOLVED - background writer process (PID 1400) exited

Reid Thompson wrote:
> PG_VERSION 8.1 - windows XP - 1GB RAM -- Desktop workstation, PG used
> for test/dev.
>
> This installation has been working fine for quite a while.  I've used
> it minimally.
>
> I rebooted yestderday- log file from reboot
> 2006-05-18 12:24:32 LOG:  database system was shut down at 2006-05-18
> 12:23:08 Eastern Daylight Time
> 2006-05-18 12:24:32 LOG:  checkpoint record is at 0/BD0966B0
> 2006-05-18 12:24:32 LOG:  redo record is at 0/BD0966B0; undo record is
> at 0/0; shutdown TRUE
> 2006-05-18 12:24:32 LOG:  next transaction ID: 386246; next OID: 37710
> 2006-05-18 12:24:32 LOG:  next MultiXactId: 1; next MultiXactOffset: 0
> 2006-05-18 12:24:32 LOG:  database system is ready
> 2006-05-18 12:24:32 LOG:  transaction ID wrap limit is 2147484148,
> limited by database "postgres"
>
>
> Today I am unable to connect to the DB.  Log file is filled with:
> 2006-05-19 09:24:09 LOG:  background writer process (PID 1400) exited
> with exit code 0
> 2006-05-19 09:24:09 LOG:  terminating any other active server processes
> 2006-05-19 09:24:09 LOG:  all server processes terminated; reinitializing
> 2006-05-19 09:24:11 LOG:  background writer process (PID 3012) exited
> with exit code 0
> 2006-05-19 09:24:11 LOG:  terminating any other active server processes
> 2006-05-19 09:24:11 LOG:  all server processes terminated; reinitializing
> 2006-05-19 09:24:13 LOG:  background writer process (PID 3076) exited
> with exit code 0
> 2006-05-19 09:24:13 LOG:  terminating any other active server processes
> 2006-05-19 09:24:13 LOG:  all server processes terminated; reinitializing
> 2006-05-19 09:24:15 LOG:  background writer process (PID 4756) exited
> with exit code 0
> 2006-05-19 09:24:15 LOG:  terminating any other active server processes
> 2006-05-19 09:24:15 LOG:  all server processes terminated; reinitializing
> 2006-05-19 09:24:17 LOG:  background writer process (PID 5644) exited
> with exit code 0
> 2006-05-19 09:24:17 LOG:  terminating any other active server processes
> 2006-05-19 09:24:17 LOG:  all server processes terminated; reinitializing
>
> I rebooted my system.  Logfile now shows a different error.  This
> error is generated when attempting to connect via either psql or
> PGAdminIII.
>
> 2006-05-19 09:42:26 LOG:  database system was shut down at 2006-05-19
> 09:17:34 Eastern Daylight Time
> 2006-05-19 09:42:26 LOG:  checkpoint record is at 0/BD0966F8
> 2006-05-19 09:42:26 LOG:  redo record is at 0/BD0966F8; undo record is
> at 0/0; shutdown TRUE
> 2006-05-19 09:42:26 LOG:  next transaction ID: 386246; next OID: 37710
> 2006-05-19 09:42:26 LOG:  next MultiXactId: 1; next MultiXactOffset: 0
> 2006-05-19 09:42:26 LOG:  database system is ready
> 2006-05-19 09:42:26 LOG:  transaction ID wrap limit is 2147484148,
> limited by database "postgres"
> 2006-05-19 09:49:38 LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>   2006-05-19 09:49:38 LOG:  incomplete startup packet
> 2006-05-19 09:50:54 LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>   2006-05-19 09:50:54 LOG:  incomplete startup packet
> 2006-05-19 09:51:29 LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>   2006-05-19 09:51:29 LOG:  incomplete startup packet
> 2006-05-19 09:56:22 LOG:  could not receive data from client: No
> connection could be made because the target machine actively refused it.
>
>   2006-05-19 09:56:22 LOG:  incomplete startup packet
>
> MS firewall is OFF.
> Un-installing and re-installing is fine.  But if there's anything that
> I can provide prior to that for debugging, etc, I am willing to do so.
> ( If i can 'fix' it w/o re-installing it would be nice too ).
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
Resolution:
  NOD32 antivirus software IMON component configured to ignore
postmaster.exe and postgres.exe.  PostgreSQL now appears to be running
as before.