[ovirt-devel] Engine-setup failing on a FE24, 1GB Digitalocean box

[Martin Perina]

On Fri, Mar 10, 2017 at 11:59 AM, Tasdik Rahman <prodicus at outlook.com>
wrote:

> +++
> $ export OVIRT_SERVICE_DEBUG=1
> $ sudo systemctl import-environment OVIRT_SERVICE_DEBUG
> [sudo] password for tasdik:
> $ systemctl start ovirt-engine
> ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
> Authentication is required to start 'ovirt-engine.service'.
> Authenticating as: tasdik
> Password:
> ==== AUTHENTICATION COMPLETE ===
> Job for ovirt-engine.service failed because the control process exited
> with error code. See "systemctl status ovirt-engine.service" and
> "journalctl -xe" for details.
> $ systemctl status ovirt-engine.service
> ● ovirt-engine.service - oVirt Engine
>    Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service;
> disabled; vendor preset: disabled)
>    Active: failed (Result: exit-code) since Fri 2017-03-10 10:57:14 UTC;
> 9s ago
>   Process: 22318 ExecStart=/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py
> --redirect-output --systemd=notify $EXTRA_ARGS start (code=exited,
> status=1/FAILURE)
>  Main PID: 22318 (code=exited, status=1/FAILURE)
> $ journalctl -xe
> No journal files were found.
>

​How is this possible? Could you please look at journal under root user and
search from the end backwards for ovirt-engine service logs?

  sudo su -
  journal
​


> -- No entries --
> $
> +++
>
> Thanks,
> Tasdik
>
> On 10-Mar-2017, at 4:22 PM, Martin Perina <mperina at redhat.com> wrote:
>
> Hmm, strange. So the only other way is to enable debug logging for
> ovirt-engine service:
>
>   export OVIRT_SERVICE_DEBUG=1
>   systemctl import-environment OVIRT_SERVICE_DEBUG
>   systemctl start ovirt-engine
>
>
> After that please take a look at journal, there should be detailed records
> about ovirt-engine service startup.
>
> Thanks
>
> Martin Perina
>
>
> On Fri, Mar 10, 2017 at 11:29 AM, Tasdik Rahman <prodicus at outlook.com>
> wrote:
>
>> +++
>> $ systemctl status ovirt-engine.service
>> ● ovirt-engine.service - oVirt Engine
>>    Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service;
>> disabled; vendor preset: disabled)
>>    Active: failed (Result: exit-code) since Fri 2017-03-10 09:58:19 UTC;
>> 29min ago
>>   Process: 19055 ExecStart=/usr/share/ovirt-eng
>> ine/services/ovirt-engine/ovirt-engine.py --redirect-output
>> --systemd=notify $EXTRA_ARGS start (code=exited, status=1/FAILURE)
>>  Main PID: 19055 (code=exited, status=1/FAILURE)
>> $ journalctl -xe
>> No journal files were found.
>> -- No entries --
>> $
>> +++
>>
>>
>> On 10-Mar-2017, at 3:53 PM, Martin Perina <mperina at redhat.com> wrote:
>>
>> No, only logs under /var/log/ovirt-engine are related to oVirt. As no
>> boot/server/engine logs exists under this directory it seems, that even
>> java process was not created properly. So could you please share error
>> about ovirt-engine service startup? You should be able to find out some
>> error in journal:
>>
>>   systemctl status ovirt-engine.service
>>   journalctl -xe
>>
>> Thanks
>>
>> Martin Perina
>>
>>
>> On Fri, Mar 10, 2017 at 11:14 AM, Tasdik Rahman <prodicus at outlook.com>
>> wrote:
>>
>>> Hey Martin
>>>
>>> +++
>>> $ pwd
>>> /var/log/ovirt-engine
>>> $ tree
>>> .
>>> ├── dump
>>> ├── host-deploy
>>> ├── notifier
>>> ├── ovirt-iso-uploader
>>> └── setup
>>>     ├── ovirt-engine-setup-20170310092548-r5c2c7.log
>>>     └── ovirt-engine-setup-20170310095712-x0n0rd.log
>>>
>>> 5 directories, 2 files
>>> $ sudo find / -iname "server.log"
>>> $ sudo find / -iname "engine.log"
>>> $ sudo find / -iname "boot.log"
>>> /var/log/boot.log
>>> find: ‘/proc/19337’: No such file or directory
>>> $
>>> +++
>>>
>>> Should I share the file `/var/log/boot.log` on the mailing list?
>>>
>>> Thanks,
>>> Tasdik
>>>
>>>
>>> On 10-Mar-2017, at 3:31 PM, Martin Perina <mperina at redhat.com> wrote:
>>>
>>>  /var/log/ovirt-engine
>>>
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170310/d7f47a98/attachment.html>