... (success) ...
inflating: /usr/local/share/ovirt-engine/engine.ear/webadmin.war/META-INF/maven/org.ovirt.engine.ui/webadmin/pom.xml
inflating: /usr/local/share/ovirt-engine/engine.ear/webadmin.war/404.html
checkdir error: /usr/local/share/ovirt-engine/engine.ear/engine-bll.jar exists but is not directory
unable to process engine-bll.jar/org/ovirt/engine/core/bll/VdsDeploy$32.class.
checkdir error: /usr/local/share/ovirt-engine/engine.ear/engine-bll.jar exists but is not directory
unable to process engine-bll.jar/org/ovirt/engine/core/bll/InitBackendServicesOnStartupBean.class.
...
make: *** [install_artifacts] Error 2
any insights?
Thanks...
On Thu, Jan 24, 2013 at 8:52 PM, Juan Hernandez
<jhernand@redhat.com> wrote:
Those instructions are out of date, use "make install". That installs the files, but you will still need some changes to make the engine work:
1. Create the ovirt user (the engine runs by default with this service, unless you change the /etc/syscofig/ovirt-engine file and add the ENGINE_USER and ENGINE_GROUP parameters):
useradd ovirt
2. Create (mkdir -p ...) and change the ownership of the directories that the engine needs to own to ovirt:ovirt (chown ovirt:ovirt ...):
/etc/ovirt-engine
/var/log/ovirt-engine
/var/lock/ovirt-engine
/var/lib/ovirt-engine/content
/var/lib/ovirt-engine/deployments
/var/tmp/ovirt-engine
/var/cache/ovirt-engine
3. Enable the HTTP connector in the engine (the default is to enable only AJP, and that doesn't work without Apache as frontend) adding the following to the /etc/sysconfig/ovirt-engine file:
ENGINE_PROXY_ENABLED=false
ENGINE_HTTP_ENABLED=true
ENGINE_HTTP_PORT=8700
ENGINE_HTTPS_ENABLED=false
ENGINE_AJP_ENABLED=false
4. Configure database connection details (the default in development environments is to use the postgres user and the trust mode) adding this to /etc/sysconfig/ovirt-engine:
ENGINE_DB_USER=postgres
ENGINE_DB_PASSWORD=
5. Make sure that you have the PostgreSQL JDBC driver installed (rpm -q postgresql-jdbc) and install it if needed (yum install postgresql-jdbc).
6. Now you can start the engine running the engine-service script:
engine-service start
Look at the system log (the file /var/log/messages) and the engine logs (the files /var/log/ovirt-engine/server.log and /var/log/ovirt-engine) for errors.
7. Connect to http://localhost:8700 and you should be able to login with user admin and letmein! as password.
Note that I am assuming that you already created the database, and that you want to use this installation for development. If you are looking for an production installation I suggest using the RPMs.
Also I tested this with the latest source from the repository, it will not work with older versions.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.