[Engine-devel] fail to setup engine

[Liu, DanqingX]

This attachment is the log

-----Original Message-----
From: Sandro Bonazzola [mailto:sbonazzo at redhat.com] 
Sent: Wednesday, July 03, 2013 5:08 PM
To: Chen, Wei D
Cc: engine-devel; Zhang, Lijuan; Liu, DanqingX
Subject: Re: [Engine-devel] fail to setup engine

If the setup log is not created (it's usually in tmp directory) can you attach the output of

OTOPI_DEBUG=1 $HOME/ovirt-engine/bin/engine-setup-2 ?


Il 03/07/2013 10:59, Chen, Wei D ha scritto:
> where is the log file? engine.log and server.log have not created yet.
>
>  
>
>  
>
> Best Regards,
>
> Dave Chen
>
>  
>
> From: Sandro Bonazzola [mailto:sbonazzo at redhat.com]
> Sent: Wednesday, July 03, 2013 4:58 PM
> To: Chen, Wei D
> Cc: engine-devel; Zhang, Lijuan; Liu, DanqingX
> Subject: Re: [Engine-devel] fail to setup engine
>
>  
>
> Il 03/07/2013 10:54, Chen, Wei D ha scritto:
>
> Hi,
>  
> We cannot setup engine based on today's source code, any ideas?
>  
>  
> $HOME/ovirt-engine/bin/engine-setup-2
> [ ERROR ] Failed to execute stage 'Booting': 5 [ INFO  ] Stage: 
> Initializing
>           Setup was run under unprivileged user this will produce development installation do you wish to proceed? (Yes, No) [No]:
> Yes
> [WARNING] engine-setup-2 is a technical preview, and yet to include all functionality that exists in legacy engine-setup.
> Specifically, engine-setup-2 does not support upgrade from previous installations.
>  
> Best Regards,
> Dave Chen
>  
>  
>
>
>
>
>
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
>
> Can you attach the log file?
>
>
>
>


--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: engine-setup.log
Type: application/octet-stream
Size: 15069 bytes
Desc: engine-setup.log
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20130703/5376b2ae/attachment.obj>