On Mar 9, 2005, at 13:20, Arenz, Ralph wrote:
Hi,
After upgrading from Zope-2.6.4 to Zope-2.7.3 i get the following error when i try to add an object from the add-list in zmi:
Unauthorized: You are not allowed to access '<property-name>' in this context (Also, an error occurred while attempting to render the standard error message.)
<Try your software on the current CVS Zope-2_7-branch and see if that <solves the problem. Some overeager security checks were fixed after <2.7.4. <jens I tried Zope-2.7.5-rc1 but the problem still exists! I can't get back to Zope-2.6.4 and i'am running in big trouble with that behaviour, because important elements won't be accessible for the many users. Of course i can change the factory-methods but in the end i'am not shure if there is a real bug or if there a common change in way container-properties are handled within factory-methods. ralph
On Mar 11, 2005, at 10:17, Arenz, Ralph wrote:
After upgrading from Zope-2.6.4 to Zope-2.7.3 i get the following error when i try to add an object from the add-list in zmi:
Unauthorized: You are not allowed to access '<property-name>' in this context (Also, an error occurred while attempting to render the standard error message.)
<Try your software on the current CVS Zope-2_7-branch and see if that <solves the problem. Some overeager security checks were fixed after <2.7.4.
<jens
I tried Zope-2.7.5-rc1 but the problem still exists! I can't get back to Zope-2.6.4 and i'am running in big trouble with that behaviour, because
important elements won't be accessible for the many users. Of course i can change the factory-methods but in the end i'am not shure if there is a real bug or if there a common change in way container-properties are handled within factory-methods.
If it still doesn't work I don't know off-hand. Did you by any chance upgrade your live site without doing any testing first? jens
ON startup, I noticed the statement that old python scripts need to recompiled by visiting this: /manage_addProduct/PythonScripts/recompile When I run this I get a POSKeyError in the browser after a few minutes. Here is the line from the event.log plus one before it that also concerns me: 2005-03-11T07:30:14 PROBLEM(100) ZODB Could not import class 'Connection' from module 'Products.ZODBCDA.DA' ------ 2005-03-11T07:30:15 INFO(0) Script (Python) Some of your Scripts have stale code cached. Since Zope cannot use this code, startup will be slightly slower until these Scripts are edited. You can automatically recompile all Scripts that have this problem by visiting /manage_addProduct/PythonScripts/recompile of your server in a browser. Any light shedders out there this fine morning? Thanks
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Allen Schmidt wrote: | ON startup, I noticed the statement that old python scripts need to | recompiled by visiting this: | /manage_addProduct/PythonScripts/recompile | | When I run this I get a POSKeyError in the browser after a few | minutes. Channeling Tim: ~ What version of Zope? You may need to run 'fstest.py' and / or ~ 'fsrefs.py' on your Data.fs, and see if they complain. Channeling Dieter: ~ You need to include the whole traceback to enable us to help you. | Here is the line from the event.log plus one before it that also | concerns me:> | | 2005-03-11T07:30:14 PROBLEM(100) ZODB Could not import class | 'Connection' from module 'Products.ZODBCDA.DA' This message is likely because you have an instance of the ZODBCDA Connection class in your database (maybe int the root of your Zope site?), but have removed the ZODBCDA product. If you aren't using ZODBCDA any longer, you should be able just to delete the connection object in the ZMI. Tres. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMZ1DGqWXf00rNCgRAlGTAKCAVBu8MtptHqtzjzZ5kXjJxkJBCQCeJs1P pjrKZ8imA6IQsihqVr/ktxE= =R8zw -----END PGP SIGNATURE-----
Duh. Sorry. Basic rules of problem reporting: RH7.2 Zope 2.7.2 ZEO Squid in front
~ What version of Zope? You may need to run 'fstest.py' and / or ~ 'fsrefs.py' on your Data.fs, and see if they complain.
I am assuming these are just reading tools and non-destructive? Can they be run against a running zeo/zope?
~ You need to include the whole traceback to enable us to help you.
No traceback that I can see. Just lines that show up in the eventlog.
| Here is the line from the event.log plus one before it that also | concerns me:> | | 2005-03-11T07:30:14 PROBLEM(100) ZODB Could not import class | 'Connection' from module 'Products.ZODBCDA.DA'
This message is likely because you have an instance of the ZODBCDA Connection class in your database (maybe int the root of your Zope site?), but have removed the ZODBCDA product. If you aren't using ZODBCDA any longer, you should be able just to delete the connection object in the ZMI.
For this one, we ran across this a long time ago if I remember correctly, and we could never find any reference to the ODBC DA. We HAD one installed several years ago but removed it when we switched to Linux and MySQL. Thanks Tres.
[Allen Schmidt]
Duh. Sorry. Basic rules of problem reporting: RH7.2 Zope 2.7.2 ZEO Squid in front
Thanks -- that's helpful.
~ What version of Zope? You may need to run 'fstest.py' and / or ~ 'fsrefs.py' on your Data.fs, and see if they complain.
I am assuming these are just reading tools and non-destructive? Can they be run against a running zeo/zope?
Short course: yes; yes; if you must but it's not recommended (won't hurt but you may get spurious error messages then). Medium course here: http://zope.org/Wikis/ZODB/FileStorageBackup You should read that. POSKeyError "shouldn't happen", so there's no guarantee it will be easy to fix. Unfortunately, in Zope 2.7.2 there were cooperating bugs (in ZODB and Zope) that could create POSKeyError situations through no fault of yours; those were repaired in Zope 2.7.3 / ZODB 3.2.4.
~ You need to include the whole traceback to enable us to help you.
No traceback that I can see. Just lines that show up in the eventlog.
Your original message didn't contain anything from any log, or copy'n'paste from any browser window, that said "POSKeyError". I don't think it's possible to get a POSKeyError without the message also including vital information like the object id of the missing object -- but we didn't see the message you saw, so can't tell.
RH7.2 Zope 2.7.2 ZEO Squid in front
~ What version of Zope? You may need to run 'fstest.py' and / or ~ 'fsrefs.py' on your Data.fs, and see if they complain. I am assuming these are just reading tools and non-destructive? Can they be run against a running zeo/zope?
Short course: yes; yes; if you must but it's not recommended (won't hurt but you may get spurious error messages then). Medium course here:
http://zope.org/Wikis/ZODB/FileStorageBackup
You should read that. POSKeyError "shouldn't happen", so there's no guarantee it will be easy to fix. Unfortunately, in Zope 2.7.2 there were cooperating bugs (in ZODB and Zope) that could create POSKeyError situations through no fault of yours; those were repaired in Zope 2.7.3 / ZODB 3.2.4.
Your original message didn't contain anything from any log, or copy'n'paste from any browser window, that said "POSKeyError". I don't think it's possible to get a POSKeyError without the message also including vital information like the object id of the missing object -- but we didn't see the message you saw, so can't tell.
My bad... The POSKeyError showed up on the browser window as a result of running the "/manage_addProduct/PythonScripts/recompile" script. Zope Error Zope has encountered an error while publishing this resource. Error Type: POSKeyError Error Value: 00000000008db667
From error_log:
Traceback (innermost last): Module ZPublisher.Publish, line 101, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Products.PythonScripts, line 53, in recompile Module OFS.FindSupport, line 151, in ZopeFind Module OFS.FindSupport, line 151, in ZopeFind Module OFS.FindSupport, line 151, in ZopeFind Module OFS.FindSupport, line 138, in ZopeFind Module ZODB.Connection, line 559, in setstate Module ZEO.ClientStorage, line 749, in load Module ZEO.ServerStub, line 82, in zeoLoad Module ZEO.zrpc.connection, line 372, in call POSKeyError: 00000000008db667
Allen Schmidt wrote at 2005-3-11 10:58 -0500:
... My bad... The POSKeyError showed up on the browser window as a result of running the "/manage_addProduct/PythonScripts/recompile" script.
Zope Error Zope has encountered an error while publishing this resource.
Error Type: POSKeyError Error Value: 00000000008db667 ... Module OFS.FindSupport, line 138, in ZopeFind Module ZODB.Connection, line 559, in setstate Module ZEO.ClientStorage, line 749, in load Module ZEO.ServerStub, line 82, in zeoLoad Module ZEO.zrpc.connection, line 372, in call POSKeyError: 00000000008db667
To find the broken object, you call "recompile" in an interactive Python interpreter (Under *nix: bin/zopectl debug; followed by "app.unrestrictedTraverse('manage_addProduct/PythonScripts/recompile)()'. You should get the same exception. Then "from pdb import pm; pm()" You are now in the Python debugger and can analyse the context of the problem. Go up with "up" until you arrive in "ZopeFind: line 138". Look which object it wants to load. You might need to go up another stack frame. -- Dieter
Does this mean anything Dieter?? Problems with a Z Class?? _________________________________
app.unrestrictedTraverse('manage_addProduct/PythonScripts/recompile')() /var/www/zope/zope275admin/lib/python/SearchIndex/__init__.py:19: DeprecationWarning: The usage of the SearchIndex package is deprecated since Zope 2.4. This package is only kept for backwards compatibility for a while and will go away in a future release.
Please use instead the re-factored modules in Products/PluginIndexes. warnings.warn("The usage of the SearchIndex package is deprecated since \ Traceback (most recent call last): File "<stdin>", line 1, in ? File "/var/www/zope/zope275admin/lib/python/Products/PythonScripts/__init__.py search_sub=1) File "/var/www/zope/zope275admin/lib/python/OFS/FindSupport.py", line 151, in REQUEST, result, sub_p) File "/var/www/zope/zope275admin/lib/python/OFS/FindSupport.py", line 151, in REQUEST, result, sub_p) File "/var/www/zope/zope275admin/lib/python/OFS/FindSupport.py", line 151, in REQUEST, result, sub_p) File "/var/www/zope/zope275admin/lib/python/OFS/FindSupport.py", line 138, in is_zclass = getattr(bs, 'meta_type', None) == 'Z Class' File "/var/www/zope/zope275admin/lib/python/ZODB/Connection.py", line 597, in p, serial = self._storage.load(oid, self._version) File "/var/www/zope/zope275admin/lib/python/ZEO/ClientStorage.py", line 757, i p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/zope275admin/lib/python/ZEO/ServerStub.py", line 82, in ze return self.rpc.call('zeoLoad', oid) File "/var/www/zope/zope275admin/lib/python/ZEO/zrpc/connection.py", line 481, raise inst # error raised by server ZODB.POSException.POSKeyError: 0x8db667
from pdb import pm; pm() /var/www/zope/zope275admin/lib/python/ZEO/zrpc/connection.py(481)call() -> raise inst # error raised by server (Pdb) up /var/www/zope/zope275admin/lib/python/ZEO/ServerStub.py(82)zeoLoad() -> return self.rpc.call('zeoLoad', oid) (Pdb) up /var/www/zope/zope275admin/lib/python/ZEO/ClientStorage.py(768)load() -> self._load_lock.release() (Pdb) up /var/www/zope/zope275admin/lib/python/ZODB/Connection.py(610)setstate() -> raise (Pdb) up /var/www/zope/zope275admin/lib/python/OFS/FindSupport.py(138)ZopeFind() -> is_zclass = getattr(bs, 'meta_type', None) == 'Z Class' (Pdb) up /var/www/zope/zope275admin/lib/python/OFS/FindSupport.py(151)ZopeFind() -> REQUEST, result, sub_p) (Pdb) up /var/www/zope/zope275admin/lib/python/OFS/FindSupport.py(151)ZopeFind() -> REQUEST, result, sub_p) (Pdb) up /var/www/zope/zope275admin/lib/python/OFS/FindSupport.py(151)ZopeFind() -> REQUEST, result, sub_p) (Pdb) up /var/www/zope/zope275admin/lib/python/Products/PythonScripts/__init__.py(53)recompile() -> search_sub=1) (Pdb) up <stdin>(1)?() (Pdb) up *** Oldest frame
Dieter Maurer wrote:
Allen Schmidt wrote at 2005-3-11 10:58 -0500:
... My bad... The POSKeyError showed up on the browser window as a result of running the "/manage_addProduct/PythonScripts/recompile" script.
Zope Error Zope has encountered an error while publishing this resource.
Error Type: POSKeyError Error Value: 00000000008db667 ... Module OFS.FindSupport, line 138, in ZopeFind Module ZODB.Connection, line 559, in setstate Module ZEO.ClientStorage, line 749, in load Module ZEO.ServerStub, line 82, in zeoLoad Module ZEO.zrpc.connection, line 372, in call POSKeyError: 00000000008db667
To find the broken object, you call "recompile" in an interactive Python interpreter (Under *nix: bin/zopectl debug; followed by "app.unrestrictedTraverse('manage_addProduct/PythonScripts/recompile)()'.
You should get the same exception.
Then "from pdb import pm; pm()" You are now in the Python debugger and can analyse the context of the problem. Go up with "up" until you arrive in "ZopeFind: line 138". Look which object it wants to load. You might need to go up another stack frame.
Allen Schmidt wrote at 2005-3-23 18:21 -0500:
Does this mean anything Dieter??
Sure, a POSKeyError...
Problems with a Z Class??
No. The code just tries to check whether "meta_type" is "Z Class" when the POSKeyError occurs. This does not mean that the problematic object is a ZClass (very unlikely, indeed)!.
... File "/var/www/zope/zope275admin/lib/python/OFS/FindSupport.py", line 138, in is_zclass = getattr(bs, 'meta_type', None) == 'Z Class'
"bs.__class__" in this place will tell you the broken objects class. Looking around in this frame or in its caller will tell you the id of the broken object. This will allow you to get rid of it (there is a HowTo for this somewhere). -- Dieter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Allen Schmidt wrote: | Duh. Sorry. Basic rules of problem reporting: | RH7.2 | Zope 2.7.2 | ZEO | Squid in front | |> ~ What version of Zope? You may need to run 'fstest.py' and / or |> ~ 'fsrefs.py' on your Data.fs, and see if they complain. | | | I am assuming these are just reading tools and non-destructive? Can they | be run against a running zeo/zope? They are non-destructive. If they report issues, then (channeling Tim again) you may need to run 'fsrecover.py' on a copy of the Data.fs and see if it helps. Another thing would be to try bringing up a copy of the data under Zope 2.7.5c1, and running the PythonScript compiler URL there: there have been a number of ZODB fixes since Zope 2.7.2 / ZODB3 3.2.3 which might help out. |> ~ You need to include the whole traceback to enable us to help you. | | | No traceback that I can see. Just lines that show up in the eventlog. Your event log listing didn't include any POSKeyError. Do you have the 'error_log' object set to write tracebacks to the log? If not, you should be able to extract the traceback from the 'error_log' entry. |> | Here is the line from the event.log plus one before it that also |> | concerns me:> |> | |> | 2005-03-11T07:30:14 PROBLEM(100) ZODB Could not import class |> | 'Connection' from module 'Products.ZODBCDA.DA' |> |> This message is likely because you have an instance of the ZODBCDA |> Connection class in your database (maybe int the root of your Zope |> site?), but have removed the ZODBCDA product. If you aren't using |> ZODBCDA any longer, you should be able just to delete the connection |> object in the ZMI. | | For this one, we ran across this a long time ago if I remember | correctly, and we could never find any reference to the ODBC DA. We HAD | one installed several years ago but removed it when we switched to Linux | and MySQL. Hmm... I would try opening the database in read-only mode and looking at the '__dict__' of the root object. E.g.: ~ $ bin/zopectl debug # even while server is running, if using ZEO! ~ ... ~ >>> for k, v in app.__dict__.items(): ~ ... print "%s :: %s" ( k, v ) and then look for the connection object there. Tres. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMbk/GqWXf00rNCgRApWYAJ4/0BK5Q69vfcNJXfAdpMcWTVdjcACfeVNt 9mn7IG8eLFhiB//A8X8hxEY= =6Pkw -----END PGP SIGNATURE-----
Following the last part first. It is on our live server but not in read-only. That can't be set per client, can it? Anyway:
for k, v in app.__dict__.items(): ... print "%s :: %s" ( k, v ) ... Traceback (most recent call last): File "<stdin>", line 2, in ? TypeError: 'str' object is not callable
This is what I get. Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Allen Schmidt wrote: | Duh. Sorry. Basic rules of problem reporting: | RH7.2 | Zope 2.7.2 | ZEO | Squid in front | |> ~ What version of Zope? You may need to run 'fstest.py' and / or |> ~ 'fsrefs.py' on your Data.fs, and see if they complain. | | | I am assuming these are just reading tools and non-destructive? Can they | be run against a running zeo/zope?
They are non-destructive. If they report issues, then (channeling Tim again) you may need to run 'fsrecover.py' on a copy of the Data.fs and see if it helps.
Another thing would be to try bringing up a copy of the data under Zope 2.7.5c1, and running the PythonScript compiler URL there: there have been a number of ZODB fixes since Zope 2.7.2 / ZODB3 3.2.3 which might help out.
|> ~ You need to include the whole traceback to enable us to help you. | | | No traceback that I can see. Just lines that show up in the eventlog.
Your event log listing didn't include any POSKeyError. Do you have the 'error_log' object set to write tracebacks to the log? If not, you should be able to extract the traceback from the 'error_log' entry.
|> | Here is the line from the event.log plus one before it that also |> | concerns me:> |> | |> | 2005-03-11T07:30:14 PROBLEM(100) ZODB Could not import class |> | 'Connection' from module 'Products.ZODBCDA.DA' |> |> This message is likely because you have an instance of the ZODBCDA |> Connection class in your database (maybe int the root of your Zope |> site?), but have removed the ZODBCDA product. If you aren't using |> ZODBCDA any longer, you should be able just to delete the connection |> object in the ZMI. | | For this one, we ran across this a long time ago if I remember | correctly, and we could never find any reference to the ODBC DA. We HAD | one installed several years ago but removed it when we switched to Linux | and MySQL.
Hmm... I would try opening the database in read-only mode and looking at the '__dict__' of the root object. E.g.:
~ $ bin/zopectl debug # even while server is running, if using ZEO! ~ ... ~ >>> for k, v in app.__dict__.items(): ~ ... print "%s :: %s" ( k, v )
and then look for the connection object there.
Tres. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCMbk/GqWXf00rNCgRApWYAJ4/0BK5Q69vfcNJXfAdpMcWTVdjcACfeVNt 9mn7IG8eLFhiB//A8X8hxEY= =6Pkw -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Allen Schmidt wrote: | Following the last part first. | It is on our live server but not in read-only. That can't be set per | client, can it? Anyway: | |>>> for k, v in app.__dict__.items(): | | ... print "%s :: %s" ( k, v ) | ... | Traceback (most recent call last): | File "<stdin>", line 2, in ? | TypeError: 'str' object is not callable | |>>> D'oh, typo. Python string substitution needs a percent between the format string and the list, e.g.: ~ >>> for k, v in app.__dict__.items(): ~ ... print "%s :: %s" % ( k, v ) Tres. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCMdXaGqWXf00rNCgRAkT6AJ95/i73bx+Pszs3bJHMI3FjoNVxdwCfez6b xGE5hIAflfLANwQ8NMohOrM= =QUgI -----END PGP SIGNATURE-----
Is this supposed to show EVERY object in the root? We have tons of stuff (probably part of our problem!) (I should have caught the missing % below. That is the only problem asking for help...one tends to rely on it verbatim without thinking.) When I run this I get listings of the ID and contents of the files in the root. We had a TIF file there and it barfed on that and started spewing greek all over the screen. Removed that file and ran it again. It got farther until it hit this below: (that dtml-var is the end of the previous file) ... ... ... <dtml-var standard_html_footer> _Test_Database_Connections_Permission :: ('Manager',) %âãÏÓienvenido :: %PDF-1.3 0000000016 00000 n xref 0000001195 00000 n 0000004490 00000 n 0000004739 00000 n ... ... ... The numbers continue for a long way and then the greek shows up again until I kill it. Where is that file coming from? _Test_Database_Connections_Permission --Allen Tres Seaver wrote:
~ >>> for k, v in app.__dict__.items(): ~ ... print "%s :: %s" % ( k, v )
Relating to this thread from last July, http://mail.zope.org/pipermail/zope-dev/2004-July/023506.html I am seeing this today. (have just recently started really looking hard at the log files so who knows what will turn up) 2005-03-11T10:49:01 INFO(0) ZEC:1-None-0 flipping cache files. new current = 0 ------ 2005-03-11T10:49:48 INFO(0) ZEC:1-None-1 flipping cache files. new current = 1 ------ 2005-03-11T10:50:28 ERROR(200) ZODB Couldn't load state for 00000000008db667 Traceback (most recent call last): File "/var/www/zope/zope272admin/lib/python/ZODB/Connection.py", line 559, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/zope272admin/lib/python/ZEO/ClientStorage.py", line 749, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/zope272admin/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/zope272admin/lib/python/ZEO/zrpc/connection.py", line 372, in call raise inst # error raised by server POSKeyError: 00000000008db667 ------ 2005-03-11T10:50:28 ERROR(200) ZODB Couldn't load state for 00000000008db667 Traceback (most recent call last): File "/var/www/zope/zope272admin/lib/python/ZODB/Connection.py", line 559, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/zope272admin/lib/python/ZEO/ClientStorage.py", line 749, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/zope272admin/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/zope272admin/lib/python/ZEO/zrpc/connection.py", line 372, in call raise inst # error raised by server POSKeyError: 00000000008db667 ------ 2005-03-11T10:50:37 INFO(0) ZEC:1-None-0 flipping cache files. new current = 0 Any ideas? RH7.2 Zope 2.7.2 / ZEO Allen
And this too in the the event.log from one of the public zeo clients 2005-03-11T13:57:35 ERROR(200) ZServer Problem in ICP (socket.error:(4, 'Interrupted system call') [/usr/local/lib/python2.3/asyncore.py|read|69] [/usr/local/lib/python2.3/asyncore.py|handle_read_event|390] [/var/www/zope/zope272c2/lib/python/ZServer/ICPServer.py|handle_read|67]) ------ Allen Schmidt wrote:
Relating to this thread from last July, http://mail.zope.org/pipermail/zope-dev/2004-July/023506.html
I am seeing this today. (have just recently started really looking hard at the log files so who knows what will turn up)
2005-03-11T10:49:01 INFO(0) ZEC:1-None-0 flipping cache files. new current = 0 ------ 2005-03-11T10:49:48 INFO(0) ZEC:1-None-1 flipping cache files. new current = 1 ------ 2005-03-11T10:50:28 ERROR(200) ZODB Couldn't load state for 00000000008db667 Traceback (most recent call last): File "/var/www/zope/zope272admin/lib/python/ZODB/Connection.py", line 559, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/zope272admin/lib/python/ZEO/ClientStorage.py", line 749, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/zope272admin/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/zope272admin/lib/python/ZEO/zrpc/connection.py", line 372, in call raise inst # error raised by server POSKeyError: 00000000008db667 ------ 2005-03-11T10:50:28 ERROR(200) ZODB Couldn't load state for 00000000008db667 Traceback (most recent call last): File "/var/www/zope/zope272admin/lib/python/ZODB/Connection.py", line 559, in setstate p, serial = self._storage.load(oid, self._version) File "/var/www/zope/zope272admin/lib/python/ZEO/ClientStorage.py", line 749, in load p, s, v, pv, sv = self._server.zeoLoad(oid) File "/var/www/zope/zope272admin/lib/python/ZEO/ServerStub.py", line 82, in zeoLoad return self.rpc.call('zeoLoad', oid) File "/var/www/zope/zope272admin/lib/python/ZEO/zrpc/connection.py", line 372, in call raise inst # error raised by server POSKeyError: 00000000008db667 ------ 2005-03-11T10:50:37 INFO(0) ZEC:1-None-0 flipping cache files. new current = 0
Any ideas? RH7.2 Zope 2.7.2 / ZEO
Allen
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Allen Schmidt wrote at 2005-3-11 14:24 -0500:
And this too in the the event.log from one of the public zeo clients
2005-03-11T13:57:35 ERROR(200) ZServer Problem in ICP (socket.error:(4, 'Interrupted system call') [/usr/local/lib/python2.3/asyncore.py|read|69] [/usr/local/lib/python2.3/asyncore.py|handle_read_event|390] [/var/www/zope/zope272c2/lib/python/ZServer/ICPServer.py|handle_read|67])
Apparently, a bug in the "ICP" server -- but unrelated to your POSKeyErrors. -- Dieter
participants (6)
-
Allen Schmidt -
Arenz, Ralph -
Dieter Maurer -
Jens Vagelpohl -
Tim Peters -
Tres Seaver