Hi Roy,

I've added /var/log/ovirt-engine/engine.log to my DropBox: 
https://www.dropbox.com/sh/21lkl6ao3hv2r85/AADDMCK4Dp7UYgs5P6dMQxHKa/vdsm?dl=0 
<https://www.dropbox.com/sh/21lkl6ao3hv2r85/AADDMCK4Dp7UYgs5P6dMQxHKa/vdsm?dl=0>

When I look in the engine.log, I see the error "unable to load number from 
serial.txt"
I did a find for serial.txt and the only file that comes up is: 
/etc/pki/ovirt-engine/serial.txt 
(Makes sense that this is the file it wants to read)
When I open /etc/pki/ovirt-engine/serial.txt, it is an empty file. 
        [root@cultivar ovirt-engine]# cat /etc/pki/ovirt-engine/serial.txt
        [root@cultivar ovirt-engine]# 

What should be in serial.txt?

I don't understand where to find the other log that you mention in your email 
below. I don't see any paths listed in the UI when I click on the failed event 
for certificate enrollment.

Cheers,
Gervais



> On May 15, 2016, at 5:10 PM, Roy Golan <rgo...@redhat.com 
> <mailto:rgo...@redhat.com>> wrote:
> 
> 
> 
> On Sun, May 15, 2016 at 1:32 AM, Gervais de Montbrun <gerv...@demontbrun.com 
> <mailto:gerv...@demontbrun.com>> wrote:
> Hey Folks,
> 
> I'm still stuck here... I believe the issue may be because the Enrolling 
> certificates stage is failing...
> 
> Any idea's how to sort this out?
> 
> I see:
>       Installing Host Cultivar2. Enrolling certificate
>       Failed to install Host Cultivar2. Certificate enrollment failed.
>       Host Cultivar2 installation failed. Certificate enrollement failed.
> 
> Any attempt to re-install fails at this step.
> 
> Cheers,
> Gervais
> 
> 
> 
> I also see in the logs that the manager (ovirt-engine) rejected the host 
> addition to the setup. Please add the /var/log/ovirt-engine/engine.log from 
> the engine machine. Also, the engine machine has the install log - open one 
> of the Event logs in the UI that says you host installation failed and you 
> will see it retrieved the install log to a path under your engine. Please 
> include this as well.
>  
> 
>> On May 13, 2016, at 1:36 PM, Gervais de Montbrun <gerv...@demontbrun.com 
>> <mailto:gerv...@demontbrun.com>> wrote:
>> 
>> Hi Nir,
>> 
>> Thank you for you input.
>> 
>> It was suggest that I try starting vdsm from the shell so I could see the 
>> output in an effort to solve my issue: 
>> http://lists.ovirt.org/pipermail/users/2016-May/039690.html 
>> <http://lists.ovirt.org/pipermail/users/2016-May/039690.html>
>> 
>> Cheers,
>> Gervais
>> 
>> 
>> 
>>> On May 13, 2016, at 12:12 PM, Nir Soffer <nsof...@redhat.com 
>>> <mailto:nsof...@redhat.com>> wrote:
>>> 
>>> On Fri, May 13, 2016 at 3:37 PM, Gervais de Montbrun
>>> <gerv...@demontbrun.com <mailto:gerv...@demontbrun.com>> wrote:
>>>> Hi Charles,
>>>> 
>>>> I think the problem I am having is due to the setup failing and not
>>>> something in vdsm configs as I have never gotten this server to start up
>>>> properly and the BRIDGE ethernet interface + ovirt routes are not setup.
>>>> 
>>>> I put the logs here:
>>>> https://www.dropbox.com/sh/5ugyykqh1lgru9l/AACXxRYWr3tgd0WbBVFW5twHa?dl=0 
>>>> <https://www.dropbox.com/sh/5ugyykqh1lgru9l/AACXxRYWr3tgd0WbBVFW5twHa?dl=0>
>>>> 
>>>> hosted-engine--deploy-logs.zip # Logs from when I tried to deploy and it
>>>> failed
>>>> vdsm.tar.gz # /var/log/vdsm
>>>> 
>>>> Output from running vdsm from the command line:
>>>> 
>>>> [root@cultivar2 log]# su -s /bin/bash vdsm
>>> 
>>> This cannot work unless supervdsmd is running...
>>> 
>>>> [vdsm@cultivar2 log]$ python /usr/share/vdsm/vdsm
>>>> (PID: 6521) I am the actual vdsm 4.17.26-1.el7
>>>> cultivar2.grove.silverorange.com 
>>>> <http://cultivar2.grove.silverorange.com/> (3.10.0-327.el7.x86_64)
>>>> VDSM will run with cpu affinity: frozenset([1])
>>>> /usr/bin/taskset --all-tasks --pid --cpu-list 1 6521 (cwd None)
>>>> SUCCESS: <err> = ''; <rc> = 0
>>>> Starting scheduler vdsm.Scheduler
>>>> started
>>>> Run and protect:
>>>> registerDomainStateChangeCallback(callbackFunc=<functools.partial object at
>>>> 0x381b158>)
>>>> Run and protect: registerDomainStateChangeCallback, Return response: None
>>>> Trying to connect to Super Vdsm
>>>> Preparing MOM interface
>>>> Using named unix socket /var/run/vdsm/mom-vdsm.sock
>>>> Unregistering all secrests
>>>> trying to connect libvirt
>>>> recovery: started
>>>> Setting channels' timeout to 30 seconds.
>>>> Starting VM channels listener thread.
>>>> Listening at 0.0.0.0:54321 <http://0.0.0.0:54321/>
>>>> Adding detector <rpc.bindingxmlrpc.XmlDetector instance at 0x3b4ecb0>
>>>> recovery: completed in 0s
>>>> Adding detector <yajsonrpc.stompreactor.StompDetector instance at 
>>>> 0x382e5a8>
>>>> Starting executor
>>>> Starting worker jsonrpc.Executor/0
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/1
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/2
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/3
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/4
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/5
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/6
>>>> Worker started
>>>> Starting worker jsonrpc.Executor/7
>>>> Worker started
>>>> XMLRPC server running
>>>> Starting executor
>>>> Starting worker periodic/0
>>>> Worker started
>>>> Starting worker periodic/1
>>>> Worker started
>>>> Starting worker periodic/2
>>>> Worker started
>>>> Starting worker periodic/3
>>>> Worker started
>>>> trying to connect libvirt
>>>> Panic: Connect to supervdsm service failed: [Errno 2] No such file or
>>>> directory
>>>> Traceback (most recent call last):
>>>> File "/usr/share/vdsm/supervdsm.py", line 78, in _connect
>>>>  utils.retry(self._manager.connect, Exception, timeout=60, tries=3)
>>>> File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 959, in retry
>>>>  return func()
>>>> File "/usr/lib64/python2.7/multiprocessing/managers.py", line 500, in
>>>> connect
>>>>  conn = Client(self._address, authkey=self._authkey)
>>>> File "/usr/lib64/python2.7/multiprocessing/connection.py", line 173, in
>>>> Client
>>>>  c = SocketClient(address)
>>>> File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, in
>>>> SocketClient
>>>>  s.connect(address)
>>>> File "/usr/lib64/python2.7/socket.py", line 224, in meth
>>>>  return getattr(self._sock,name)(*args)
>>>> error: [Errno 2] No such file or directory
>>> 
>>> Vdsm tries to connect to supervdsmd on startup, and if it is not running
>>> it will fail.
>>> 
>>> You can do:
>>> 
>>> systemctl start supervdsmd
>>> 
>>> And they you can run vdsmd from the shell.
>>> 
>>> But why do you need to run vdsm from the shell?
>>> 
>>> Nir
>> 
> 
> 
> _______________________________________________
> Users mailing list
> Users@ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users 
> <http://lists.ovirt.org/mailman/listinfo/users>
> 
> 

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to