I'm getting reports of some very strange behavior with Zope 2.2.5 using the LocalFS product, which seems to involve the authentication mechanism somehow. I'm rather at a loss where to even begin troubleshooting here. If anyone has any suggestions they would be much appreciated. Thanks, --jfarr ----- Original Message ----- From: "Kent Polk" <kent@tiamat.goathill.org> To: "Jonothan Farr" <jfarr@speakeasy.org> Sent: Friday, January 26, 2001 9:25 AM Subject: Re: apparent problems with LocalFS after zope upgrade
Unders some (unknown) conditions, subdirectories under a localfs mount point can no longer be found:
<TD WIDTH="90%"> <H2>Zope Error</H2> <P>Zope has encountered an error while publishing this resource. </P> <P><STRONG>Resource not found</STRONG></P>
Sorry, the requested Zope resource does not exist.<p>Check the URL and try again.<p> <!-- macpysrc -->
...
<!-- Traceback (innermost last): File /usr/pkg/share/zope/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /usr/pkg/share/zope/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/pkg/share/zope/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: pysrc) File /usr/pkg/share/zope/lib/python/ZPublisher/Publish.py, line 162, in publish File /usr/pkg/share/zope/lib/python/ZPublisher/BaseRequest.py, line 338, in traverse File /var/zope/Products/LocalFS/LocalFS.py, line 462, in __bobo_traverse__ (Object: pysrc) File /usr/pkg/share/zope/lib/python/ZPublisher/HTTPResponse.py, line 529, in notFoundError NotFound: (see above)
Note that 'macpysrc' folder (above) shows up in the default directory listing, but the above is what I get when I select it. Files which are contained within the directory are available though... Only the direcoty listing is not, and this is true whether there is an index.html file in the directory or not (as well as one in the parent-mount point or not).
---------
I did note that when entering the subdirectories (using localfs) the authentication mechanism had lost track of who I was and I was now an Anonymous User. This doesn't happen with all LocalFS mount points though, and haven't been able to determine what is different between the ones that work correctly and the ones that don't except that the ones that don't were fairly recently created using Zope-2.2.4 LocalFS v0.9.4 while the ones that do work were created last summer sometime.
Note that this is observed on two different zope servers - different hosts - using both Localfsv0.9.4 and Localfsv0.9.6. Again, this appeared almost immediately after I upgraded to Zope-2.2.5. I had already upgraded both servers before I noticed the problem. :^(
Any suggestions on what to check?
Thanks!