3:23 p.m.
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
Hi all,
I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open the =
oVirt Manager and added a new system to it.=20
The manager says installing and after that is fails to connect. Looking =
on the system I see:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_coredump
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_vdsm_logs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
wait_for_network
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running run_init_hooks
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
upgraded_version_check
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
check_is_configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not =
configured to work with VDSM.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the module use =
the following:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure =
[--module module-name]'.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are not =
configured try to use:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure =
--force'
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop =
the module's service and start it
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: afterwards automatically to =
load the new configuration.)
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: libvirt is already =
configured for vdsm
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not =
configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute =
check_is_configured task (task returned with error code 1).
So I run vdsm-tool configure after I stop sanlock.=20
# vdsm-tool configure
Checking configuration status...
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts
Running configure...
Reconfiguration of sanlock is done.
Done configuring modules to VDSM.
But when I want to start vdsmd it still gives the error that sanlock is =
not configured.
Does somebody has a solution for this?=20
I am a bit lost on this=85 Google only tells me that there was a bug in =
3.4.=20
Thanks in advance,
Jurri=EBn=
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word;
=
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi =
all,<div><br></div><div>I have CentOS 7 running and I added the
oVirt =
3.5 repo to it. I open the oVirt Manager and added a new system to =
it. </div><div>The manager says installing and after that is fails =
to connect. Looking on the system I
see:</div><div><br></div><div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_coredump</div><div style=3D"margin: 0px; font-family: 'Courier
=
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
configure_vdsm_logs</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
wait_for_network</div><div style=3D"margin: 0px; font-family: 'Courier
=
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
run_init_hooks</div><div style=3D"margin: 0px; font-family: 'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
upgraded_version_check</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running =
check_is_configured</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]:
Error:</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not =
configured to work with VDSM.</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To =
configure the module use the following:</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: =
'vdsm-tool configure [--module module-name]'.</div><div
style=3D"margin: =
0px; font-family: 'Courier New'; color: rgb(245, 245, 245); =
background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: If all modules are not =
configured try to use:</div><div style=3D"margin: 0px; font-family: =
'Courier New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, =
0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool =
configure --force'</div><div style=3D"margin: 0px; font-family:
'Courier =
New'; color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop the =
module's service and start it</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Mar 30 21:09:37 vdsmd_init_common.sh[7106]: =
afterwards automatically to load the new configuration.)</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: libvirt is already configured =
for vdsm</div><div style=3D"margin: 0px; font-family: 'Courier New';
=
color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not =
configured</div><div style=3D"margin: 0px; font-family: 'Courier
New'; =
color: rgb(245, 245, 245); background-color: rgb(0, 0, 0);">Mar 30 =
21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute =
check_is_configured task (task returned with error code =
1).</div></div><div><br></div><div>So I run vdsm-tool
configure after I =
stop sanlock. </div><div><br></div><div><div
style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);"># vdsm-tool configure</div><div style=3D"margin: 0px;
=
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0); min-height: 14px;"><br></div><div
style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Checking configuration status...</div><div
style=3D"margin:=
0px; font-family: 'Courier New'; color: rgb(245, 245, 245); =
background-color: rgb(0, 0, 0); min-height: 14px;"><br></div><div
=
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">libvirt is already configured for =
vdsm</div><div style=3D"margin: 0px; font-family: 'Courier New';
color: =
rgb(245, 245, 245); background-color: rgb(0, 0, 0);">SUCCESS: ssl =
configured to true. No conflicts</div><div style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0); min-height: 14px;"><br></div><div
style=3D"margin: 0px; =
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Running configure...</div><div style=3D"margin: 0px;
=
font-family: 'Courier New'; color: rgb(245, 245, 245); background-color: =
rgb(0, 0, 0);">Reconfiguration of sanlock is done.</div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0); min-height:
14px;"><br></div><div =
style=3D"margin: 0px; font-family: 'Courier New'; color: rgb(245, 245, =
245); background-color: rgb(0, 0, 0);">Done configuring modules to =
VDSM.</div></div><div><br></div><div>But when I want
to start vdsmd it =
still gives the error that sanlock is not =
configured.</div><div><br></div><div>Does somebody has a
solution for =
this? </div><div><br></div><div>I am a bit lost on
this=85 Google =
only tells me that there was a bug in =
3.4. </div><div><br></div><div>Thanks in =
advance,</div><div><br></div><div>Jurri=EBn</div></body></html>=
--Apple-Mail=_B0F5D3E0-FE6C-44CC-9D86-DD009DD544F1--
11:41 a.m.
----- Original Message -----
Hi all,
I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open the
oVirt Manager and added a new system to it.
The manager says installing and after that is fails to connect. Looking on
the system I see:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configure_coredump
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configure_vdsm_logs
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running wait_for_network
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running run_init_hooks
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running
upgraded_version_check
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running check_is_configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: One of the modules is not
configured to work with VDSM.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the module use the
following:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure [--module
module-name]'.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are not configured
try to use:
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure --force'
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: (The force flag will stop the
module's service and start it
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: afterwards automatically to load
the new configuration.)
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: libvirt is already configured for
vdsm
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are not
configured
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execute
check_is_configured task (task returned with error code 1).
So I run vdsm-tool configure after I stop sanlock.
# vdsm-tool configure
Checking configuration status...
libvirt is already configured for vdsm
SUCCESS: ssl configured to true. No conflicts
Running configure...
Reconfiguration of sanlock is done.
Done configuring modules to VDSM.
But when I want to start vdsmd it still gives the error that sanlock is not
configured.
Does somebody has a solution for this?
This thread from a few days ago might be relevant.
https://www.mail-archive.com/users@ovirt.org/msg25531.html
especially the "groups sanlock" part
I am a bit lost on this… Google only tells me that there was a bug in 3.4.
Thanks in advance,
Jurriën
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3551
days inactive
3558
days old
1 comments
2 participants
participants (2)
-
Jurriën Bloemen -
Mooli Tayer