Problems with Zope 2.4.3 package for Mac OSX
I've had some problems with the OSX package release described at: http://www.zope.org/Members/richard/zope_for_osx/news_item 1. The package install appears to set permissions in a way that doesn't allow running on port 80. I've compared key files and directories with my previous 2.4.0 that I do run on port 80 and I don't see significant differences, but I must be missing something. Perhaps this has something to do with starting from the OSX GUI (rather than 'sudo' from the terminal), but I'm able to start my 2.4.0 on port 80 with a copy of the GUI. (Running on higher ports is OK except for the SSL-related error noted below). 2. There appears to be a path problem with the M2Crypto module. Both the https and secure webdav modules fail to find it on the attempted import. A search reveals an M2Crypto directory containing _m2crypto.py, but explicitly specifying that path doesn't help. Mac OSX 10.1.1; b/w G3-350. Jim Harrison Univ. of Pittsburgh
On Tuesday 20 November 2001 03:47, Jim Harrison wrote:
I've had some problems with the OSX package release described at:
http://www.zope.org/Members/richard/zope_for_osx/news_item
1. The package install appears to set permissions in a way that doesn't allow running on port 80. I've compared key files and directories with my previous 2.4.0 that I do run on port 80 and I don't see significant differences, but I must be missing something. Perhaps this has something to do with starting from the OSX GUI (rather than 'sudo' from the terminal), but I'm able to start my 2.4.0 on port 80 with a copy of the GUI. (Running on higher ports is OK except for the SSL-related error noted below).
In your case, the problem lies in the controller - it cannot do the equivalent of "sudo" as yet - the Mac OS X documentation on the Authorisation API is completely non-existent, and I haven't guessed correctly to make it work yet :( So for now, you can't run on port 80 :( The controller source on zope.org is out of date, and I'll try to update it so that people can play with it themselves (and hopefully someone will figure out the auth problem.)
2. There appears to be a path problem with the M2Crypto module. Both the https and secure webdav modules fail to find it on the attempted import. A search reveals an M2Crypto directory containing _m2crypto.py, but explicitly specifying that path doesn't help.
I'll fix that in the next release. Richard
On Tuesday 20 November 2001 03:47, Jim Harrison wrote:
2. There appears to be a path problem with the M2Crypto module. Both the https and secure webdav modules fail to find it on the attempted import. A search reveals an M2Crypto directory containing _m2crypto.py, but explicitly specifying that path doesn't help.
I've just checked, and everything looks OK to me. What happens if you open a terminal, and: % cd /Applications/Zope % ./python Python 2.1.1 (#1, 10/16/01, 15:19:48) [GCC Apple devkit-based CPP 6.0] on darwin1 Type "copyright", "credits" or "license" for more information.
import M2Crypto ^D
That should work with no errors. Could you paste the log entries where the ssl stuff fails? Richard
on 11/19/01 4:22 PM, Richard Jones at richard@bizarsoftware.com.au wrote:
2. There appears to be a path problem with the M2Crypto module. Both the https and secure webdav modules fail to find it on the attempted import. A search reveals an M2Crypto directory containing _m2crypto.py, but explicitly specifying that path doesn't help.
I've just checked, and everything looks OK to me. What happens...
Well, I deleted the Zope folder (this morning's install) from the Applications directory and reinstalled Zope from the package. Interestingly, the installer did not create a var directory (I deleted and reinstalled a couple of times with the same result). So on startup Zope complained about the lack of data.fs and zProcessManager.pid files. I created a var folder and copied these files in from my Zope 2.4.0 installation, plus the Products needed to support the stuff in data.fs (Squishdot, TinyTables, Zwiki and Zchat). Then I fired it up on port 8080 and it started OK. HTTP, WebDAV, HTTPS and FTP seemed to work fine, though some browsers have issues with the certificate identity in HTTPS (I need to do some reading on that). It's also interesting that the installer did not ask for a user name and password during the installs subsequent to deleting the Zope folder, and the newly installed Zope used the name and password that was previously entered. This would appear to mean that some configuration files are being kept in places other than the Zope folder. Perhaps a second write in this or these locations fixed the path problem. The bottom line is that I'm not now seeing the problem with M2Crypto that I saw this morning, though I promise that it did happen. Jim Harrison
On Tuesday 20 November 2001 09:35, Jim Harrison wrote:
on 11/19/01 4:22 PM, Richard Jones at richard@bizarsoftware.com.au wrote:
2. There appears to be a path problem with the M2Crypto module. Both the https and secure webdav modules fail to find it on the attempted import. A search reveals an M2Crypto directory containing _m2crypto.py, but explicitly specifying that path doesn't help.
I've just checked, and everything looks OK to me. What happens...
Well, I deleted the Zope folder (this morning's install) from the Applications directory and reinstalled Zope from the package. Interestingly, the installer did not create a var directory (I deleted and reinstalled a couple of times with the same result).
That'll be because there's a receipt for the previous install in your /Library/Receipts folder (a sub-directory with the same name as the install package) and therefore the installer thinks you're upgrading, not installing. Thus it doesn't run the post-install script. I'll have to include a post-upgrade script I suppose...
So on startup Zope complained about the lack of data.fs and zProcessManager.pid files. I created a var folder and copied these files in from my Zope 2.4.0 installation, plus the Products needed to support the stuff in data.fs (Squishdot, TinyTables, Zwiki and Zchat).
The "create instance" button (or whatever it is - I don't have it in front it me) is for. I can't even remember how far I got with that... I have a feeling that it's mostly there. You can't switch between instances using the drop-down menu at the bottom though, that's definitely not done...
Then I fired it up on port 8080 and it started OK. HTTP, WebDAV, HTTPS and FTP seemed to work fine, though some browsers have issues with the certificate identity in HTTPS (I need to do some reading on that).
You'll need to get a "real" cert (ie. buy one) to stop it complaining. The SSL works fine - it encrypts - but the browser can't be _really_ sure that the server is who it says it is :)
It's also interesting that the installer did not ask for a user name and password during the installs subsequent to deleting the Zope folder, and the newly installed Zope used the name and password that was previously entered. This would appear to mean that some configuration files are being kept in places other than the Zope folder. Perhaps a second write in this or these locations fixed the path problem.
The user thing is a part of the instance creation component of the controller. That is, it'll ask the same thing if you hit "create instance"
The bottom line is that I'm not now seeing the problem with M2Crypto that I saw this morning, though I promise that it did happen.
Be great if you could reproduce the problem :) Richard
participants (2)
-
Jim Harrison -
Richard Jones