[ovirt-users] info about ovirtmgmt bridge config in master
Gianluca Cecchi
gianluca.cecchi at gmail.com
Fri Aug 15 11:01:50 UTC 2014
On Fri, Aug 15, 2014 at 12:30 PM, Dan Kenigsberg <danken at redhat.com> wrote:
>
>
> ifcfg-ovirtmgmt network should be found on disk after a successful
> installation of a host. However, if network configuration phase fails,
> ifcfg files should be reverted to their original values.
>
ok.
>
> Could you see your super/vdsm.log if that is the case?
> Could you explain when did "hypervisor part goes in timeout". Can you
> correlate this to something in vdsm.log?
>
> Dan.
>
So, initial config was no dns and I forgot the /etc/hosts part too.
So engine-setup complained about hostname input and asked again.
At this point I filled up /etc/hosts and confirmed hostname in engine-setup
prompt.
It complained about dns part but continued.
As this is an all-in-one setup it arrived at the hypervisor config part.
It gave in engine-setup output the message about time out in having
hypervisor host up a few times and at the end
[ INFO ] Still waiting for VDSM host to become operational...
[ ERROR ] Timed out while waiting for host to start. Please check the logs.
During these recurring time-out warnings I see in vdsm.log
Detector thread::ERROR::2014-08-13
17:48:59,482::protocoldetector::104::vds.MultiProtocolAcceptor::(serve_forever)
Unhandled exception
Traceback (most recent call last):
File "/usr/share/vdsm/protocoldetector.py", line 100, in serve_forever
self._process_events()
File "/usr/share/vdsm/protocoldetector.py", line 117, in _process_events
self._accept_connection()
File "/usr/share/vdsm/protocoldetector.py", line 180, in
_accept_connection
client_socket, _ = self._socket.accept()
File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line 121, in
accept
raise SSL.SSLError("%s, client %s" % (e, address[0]))
SSLError: unexpected eof, client 192.168.122.51
engine-setup went ahead with these messages:
[WARNING] Local storage domain not added because the VDSM host was not up.
Please add it manually.
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140813173448-i47i1l.log
[ INFO ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20140813174959-setup.conf'
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ INFO ] Execution of setup completed successfully
inside supervdsm.log no error message. See it here:
https://drive.google.com/file/d/0BwoPbcrMv8mvRVpxR3UzYU9hUmM/edit?usp=sharing
in connectivity.log I see only:
2014-08-13 17:39:41,206:DEBUG:recent_client:True, lo:(operstate:up speed:0
duplex:unknown), ;vdsmdum
my;:(operstate:down speed:0 duplex:unknown), bond0:(operstate:down speed:0
duplex:unknown), eth0:(operstate:up speed:0 duplex:unknown)
2014-08-13 17:40:11,360:DEBUG:recent_client:False
At this moment it seems I can't do anything on the host, nor reinstall or
activate or anything...
BTW: the VM fo all-in-one has 6Gb of ram configured... could it be the
cause in any way?
Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140815/568191ad/attachment-0001.html>
More information about the Users
mailing list