Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AssertionError: Module ZODB.blob, line 435, in getPathForOID #309

Open
zopyx opened this issue May 12, 2020 · 1 comment
Open

AssertionError: Module ZODB.blob, line 435, in getPathForOID #309

zopyx opened this issue May 12, 2020 · 1 comment

Comments

@zopyx
Copy link
Member

zopyx commented May 12, 2020

I am getting this error with ZODB 5.5.1 (Python 3) as part of a Plone migration.

Not sure if this is related to a low memory situation (14,2 GB out of 15,7 GB RAM used, 15 GB free on disk (blobstorage)

2020-05-12 09:37:45,454 ERROR   [Zope.SiteErrorLog:251][waitress] 1589269065.4233440.9204063557356513 http://localhost:20081/plone_portal/img/dbz/diversiteit-en-gender/ugentinzicht/POST_application_json_
Traceback (innermost last):
  Module ZPublisher.WSGIPublisher, line 162, in transaction_pubevents
  Module transaction._manager, line 252, in commit
  Module transaction._manager, line 131, in commit
  Module transaction._transaction, line 311, in commit
  Module transaction._compat, line 50, in reraise
  Module transaction._transaction, line 302, in commit
  Module transaction._transaction, line 447, in _commitResources
  Module transaction._compat, line 50, in reraise
  Module transaction._transaction, line 421, in _commitResources
  Module ZODB.Connection, line 497, in commit
  Module ZODB.Connection, line 546, in _commit
  Module ZODB.Connection, line 595, in _store_objects
  Module ZODB.mvccadapter, line 170, in storeBlob
  Module ZEO.ClientStorage, line 586, in storeBlob
  Module ZODB.blob, line 435, in getPathForOID

https://github.com/zopefoundation/ZODB/blob/master/src/ZODB/blob.py#L429-L437

@mgedmin
Copy link
Member

mgedmin commented May 12, 2020

That is evil code, it ought to ignore errno.EEXISTS and re-raise on any other error. It should at least log about the exception it got!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants