| From: | Shani Israeli <sisraeli(at)illusivenetworks(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Date: | 2020-11-04 10:24:03 |
| Message-ID: | CAHwa7Ea1R7kYuyEOKU6LW-tYMXJAM30zy9K+4iYW5TykAgKDgQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| Attachment | Content-Type | Size |
|---|---|---|
| postgres.conf | application/octet-stream | 21.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2020-11-04 12:24:46 | Re: PANIC: could not write to log file {} at offset {}, length {}: Invalid argument |
| Previous Message | Magnus Hagander | 2020-11-04 09:16:04 | Re: CentOS 7 yum package systemd bug? |