[ovirt-users] Re: oVirt 4.5.5 VDSM error
Hi.
Can you send the logs for us?
/var/log/vdsm/vdsm.log
Cheers.
Em ter., 22 de ago. de 2023 às 09:59, escreveu:
> HI guys,
>
> I've installed a new ovirt stack 4.5 and everything works fine.
> After the upgrade to 4.5.5 VDSM doesn't work correctly
>
> ---
> [root@lce8cdpnode2 opt]# systemctl status vdsmd.service
> ● vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: disabled)
>Active: active (running) since Tue 2023-08-22 14:34:44 CEST; 19min ago
> Process: 3332 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
> --pre-start (code=exited, status=0/SUCCESS)
> Main PID: 3413 (vdsmd)
> Tasks: 56 (limit: 823896)
>Memory: 312.3M
>CGroup: /system.slice/vdsmd.service
>├─3413 /usr/bin/python3 /usr/libexec/vdsm/vdsmd
>└─4704 /usr/libexec/ioprocess --read-pipe-fd 59 --write-pipe-fd
> 58 --max-threads 10 --max-queued-requests 10
>
> Aug 22 14:34:44 lce8cdpnode2..local vdsmd_init_common.sh[3332]: vdsm:
> Running test_space
> Aug 22 14:34:44 lce8cdpnode2..local vdsmd_init_common.sh[3332]: vdsm:
> Running test_lo
> Aug 22 14:34:44 lce8cdpnode2..local systemd[1]: Started Virtual Desktop
> Server Manager.
> Aug 22 14:34:47 lce8cdpnode2..local vdsm[3413]: WARN MOM not available.
> Error: [Errno 2] No such file or directory
> Aug 22 14:34:47 lce8cdpnode2..local vdsm[3413]: WARN MOM not available,
> KSM stats will be missing. Error:
> Aug 22 14:41:30 lce8cdpnode2..local vdsm[3413]: WARN unhandled write event
> Aug 22 14:41:40 lce8cdpnode2..local vdsm[3413]: WARN unhandled write event
> Aug 22 14:41:43 lce8cdpnode2..local vdsm[3413]: ERROR Error getting
> managedvolume connector info: Managed Volume Helper failed.: ('Error
> executing helper: Command [\'/usr/bin/python3\',
> \'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with
> rc>
> Traceback (most
> recent call last):
> File
> "/usr/lib/python3.6/site-packages/vdsm/host/caps.py", line 161, in get
>
> caps["connector_info"] = managedvolume.connector_info()
> File
> "/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 63,
> in wrapper
> return
> func(*args, **kwargs)
> File
> "/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 78,
> in connector_info
> return
> run_helper("connector_info")
> File
> "/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 184,
> in run_helper
> sub_cmd,
> cmd_input=cmd_input)
> File
> "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 38, in
> __call__
> return
> callMethod()
> File
> "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 36, in
>
> **kwargs)
> File "",
> line 2, in managedvolume_run_helper
> File
> "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod
> raise
> convert_to_error(kind, result)
>
> vdsm.storage.exception.ManagedVolumeHelperFailed: Managed Volume Helper
> failed.: ('Error executing helper: Command [\'/usr/bin/python3\',
> \'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with
> rc>
> Aug 22 14:41:43 lce8cdpnode2..local vdsm[3413]: ERROR Error getting
> managedvolume connector info: Managed Volume Helper failed.: ('Error
> executing helper: Command [\'/usr/bin/python3\',
> \'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with
> rc>
> Traceback (most
> recent call last):
> File
> "/usr/lib/python3.6/site-packages/vdsm/host/caps.py", line 161, in get
>
> caps["connector_info"] = managedvolume.connector_info()
> File
> "/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 63,
> in wrapper
> return
> func(*args, **kwargs)
> File
> "/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 78,
> in
[ovirt-users] oVirt 4.5.5 VDSM error
HI guys,
I've installed a new ovirt stack 4.5 and everything works fine.
After the upgrade to 4.5.5 VDSM doesn't work correctly
---
[root@lce8cdpnode2 opt]# systemctl status vdsmd.service
● vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
preset: disabled)
Active: active (running) since Tue 2023-08-22 14:34:44 CEST; 19min ago
Process: 3332 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start
(code=exited, status=0/SUCCESS)
Main PID: 3413 (vdsmd)
Tasks: 56 (limit: 823896)
Memory: 312.3M
CGroup: /system.slice/vdsmd.service
├─3413 /usr/bin/python3 /usr/libexec/vdsm/vdsmd
└─4704 /usr/libexec/ioprocess --read-pipe-fd 59 --write-pipe-fd 58
--max-threads 10 --max-queued-requests 10
Aug 22 14:34:44 lce8cdpnode2..local vdsmd_init_common.sh[3332]: vdsm: Running
test_space
Aug 22 14:34:44 lce8cdpnode2..local vdsmd_init_common.sh[3332]: vdsm: Running
test_lo
Aug 22 14:34:44 lce8cdpnode2..local systemd[1]: Started Virtual Desktop Server
Manager.
Aug 22 14:34:47 lce8cdpnode2..local vdsm[3413]: WARN MOM not available. Error:
[Errno 2] No such file or directory
Aug 22 14:34:47 lce8cdpnode2..local vdsm[3413]: WARN MOM not available, KSM
stats will be missing. Error:
Aug 22 14:41:30 lce8cdpnode2..local vdsm[3413]: WARN unhandled write event
Aug 22 14:41:40 lce8cdpnode2..local vdsm[3413]: WARN unhandled write event
Aug 22 14:41:43 lce8cdpnode2..local vdsm[3413]: ERROR Error getting
managedvolume connector info: Managed Volume Helper failed.: ('Error executing
helper: Command [\'/usr/bin/python3\',
\'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with rc>
Traceback (most recent
call last):
File
"/usr/lib/python3.6/site-packages/vdsm/host/caps.py", line 161, in get
caps["connector_info"] = managedvolume.connector_info()
File
"/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 63, in
wrapper
return func(*args,
**kwargs)
File
"/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 78, in
connector_info
return
run_helper("connector_info")
File
"/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 184, in
run_helper
sub_cmd,
cmd_input=cmd_input)
File
"/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 38, in
__call__
return callMethod()
File
"/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 36, in
**kwargs)
File "", line
2, in managedvolume_run_helper
File
"/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod
raise
convert_to_error(kind, result)
vdsm.storage.exception.ManagedVolumeHelperFailed: Managed Volume Helper
failed.: ('Error executing helper: Command [\'/usr/bin/python3\',
\'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with rc>
Aug 22 14:41:43 lce8cdpnode2..local vdsm[3413]: ERROR Error getting
managedvolume connector info: Managed Volume Helper failed.: ('Error executing
helper: Command [\'/usr/bin/python3\',
\'/usr/libexec/vdsm/managedvolume-helper\', \'connector_info\'] failed with rc>
Traceback (most recent
call last):
File
"/usr/lib/python3.6/site-packages/vdsm/host/caps.py", line 161, in get
caps["connector_info"] = managedvolume.connector_info()
File
"/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 63, in
wrapper
return func(*args,
**kwargs)
File
"/usr/lib/python3.6/site-packages/vdsm/storage/managedvolume.py", line 78, in
connector_info
return
[ovirt-users] Re: ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials
Thanks a lot. Sorry for the delay ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KRY33XVL5UQUC53NAPZVUFEDLXYDVC35/
[ovirt-users] Re: Active Active Stretched Node cluster not working as expected.
On Tue, Aug 22, 2023 at 8:52 AM Gaurang Patel wrote: > Suggest any other solution if any. > > > Your subject says "not working as expected" and you refer to the RHV DR guides. My comment is that in my opinion HCI architecture is not expected to work / be supported for active active DR scenarios as described there. But you can follow general GlusterFS indications for solving split brain scenarios, like this one: https://docs.gluster.org/en/main/Troubleshooting/resolving-splitbrain/ and / or submit your question also to GlusterFS mailing lists or see if here you find useful information for supported configurations, quorum setup to prevent split brain conditions, ecc: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/configuring_red_hat_virtualization_with_red_hat_gluster_storage/index https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5/html/administration_guide/sect-managing_split-brain#sect-Preventing_Split-brain HIH, Gianluca ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FOMMIWHGCPKZYC5TKU5SNXVQK2DHJLW6/
