Difference between pages "Zope HOWTO" and "Installation Troubleshooting"

From Funtoo
(Difference between pages)
Jump to: navigation, search
 
 
Line 1: Line 1:
This page documents how to use Zope with Funtoo Experimental, which currently has good Zope support thanks to [[Progress Overlay Python]] integration.
+
This page shows you how to troubleshoot issues with your Funtoo Linux installation.
  
== About Zope ==
+
== Boot failure ==
  
Zope is an Open Source application server framework written in Python. It has an interesting history which you should familiarize yourself with before starting Zope development, as it contains several interesting twists and turns.
+
If you did not get a <tt>login:</tt> prompt, it's possible that your install was not successful. You can reboot from the live CD and bind-mount your existing installation without repartitioning or recreating filesystems, chroot inside, and then check your system to ensure everything is configured properly:
  
=== Zope History ===
 
 
{{fancynote| This HOWTO targets Zope 2.13, which includes Five. It is typically the version you should be using for new Zope projects.}}
 
 
* There are two versions of Zope, Zope 2 and Zope 3. One might assume that Zope 3 is the version that people should use for new software development projects by default, but this is not the case. Most Zope-based projects continue to use Zope 2. Zope 3 was an attempt to redesign Zope 2 from scratch, and is completely different from Zope 2, but it was not adopted by the community.
 
 
* There is also something called [http://codespeak.net/z3/five/ Five] (named because it is "2 + 3") that backports many of the new features of Zope 3 into the Zope 2 framework. Several projects will use Zope 2 plus Five in order to use some of the newer features in Zope. Five was merged into mainline Zope 2 in early 2010, and first appeared in Zope 2.8.
 
 
* You can learn more about the history of Zope 2, 3 and Five in the [http://svn.zope.org/Zope/trunk/src/Products/Five/README.txt?view=markup Five README].
 
 
* To make things even more interesting, work on [http://docs.zope.org/zope2/releases/4.0/ Zope 4] is underway, and it will be based on 2.13 rather than 3.x. It includes a number of [http://docs.zope.org/zope2/releases/4.0/CHANGES.html#restructuring incompatible changes] with prior versions.
 
=== Zope Resources ===
 
 
Now that you understand what version of Zope you should be targeting (2.13), we can point you towards the correct documentation :)
 
 
; '''[http://docs.zope.org/zope2/zope2book/ The Zope 2 Book]'''
 
: This book provides a general introduction to Zope concepts and ZMI. It is a good place to start, but doesn't provide a direct introduction to Zope development. It's recommended that you skim through this book to familiarize yourself with Zope. It generally does not assume much prior knowledge about Web development or Python.
 
; '''[http://docs.zope.org/zope2/zdgbook/ Zope Developer's Guide]'''
 
: This guide will give you a better introduction to Zope development. It assumes you already know Python. Skip chapters 1 and 2 and start in [http://docs.zope.org/zope2/zdgbook/ComponentsAndInterfaces.html chapter 3], which covers components and interfaces. [http://docs.zope.org/zope2/zdgbook/Products.html Chapter 5] covers the creation of your first product.
 
; '''[http://codespeak.net/z3/five/manual.html The Five Manual]'''
 
: We're not done yet. There is a bunch of stuff in Zope 2.13 that is not in the official documentation. Namely, the stuff in Five.
 
; '''[http://docs.zope.org/ztkpackages.html ZTK Documentation]'''
 
: ZTK 
 
; '''ZCA'''
 
: [http://www.muthukadan.net/docs/zca.html A Comprehensive Guide to Zope Component Architecture] offers a good introduction to the programming concepts of ZCA. We also have a new page on [[Zope Component Architecture]] which will help you to understand the big picture of ZCA and why it is useful. ZCML ("Z-camel") is a part of ZCA and  was introduced in Zope 3, so typically you will find ZCML documented within Zope 3 documentation and book.
 
; '''Content Components'''
 
: Views and Viewlets: [http://docs.zope.org/zope.viewlet/index.html This tutorial on viewlets] also contains some viewlet-related ZCML examples near the end. The "Content Component way" of developing in Zope seems to be a Zope 3 thing and tied to ZCML. Chapter 13+ of Stephan Richter's ''Zope 3 Developer's Handbook'' (book) seems to cover this quite well. You will probably also want to check out Philipp Weitershausen's ''Web Component Development with Zope 3'' (book).
 
; '''[http://wiki.zope.org/zope2/Zope2Wiki Zope 2 Wiki]'''
 
: Main wiki page for all things related to Zope 2.
 
; '''[http://docs.zope.org docs.zope.org]'''
 
: This is the main site for Zope documentation.
 
 
== First Steps ==
 
 
First, you will need to emerge {{Package|net-zope/zope}}:
 
 
<console>
 
<console>
###i## emerge zope
+
# ##i##mkdir /mnt/funtoo
 +
# ##i##mount /dev/sda4 /mnt/funtoo
 +
# ##i##mount /dev/sda1 /mnt/funtoo/boot
 +
# ##i##cd /mnt/funtoo
 +
# ##i##mount --bind /proc proc
 +
# ##i##mount --bind /dev dev
 +
# ##i##cp /etc/resolv.conf etc/
 +
# ##i##env -i HOME=/root TERM=$TERM PATH='/bin:/sbin:/usr/bin:/usr/sbin' chroot /mnt/funtoo
 
</console>
 
</console>
  
Zope is now installed.
+
Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:
  
== Project Skeleton ==
 
 
{{fancynote| Zope should be run by a regular user account, not as the root user.}}
 
 
The first step in using Zope is to ensure that you are using a regular user account. Create a new directory called <tt>zope_test</tt>:
 
 
<console>
 
<console>
$##i## cd
+
(chroot) # ##i##exit
$##i## mkdir zope_test
+
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo
 +
# ##i##reboot
 
</console>
 
</console>
  
Now, enter the directory, and create an "instance", which is a set of files and directories that are used to contain a Zope project:
+
If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [http://forums.funtoo.org/ forums].
<console>
+
$##i## cd zope_test
+
$##i## /usr/lib/zope-2.13/bin/mkzopeinstance
+
</console>
+
  
You will see the following output, and will be prompted to answer a few questions:
+
== Debugging system startup ==
<console>
+
Please choose a directory in which you'd like to install
+
Zope "instance home" files such as database files, configuration
+
files, etc.
+
  
Directory: instance
+
<tt>/etc/rc.conf</tt> contains system settings related to the system initialization scripts. If you are experiencing problems with the system startup scripts, you may find it beneficial to set <tt>rc_logger</tt> to <tt>YES</tt>. This will instruct OpenRC to launch a logging daemon to log the entire rc process to <tt>/var/log/rc.log</tt>.
Please choose a username and password for the initial user.
+
These will be the credentials you use to initially manage
+
your new Zope instance.
+
  
Username: admin
+
== Graphics Corruption at boot ==
Password: ****
+
Verify password: ****
+
</console>
+
 
+
Now, we will start our Zope instance:
+
<console>
+
$##i## cd instance
+
$##i## bin/runzope
+
</console>
+
 
+
Now that Zope is running, you can visit <tt>localhost:8080</tt> in your Web browser. You will see a nice introductory page to Zope.
+
 
+
If you now go to the <tt>localhost:8080/manage</tt> URL, you will be prompted to log in. Enter the username and password you specified. You are now logged in to the ZMI (Zope Management Interface.)
+
 
+
You can stop your application by pressing Control-C. In the future, you can start and stop your Zope instance using the following commands:
+
 
+
<console>
+
$##i## zopectl start
+
$##i## zopectl stop
+
</console>
+
 
+
{{fancynote| <tt>zopectl start</tt> will cause your instance to run in the background rather than consuming a shell console.}}
+
 
+
== First Project ==
+
 
+
We will create a single very primitive Zope package, consisting of an Interface for a TODO class, and a TODO class.
+
 
+
Create the following files and directories relative to your project root:
+
 
+
* Create the directory <tt>lib/python/example</tt>.
+
* Create the file <tt>lib/python/example/__init__.py</tt> by typing <tt>touch lib/python/example/__init__.py</tt>.
+
* Create these files:
+
 
+
=== <tt>example-configure.zcml</tt> ===
+
 
+
This file registers the <tt>example</tt> directory you created in <tt>lib/python</tt> as a ''package'', so that it is seen by Zope. Edit <code>/etc/package-includes/example-configure.zcml</code>:
+
  
 +
If you experience graphics corruption issues at boot time, you may be experiencing an issue with the [http://fedoraproject.org/wiki/Features/KernelModesetting Kernel Mode Setting subsystem], known as KMS. To resolve this problem, boot from the live CD again [[#boot failure|following the steps above]]. Then, from within the chroot, edit <tt>/etc/boot.conf</tt> and add the line "<tt>params += nomodeset</tt>" to the "<tt>Funtoo Linux genkernel</tt>" section. Your <tt>/etc/boot.conf</tt> should now look like this:
  
 
<pre>
 
<pre>
<include package="example" />
+
"Funtoo Linux genkernel" {
 +
        kernel kernel[-v]
 +
        initrd initramfs[-v]
 +
        params += real_root=auto
 +
        params += nomodeset
 +
}
 
</pre>
 
</pre>
  
=== <tt>interfaces.py</tt> ===
+
Now, save your changes and run <tt>boot-update</tt>:
  
The following file defines the <tt>ITODO</tt> interface, and also uses some Zope Schema functions to define what kind of data we expect to store in objects that implement <tt>ITODO</tt>. Edit <code>/lib/python/example/interfaces.py</code> with your favorite text editor:
 
 
<syntaxhighlight lang="python">
 
from zope.interface import Interface
 
from zope.schema import List, Text, TextLine, Int
 
 
class ITODO(Interface):
 
    name = TextLine(title=u'Name', required=True)
 
    todo = List(title=u"TODO Items", required=True, value_type=TextLine(title=u'TODO'))
 
    daysleft = Int(title=u'Days left to complete', required=True)
 
    description = Text(title=u'Description', required=True)
 
</syntaxhighlight>
 
 
=== <tt>TODO.py</tt> ===
 
 
Now, we define <tt>TODO</tt> to be a ''persistent'' object, meaning it can be stored in the ZODB. We specify that it implements our previously-defined <tt>ITODO</tt> interface, and provide reasonable defaults for all values when we create a new TODO object. Edit <code>/lib/python/example/TODO.py<code> using your favorite text editor:
 
<syntaxhighlight lang="python">
 
from persistent import Persistent
 
from zope.interface import implements
 
from example.interfaces import ITODO
 
 
class TODO(Persistent):
 
    implements(ITODO)
 
    name = u''
 
    todo = []
 
    daysleft = 0
 
    description = u''
 
</syntaxhighlight>
 
 
=== <tt>configure.zcml</tt> ===
 
 
Create the <tt>/lib/python/example/configure.zcml</tt> configuration file:
 
<syntaxhighlight lang="xml">
 
<configure xmlns="http://namespaces.zope.org/zope"
 
    xmlns:five="http://namespaces.zope.org/five"
 
    xmlns:browser="http://namespaces.zope.org/browser">
 
</configure>
 
</syntaxhighlight>
 
 
== Debug Mode ==
 
 
We can test our first project by entering debug mode:
 
 
<console>
 
<console>
$##i## bin/zopectl debug
+
(chroot) # ##i##boot-update
Starting debugger (the name "app" is bound to the top-level Zope object)
+
 
</console>
 
</console>
  
Now, let's try creating a new TODO object and writing it out to a ZODB database:
+
Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions.
<console>
+
>>> from ZODB import FileStorage, DB
+
>>> storage = FileStorage.FileStorage('mydatabase.fs')
+
>>> db = DB(storage)
+
>>> connection = db.open()
+
>>> import transaction
+
>>> root = connection.root()
+
>>> from example.TODO import TODO
+
>>> a = TODO
+
>>> a.name = u'My TODOs'
+
>>> a.TODOS = [ u'Do Laundry', u'Wash Dishes' ]
+
>>> a.daysleft = 1
+
>>> a.description = u'Things I need to do today.'
+
>>> root[u'today'] = a
+
>>> transaction.commit()
+
</console>
+
  
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
[[Category:Featured]]
+
[[Category:Install]]

Revision as of 22:56, 19 February 2014

This page shows you how to troubleshoot issues with your Funtoo Linux installation.

Boot failure

If you did not get a login: prompt, it's possible that your install was not successful. You can reboot from the live CD and bind-mount your existing installation without repartitioning or recreating filesystems, chroot inside, and then check your system to ensure everything is configured properly:

# mkdir /mnt/funtoo
# mount /dev/sda4 /mnt/funtoo
# mount /dev/sda1 /mnt/funtoo/boot
# cd /mnt/funtoo
# mount --bind /proc proc
# mount --bind /dev dev
# cp /etc/resolv.conf etc/
# env -i HOME=/root TERM=$TERM PATH='/bin:/sbin:/usr/bin:/usr/sbin' chroot /mnt/funtoo

Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:

(chroot) # exit
# umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo 
# reboot

If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the forums.

Debugging system startup

/etc/rc.conf contains system settings related to the system initialization scripts. If you are experiencing problems with the system startup scripts, you may find it beneficial to set rc_logger to YES. This will instruct OpenRC to launch a logging daemon to log the entire rc process to /var/log/rc.log.

Graphics Corruption at boot

If you experience graphics corruption issues at boot time, you may be experiencing an issue with the Kernel Mode Setting subsystem, known as KMS. To resolve this problem, boot from the live CD again following the steps above. Then, from within the chroot, edit /etc/boot.conf and add the line "params += nomodeset" to the "Funtoo Linux genkernel" section. Your /etc/boot.conf should now look like this:

"Funtoo Linux genkernel" {
        kernel kernel[-v]
        initrd initramfs[-v]
        params += real_root=auto 
        params += nomodeset
} 

Now, save your changes and run boot-update:

(chroot) # boot-update

Now, exit the chroot, unmount filesystems and reboot following the boot failure instructions.