This FAQ is created to help users find answers to their queries regarding the use of the ERP5 LiveCD.
This is a compilation of questions and answers collected from various discussions about the LiveCD and its usage.
Information about how to download and get started with the LiveCD can be found at DownloadLiveCd.
If you read this and would like to improve it, please go ahead and edit Wiki provided you try to stick to the writing style. If you still have questions, join the email@example.com mailing list http://mail.nexedi.com/mailman/listinfo/erp5-users.
Q: When I try to install a business template after booting from the LiveCD, I get an error message about missing base_id attribute.
Probably you are trying to install a CVS business template into the old erp5 site that came with the LiveCD. The default site has been created before you updated ERP5 - that's why it is recommended to create a new ERP5 Site.
Q: I created some objects in an X module, but they do not show on the list in the module
When creating the site, did you check "I want CMF Activity", or "I'll use it later"? If you are using CMF Activity (verify its existance by checking if a tool named portal_activities exists in your site), then the catalog is not refreshed automatically. You have to configure and run a script called zope_tic_loop, it will flush activities every 5 seconds.
Note that you don't have to run the script manually, as it is started by inittab.
Starting from version 1.0rc8, there is no longer need of zope_tic_loop. It was replaced by a Zope Product called Timer Service.
One problem may happen with TimerService, it uses gethostname(gethostbyname()) to guess the address of the current node, so if you change your network configuration, you better check the IP address corresponding to your hosname in /etc/hosts .
Q: Upon configuring the eth0 interface with a static IP, I started getting 'kernel logger: Disabling IRQ #11' messages
When booting from livecd turn-off apic by giving noapic:
Q: How can I persist my network settings across reboots?
Copy the file /root/config.xml into /mnt/erp5_cd and edit it to reflect your network settings.
An example of static IP configuration in config.xml is as follows:
<erp5> <group id="nexedi"> <host id="master"> <hostname>iaphoenix-erp5</hostname> <domainname>sampledomain.net</domainname> <connection_type>static</connection_type> <!-- static or dhcp --> <network_device>eth0</network_device> <ip_address>192.168.1.101</ip_address> <netmask>255.255.255.0</netmask> <network_address>192.168.1.0</network_address> <broadcast_address>192.168.1.255</broadcast_address> <gateway>192.168.1.1</gateway> <nameservers>126.96.36.199 188.8.131.52</nameservers> <!-- separated by spaces--> <wlan_wep_key></wlan_wep_key> <wlan_essid></wlan_essid> <wlan_channel></wlan_channel> <cups_network></cups_network> <time_zone>Asia/Singapore</time_zone> <!-- Look in /usr/share/zoneinfo/ --> <system_language>en_US</system_language> <!-- lang_COUNTRY --> <root_password>erp5root</root_password> <user_password>erp5user</user_password> <zope_password>zope</zope_password> <web_password>erp5web</web_password> <!-- Not used --> </host> </group> </erp5>
Q: How can I customise some services and/or settings after booting from the livecd?
Create a file /mnt/erp5_cd/config.sh and enter all you need to custom configure into it. Upon boot-up the configuration settings from config.sh shall be effected. This is useful to, for example, start certain services that may not have been started by default or setting up cron jobs onto your livecd machine.
Here is an example of a custom config.sh file I use to automaticcally configure the server with auto-offsite backups and minimum services:
# Reduce the MTU, because some networks drop long packets ifconfig eth0 mtu 576 ifconfig eth1 mtu 576 # Register the cron backup entries cp /mnt/erp5_cd/config/cron/* /etc/cron.d/ # Copy rsa key in root folder for unattended backup ## XXX why root ???? rm -rf /root/.ssh mkdir /root/.ssh cp -R /mnt/erp5_cd/config/ssh-root-autologin/* /root/.ssh/ # Lauch openvpn with good certificates #cp -f /mnt/erp5_cd/config/openvpn/* /etc/openvpn/ #/etc/init.d/openvpn restart # Stop unecessary services to have a light server /etc/init.d/nfs stop /etc/init.d/netfs stop /etc/init.d/nfslock stop /etc/init.d/postfix stop /etc/init.d/portmap stop /etc/init.d/xfs stop /etc/init.d/cups stop # Be sure that most important services are running /etc/init.d/mysql-max restart /etc/init.d/crond restart /etc/init.d/zope restart
Here is the content of the /mnt/erp5_cd/config directory:
[root@erp5 config]# pwd /mnt/erp5_cd/config [root@erp5 config]# ls -R1 .: cron/ openvpn/ rsync.log rsync.sh ssh-root-autologin/ ./cron: rsync-backup ./openvpn: ag-ca.crt client.conf client.crt client.csr client.key home.up ./ssh-root-autologin: id_rsa id_rsa.pub known_hosts
Content of /mnt/erp5_cd/config/cron/rsync-backup:
59 2 * * * root /mnt/erp5_cd/config/rsync.sh > /mnt/erp5_cd/config/rsync.log
Content of /mnt/erp5_cd/config/rsync.sh:
# Pack the Data.fs to reduce its size # WARNING: It's a bad idea because you loose ZODB "undo" data (so you # also loose the traceability of objects modifications) # wget --spider --user=zope --password=zope -q http://127.0.0.1:80/Control_Panel/Database/main/manage_pack?days:float=14 > /dev/null # Don't forget to create a pair of cryptographic keys (public, private): # use the command "ssh-keygen -t rsa" and then register you on the # remote server using : # ssh-copy-id -i ~/.ssh/id_rsa.pub firstname.lastname@example.org" # If you want to run this script with a cron entry, the only solution # found is to create a key without a passphrase; you can limit the commands # this user can execute with that key as explained in http://www.jdmz.net/ssh/ rsync -axHzv --delete --delete-excluded --delete-after --partial -e ssh\ /mnt/erp5_cd email@example.com:/home/kevin/backup/mnt
Q: Why OpenVpn don't want to start ?
There is a know bug in the v1.0rc8 of the live cd: the file /dev/net/tun is missing and prevent openvpn to start. You can create the file with the following command:
mknod /dev/net/tun c 10 200
It also a good idea to put this line in your config.sh script (see above for more details).
Q: How to keep system users across reboots
- $HOME must be created in a persistent folder, I use /mnt/erp5_cd/homes/$USER
- Store /etc/passwd /etc/shadow in config.tgz (store /etc/sudoers as well if you use sudo)
- Don't forget to update config.tgz when you add new users