| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| 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 12:24:46 |
| Message-ID: | 58D3BF80-A360-4E40-883A-B3DE64DE1189@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4 November 2020 11:24:03 CET, Shani Israeli <sisraeli(at)illusivenetworks(dot)com> 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?
wild guess: Antivirus Software?
>
>Thanks is advance,
>Shani Israeli - Software Developer
>
>+972 54 6689920
>sisraeli(at)illusivenetworks(dot)com
>www.illusivenetworks.com
--
2ndQuadrant - The PostgreSQL Support Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Day | 2020-11-04 13:42:04 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Previous Message | Shani Israeli | 2020-11-04 10:24:03 | PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |