| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Shani Israeli <sisraeli(at)illusivenetworks(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Date: | 2020-11-04 16:42:54 |
| Message-ID: | d0fa9613-97c2-9a78-a704-fd03464d90e6@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/4/20 2:24 AM, Shani Israeli wrote:
> Hi all,
>
> We are running PostgreSQL v9.5.19 over Windows Server 2012 R2, 16GB RAM.
> Lately, postgres started to crash (happened already 3 times ~once a
> month) and before its crashes I found this message in Event Log:
>
> PANIC: could not write to log file {} at offset {}, length {}:
> Invalid argument
>
> (so I assumed it is related).
>
> attached is our configuration.
>
> Any ideas about what is the problem? or anything else I need to check?
Any time I see seemingly random crashes involving file corruption on
Windows I think anti-virus software. Has someone turned an AV program
loose on this machine?
>
> Thanks is advance,
> Shani Israeli - Software Developer
> +972 54 6689920
>
> sisraeli(at)illusivenetworks(dot)com
>
> www.illusivenetworks.com <https://www.illusivenetworks.com/>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brad Nicholson | 2020-11-04 20:09:40 | Race condition with restore_command on streaming replica |
| Previous Message | David Day | 2020-11-04 13:42:04 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |