Ticket #10248 (reopened Bug)
ValueError: database_name 'share' already in databases
Reported by: | neaj | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | General | Version: | 3.3 |
Keywords: | Cc: | mamico |
Description (last modified by kleist) (diff)
Previously logged at https://bugs.launchpad.net/plone/+bug/397385 Opening a bug here on Limi's request.
This is biting me almost every time I startup a Zope instance with Plone sites in mounted storages. Don't know if it's relevant, but the filesystem on this box is quite slow.
Here are relevant bits from the log. Zope 2.9.9.
2010-01-27T05:11:04 INFO ZServer HTTP server started at Wed Jan 27 05:11:04 2010 Hostname: 0.0.0.0 Port: 12101 ------ 2010-01-27T05:11:04 INFO ZServer ICP server started Address: 0.0.0.0 Port: 7102 ------ [...] 2010-01-27T05:11:33 INFO Zope Ready to handle requests ------ 2010-01-27T05:11:33 INFO ZODB.lock_file locked <open file '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock', mode 'r+' at 0xb714aa88> ------ 2010-01-27T05:11:33 WARNING ZODB.lock_file failed to lock <open file '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock', mode 'r+' at 0xb477e5c0> ------ 2010-01-27T05:11:33 WARNING ZODB.lock_file failed to lock <open file '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock', mode 'r+' at 0xb477e890> ------ 2010-01-27T05:11:33 WARNING ZODB.lock_file failed to lock <open file '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock', mode 'r+' at 0xb477e8d8> ------ [...] ------ 2010-01-27T05:14:32 ERROR Zope.ZODBMountPoint Failed to mount database. exceptions.OSError ([Errno 2] No such file or directory: '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock') Traceback (most recent call last): File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 257, in _getOrOpenObject conn = self._getMountedConnection(anyjar) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 147, in _getMountedConnection self._getDB() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 157, in _getDB return getConfiguration().getDatabase(self._path) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 280, in getDatabase db = factory.open(name, self.databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 178, in open DB = self.createDB(database_name, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 175, in createDB return ZODBDatabase.open(self, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/config.py", line 107, in open storage.close() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/FileStorage/FileStorage.py", line 400, in close self._lock_file.close() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/lock_file.py", line 79, in close os.unlink(self._path) OSError: [Errno 2] No such file or directory: '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock' ------ 2010-01-27T05:14:53 ERROR Zope.ZODBMountPoint Failed to mount database. exceptions.OSError ([Errno 2] No such file or directory: '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock') Traceback (most recent call last): File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 257, in _getOrOpenObject conn = self._getMountedConnection(anyjar) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 147, in _getMountedConnection self._getDB() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 157, in _getDB return getConfiguration().getDatabase(self._path) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 280, in getDatabase db = factory.open(name, self.databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 178, in open DB = self.createDB(database_name, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 175, in createDB return ZODBDatabase.open(self, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/config.py", line 107, in open storage.close() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/FileStorage/FileStorage.py", line 400, in close self._lock_file.close() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/lock_file.py", line 79, in close os.unlink(self._path) OSError: [Errno 2] No such file or directory: '/home/zope/instances/instance1/site-buildout_1.0.5/var/filestorage/siteData.fs.lock' ------ 2010-01-27T05:15:02 ERROR Zope.ZODBMountPoint Failed to mount database. exceptions.ValueError (database_name 'site' already in databases) Traceback (most recent call last): File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 257, in _getOrOpenObject conn = self._getMountedConnection(anyjar) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 147, in _getMountedConnection self._getDB() File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Products/ZODBMountPoint/MountedObject.py", line 157, in _getDB return getConfiguration().getDatabase(self._path) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 280, in getDatabase db = factory.open(name, self.databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 178, in open DB = self.createDB(database_name, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 175, in createDB return ZODBDatabase.open(self, databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/config.py", line 105, in open databases=databases) File "/home/zope/instances/instance1/site-buildout_1.0.5/parts/zope2/lib/python/ZODB/DB.py", line 262, in __init__ raise ValueError("database_name %r already in databases" % ValueError: database_name 'site' already in databases ------
Change History
comment:2 Changed 5 years ago by kleist
- Component changed from Unknown to Infrastructure
- Description modified (diff)
I've seen this too, using Plone 4 on a vServer (which possibly has a slowish SAN). Happens only the first time after buildout?? Seems to be harmless, i.e. I've seen no bad things happen afterwards. [wrapped traceback in triple curly brackets]
comment:3 Changed 5 years ago by kleist
No, this does not happen only the first time after buildout.
comment:4 Changed 4 years ago by kleist
- Status changed from new to confirmed
- Version set to 3.3
- Milestone changed from 3.3.x to 4.x
Is this still an issue with Plone 4?
comment:6 Changed 3 years ago by eleddy
- Status changed from confirmed to closed
- Resolution set to wontfix
This ticket has not been modified in over 9 months. In another brazen attempt to clean this tracker up, this is closed. If you really, REALLY care about this ticket, please re-verify that it is still an issue on the current supported releases (4.2 or 4.3) and reopen. Better yet, submit a pull request to fix the bug and then close the bug properly. We <3 you and all of your effort, but we can't go on like this anymore. I hope you aren't too mad and we can still be friends. Hugs.
comment:7 Changed 2 years ago by frisi
- Status changed from closed to reopened
- Resolution wontfix deleted
this is still a valid issues. as soon as there are more than one zodb mountpoints configured, i almost always geht this error for one of the storages. happens on plone 4.0 throughout to 4.3.
comment:8 Changed 2 years ago by frisi
as dieter maurer said in http://plone.293351.n2.nabble.com/zodb-mountpoint-error-in-log-td2584696.html we might get rid of this error by adding an event listener for the opening of the main database that opens all other databases too.