On Wednesday 22 December 2010, you wrote: > may be the export code can check for the DB dump file size and give a > better hint. ... it's likely that everyone who stores (larger) images will > run into such (now known) problems
Well, I have not figured out what the limit is so far. But I'm sure that all protocols (Net-RPC, XML-RPC, Pyro ;) ) have some limit, perhaps depending on other thinks like python version, platform etc. Even if we allowed dbs < Limit to be dumped, that would be a dangerous practice, because an admin would setup that and forget to check his backups the day they cross the limit. It's all dictated by Murphy's Law. So, my advice: Just don't use the client facility for backups. Use pg_dump or continuous backup/replication at the server side. and, by all means: always check your backups! The fact that you had left a backup script running for months doesn't guarrantee you that your data will be available, when you will eventually need them! -- You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. https://bugs.launchpad.net/bugs/614937 Title: backup database unpickling stack underflow Status in OpenObject Server: Incomplete Bug description: Traceback (most recent call last): File "/usr/lib64/python2.5/threading.py", line 486, in __bootstrap_inner self.run() File "/home/terp/OpenERP/branch/server/5.0/bin/netsvc.py", line 400, in run ts.mysend(result) File "/home/terp/OpenERP/branch/server/5.0/bin/tiny_socket.py", line 56, in mysend sent = self.sock.send(msg[totalsent:]) error: (32, 'Broken pipe') the error seems to happen during or after the transfer of the dump to the client. BTW backup of other databases of this server work in the problematic db some images are stored _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
