[RC3] Broken pipe when install a new database

[Christophe CHAUVET]

Server revno: 1704
Addons revno: 2194
Client revno: 929

Create a new database with "Service Profile"

--------------8<---------------8<-------------
[2009-02-06 01:37:22,652] INFO:init:module profile_service: registering objects
[2009-02-06 01:37:22,654] INFO:init:module profile_service: loading objects
[2009-02-06 01:37:22,662] INFO:init:module profile_service: creating or updating database tables
[2009-02-06 01:37:22,771] INFO:init:module profile_service: loading security/ir.model.access.csv
[2009-02-06 01:37:22,801] INFO:init:module profile_service: loading profile_service.xml
[2009-02-06 01:37:22,940] INFO:i18n:module profile_service: loading translation file for language fr_FR
[2009-02-06 01:37:23,577] INFO:init:[01]: Assertions report:
[2009-02-06 01:37:23,578] INFO:init:[02]: Level success failed
[2009-02-06 01:37:23,578] INFO:init:[03]: error 5 0
[2009-02-06 01:37:23,583] INFO:init:[04]: total 5 0
[2009-02-06 01:37:23,584] INFO:init:[05]: end of report (5 assertion(s) checked)
[2009-02-06 01:37:23,636] INFO:orm:Computing parent left and right for table account_account...
Exception in thread Thread-100:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/home/openerp/OpenERP/5.0/server/bin/netsvc.py", line 365, in run
    ts.mysend(result)
  File "/home/openerp/OpenERP/5.0/server/bin/tiny_socket.py", line 53, in mysend
    self.sock.send(exception and "1" or "0")
error: (32, 'Relais bris\xc3\xa9 (pipe)')
--------------8<---------------8<-------------

Distribution: Ubuntu
Version: 8.04 (hardy)
Python 2.5.2

[Christophe CHAUVET (christophe-chauvet)]

I have already a Timeout Message box on the GTK Client.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Sorry, I dont get such an error, i made 2 people check but I cant reproduce it.

Can you provide more info?

[Christophe CHAUVET (christophe-chauvet)]

This is an VirtualBox issue.

I follow it and post an answer after.

[Christophe CHAUVET (christophe-chauvet)]

Hi

The problem appear also with VMware Workstation and on a slow machine(It's not a virtual box problem ;) )
After 3 minutes on the GTK Client, i have a Timeout, but the server continue to install, after compute value "account.account" it fail with broken pipe.

[Christophe CHAUVET (christophe-chauvet)]

On a slow machine, install profile service with demo to reproduce.

[Davide Corio (enlightx-deactivatedaccount)]

is it possibile to increment the timeout value? i think this should be enough

[Christophe CHAUVET (christophe-chauvet)]

Patch add config value on .openerprc file

[Christophe CHAUVET (christophe-chauvet)]

By default the timeout value is 5 minutes.

[Fabien (Open ERP) (fp-tinyerp)]

upgrdaed to 200.

[Christophe CHAUVET (christophe-chauvet)]

Sorry Fabien but with my students when use it in VirtualBox (Network Security) to learn OpenERP, the minimal TimeOut is 8 Minutes when install Manufacturing profile.

It very usefull to apply my patch that can be defined the default timeout.

Thanks in advance,

[Carlos Liebana (carlos-liebana)]

Hi,

How can I do this now? The tiny_socket file has changed since 5.0.2 and there's no chance to make this hack in tiny_socket.py. I'm trying to fill an inventory, but we have more than 53.000 references and it crashes, returning that "Timed out error".

Any help is truly welcome!

Best regards!

[Jay Vora (Serpent Consulting Services) (jayvora)]

Hello Carlos,
Are you using an updated code?

[Carlos Liebana (carlos-liebana)]

Hi Jay,

I've tested with:
- 5.0.1 GTK and web clients
- 5.0.2 GTK client
- 5.0.5 GTK client

against a 5.0.1 server. I haven't been able to increment the timeout time with the new clients.

Thanks!

[Christophe CHAUVET (christophe-chauvet)]

Hi

Can you use import to made the inventory ?

Regards,

[Carlos Liebana (carlos-liebana)]

Mmm I haven't tried that...

[Carlos Liebana (carlos-liebana)]

Hello,

1) We're not able to import the inventory directly, we receive also a timeout error.
2) If we change the socket timeout in the tiny_socket.py of the server, after a 5 minutes we receive an error "socket communication broken", no matter the new time we change there. Always, around 5 minutes after the operation the error appears.

:(