-
Notifications
You must be signed in to change notification settings - Fork 127
This section groups all common problems you may have installing or using Archipel.
First of all, and before continuing, update your copy or Archipel doing from the root source directory # git pull Then bootstrap and try again. If it still doesn't work, you can continue to read
You can use :
- Chromium (All platform) : best choice
- WebKit (Mac OS) : the other best choice
- Chrome (All platform)
- Safari (Mac OS)
- Firefox (All platform)
- ReKong
Are you kidding ?
I have a "No connection has been defined for this thread or process" error when connecting to the GUI displayed on server
You MUST use the easy_install package of SQLObject, not the one eventually packaged in your distribution
Install the xmpppy package with easy_install, at least the package in Ubuntu is too old
Use the Java's SUN JDK, not OpenJDK. This is a problem with the Cappuccino build tools. Note that it will only be necessary to build Archipel Client, not to use it.
When I want to launch Archipel GUI and I look at the Debug Console, I have a lot of error telling "Info.plist" not found
This is not a problem. This is the way Cappuccino determines if a folder is a bundle or a framework or just a standard folder. It tries to get Info.plist from folders and this can result as a 404 error displayed in the console.
Your XMPP admin account SHOULD to be called "admin" (for example [email protected]). Otherwise, it needs some more advanced configuration in ArchipelClient's Info.plist, which need to re-build it.
you get something like ERROR ::2011-01-14 16:09:09::<archipelHypervisor.TNArchipelHypervisor instance at 0x14ab5f0>.iq_get_permission: exception raised is : No connection has been defined for this thread or process
. This mean you use a too old version of python SQLObject. remove any installation of this egg, and reinstall it with
# easy_install sqlobject
I have sucessfully installed archipel, I'm connected, and I have added the hypervisor in the roster, but it is displayed as "Offline"
You probably have manually created the hypervisor account using ejabberdctl
which is bad. You have now two solutions:
- change the account of the hypervisor of the token
hypervisor_xmpp_jid
in thearchipel.conf
file and restart Archipel. - unregister the account using
ejabberdctl unregister hypervisor FQDN
and restart Archipel.
YOU MUST NOT CREATE ANY XMPP ACCOUNT FOR ARCHIPEL ENTITIES. Manually account can be created for users
export PYTHONDONTWRITEBYTECODE as empty value first and rerun easy_install # export PYTHONDONTWRITEBYTECODE= # easy_install archipel-agent