--_000_D140156742F5jurrienbloemendmcamcnetworkscom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I did that also. I forgot to mention it because you only have to run --forc= e if you didn=92t stop the sanlock process of running. The result of with and without is the same. Still the vdsmd process cannot = start. From: Roy Golan <rgolan@redhat.com<mailto:rgolan@redhat.com>> Date: Monday 30 March 2015 23:25 To: Jurri=EBn Bloemen <jurrien.bloemen@dmc.amcnetworks.com<mailto:jurrien.b= loemen@dmc.amcnetworks.com>> Cc: "users@ovirt.org<mailto:users@ovirt.org>" <users@ovirt.org<mailto:users= @ovirt.org>> Subject: Re: [ovirt-users] Modules sanlock are not configured On Mar 30, 2015 10:45 PM, Jurri=EBn <Jurrien.Bloemen@dmc.amcnetworks.com<ma= ilto:Jurrien.Bloemen@dmc.amcnetworks.com>> wrote:
Hi all,
I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open the =
The manager says installing and after that is fails to connect. Looking o= n 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_cored= ump 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_networ= k 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_versio= n_check Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running check_is_config= ured 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 con=
oVirt Manager and added a new system to it. figured to work with VDSM.
Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the module use t= he following: Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure [--modul= e module-name]'. Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are not config= ured 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 l= oad 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 confi= gured 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
Try adding --force (this is what the log suggests)
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 n=
ot configured.
Does somebody has a solution for this?
I am a bit lost on this=85 Google only tells me that there was a bug in 3=
.4.
Thanks in advance,
Jurri=EBn This message (including any attachments) may contain information that is =
privileged or confidential. If you are not the intended recipient, please n= otify the sender and delete this email immediately from your systems and de= stroy all copies of it. You may not, directly or indirectly, use, disclose,= distribute, print or copy this email or any part of it if you are not the = intended recipient --_000_D140156742F5jurrienbloemendmcamcnetworkscom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <47CEC3EA5795164B9BFF70BF216D5617@chellomedia.com> Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> </head> <body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin= e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami= ly: Calibri, sans-serif;"> <div>I did that also. I forgot to mention it because you only have to run -= -force if you didn=92t stop the sanlock process of running.</div> <div>The result of with and without is the same. Still the vdsmd process ca= nnot start.</div> <div><br> </div> <div><br> </div> <div><br> </div> <span id=3D"OLK_SRC_BODY_SECTION"> <div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b= lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:= 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;= BORDER-RIGHT: medium none; PADDING-TOP: 3pt"> <span style=3D"font-weight:bold">From: </span>Roy Golan <<a href=3D"mail= to:rgolan@redhat.com">rgolan@redhat.com</a>><br> <span style=3D"font-weight:bold">Date: </span>Monday 30 March 2015 23:25<br=
<span style=3D"font-weight:bold">To: </span>Jurri=EBn Bloemen <<a href= =3D"mailto:jurrien.bloemen@dmc.amcnetworks.com">jurrien.bloemen@dmc.amcnetw= orks.com</a>><br> <span style=3D"font-weight:bold">Cc: </span>"<a href=3D"mailto:users@o= virt.org">users@ovirt.org</a>" <<a href=3D"mailto:users@ovirt.org">= users@ovirt.org</a>><br> <span style=3D"font-weight:bold">Subject: </span>Re: [ovirt-users] Modules = sanlock are not configured<br> </div> <div><br> </div> <div> <div> <p dir=3D"ltr"><br> On Mar 30, 2015 10:45 PM, Jurri=EBn <<a href=3D"mailto:Jurrien.Bloemen@d= mc.amcnetworks.com">Jurrien.Bloemen@dmc.amcnetworks.com</a>> wrote:<br> ><br> > Hi all,<br> ><br> > I have CentOS 7 running and I added the oVirt 3.5 repo to it. I open t= he oVirt Manager and added a new system to it. <br> > The manager says installing and after that is fails to connect. Lookin= g on the system I see:<br> ><br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running mkdirs<= br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configu= re_coredump<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running configu= re_vdsm_logs<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running wait_fo= r_network<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running run_ini= t_hooks<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running upgrade= d_version_check<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: Running check_i= s_configured<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Error:<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: One of the modules is= not configured to work with VDSM.<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: To configure the modu= le use the following:<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure = [--module module-name]'.<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: If all modules are no= t configured try to use:<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: 'vdsm-tool configure = --force'<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: (The force flag will = stop the module's service and start it<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: afterwards automatica= lly to load the new configuration.)<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: libvirt is already co= nfigured for vdsm<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: Modules sanlock are n= ot configured<br> > Mar 30 21:09:37 vdsmd_init_common.sh[7106]: vdsm: stopped during execu= te check_is_configured task (task returned with error code 1).<br> ><br> > So I run vdsm-tool configure after I stop sanlock. <br> ><br> > # vdsm-tool configure </p> <p dir=3D"ltr">Try adding --force (this is what the log suggests)</p> <p dir=3D"ltr">><br> > Checking configuration status...<br> ><br> > libvirt is already configured for vdsm<br> > SUCCESS: ssl configured to true. No conflicts<br> ><br> > Running configure...<br> > Reconfiguration of sanlock is done.<br> ><br> > Done configuring modules to VDSM.<br> ><br> > But when I want to start vdsmd it still gives the error that sanlock i= s not configured.<br> ><br> > Does somebody has a solution for this? <br> ><br> > I am a bit lost on this=85 Google only tells me that there was a bug i= n 3.4. <br> ><br> > Thanks in advance,<br> ><br> > Jurri=EBn<br> > This message (including any attachments) may contain information that = is privileged or confidential. If you are not the intended recipient, pleas= e notify the sender and delete this email immediately from your systems and= destroy all copies of it. You may not, directly or indirectly, use, disclose, distribute, print or copy this= email or any part of it if you are not the intended recipient</p> </div> </div> </span> </body> </html> --_000_D140156742F5jurrienbloemendmcamcnetworkscom_--