Just to inform u that my log Yesterday didn't show any 'recovery' which is
the main goal of this post.
Looks like the script was causing the issue, I test and change it to the
one from Scott I'.
On odoo I switch user sessions from default value 1 week(:-/) to 1 hour.
I found that option in the f
2016-10-10 21:43 GMT+02:00 Periko Support :
> For the life time in odoo session, can u point me where I can manage that
> setting?
>
> The configuration /etc/openerp-server.conf doesn't have any parameter for
> that.
>
> That must be in a odoo file...?
>
https://www.odoo.com/forum/help-1/question
Scott your script is very clean, I'm testing, thanks.
On Mon, Oct 10, 2016 at 3:28 PM, Scott Mead wrote:
>
>
> On Mon, Oct 10, 2016 at 6:15 PM, Tom Lane wrote:
>>
>> Adrian Klaver writes:
>> > On 10/10/2016 12:18 PM, Periko Support wrote:
>> >> I was on vacation, but the issue have the same beh
On Mon, Oct 10, 2016 at 6:15 PM, Tom Lane wrote:
> Adrian Klaver writes:
> > On 10/10/2016 12:18 PM, Periko Support wrote:
> >> I was on vacation, but the issue have the same behavior:
>
> > Actually no. Before you had:
>
> > 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
> > termi
Adrian Klaver writes:
> On 10/10/2016 12:18 PM, Periko Support wrote:
>> I was on vacation, but the issue have the same behavior:
> Actually no. Before you had:
> 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
> terminated by signal 9: Killed
> Now you have:
> 2016-10-10 07:50:09
Adrian
2016-10-10 12:00:01 PDT LOG: connection authorized: user=openerp
database=template1
2016-10-10 12:00:01 PDT LOG: server process (PID 30394) was
terminated by signal 9: Killed
2016-10-10 12:00:01 PDT DETAIL: Failed process was running: SELECT
"name", "model", "description", "month" FROM "
> On 10 Oct 2016, at 21:43, Periko Support wrote:
>
> For the life time in odoo session, can u point me where I can manage that
> setting?
>
> The configuration /etc/openerp-server.conf doesn't have any parameter for
> that.
>
> That must be in a odoo file...?
>
> Thanks.
>
> On Mon, Oct 1
On 10/10/2016 12:18 PM, Periko Support wrote:
I was on vacation, but the issue have the same behavior:
Actually no. Before you had:
2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
terminated by signal 9: Killed
Now you have:
2016-10-10 07:50:09 PDT WARNING: terminating connecti
For the life time in odoo session, can u point me where I can manage that
setting?
The configuration /etc/openerp-server.conf doesn't have any parameter for
that.
That must be in a odoo file...?
Thanks.
On Mon, Oct 10, 2016 at 12:25 PM, Pavel Stehule
wrote:
>
>
> 2016-10-10 21:12 GMT+02:00 Pe
That script was from a vendor called 'allianzgrp.com'.
Was their solution.
Them I have a lot of work to do here.
On Mon, Oct 10, 2016 at 12:32 PM, Alban Hertroys wrote:
>
>> On 10 Oct 2016, at 21:28, Alban Hertroys wrote:
>>
>>
>>> On 10 Oct 2016, at 21:12, Periko Support wrote:
>>>
>>>fo
> On 10 Oct 2016, at 21:28, Alban Hertroys wrote:
>
>
>> On 10 Oct 2016, at 21:12, Periko Support wrote:
>>
>>for pid in idle_record:
>>try:
>> #print "process details",pid
>> #os.system("kill -9 %s" % (int(pid[0]), ))
>>os.kill(int(pid[0]), sig
> On 10 Oct 2016, at 21:12, Periko Support wrote:
>
> for pid in idle_record:
> try:
> #print "process details",pid
> #os.system("kill -9 %s" % (int(pid[0]), ))
> os.kill(int(pid[0]), signal.SIGKILL)
> except OSError as ex:
> co
2016-10-10 21:12 GMT+02:00 Periko Support :
> Andreo u got a good observation here.
>
> I got a script that run every hour why?
>
> Odoo got some issues with IDLE connections, if we don't check our current
> psql connections after a while the system eat all connections and a lot of
> them are IDLE
I was on vacation, but the issue have the same behavior:
2016-10-10 07:50:09 PDT WARNING: terminating connection because of
crash of another server process
2016-10-10 07:50:09 PDT DETAIL: The postmaster has commanded this
server process to roll back the current transaction and exit, because
anot
Andreo u got a good observation here.
I got a script that run every hour why?
Odoo got some issues with IDLE connections, if we don't check our current
psql connections after a while the system eat all connections and a lot of
them are IDLE and stop answering users, we create a script that runs e
On 10/10/2016 11:14 AM, Moreno Andreo wrote:
Il 10/10/2016 18:24, Periko Support ha scritto:
2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
terminated by signal 9: Killed
2016-09-12 10:00:01 PDT LOG: server process (PID 30766) was
terminated by signal 9: Killed
2016-09-12 1
Periko Support writes:
> My current server has 82GB memory.
You said this was running inside a VM, though --- maybe the VM is
resource-constrained?
In any case, turning off memory overcommit would be a good idea if
you're not concerned about running anything but Postgres.
On Mon, Oct 10, 2016 at 2:14 PM, Moreno Andreo
wrote:
>
> Il 10/10/2016 18:24, Periko Support ha scritto:
>
>> 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
>> terminated by signal 9: Killed
>>
>
> 2016-09-12 10:00:01 PDT LOG: server process (PID 30766) was
>> terminated by signal
Il 10/10/2016 18:24, Periko Support ha scritto:
2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
terminated by signal 9: Killed
2016-09-12 10:00:01 PDT LOG: server process (PID 30766) was
terminated by signal 9: Killed
2016-09-12 15:00:01 PDT LOG: server process (PID 22030) w
Or add more memory to my server?
On Mon, Oct 10, 2016 at 11:05 AM, Periko Support
wrote:
> My current server has 82GB memory.
>
> Default settings but the only parameter I had chance is shared_buffers
> from 128MB to 6G.
>
> This server is dedicated to postgresql+odoo.
>
> Is the only parameter I
My current server has 82GB memory.
Default settings but the only parameter I had chance is shared_buffers
from 128MB to 6G.
This server is dedicated to postgresql+odoo.
Is the only parameter I can thing can reduce my memory utilization?
Thanks Tom.
On Mon, Oct 10, 2016 at 10:03 AM, Tom Lane
Periko Support writes:
> I got some issues with my DB under ubuntu 14.x.
> PSQL 9.3, odoo 7.x.
> 2016-09-12 09:00:01 PDT LOG: server process (PID 23958) was
> terminated by signal 9: Killed
Usually, SIGKILLs coming out of nowhere indicate that the Linux OOM killer
has decided to target some dat
I want to add my server load normally, please see attachment, thanks.
On Mon, Oct 10, 2016 at 9:24 AM, Periko Support
wrote:
> I got some issues with my DB under ubuntu 14.x.
> PSQL 9.3, odoo 7.x.
>
> This machine is under KVM with centos 6.x
>
> It has a Raid1 with ssd drives only for this
I got some issues with my DB under ubuntu 14.x.
PSQL 9.3, odoo 7.x.
This machine is under KVM with centos 6.x
It has a Raid1 with ssd drives only for this vm.
I detect some unexpected shutdows, see this lines:
2016-09-12 08:59:25 PDT ERROR: missing FROM-clause entry for table
"rp" at characte
24 matches
Mail list logo
