Comment 9 for bug 713216

Revision history for this message
Raphaƫl Valyi - http://www.akretion.com (rvalyi) wrote : Re: [Bug 713216] Re: MRP Locks down server

>
> So, a few points to consider:
> - are you totally unable to login() during these problems?

Sometimes not at all

> What is the load
> of the system at that time? (we want to see if it's PG locks or python GIL)
>

This typically looks like 60% Python 40% Postgres, possibly spit in two
processes or more

> - does the system recover by itself, or needs some intervention (restart
> of
> server eg.)
>

In some situations I've seen with the MRP yes: after the MRP cron ends, you
can connect. Notice that I had similar issues on v5 already so it doesn't
sounds it's a regression.

> - do the ecommerce connectors, by any means, touch the res.users table?
>

I doubt this is related at all. The reason I cited ecommerces is that you'll
easily import many confirmed orders and thus MRP will be heavier, but it's
juts the regular MRP or other processes that create the lock.

> - please, try to run the query Odo gave you, while the lockups are
> happening.
> - can you count the threads of the openerp-server process?
>

I'm currently not experiencing such issues with MRP (because I did the clean
up with OOOR on our installs), but eventually I'll do it for the other bugs
I reported. Kyle, I let you put your data in your case.

> --
> You received this bug notification because you are subscribed to OpenERP
> Server.
> https://bugs.launchpad.net/bugs/713216
>
> Title:
> Cannot login while MRP scheduler is running
>
> Status in OpenERP Server:
> Incomplete
>
> Bug description:
> When using the Manufacturing scheduler in a medium sized environment
> the scheduler will lock down the server in a way where not a single
> user may connect to the server. The login window shows up but when you
> type your password and click login it goes to a white screen and
> nothing happens, because the manufacturing scheduler is preventing the
> server from letting anyone log in. If you were already logged in then
> you can use the program. Quite frustrating. Sure the manufacturing
> scheduler is supposed to run at night, but that is still a bug.
>