System upgraded to python-2.2.2. Was using zope-2.6.0-r1. zope would not start using /etc/init.d/zope start: "Zope failed to start" results. Tried the following: nlinuxserver 2.6.0 # python z2.py z2.py:385: UserWarning: You are running Python version 2.2.2. This Python version has not yet been tested with Zope and you may experience operational problems as a result. Consider using Python 2.1.3 instead. warnings.warn(err) /usr/share/zope/2.6.0/lib/python/ZPublisher/BaseRequest.py:21: RuntimeWarning: Python C API version mismatch for module ExtensionClass: This Python has API version 1011, module ExtensionClass has version 1010. from ExtensionClass import Base Looked at the zope ebuild script and it DEPENDS on python-2.1.3. This zope version is failing to start due the the later python version it appears. I am not sure how to roll back python to 2.1.3 from 2.2.2. Obviously, if you remove python 2.2.2, then you are in trouble with portage, emerge and all the Gentoo programs that require python. Also, after emerging zope the post-emerge directs you to configure using: ebuild /var/db/pkg/net-www/zope/zope/2.6.0-r1/zope-2.6.0-r1.ebuild config the zope package in now in it's own tree of: var/db/pkg/net-zope/zope-2.6.0-r1/zope-2.6.0-r1.ebuild so this needs to be changed. I had two versions of zope showing up (one for each of the two portage tree paths--net-www/zope and net-zope/zope in the gentoo package database. I had to do emerge --unmerge directly on both of the ebuild scripts in these separate paths to get rid of both of them in the gentoo package DB and then I reinstalled the /net-zope/ model and now there is only one--the correct one. I had zope running fine until I completed an update that allowed python to go to 2.2.2. Now I am dead in the water with zope since I can't revert to the previous version of python (2.1.3) which zope DEPENDS on. I am going to put zope on a separate non-gentoo box until these issues are sorted out in the meantime. Reproducible: Always Steps to Reproduce: 1. emerge zope 2. emerge --update python (2.2.2) 3. zope won't start Actual Results: see details Expected Results: expected [OK] from /etc/init.d/zope start emerges all worked without any problem with the exception of the configuration path issue previously described
What does it show: python2.1 -V How about: emerge =python-2.1.3-r1 -p Python-2.1* and python-2.2* can co-exists. Not sure why python-2.1* was removed during an upgrade, because python uses SLOTs. Thanks, --kutsuya
Okay. I found a couple of things. First, I used the emerge =python-2.1.3-r1 you suggested and I have now have both 2.1.3 and 2.2.2 on my system. Voila. Great fix. I learned something there. The message at the end of the zope emerge is: >>> original instance of package unmerged safely. * To get zope running you must execure the following: * ebuild /var/db/pkg/net-www/zope-2.6.0-r1/zope-2.6.0-r1.ebuild config >>> Regenerating /etc/ld.so.cache... >>> net-zope/zope-2.6.0-r1 merged. the word "execute' is mispelled and the directory net-www/zope-2.6.0-r1 does not exist. It is net-zope/zope-2.6.0-r1. Small points, but while I am at this... If you use: ebuild /var/db/pkg/net-zope/zope-2.6.0-r1/zope-2.6.0-r1.ebuild config instead, the script to configure zope runs fine. Next, I attempted to start zope-2.6.0-r1 in its /usr/share/zope/2.6.0 directory using "python2.1 z2.py" and I do not get the same squawking about Python 2.2.2. However, if I quickly do a ps -aux I see 2 zope/python processes attempting to start, but they quickly die. Since I know I have python-2.1.3 (python2.1) I retried the /etc/init.d/zope start and got: nlinuxserver 2.6.0 # /etc/init.d/zope start * Starting zope... * Failed to start zope [ !! ] nlinuxserver 2.6.0 # So the z2.py zope python module is choking and it is not that python or the wrong version is to blame here. It may be the zope release. I am not sure. I have re-emergesd it more than once during all of this, so I am not sure why it is choking. I have another gentoo partition on my laptop that I boot to using grub or to MS WIN2K (sorry I am not proud to say that). I will try to duplicate the same ebuilds/emerges on my laptop (python 2.2.2 and python 2.1.3) and zope 2.6.0 to see if the behavior is the same. I am not sure which version of python I have on the laptop now, but I am hoping I only have 2.1.3. I am speculating that maybe there is some interaction with the pyhton 2.2.2 version when zope is being compiled/installed. If I can't duplicate this on my laptop and zope runs okay, then my other system is dorked up somehow I would guess. I did have it working until I did a emerge --update world and that is when the trouble started. Zope would not start after that. ***David Miller
Well my first guess is that there might be a .pid file problem. It's an issue with zope-2.6.0-r1. Somethings to try: # # Let's set zope into debug mode, so can see what's going on. # nano -w /etc/conf.d/zope ZOPE_OPTS="-u root -D" ... # /etc/init.d/zope start * Starting zope... * Failed to start zope [ !! ] # # the command 'stop' moves old .pid files out of the way. # /etc/init.d/zope stop # /etc/init.d/zope start I re-commited zope-2.6.0-r1.ebuild with some of the fixes you suggested. Thanks for the help. Let me know how it goes. --kutsuya
Found problem arose from a questionable emerge --update world. Found problems with other programs. Accomplished an emerge update using --emptytree and remerged zope. Apprears to be functioning normally at this time. However, my laptop which had a gentoo partition and for which I also had accomplished an emerge update world at about the same time appears to be permanently dorked up. I now cannot commpile anything on that box. Not directly related, but two computers in one day getting whacked by an update is unusual. Up until this recent update, both of my systems had been running fine for a long time using gentoo and zope.