3:12 p.m.
Hello,
I'm not sure if this is proper list but maybe someone will help.
I'm trying to start ovirt-engine and node on same server but it appears
that vdsm has strange problem. Below are steps i took and vdsm error:
1. install fedora 15 (my service provider don't have 16)
2. upgrade to fedora 16 (dirty yum way)
3. install ovirt-engine (with yum)
4. install vdsm and vdsm-cli (with yum)
now vdsm seems to not start completely and i can see this error in vdsm.log:
MainThread::ERROR::2012-03-01 12:40:20,731::vdsm::74::vds::(run)
Traceback (most recent call last):
File "/usr/share/vdsm/vdsm", line 72, in run
serve_clients(log)
File "/usr/share/vdsm/vdsm", line 40, in serve_clients
cif = clientIF.clientIF(log)
File "/usr/share/vdsm/clientIF.py", line 115, in __init__
self._createLibvirtNetworks()
File "/usr/share/vdsm/clientIF.py", line 152, in _createLibvirtNetworks
nf = netinfo.NetInfo()
File "/usr/share/vdsm/netinfo.py", line 268, in __init__
_netinfo = get()
File "/usr/share/vdsm/netinfo.py", line 207, in get
routes = getRoutes()
File "/usr/share/vdsm/netinfo.py", line 165, in getRoutes
with open("/proc/net/route") as route_file:
IOError: [Errno 2] No such file or directory: '/proc/net/route'
MainThread::INFO::2012-03-01 12:40:20,731::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<_MainThread(MainThread, started 139809442313984)>
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<Thread(libvirtEventLoop, started daemon 139809298802432)>
MainThread::INFO::2012-03-01 12:40:20,789::vdsm::71::vds::(run) I am the
actual vdsm 4.9-0
Also, I'm able to cat this /proc/net/route file as root
--
Michal
5:42 p.m.
On 03/01/2012 03:12 PM, Michal Kopacki wrote:
Hello,
I'm not sure if this is proper list but maybe someone will help.
I'm trying to start ovirt-engine and node on same server but it appears
that vdsm has strange problem. Below are steps i took and vdsm error:
1. install fedora 15 (my service provider don't have 16)
2. upgrade to fedora 16 (dirty yum way)
3. install ovirt-engine (with yum)
4. install vdsm and vdsm-cli (with yum)
not sure about the error below, but installing vdsm requires more
configuration done by engine when you choose to add a host.
can you try adding the host via the engine (it will reboot in the last
phase...).
now vdsm seems to not start completely and i can see this error in
vdsm.log:
MainThread::ERROR::2012-03-01 12:40:20,731::vdsm::74::vds::(run)
Traceback (most recent call last):
File "/usr/share/vdsm/vdsm", line 72, in run
serve_clients(log)
File "/usr/share/vdsm/vdsm", line 40, in serve_clients
cif = clientIF.clientIF(log)
File "/usr/share/vdsm/clientIF.py", line 115, in __init__
self._createLibvirtNetworks()
File "/usr/share/vdsm/clientIF.py", line 152, in _createLibvirtNetworks
nf = netinfo.NetInfo()
File "/usr/share/vdsm/netinfo.py", line 268, in __init__
_netinfo = get()
File "/usr/share/vdsm/netinfo.py", line 207, in get
routes = getRoutes()
File "/usr/share/vdsm/netinfo.py", line 165, in getRoutes
with open("/proc/net/route") as route_file:
IOError: [Errno 2] No such file or directory: '/proc/net/route'
MainThread::INFO::2012-03-01 12:40:20,731::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<_MainThread(MainThread, started 139809442313984)>
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<Thread(libvirtEventLoop, started daemon 139809298802432)>
MainThread::INFO::2012-03-01 12:40:20,789::vdsm::71::vds::(run) I am the
actual vdsm 4.9-0
Also, I'm able to cat this /proc/net/route file as root
8:41 p.m.
--------------------------------------------------------------
On 2012-03-01 17:42:42 , Itamar Heim (iheim(a)redhat.com) wrote:
not sure about the error below, but installing vdsm requires more
configuration done by engine when you choose to add a host.
I'm not sure
what you mean by "more configuration". As I
understand after install of vdsm it will be started as a service which
apparently is not going well.
can you try adding the host via the engine (it will reboot in the
last
phase...).
It's exactly what I did. After vsdm install I went to
ovirt-engine
page and add host (localhost in this case). In event window i saw that
there are components installing and after reboot i can see information
as below:
"This host is in non responding state. Try to Activate it; If the
problem persists, switch Host to Maintenance mode and try to reinstall it."
Of course Activate solves nothing.
--
Michal
8:50 p.m.
I wonder about that dirty yum upgrade bit -- I upgraded a remote F15
server to F16 yesterday using preupgrade-cli and then went on to
configure that server as engine+host as you're doing. It worked fine.
On 03/01/2012 10:41 AM, Michal Kopacki wrote:
--------------------------------------------------------------
On 2012-03-01 17:42:42 , Itamar Heim (iheim(a)redhat.com) wrote:
>
> not sure about the error below, but installing vdsm requires more
> configuration done by engine when you choose to add a host.
I'm not sure what you mean by "more configuration". As I understand
after install of vdsm it will be started as a service which apparently
is not going well.
> can you try adding the host via the engine (it will reboot in the last
> phase...).
It's exactly what I did. After vsdm install I went to ovirt-engine
page and add host (localhost in this case). In event window i saw that
there are components installing and after reboot i can see information
as below:
"This host is in non responding state. Try to Activate it; If the
problem persists, switch Host to Maintenance mode and try to reinstall it."
Of course Activate solves nothing.
8:32 a.m.
On Thu, 1 Mar 2012 10:50:48 -0800
Jason Brooks <jbrooks(a)redhat.com> wrote:
I wonder about that dirty yum upgrade bit -- I upgraded a remote F15
server to F16 yesterday using preupgrade-cli and then went on to
configure that server as engine+host as you're doing. It worked fine.
I'm afraid it could be the case. There is raid on /boot and /
(root) partitions and preupgrade-cli didn't work, so I was forced to
go dirty way. Everything seems to be fine besides vdsm though.
I'm clueless now. I think I will try to reinstall F15, break raid
and then try preupgrade.
btw. how about software raid and ovirt ? did anyone submit issues on
that ?
--
Michal
2:06 a.m.
On 03/01/2012 08:41 PM, Michal Kopacki wrote:
--------------------------------------------------------------
On 2012-03-01 17:42:42 , Itamar Heim (iheim(a)redhat.com) wrote:
>
> not sure about the error below, but installing vdsm requires more
> configuration done by engine when you choose to add a host.
I'm not sure what you mean by "more configuration". As I understand
after install of vdsm it will be started as a service which apparently
is not going well.
> can you try adding the host via the engine (it will reboot in the last
> phase...).
It's exactly what I did. After vsdm install I went to ovirt-engine page
and add host (localhost in this case). In event window i saw that there
are components installing and after reboot i can see information as below:
"This host is in non responding state. Try to Activate it; If the
problem persists, switch Host to Maintenance mode and try to reinstall it."
Of course Activate solves nothing.
how did you add the host (did you use fqdn?)
8:33 a.m.
On Fri, 2 Mar 2012 02:06:15 +0200
Itamar Heim <iheim(a)redhat.com> wrote:
On 03/01/2012 08:41 PM, Michal Kopacki wrote:
> --------------------------------------------------------------
> On 2012-03-01 17:42:42 , Itamar Heim (iheim(a)redhat.com) wrote:
>>
>> not sure about the error below, but installing vdsm requires more
>> configuration done by engine when you choose to add a host.
> I'm not sure what you mean by "more configuration". As I understand
> after install of vdsm it will be started as a service which
> apparently is not going well.
>> can you try adding the host via the engine (it will reboot in the
>> last phase...).
> It's exactly what I did. After vsdm install I went to ovirt-engine
> page and add host (localhost in this case). In event window i saw
> that there are components installing and after reboot i can see
> information as below:
>
> "This host is in non responding state. Try to Activate it; If the
> problem persists, switch Host to Maintenance mode and try to
> reinstall it."
>
> Of course Activate solves nothing.
>
how did you add the host (did you use fqdn?)
I did this using ip address and I'm sure it's not the issue here - I
have done this exactly same on different engine host and it is fine.
--
Michal
3:09 p.m.
I found it.
My provider (ovh) provides own kernel with grsecurity
patch. During upgrade F15->F16 it wasn't changed. In grub config
files, kernel from ovh has lower number (09) than regular distro
kernels (10). Due to that fact I was constantly starting with
grsecurity kernel from F15. Without proper configuration for gr
regular users (like vdsm) were limited.
After switch to default distro kernel, everything is ok.
--
Michal
On Thu, 1 Mar 2012 14:12:06 +0100
Michal Kopacki <mkopacki(a)gmail.com> wrote:
Hello,
I'm not sure if this is proper list but maybe someone will help.
I'm trying to start ovirt-engine and node on same server but it
appears that vdsm has strange problem. Below are steps i took and
vdsm error:
1. install fedora 15 (my service provider don't have 16)
2. upgrade to fedora 16 (dirty yum way)
3. install ovirt-engine (with yum)
4. install vdsm and vdsm-cli (with yum)
now vdsm seems to not start completely and i can see this error in
vdsm.log:
MainThread::ERROR::2012-03-01 12:40:20,731::vdsm::74::vds::(run)
Traceback (most recent call last):
File "/usr/share/vdsm/vdsm", line 72, in run
serve_clients(log)
File "/usr/share/vdsm/vdsm", line 40, in serve_clients
cif = clientIF.clientIF(log)
File "/usr/share/vdsm/clientIF.py", line 115, in __init__
self._createLibvirtNetworks()
File "/usr/share/vdsm/clientIF.py", line 152, in
_createLibvirtNetworks nf = netinfo.NetInfo()
File "/usr/share/vdsm/netinfo.py", line 268, in __init__
_netinfo = get()
File "/usr/share/vdsm/netinfo.py", line 207, in get
routes = getRoutes()
File "/usr/share/vdsm/netinfo.py", line 165, in getRoutes
with open("/proc/net/route") as route_file:
IOError: [Errno 2] No such file or directory: '/proc/net/route'
MainThread::INFO::2012-03-01 12:40:20,731::vdsm::76::vds::(run) VDSM
main thread ended. Waiting for 1 other threads...
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<_MainThread(MainThread, started 139809442313984)>
MainThread::INFO::2012-03-01 12:40:20,732::vdsm::79::vds::(run)
<Thread(libvirtEventLoop, started daemon 139809298802432)>
MainThread::INFO::2012-03-01 12:40:20,789::vdsm::71::vds::(run) I am
the actual vdsm 4.9-0
Also, I'm able to cat this /proc/net/route file as root
4660
days inactive
4661
days old
7 comments
3 participants
participants (3)
-
Itamar Heim -
Jason Brooks -
Michal Kopacki