subject:"\[ovirt\-users\] vdsmd fails after upgrade 4.1 \-> 4.2"

Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-08 Thread Frank Rothenstein

Thanks Thomas,

it seems you were right. I followed the instructions to enable
hugepages via kernel command line and after reboot vdsmd starts
correctly.
(I went back to 4.1.9 in between, added the kernel command line and
upgraded to 4.2)

The docs/release notes should mention it - or did I miss it?

Am Dienstag, den 06.02.2018, 17:17 -0800 schrieb Thomas Davis:
> sorry, make that:
> 
> hugeadm --pool-list
>   Size  Minimum  Current  Maximum  Default
>   2097152 1024 1024 1024*
> 1073741824   4   4   4 
> 
> 
> On Tue, Feb 6, 2018 at 5:16 PM, Thomas Davis  wrote:
> > I found that you now need hugepage1g support.  The error messages
> > are wrong - it's not truly a libvirt problem, it's hugepages1g are
> > missing for libvirt.
> > 
> > add something like:
> > 
> > default_hugepagesz=1G hugepagesz=1G hugepages=4 hugepagesz=2M
> > hugepages=1024 to the kernel command line.
> > 
> > You can also do a 'yum install libhugetlbfs-utils', then do:
> > 
> > hugeadm --list
> > Mount Point  Options
> > /dev/hugepages   rw,seclabel,relatime
> > /dev/hugepages1G rw,seclabel,relatime,pagesize=1G
> > 
> > if you do not see the /dev/hugepages1G listed, then vdsmd/libvirt
> > will not start.
> > 
> > 
> > 
> > 
> > 
> > 
> > On Mon, Feb 5, 2018 at 5:49 AM, Frank Rothenstein  > dden-kliniken.de> wrote:
> > > Hi, 
> > > 
> > > I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start
> > > the 
> > > host-processes. 
> > > systemctl start vdsmd fails with following lines in journalctl: 
> > > 
> > >  
> > > 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running run_init_hooks 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: Running check_is_configured 
> > > Feb 05 14:40:15 glusternode1.bodden-kliniken.net 
> > > sasldblistusers2[10440]: DIGEST-MD5 common mech free 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Error: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: One of the modules is not configured
> > > to 
> > > work with VDSM. 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: To configure the module use the
> > > following: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure [--module
> > > module- 
> > > name]'. 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: If all modules are not configured
> > > try to 
> > > use: 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: 'vdsm-tool configure --force' 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: (The force flag will stop the
> > > module's 
> > > service and start it 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: afterwards automatically to load the
> > > new 
> > > configuration.) 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: abrt is already configured for vdsm 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: lvm is configured for vdsm 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: libvirt is not configured for vdsm
> > > yet 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Current revision of multipath.conf 
> > > detected, preserving 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: Modules libvirt are not configured 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net 
> > > vdsmd_init_common.sh[10414]: vdsm: stopped during execute 
> > > check_is_configured task (task returned with error code 1). 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: 
> > > vdsmd.service: control process exited, code=exited status=1 
> > > Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]:
> > > Failed to 
> > > start Virtual Desktop Server Manager. 
> > > -- Subject: Unit vdsmd.service has failed 
> > > -- Defined-By: systemd 
> > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd
> > > -devel 
> > > -- 
> > > -- Unit vdsmd.service has failed. 



Frank Rothenstein 

Systemadministrator
Fon: +49 3821 700 125
Fax: +49 3821 700 190Internet: www.bodden-kliniken.de
E-Mail: f.rothenst...@bodden-kliniken.de


_
BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
Sandhufe 2
18311 Ribnitz-Damgarten

Telefon: 03821-700-0
Telefax: 03821-700-240

E-Mail: i...@bodden-kliniken.de 
Internet:

Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-05 Thread Petr Kotas

Hi Frank,

can you please send a vdsm logs? The 4.2 release added the little different
deployment from the engine.
Now the ansible is also called. Although I am not sure if this is your case.

I would go for entirely removing the vdsm and installing it from scratch if
it is possible for you.
This could solve your issue.

Looking forward to hear from you.

Petr

On Mon, Feb 5, 2018 at 2:49 PM, Frank Rothenstein <
f.rothenst...@bodden-kliniken.de> wrote:

> Hi,
>
> I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start the
> host-processes.
> systemctl start vdsmd fails with following lines in journalctl:
>
> 
>
> Feb 05 14:40:15 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network
> Feb 05 14:40:15 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: vdsm: Running run_init_hooks
> Feb 05 14:40:15 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: vdsm: Running check_is_configured
> Feb 05 14:40:15 glusternode1.bodden-kliniken.net
> sasldblistusers2[10440]: DIGEST-MD5 common mech free
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: Error:
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: One of the modules is not configured to
> work with VDSM.
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: To configure the module use the following:
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: 'vdsm-tool configure [--module module-
> name]'.
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: If all modules are not configured try to
> use:
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: 'vdsm-tool configure --force'
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: (The force flag will stop the module's
> service and start it
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: afterwards automatically to load the new
> configuration.)
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: abrt is already configured for vdsm
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: lvm is configured for vdsm
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: libvirt is not configured for vdsm yet
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: Current revision of multipath.conf
> detected, preserving
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: Modules libvirt are not configured
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net
> vdsmd_init_common.sh[10414]: vdsm: stopped during execute
> check_is_configured task (task returned with error code 1).
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]:
> vdsmd.service: control process exited, code=exited status=1
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: Failed to
> start Virtual Desktop Server Manager.
> -- Subject: Unit vdsmd.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit vdsmd.service has failed.
> --
> -- The result is failed.
> Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: Dependency
> failed for MOM instance configured for VDSM purposes.
> -- Subject: Unit mom-vdsm.service has failed
>
> 
>
> The suggested "vdsm-tool configure --force" runs w/o errors, the
> following restart of vdsmd shows the same error.
>
> Any hints on that topic?
>
> Frank
>
>
>
> Frank Rothenstein
>
> Systemadministrator
> Fon: +49 3821 700 125 <+49%203821%20700125>
> Fax: +49 3821 700 190 <+49%203821%20700190>
> Internet: www.bodden-kliniken.de
> E-Mail: f.rothenst...@bodden-kliniken.de
>
>
> _
> BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
> Sandhufe 2
> 18311 Ribnitz-Damgarten
>
> Telefon: 03821-700-0
> Telefax: 03821-700-240
>
> E-Mail: i...@bodden-kliniken.de
> Internet: http://www.bodden-kliniken.de
>
> Sitz: Ribnitz-Damgarten, Amtsgericht: Stralsund, HRB 2919, Steuer-Nr.:
> 079/133/40188
> Aufsichtsratsvorsitzende: Carmen Schröter, Geschäftsführer: Dr. Falko
> Milski, MBA
>
> Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten
> Adressaten bestimmt. Wenn Sie nicht der
> vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten,
> beachten Sie bitte, dass jede
> Form der Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts
> dieser E-Mail unzulässig ist.
> Wir bitten Sie, sofort den Absender zu informieren und die E-Mail zu
> löschen.
>
>   © BODDEN-KLINIKEN Ribnitz-Damgarten GmbH 2017
> *** Virenfrei durch Kerio Mail Server und SOPHOS Antivirus ***
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>

[ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

2018-02-05 Thread Frank Rothenstein

Hi,

I'm currently stuck - after upgrading 4.1 to 4.2 I cannot start the
host-processes.
systemctl start vdsmd fails with following lines in journalctl:



Feb 05 14:40:15 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: vdsm: Running wait_for_network
Feb 05 14:40:15 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: vdsm: Running run_init_hooks
Feb 05 14:40:15 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: vdsm: Running check_is_configured
Feb 05 14:40:15 glusternode1.bodden-kliniken.net
sasldblistusers2[10440]: DIGEST-MD5 common mech free
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: Error:
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: One of the modules is not configured to
work with VDSM.
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: To configure the module use the following:
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: 'vdsm-tool configure [--module module-
name]'.
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: If all modules are not configured try to
use:
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: 'vdsm-tool configure --force'
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: (The force flag will stop the module's
service and start it
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: afterwards automatically to load the new
configuration.)
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: abrt is already configured for vdsm
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: lvm is configured for vdsm
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: libvirt is not configured for vdsm yet
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: Current revision of multipath.conf
detected, preserving
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: Modules libvirt are not configured
Feb 05 14:40:16 glusternode1.bodden-kliniken.net
vdsmd_init_common.sh[10414]: vdsm: stopped during execute
check_is_configured task (task returned with error code 1).
Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]:
vdsmd.service: control process exited, code=exited status=1
Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: Failed to
start Virtual Desktop Server Manager.
-- Subject: Unit vdsmd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vdsmd.service has failed.
-- 
-- The result is failed.
Feb 05 14:40:16 glusternode1.bodden-kliniken.net systemd[1]: Dependency
failed for MOM instance configured for VDSM purposes.
-- Subject: Unit mom-vdsm.service has failed



The suggested "vdsm-tool configure --force" runs w/o errors, the
following restart of vdsmd shows the same error.

Any hints on that topic?

Frank



Frank Rothenstein 

Systemadministrator
Fon: +49 3821 700 125
Fax: +49 3821 700 190Internet: www.bodden-kliniken.de
E-Mail: f.rothenst...@bodden-kliniken.de


_
BODDEN-KLINIKEN Ribnitz-Damgarten GmbH
Sandhufe 2
18311 Ribnitz-Damgarten

Telefon: 03821-700-0
Telefax: 03821-700-240

E-Mail: i...@bodden-kliniken.de 
Internet: http://www.bodden-kliniken.de

Sitz: Ribnitz-Damgarten, Amtsgericht: Stralsund, HRB 2919, Steuer-Nr.: 
079/133/40188
Aufsichtsratsvorsitzende: Carmen Schröter, Geschäftsführer: Dr. Falko Milski, 
MBA

Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der 
vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, beachten 
Sie bitte, dass jede 
Form der Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser 
E-Mail unzulässig ist. 
Wir bitten Sie, sofort den Absender zu informieren und die E-Mail zu löschen. 

      © BODDEN-KLINIKEN Ribnitz-Damgarten GmbH 2017
*** Virenfrei durch Kerio Mail Server und SOPHOS Antivirus ***
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

Re: [ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

[ovirt-users] vdsmd fails after upgrade 4.1 -> 4.2

3 matches

Site Navigation

Mail list logo

Footer information