| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Turn Jensen <thomas(at)turn(dot)dk> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1861: Possible Incompatibly with NOD32 AV. |
| Date: | 2005-09-03 14:28:29 |
| Message-ID: | 200509031428.j83ESTF08671@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I would contact the people who created NOD32, give them the URL to
pginstaller, and tell them it breaks PostgreSQL.
---------------------------------------------------------------------------
Thomas Turn Jensen wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1861
> Logged by: Thomas Turn Jensen
> Email address: thomas(at)turn(dot)dk
> PostgreSQL version: 8.0.3
> Operating system: Windows XP SP2
> Description: Possible Incompatibly with NOD32 AV.
> Details:
>
> I'm aware this will not be a "complete" bug report with all neccesary
> information. I have not tried to reproduce the problem but am satisfied I
> found a solution. The reason I make this bug report is a result of someone
> (rightly) saying "im not sure who you would mail but i think it needs
> documenting.." after the fact. Since I know of no better means of
> documenting it, I use this approach.
>
>
> PROBLEM:
> After installing NOD32 antivirus (www.nod32.com) PostgreSQL no longer
> works.
>
> SYMPTOMS:
> Any application trying to connect/log into PG freezes. Only a termination of
> the PG service will unfreeze the applications with an error about unexpected
> EOF from socket (or something to that effect. Sorry, I don't have the exact
> message).
>
> Log in pg_log/postrgresql-#date-#postfix contains the following entries for
> every frozen application:
> 2005-09-03 02:46:11 LOG: could not receive data from client: No connection
> could be made because the target machine actively refused it.
> 2005-09-03 02:46:11 LOG: incomplete startup packet
>
> POSSIBLE MITIGATING FACTORS:
> NOD32 was installed together with PC-cillin 2002 (AV). However only NOD32
> was active. Disabling NOD32 did not have any effect.
> "Google Desktop" reports possible conflicts with NOD32.
>
> WORKARROUND:
> After uninstalling NOD32 and rebooting, PG works as expected.
>
> SELECT version():
> PostgreSQL 8.0.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2
> (mingw-special)
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | al979663 | 2005-09-03 18:26:41 | Error number -2147467259 with driver PgOleDb |
| Previous Message | Dick Kniep | 2005-09-03 09:46:05 | Re: BUG #1858: setting search path in select doesn't (always) work |