| From: | David Day <djd2403(at)gmail(dot)com> |
|---|---|
| To: | Shani Israeli <sisraeli(at)illusivenetworks(dot)com> |
| Cc: | 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 13:42:04 |
| Message-ID: | CA+Biohef-ZTEVgxxkJ_fH2B+=Jkj6M-05CEHGWe-xVA5PUHbNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I Could not read your config file but
What is the size of the Postgres log file?
Do you have a log rotation policy on it?
Perhaps your Postgres log level is to high or your connections are
generating a lot of errors that need investigating.
Dave
On Wed, Nov 4, 2020 at 5:24 AM 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?
>
> Thanks is advance,
> Shani Israeli - Software Developer
>
> +972 54 6689920
> sisraeli(at)illusivenetworks(dot)com
> www.illusivenetworks.com
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-11-04 16:42:54 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Previous Message | Andreas Kretschmer | 2020-11-04 12:24:46 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |