Enclosing parts of the log - I see a hint to increase max_wal_size
And also these lines:
2018-05-11 07:03:59 UTC [16449-2] LOG: server process (PID 18016) was
terminated by signal 9: Killed
2018-05-11 07:03:59 UTC [16449-3] DETAIL: Failed process was running:
create index "in_uidlevel4_ax_2015
It will most likely be a memory issue which gets exhausted at the same
place each time. The log should be in standard place of
/var/log/postgreswl/ etc. Not really anything to do with tools.
On Thu, 10 May 2018, 22:00 Knut Staring, wrote:
> Thanks Bob, I will try, but where is the postgresql log
Thanks Bob, I will try, but where is the postgresql log file in your setup
(with dhis2-tools)?
The strange thing is that everything else works up until the last part of
aggregation. In other words, I can do this again and again,
Knut
On Thu, May 10, 2018 at 6:19 PM, Bob Jolliffe wrote:
> Your
Your database has popped 😕
To find out why take a look in the postgresql log file around the same
time.
On Thu, 10 May 2018, 13:51 Knut Staring, wrote:
> Hi all,
>
> Wondering if anyone has a tip for what is going wrong on my serer. I just
> tested running Analytics in 2.29 with the same db on
Hi all,
Wondering if anyone has a tip for what is going wrong on my serer. I just
tested running Analytics in 2.29 with the same db on my laptop and there
were no issues, but everytime I try to do this on the server, it gives me
the following:
INFO 2018-05-10 08:06:51,987 [Level: INFO, category
5 matches
Mail list logo
