Hi, my plone server 4.0.5 just stopped working, is it possible to recover all the data on new 5.0 plone? if so how to do it?
Than you for your help.
We need to know more, e.g. buildout.cfg, operating system, how you know it stopped working, etc.
It's probably better to figure out what the problem is on your current site than to compound the problem...
Ok so at 21 of march server lost power and then it stopped working just stuck on starting plone 4.0.5 i had to remove init.d daemon just to start the system(debian 6.0). here is the old builout:
############################################
#
# Buildout Configuration File for Standalone Plone
# ------------------------------------------------
# $LastChangedDate: 2011-04-10 09:34:13 -0700 (Sun, 10 Apr 2011) $ $LastChangedRevision: 47921M $
#
# After making changes in this configuration file,
# you should run bin/buildout to update the components.
#
# ALWAYS back up all Plone/Zope data and components
# before changing configuration.
#
# Running "bin/buildout" will update your installation,
# installing missing components as necessary.
#
# Use "bin/buildout -n" to update many components here to the newest
# available releases.
# This will update the add-on products you've added in the eggs= lines.
# This will not, however, upgrade Plone itself (or anything else you've
# pinned with a version specification). To upgrade Plone itself, see the
# comments in "Plone Component Versions".
#
# Tutorial instructions for using zc.buildout for
# configuration management are available at:
# http://plone.org/documentation/tutorial/buildout
# Full details at http://pypi.python.org/pypi/zc.buildout
#
############################################
[buildout]
############################################
# Plone Component Versions
# ------------------------
# This version of the Unified Installer has the components of Plone 4
# preloaded so that it can install without an Internet connection.
# If you want to update, uncomment the "http://..." line below,
# edit it to point to the current version URL, comment out the
# "versions.cfg" line and run "bin/buildout" while attached to the
# Internet. Generally, you only want to do that as part of a planned migration.
# Note that if you are updating components, you should also check the versions
# section at the end of this file, since recipes or components other than
# those of Zope and Plone may need updating at the same time.
#
extends =
base.cfg
versions.cfg
# http://dist.plone.org/release/4.0-latest/versions.cfg
############################################
# Ports
# -----
# Specify the port on which your Zope installation
# will listen:
# 0.0.0.0 - klausomasi is visu IP
# http-adress = 0.0.0.0:8080
http-address = 0.0.0.0:8080
# If you try to start Zope as root, it will change user id to run as
# the effective user specified here. This user id must own the var directory
# of your buildout.
effective-user = plone-user
############################################
# Eggs
# ----
# Add an indented line to the eggs section for any Python
# eggs or packages you wish to include.
#
eggs =
Plone
PIL==1.1.6
plone.app.ldap
quintagroup.plonecomments
# Optional Functionality
# ----------------------
# Uncomment the indented lines to include these add-on products.
# Documentation on all of them, along with many more products,
# is available at
# http://plone.org/products/
#
# Example products:
# * LinguaPlone provides tools for building multi-lingual sites
# * PloneFormGen provides through-the-web form building
#
# Products.LinguaPlone==4.0.1
# Products.PloneFormGen==1.6.0
#
# Note that versions may be specified here or in the [versions]
# section below. You should always specify versions that you know
# are compatible with the Plone release and at an acceptable
# development level.
#
# Commonly used development tools:
# Several excellent development tools are included in the develop.cfg
# buildout extension. Read it to learn how to activate these tools.
# Products.PloneKeywordManager
############################################
# ZCML Slugs
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. This is increasingly rare.
zcml =
plone.app.ldap
# plone.reload
quintagroup.plonecomments
quintagroup.plonecomments-overrides
############################################
# Development Eggs
# ----------------
# You can use paster to create "development eggs" to
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.
#
# Provide the *paths* to the eggs you are developing here:
develop =
# src/my.package
############################################
# Debug Mode
# ----------
# Change debug-mode to "on" to run in development mode.
# This will dramatically slow Plone.
#
debug-mode = off
# Add-on developers should turn deprecation warnings on
deprecation-warnings = off
# change verbose-security to "on" for useful security errors while developing
verbose-security = off
############################################
# Backup Directory
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but ideally
# this should be on a separate volume or backup server.
#
backups-dir=${buildout:directory}/var
############################################
# Initial User
# ------------
# This is the user id and password that will be used to create the initial
# user id that will allow you to log in and create a Plone site. This only
# sets the initial password; it will not allow you to change an already
# existing password. If you change the admin password via the web interface,
# the one below will no longer be valid.
# If you find yourself locked out of your Zope/Python installation, you may
# add an emergency user via "bin/plonectl adduser".
user=admin:xxxxxxxxx
############################################
# Parts Specification
#--------------------
# Specifies the components that should be included in the buildout.
# All the basics are in the base.cfg extension; you may add your
# own if you need them at the end of this file.
parts =
instance
zopepy
zopeskel
unifiedinstaller
chown
############################################
# Versions Specification
# ----------------------
# Version information supplied here will "pin" Python packages to a particular
# version number, even when you use the "newest" flag running buildout.
# Specifying versions for all packages is a good idea and can prevent
# accidental changes when you add new packages to your buildout.
# Note that versions specified here will override those specified earlier
# in the configuration, including those from the Plone and Zope version
# config files.
#
[versions]
Cheetah = 2.2.1
Paste = 1.7.5.1
PasteScript = 1.7.3
ZopeSkel = 2.19
collective.recipe.backup = 1.7
plone.recipe.command = 1.1
plone.recipe.osxcontroller = 0.4
plone.recipe.unifiedinstaller = 4.0rc1
#Required by:
#PasteScript 1.7.3
PasteDeploy = 1.3.4
#[instance]
#
#zope-conf-additional = <zodb_db kaukodok_testing>
# # Kaukodok testavimas
# cache-size 10000
# # Blob-enabled FileStorage database
# <blobstorage>
# blob-dir /var/www/plone/zinstance/var/blobstorage/kaukodok_testing
# <filestorage>
# path /var/www/plone/zinstance/var/filestorage/kaukodok_testing/Data.fs
# </filestorage>
# </blobstorage>
# mount-point /kaukodok_testing
# </zodb_db>
#Kauko planai
#zope-conf-additional = <zodb_db planai>
# cache-size 20000
# <blobstorage>
# blob-dir /var/www/plone/zinstance/var/blobstorage/planai
# <filestorage>
# path /var/www/plone/zinstance/var/filestorage/planai/Data.fs
# </filestorage>
# </blobstorage>
# mount-point /planai
# </zodb_db>is almost impossible to read this; use the right formating or paste it in another place.
IMO, nobody is going to take the time to help you otherwise.
You did not provide any information about "stopped working" exactly means...error messages? What exactly is not working? What are you doing? What is the expected behavior and where does it differ?
-aj
Solved it, thanks for your help.
What was the problem and fix?
the problem was with exim, i deleted exim logs then restarted it, and rerun biuldout and that's it.
thanks!
1 Like
Now i have other question: how do i migrate from 4.0.5 to 5 plone?
What has Exim to do with Plone? Nothing...please explain in depth.
-aj