Zope 2.8 Installation trouble on XP
Hi everyone, I'm a beginner in Zope. I've just installed the Zope 2.8 final package. The installation seems to have completed normally. However when the zope instance is run I have the following message : C:\Zope-Instance\bin>runzope.bat C:\Zope-Instance\bin>"C:\Zope-2.8.0-final\bin\python.exe" "C:\Zope-2.8.0-final\l ib\python\Zope2\Startup\run.py" -C "C:\Zope-Instance\etc\zope.conf" Traceback (most recent call last): File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 56, in ? run() File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 17, in run import Zope2.Startup File "C:\Zope-2.8.0-final\lib\python\Zope2\__init__.py", line 60, in ? from Zope2.Startup.run import configure File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\__init__.py", line 26, in ? from ZConfig.components.logger import loghandler ImportError: No module named components.logger There was no previous message with keyword "loghandler" in the mailing list. All Zope services are stopped. Here are the system variable that are relevent : CONFIG_FILE=C:\Zope-Instance\etc\zope.conf INSTANCE_HOME=C:\Zope-Instance Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Pi nnacle\Shared Files\InstantCDDVD\ PYTHON=C:\Zope-2.8.0-final\bin\python.exe PYTHONPATH=C:\Zope-2.8.0-final\lib\python SOFTWARE_HOME=C:\Zope-2.8.0-final\lib\python ZOPE_HOME=C:\Zope-2.8.0-final ZOPE_RUN=C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py The Zope instance is the one created by the install package. Seems that something is not working with my configuration, but what? Pedro ___________________________________________________________________________ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com
[Pedro Cristian]
I'm a beginner in Zope. I've just installed the Zope 2.8 final package. The installation seems to have completed normally. However when the zope instance is run I have the following message :
C:\Zope-Instance\bin>runzope.bat
C:\Zope-Instance\bin>"C:\Zope-2.8.0-final\bin\python.exe" "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py" -C "C:\Zope-Instance\etc\zope.conf" Traceback (most recent call last): File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 56, in ? run() File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 17, in run import Zope2.Startup File "C:\Zope-2.8.0-final\lib\python\Zope2\__init__.py", line 60, in ? from Zope2.Startup.run import configure File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\__init__.py", line 26, in ?
from ZConfig.components.logger import loghandler ImportError: No module named components.logger
Sorry, I can't reproduce this, on Win XP Pro SP2: C:\Zope-Instance\bin>runzope.bat C:\Zope-Instance\bin>"C:\Zope-2.8.0-final\bin\python.exe" "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py" -C "C:\Zope-Instance\etc\zope.conf" and that's it -- Zope is running at that point, and there's no more console output. \Zope-Instance\log\event.log shows "Zope Ready to handle requests", though. You may find more clues in your event.log.
There was no previous message with keyword "loghandler" in the mailing list. All Zope services are stopped.
Why the plural ("services" as opposed to "service")? Do you have more than one Zope installed? Installing Zope installs exactly one Windows service (if you allow it to), so I expected to see the singular "service" here. Not trying to be picky for the sake of it, but there must _something_ different in your system from what others are doing.
Here are the system variable that are relevent : CONFIG_FILE=C:\Zope-Instance\etc\zope.conf INSTANCE_HOME=C:\Zope-Instance Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Pinnacle\Shared Files\InstantCDDVD\ PYTHON=C:\Zope-2.8.0-final\bin\python.exe PYTHONPATH=C:\Zope-2.8.0-final\lib\python SOFTWARE_HOME=C:\Zope-2.8.0-final\lib\python ZOPE_HOME=C:\Zope-2.8.0-final ZOPE_RUN=C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py
Those look normal. Did you change \Zope-Instance\etc\zope.conf in any way?
The Zope instance is the one created by the install package.
Same for me above.
Seems that something is not working with my configuration, but what?
I don't know, and I haven't seen this reported by anyone else before. Let's try this: cd to your Zope's (not Zope-Instance's) bin directory, and start Python from there. Your DOS box should look like this then: C:\Zope-2.8.0-final\bin>python Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
Then type in "from ZConfig.components.logger import loghandler", to try the same import you got a complaint about before. Here's what happens when I do that:
from ZConfig.components.logger import loghandler
That means the import worked fine -- and it should work fine. What happens when you try it?
Tim Peters wrote:
[Pedro Cristian]
I'm a beginner in Zope. I've just installed the Zope 2.8 final package. The installation seems to have completed normally. However when the zope instance is run I have the following message :
C:\Zope-Instance\bin>runzope.bat
C:\Zope-Instance\bin>"C:\Zope-2.8.0-final\bin\python.exe" "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py" -C "C:\Zope-Instance\etc\zope.conf" Traceback (most recent call last): File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 56, in ? run() File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py", line 17, in run import Zope2.Startup File "C:\Zope-2.8.0-final\lib\python\Zope2\__init__.py", line 60, in ? from Zope2.Startup.run import configure File "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\__init__.py", line 26, in ?
from ZConfig.components.logger import loghandler ImportError: No module named components.logger
Sorry, I can't reproduce this, on Win XP Pro SP2:
I have the same problem on Win 2000.
C:\Zope-Instance\bin>runzope.bat
C:\Zope-Instance\bin>"C:\Zope-2.8.0-final\bin\python.exe" "C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py" -C "C:\Zope-Instance\etc\zope.conf"
and that's it -- Zope is running at that point, and there's no more console output. \Zope-Instance\log\event.log shows "Zope Ready to handle requests", though. You may find more clues in your event.log.
There was no previous message with keyword "loghandler" in the mailing list. All Zope services are stopped.
Why the plural ("services" as opposed to "service")? Do you have more than one Zope installed? Installing Zope installs exactly one Windows service (if you allow it to), so I expected to see the singular "service" here. Not trying to be picky for the sake of it, but there must _something_ different in your system from what others are doing.
Here are the system variable that are relevent : CONFIG_FILE=C:\Zope-Instance\etc\zope.conf INSTANCE_HOME=C:\Zope-Instance Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Pinnacle\Shared Files\InstantCDDVD\ PYTHON=C:\Zope-2.8.0-final\bin\python.exe PYTHONPATH=C:\Zope-2.8.0-final\lib\python SOFTWARE_HOME=C:\Zope-2.8.0-final\lib\python ZOPE_HOME=C:\Zope-2.8.0-final ZOPE_RUN=C:\Zope-2.8.0-final\lib\python\Zope2\Startup\run.py
Those look normal. Did you change \Zope-Instance\etc\zope.conf in any way?
The Zope instance is the one created by the install package.
Same for me above.
Seems that something is not working with my configuration, but what?
I don't know, and I haven't seen this reported by anyone else before. Let's try this: cd to your Zope's (not Zope-Instance's) bin directory, and start Python from there. Your DOS box should look like this then:
C:\Zope-2.8.0-final\bin>python Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
Then type in "from ZConfig.components.logger import loghandler", to try the same import you got a complaint about before. Here's what happens when I do that:
from ZConfig.components.logger import loghandler
That means the import worked fine -- and it should work fine. What happens when you try it?
I see the same error message that ZOPE gives. Any solution? Martin
[Tim Peters] ...
I don't know, and I haven't seen this reported by anyone else before. Let's try this: cd to your Zope's (not Zope-Instance's) bin directory, and start Python from there. Your DOS box should look like this then:
C:\Zope-2.8.0-final\bin>python Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
Then type in "from ZConfig.components.logger import loghandler", to try the same import you got a complaint about before. Here's what happens when I do that:
from ZConfig.components.logger import loghandler
That means the import worked fine -- and it should work fine. What happens when you try it?
[Martin Raspe]
I see the same error message that ZOPE gives.
FYI, pasting the exact DOS box input and output (as I did above) saves the reader from needing to guess at 100 details.
Any solution?
Sorry, not unless someone can give useful information. If you're familiar with Python, you should be able to figure out why the import doesn't work, and tell us the solution. If you're not familiar with Python, it will have to wait until someone who is familiar, and can reproduce the problem (I cannot), does this work.
Tim Peters wrote:
That means the import worked fine -- and it should work fine. What happens when you try it?
[Martin Raspe]
I see the same error message that ZOPE gives.
FYI, pasting the exact DOS box input and output (as I did above) saves the reader from needing to guess at 100 details.
Any solution?
Sorry, not unless someone can give useful information. If you're familiar with Python, you should be able to figure out why the import doesn't work, and tell us the solution. If you're not familiar with Python, it will have to wait until someone who is familiar, and can reproduce the problem (I cannot), does this work.
Sorry, I thought that was clear. It says exactly the same as the ZOPE error message: U:\>U:\programme\Zope-2.8.0\bin\python.exe Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
from ZConfig.components.logger import loghandler Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named components.logger
But I think I found the error: On Windows, Python seems to prefer information from the Registry to the environment vars. The wrong registry information was left there from a prior Zope/Plone installation. It seems the Zope-2.8.0 Windows installer does not update the registry for Python, so Python takes a wrong import path. I found out by saying import ZConfig globals() and the wrong directory would show up. Removing the old installation solved the problem. Other Zope installations (2.7.4, 2.7.6) were not affected by the left-over registry entries. So I suppose this is a subtle bug in the 2.8.0 Windows installer. Martin
... [Martin Raspe]
I see the same error message that ZOPE gives.
[Tim Peters]
FYI, pasting the exact DOS box input and output (as I did above) saves the reader from needing to guess at 100 details.
Any solution?
Sorry, not unless someone can give useful information. If you're familiar with Python, you should be able to figure out why the import doesn't work, and tell us the solution. If you're not familiar with Python, it will have to wait until someone who is familiar, and can reproduce the problem (I cannot), does this work.
[Martin]
Sorry, I thought that was clear. It says exactly the same as the ZOPE error message:
U:\>U:\programme\Zope-2.8.0\bin\python.exe Python 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
from ZConfig.components.logger import loghandler Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named components.logger
Thank you -- that way we don't have to guess about anything. I note there that you did _not_ run Python while in Zope's bin\ directory, but instead ran it while in the root of your U: disk. That differs from what I did, and may be significant (although I doubt it, the current directory does play a role in setting up sys.path).
But I think I found the error: On Windows, Python seems to prefer information from the Registry to the environment vars.
No, despite popular myth, Python on Windows normally doesn't consult the registry for anything. The exception is obscure "application paths", never used in core Python, described in the near-inscrutable comment block at top of this: http://cvs.sf.net/viewcvs.py/python/python/dist/src/PC/getpathp.c?rev=1. Unfortunately, older (than build 204) versions of the pywin32 (aka win32all) extensions did set "application paths" in the registry, and Zope used to go on to install pywin32 in a broken way, causing no end of potential PYTHONPATH confusions. The Zope Windows installer does not (and never did) set "application paths" in this sense.
The wrong registry information was left there from a prior Zope/Plone installation.
Do recall exactly which registry keys seemed to be significant?
It seems the Zope-2.8.0 Windows installer does not update the registry for Python,
As above.
so Python takes a wrong import path.
Since Python doesn't normally consult the registry to build sys.path, I don't think the problem is understood yet.
I found out by saying import ZConfig globals() and the wrong directory would show up.
I'm not clear on what you did here. Earlier you showed that you were unable to import ZConfig.components.logger. But you _were_ able to import ZConfig on its own?
Removing the old installation solved the problem.
That's good -- I think <wink>.
Other Zope installations (2.7.4, 2.7.6) were not affected by the left-over registry entries.
Which registry entries, specifically?
So I suppose this is a subtle bug in the 2.8.0 Windows installer.
The Zope Windows installer installs pywin32 in a very different way than it used to, and installs a very different version of pywin32 than it used to, but the zope.iss.in files (which are the input Inno Setup uses to build the installer, and which contain the code for setting Zope's registry entries) are byte-for-byte identical across 2.7 and 2.8.
Just to chirp in, I just tried to install 2.8 on my dev box and I am receiving the same error (XP SP2) Previous versions of Zope that have been (and still are) installed: 2.7.3, 2.7.5, 2.7.6
--On 28. Juli 2005 13:59:54 +1200 Chris Beaven <chris@d-designz.co.nz> wrote:
Just to chirp in, I just tried to install 2.8 on my dev box and I am receiving the same error (XP SP2)
Could you please tell us *which error*? The people in charge for fixing such issues need some more useful information that "the same error". -aj
participants (5)
-
Andreas Jung -
Chris Beaven -
Martin Raspe -
Pedro Cristian -
Tim Peters