extract of the last engine logs, thank you
Le 16/12/2016 à 14:02, Sahina Bose a écrit :
Could you attach the engine log with this error?
On Fri, Dec 16, 2016 at 4:29 PM, Nathanaël Blanchet <[email protected]
<mailto:[email protected]>> wrote:
Hi,
I used to successfully run a replica 3 gluster volume, but since
the last 4.0.5 update, they can't connect each other with the
message : gluster [gluster peer status guadalupe1.v100.abes.fr
<http://guadalupe1.v100.abes.fr>] command failed on server
guadalupe2.v100.abes.fr <http://guadalupe2.v100.abes.fr>.
So host guadalupe1 can't never be up.
When doing gluster peer probe, they are connected as expected. I
reinstalled vdsm and gluster, but it is still the same.
I found this on guadalupe2 supervdsm.log
MainProcess|jsonrpc.Executor/6::DEBUG::2016-12-16
11:53:21,429::supervdsmServer::99::SuperVdsm.ServerCallback::(wrapper)
return peerStatus with [{'status': 'CONNECTED', 'hostname':
'10.34.101.56/24 <http://10.34.101.56/24>', 'uuid':
'c259c09b-8d7c-4b12-8745-677199877583'}, {'status': 'CONNECTED',
'hostname': 'guadalupe3.v100.abes.fr
<http://guadalupe3.v100.abes.fr>', 'uuid':
'6af67cd3-7931-446d-aaa2-ffea51325adc'}, {'status': 'CONNECTED',
'hostname': 'guadalupe1.v100.abes.fr
<http://guadalupe1.v100.abes.fr>', 'uuid':
'8eb485cd-31c4-4c3a-a315-3dc6d3ddc0c9'}]
MainProcess|jsonrpc.Executor/7::DEBUG::2016-12-16
11:53:21,490::supervdsmServer::92::SuperVdsm.ServerCallback::(wrapper)
call peerProbe with () {}
MainProcess|jsonrpc.Executor/7::DEBUG::2016-12-16
11:53:21,491::commands::68::root::(execCmd) /usr/bin/taskset
--cpu-list 0-63 /usr/sbin/gluster --mode=script peer probe
guadalupe1.v100.abes.fr <http://guadalupe1.v100.abes.fr> --xml
(cwd None)
MainProcess|jsonrpc.Executor/7::DEBUG::2016-12-16
11:53:21,570::commands::86::root::(execCmd) SUCCESS: <err> = '';
<rc> = 0
MainProcess|jsonrpc.Executor/7::DEBUG::2016-12-16
11:53:21,570::supervdsmServer::99::SuperVdsm.ServerCallback::(wrapper)
return peerProbe with True
We can see guadalupe2 can see guadalupe1 but taskset still
executes peer probe to guadalupe1 with message "Host
guadalupe1.v100.abes.fr <http://guadalupe1.v100.abes.fr> port
24007 already in peer list"
How can I say to guadalupe2 stop trying to probe guadalupe1?
--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
[email protected] <mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
--
Nathanaël Blanchet
Supervision réseau
Pôle Infrastrutures Informatiques
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
[email protected]
2016-12-16 14:20:31,403 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler3) [54d71ad2] START, GlusterServersListVDSCommand(HostName = guadalupe1, VdsIdVDSCommandParametersBase:{runAsync='true', hostId='7a30c899-a317-479a-b07b-244bc2374485'}), log id: 19da9b4e
2016-12-16 14:20:31,553 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler5) [] FINISH, GlusterServersListVDSCommand, return: [10.34.100.58/24:CONNECTED, rafale.v100.abes.fr:CONNECTED, taal.v100.abes.fr:CONNECTED], log id: 1bfc1bb6
2016-12-16 14:20:31,559 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler5) [] START, GlusterVolumesListVDSCommand(HostName = zonda, GlusterVolumesListVDSParameters:{runAsync='true', hostId='2614fcc0-c0eb-4893-8d90-8e33a1d5e47d'}), log id: 2a835a54
2016-12-16 14:20:31,559 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (DefaultQuartzScheduler3) [54d71ad2] FINISH, GlusterServersListVDSCommand, return: [10.34.101.55/24:CONNECTED, guadalupe2.v100.abes.fr:CONNECTED, guadalupe3.v100.abes.fr:CONNECTED], log id: 19da9b4e
2016-12-16 14:20:31,560 INFO [org.ovirt.engine.core.bll.InitGlusterCommandHelper] (DefaultQuartzScheduler3) [54d71ad2] Failed to find host 'Host[guadalupe1,7a30c899-a317-479a-b07b-244bc2374485]' in gluster peer list from 'Host[guadalupe1,7a30c899-a317-479a-b07b-244bc2374485]' on attempt 2
2016-12-16 14:20:31,579 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler3) [e85ac12] Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 7a30c899-a317-479a-b07b-244bc2374485 Type: VDS
2016-12-16 14:20:31,582 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler3) [e85ac12] START, SetVdsStatusVDSCommand(HostName = guadalupe1, SetVdsStatusVDSCommandParameters:{runAsync='true', hostId='7a30c899-a317-479a-b07b-244bc2374485', status='NonOperational', nonOperationalReason='GLUSTER_COMMAND_FAILED', stopSpmFailureLogged='false', maintenanceReason='null'}), log id: 316efc10
2016-12-16 14:20:31,587 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler3) [e85ac12] FINISH, SetVdsStatusVDSCommand, log id: 316efc10
2016-12-16 14:20:31,609 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler3) [e85ac12] Correlation ID: e85ac12, Job ID: 4de8e610-04f3-47fa-b5ee-f9260fb96e14, Call Stack: null, Custom Event ID: -1, Message: Gluster command [gluster peer status guadalupe1.v100.abes.fr] failed on server guadalupe2.v100.abes.fr.
2016-12-16 14:20:31,621 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler3) [e85ac12] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Failed to verify Power Management configuration for Host guadalupe1.
2016-12-16 14:20:31,642 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler3) [5270389] Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 7a30c899-a317-479a-b07b-244bc2374485 Type: VDS
2016-12-16 14:20:31,645 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (DefaultQuartzScheduler3) [5270389] Host 'guadalupe1'(7a30c899-a317-479a-b07b-244bc2374485) is already in NonOperational status for reason 'GLUSTER_COMMAND_FAILED'. SetNonOperationalVds command is skipped.
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
