Hi there! I am running a Debian Linux box with Debian/testing (Sarge) and I am trying to get Plone up and running. I have made a clean, new install of the whole system last week, so all packages are really up-to-date and there was no dirty installation that was updated. I have noticed that the Plone package on Debian is or was somewhat broken, but there was a notice about that on the Plone website (download page) which has disappeared. For me that looked like this problem was fixed by the package maintainer. Unfortunately still, after installing Plone (and implicitly thus Zope 2.7) Zope did not want to come up, saying: Zope starting all instances.... '*' is an old/purged instance, not started What is wrong here? I know I have to set up a new Plone site (obviously using the Zope interface at http://localhost:9673), but how can I when Zope is not running. Any help is greatly appreciated! Cheers, Peter -- "Free software is like free speech, not free beer" (Richard Stallman)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Bittner wrote:
I am running a Debian Linux box with Debian/testing (Sarge) and I am trying to get Plone up and running. I have made a clean, new install of the whole system last week, so all packages are really up-to-date and there was no dirty installation that was updated.
I have noticed that the Plone package on Debian is or was somewhat broken, but there was a notice about that on the Plone website (download page) which has disappeared. For me that looked like this problem was fixed by the package maintainer.
Unfortunately still, after installing Plone (and implicitly thus Zope 2.7) Zope did not want to come up, saying:
Zope starting all instances.... '*' is an old/purged instance, not started
What is wrong here?
You need to supply more detail, like showing the exact working directory, comand lines, etc. you used, and the full traceback, if any. Also note that the Debian maintainer should probably be your first line of contact: very few folks on this list are likely to grok the details of packaging for Debian.
I know I have to set up a new Plone site (obviously using the Zope interface at http://localhost:9673), but how can I when Zope is not running.
Any help is greatly appreciated!
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 iD8DBQFCTWNCGqWXf00rNCgRAioBAJ9TjpjdUT9dvzS88pYt+h3+qHLfWgCffyhs 0WUBtrHLRi4YSJzl+XF0ZOA= =l//E -----END PGP SIGNATURE-----
google search for your error message yielded: http://mail.zope.org/pipermail/zope/2005-January/155790.html If you did an 'apt-get install plone' it's still trying to pull in Zope 2.6. What I ended up doing was to uninstall plone and then 'apt-get install zope2.7', create my default instance w/ mkzopeinstance.py (installed to /var/lib/zope2.7/instance/default) and then just dropped the Plone, etc packages into my /instances/default/Producs folder. Shane On Apr 1, 2005 10:05 AM, Tres Seaver <tseaver@zope.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Peter Bittner wrote:
I am running a Debian Linux box with Debian/testing (Sarge) and I am trying to get Plone up and running. I have made a clean, new install of the whole system last week, so all packages are really up-to-date and there was no dirty installation that was updated.
I have noticed that the Plone package on Debian is or was somewhat broken, but there was a notice about that on the Plone website (download page) which has disappeared. For me that looked like this problem was fixed by the package maintainer.
Unfortunately still, after installing Plone (and implicitly thus Zope 2.7) Zope did not want to come up, saying:
Zope starting all instances.... '*' is an old/purged instance, not started
What is wrong here?
You need to supply more detail, like showing the exact working directory, comand lines, etc. you used, and the full traceback, if any. Also note that the Debian maintainer should probably be your first line of contact: very few folks on this list are likely to grok the details of packaging for Debian.
I know I have to set up a new Plone site (obviously using the Zope interface at http://localhost:9673), but how can I when Zope is not running.
Any help is greatly appreciated!
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
iD8DBQFCTWNCGqWXf00rNCgRAioBAJ9TjpjdUT9dvzS88pYt+h3+qHLfWgCffyhs 0WUBtrHLRi4YSJzl+XF0ZOA= =l//E -----END PGP SIGNATURE-----
_______________________________________________ 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 )
On 01.Apr 2005 - 10:14:36, Shane Graber wrote:
google search for your error message yielded:
http://mail.zope.org/pipermail/zope/2005-January/155790.html
If you did an 'apt-get install plone' it's still trying to pull in Zope 2.6.
That's not correct, current Plone will favor zope27 over zope package, you can see that in the dependecies. However, the Plone Product(s) will still be installed in a path where the old Zope2.6 will find it and thus are not automatically seen by Zope2.7. Anyway, how this can be changed and how to setup the 2.7 zope is explained via debconf-pages during the installation of zope27 and plone and even when you disable debconf, you can still do RTFM in /usr/share/doc/(zope|plone). I tried it lately and it took about 5 Minutes to get both zope27 and plone up and running (including installtion via apt-get). Andreas -- You will be traveling and coming into a fortune.
On 01.Apr 2005 - 14:34:22, Peter Bittner wrote:
Hi there!
I am running a Debian Linux box with Debian/testing (Sarge) and I am trying to get Plone up and running. I have made a clean, new install of the whole system last week, so all packages are really up-to-date and there was no dirty installation that was updated.
I have noticed that the Plone package on Debian is or was somewhat broken, but there was a notice about that on the Plone website (download page) which has disappeared. For me that looked like this problem was fixed by the package maintainer.
Unfortunately still, after installing Plone (and implicitly thus Zope 2.7) Zope did not want to come up, saying:
Did you read the debconf-pages that were presented to you during the installation of zope and plone? I guess not, because else you won't ask that question. Short answer: create a new Zope instance using mkzope2.7instance, check it's config and remove the '#' on the lines: products /usr/lib/zope2.7/lib/python/Products products /usr/lib/zope/lib/python/Products products $INSTANCE/Products To have Zope 2.7 find the Plone Product. The documentation of Zope and Plone will explain why you need to do that.
Zope starting all instances.... '*' is an old/purged instance, not started
Looks like Zope2.7 finds an old 2.6 instance, but I'm not sure... Andreas -- You're definitely on their list. The question to ask next is what list it is.
The moral of this whole story seems to shine through: Don't install Zope from OS packages like debian, they never get it right and you will just end up getting confused ;-) cheers, Chris Andreas Pakulat wrote:
On 01.Apr 2005 - 14:34:22, Peter Bittner wrote:
Hi there!
I am running a Debian Linux box with Debian/testing (Sarge) and I am trying to get Plone up and running. I have made a clean, new install of the whole system last week, so all packages are really up-to-date and there was no dirty installation that was updated.
I have noticed that the Plone package on Debian is or was somewhat broken, but there was a notice about that on the Plone website (download page) which has disappeared. For me that looked like this problem was fixed by the package maintainer.
Unfortunately still, after installing Plone (and implicitly thus Zope 2.7) Zope did not want to come up, saying:
Did you read the debconf-pages that were presented to you during the installation of zope and plone? I guess not, because else you won't ask that question. Short answer: create a new Zope instance using mkzope2.7instance, check it's config and remove the '#' on the lines:
products /usr/lib/zope2.7/lib/python/Products products /usr/lib/zope/lib/python/Products products $INSTANCE/Products
To have Zope 2.7 find the Plone Product. The documentation of Zope and Plone will explain why you need to do that.
Zope starting all instances.... '*' is an old/purged instance, not started
Looks like Zope2.7 finds an old 2.6 instance, but I'm not sure...
Andreas
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On 04.Apr 2005 - 14:02:43, Chris Withers wrote:
The moral of this whole story seems to shine through:
Don't install Zope from OS packages like debian, they never get it right and you will just end up getting confused ;-)
Yepp, especially, since Zope is that easy to install into your home... Andreas -- Chicken Little was right.
Andreas Pakulat wrote:
On 04.Apr 2005 - 14:02:43, Chris Withers wrote:
The moral of this whole story seems to shine through:
Don't install Zope from OS packages like debian, they never get it right and you will just end up getting confused ;-)
Yepp, especially, since Zope is that easy to install into your home...
Andreas
I (a relative zope amateur) would offer my own counter-experience. I recently set up zope-coreblog and zope2.7 (using packages from debian sarge/testing), and it's been running with very few issues for several months (and I additionally was able to get ldap integration working using the ldapuserfolder Product) maybe the "better" or "surer" way to do things is to install zope (os-agnostic) binaries, but being already familiar with debian, for me it's worked out fine (so far) to use the debian-packaged stuff (though I've admittedly not played substantially with plone yet) ~c
charlie derr wrote:
I (a relative zope amateur) would offer my own counter-experience. I recently set up zope-coreblog and zope2.7 (using packages from debian sarge/testing), and it's been running with very few issues for several months (and I additionally was able to get ldap integration working using the ldapuserfolder Product)
Wait till you want to use a feature or need a bugfix from a later point release than the one you're currently on ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Mon, Apr 04, 2005 at 02:02:43PM +0100, Chris Withers wrote: | The moral of this whole story seems to shine through: | | Don't install Zope from OS packages like debian, they never get it right | and you will just end up getting confused ;-) Never say never. The problem with debian is the former zope maintainers are no longer maintaining the packages and only very recently has a replacement stepped up to update the packages and resolve the outstanding issues. The current situation is filled with bit-rot, but before that began the packages were just fine. It would seem, too, that the bit-rot will recede in the near future. In the meantime, I would recommend using the upstream source for installation. -D -- \begin{humor} Disclaimer: If I receive a message from you, you are agreeing that: 1. I am by definition, "the intended recipient" 2. All information in the email is mine to do with as I see fit and make such financial profit, political mileage, or good joke as it lends itself to. In particular, I may quote it on USENET or the WWW. 3. I may take the contents as representing the views of your company. 4. This overrides any disclaimer or statement of confidentiality that may be included on your message \end{humor} www: http://dman13.dyndns.org/~dman/ jabber: dman@dman13.dyndns.org
On 05.Apr 2005 - 12:01:14, Derrick Hudson wrote:
On Mon, Apr 04, 2005 at 02:02:43PM +0100, Chris Withers wrote: | The moral of this whole story seems to shine through: | | Don't install Zope from OS packages like debian, they never get it right | and you will just end up getting confused ;-)
The current situation is filled with bit-rot,
?? bit-rot?
but before that began the packages were just fine. It would seem, too, that the bit-rot will recede in the near future. In the meantime, I would recommend using the upstream source for installation.
As I said, if you install zope27 you get a message what to do next to get the instance up and running. The same with plone. The only drawback at the moment is, that you need to change the zope.conf to get some packages to work with zope27. This will probably change when Debian finally drops zope26 (I don't understand why they keep it anyway...) Andreas -- Tuesday After Lunch is the cosmic time of the week.
participants (7)
-
Andreas Pakulat -
charlie derr -
Chris Withers -
Derrick Hudson -
Peter Bittner -
Shane Graber -
Tres Seaver