Re: [ovirt-users] failed to activate a (gluster) host. ovirt 4.0.4

[Tom Gamull]

This is pointing to network connectivity issues

You can look at logs under /var/logs/ovirt-*

Check your dns and make sure the hosts can connect to each other.  You can 
restart the host, mark it as restarted in the manager and then activate it.

Worst case, you can remove it using hosted-engine commands

Tom

> On Oct 26, 2016, at 8:53 PM, Thing  wrote:
> 
> from the engine log I see,
> 
> 
> 2016-10-27 13:45:24,595 INFO  
> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
> (DefaultQuartzScheduler2) [3877c2ef] START, 
> GetGlusterHostUUIDVDSCommand(HostName = glusterp1, 
> VdsIdVDSCommandParametersBase:{runAsync='true', 
> hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'}), log id: 51f83f78
> 2016-10-27 13:46:15,780 INFO  
> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
> (DefaultQuartzScheduler3) [] No up server in cluster
> 2016-10-27 13:47:12,326 INFO  
> [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] 
> (DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster 'Default' 
> for snapshot monitoring
> 2016-10-27 13:47:12,329 INFO  
> [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] 
> (DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster 'Default' 
> for snapshot configurations monitoring
> 2016-10-27 13:47:15,783 INFO  
> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
> (DefaultQuartzScheduler4) [27554ab4] No up server in cluster
> 2016-10-27 13:48:15,785 INFO  
> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
> (DefaultQuartzScheduler4) [27554ab4] No up server in cluster
> 2016-10-27 13:48:24,879 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (DefaultQuartzScheduler2) [3877c2ef] Correlation ID: null, Call Stack: null, 
> Custom Event ID: -1, Message: VDSM glusterp1 command failed: Message timeout 
> which can be caused by communication issues
> 2016-10-27 13:48:24,879 ERROR 
> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
> (DefaultQuartzScheduler2) [3877c2ef] Command 
> 'GetGlusterHostUUIDVDSCommand(HostName = glusterp1, 
> VdsIdVDSCommandParametersBase:{runAsync='true', 
> hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'})' execution failed: 
> VDSGenericException: VDSNetworkException: Message timeout which can be caused 
> by communication issues
> 2016-10-27 13:48:24,879 INFO  
> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
> (DefaultQuartzScheduler2) [3877c2ef] FINISH, GetGlusterHostUUIDVDSCommand, 
> log id: 51f83f78
> 2016-10-27 13:48:24,879 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] 
> (DefaultQuartzScheduler2) [3877c2ef] Command 
> 'org.ovirt.engine.core.bll.InitVdsOnUpCommand' failed: EngineException: 
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
> VDSGenericException: VDSNetworkException: Message timeout which can be caused 
> by communication issues (Failed with error VDS_NETWORK_ERROR and code 5022)
> 2016-10-27 13:48:24,887 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (DefaultQuartzScheduler2) [3877c2ef] Correlation ID: 3877c2ef, Call Stack: 
> null, Custom Event ID: -1, Message: Failed to fetch gluster peer list from 
> server glusterp1 on Cluster Default.
> 2016-10-27 13:48:24,908 INFO  
> [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler2) 
> [6083469d] Running command: HandleVdsVersionCommand internal: true. Entities 
> affected :  ID: 260c0a92-2856-4cd6-a784-01ac95fc41d5 Type: VDS
> 2016-10-27 13:48:24,959 INFO  [org.ovirt.engine.core.vdsbroker.VdsManager] 
> (org.ovirt.thread.pool-8-thread-42) [3877c2ef] Server failed to respond, 
> vds_id='260c0a92-2856-4cd6-a784-01ac95fc41d5', vds_name='glusterp1', 
> vm_count=0, spm_status='None', non-responsive_timeout (seconds)=60, error: 
> VDSGenericException: VDSNetworkException: Message timeout which can be caused 
> by communication issues
> 2016-10-27 13:48:25,003 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (org.ovirt.thread.pool-8-thread-42) [3877c2ef] Correlation ID: null, Call 
> Stack: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
> VDSGenericException: VDSNetworkException: Message timeout which can be caused 
> by communication issues
> at 
> org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:188)
> at 
> org.ovirt.engine.core.vdsbroker.gluster.AbstractGlusterBrokerCommand.proceedProxyReturnValue(AbstractGlusterBrokerCommand.java:122)
> at 
> org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand.executeVdsBrokerCommand(GetGlusterHostUUIDVDSCommand.java:19)
> at 
> org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110)
> at 
> org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
> 

Re: [ovirt-users] failed to activate a (gluster) host. ovirt 4.0.4

[Tom Gamull]

What does gluster peer status say on each host?

Tom Gamull
Red Hat | Solutions Architect
(404) 494-0280 | @magicalyak

> On Oct 26, 2016, at 8:55 PM, Tom Gamull  wrote:
> 
> This is pointing to network connectivity issues
> 
> You can look at logs under /var/logs/ovirt-*
> 
> Check your dns and make sure the hosts can connect to each other.  You can 
> restart the host, mark it as restarted in the manager and then activate it.
> 
> Worst case, you can remove it using hosted-engine commands
> 
> Tom
> 
>> On Oct 26, 2016, at 8:53 PM, Thing > > wrote:
>> 
>> from the engine log I see,
>> 
>> 
>> 2016-10-27 13:45:24,595 INFO  
>> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
>> (DefaultQuartzScheduler2) [3877c2ef] START, 
>> GetGlusterHostUUIDVDSCommand(HostName = glusterp1, 
>> VdsIdVDSCommandParametersBase:{runAsync='true', 
>> hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'}), log id: 51f83f78
>> 2016-10-27 13:46:15,780 INFO  
>> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
>> (DefaultQuartzScheduler3) [] No up server in cluster
>> 2016-10-27 13:47:12,326 INFO  
>> [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] 
>> (DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster 
>> 'Default' for snapshot monitoring
>> 2016-10-27 13:47:12,329 INFO  
>> [org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob] 
>> (DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster 
>> 'Default' for snapshot configurations monitoring
>> 2016-10-27 13:47:15,783 INFO  
>> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
>> (DefaultQuartzScheduler4) [27554ab4] No up server in cluster
>> 2016-10-27 13:48:15,785 INFO  
>> [org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService] 
>> (DefaultQuartzScheduler4) [27554ab4] No up server in cluster
>> 2016-10-27 13:48:24,879 ERROR 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>> (DefaultQuartzScheduler2) [3877c2ef] Correlation ID: null, Call Stack: null, 
>> Custom Event ID: -1, Message: VDSM glusterp1 command failed: Message timeout 
>> which can be caused by communication issues
>> 2016-10-27 13:48:24,879 ERROR 
>> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
>> (DefaultQuartzScheduler2) [3877c2ef] Command 
>> 'GetGlusterHostUUIDVDSCommand(HostName = glusterp1, 
>> VdsIdVDSCommandParametersBase:{runAsync='true', 
>> hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'})' execution failed: 
>> VDSGenericException: VDSNetworkException: Message timeout which can be 
>> caused by communication issues
>> 2016-10-27 13:48:24,879 INFO  
>> [org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand] 
>> (DefaultQuartzScheduler2) [3877c2ef] FINISH, GetGlusterHostUUIDVDSCommand, 
>> log id: 51f83f78
>> 2016-10-27 13:48:24,879 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] 
>> (DefaultQuartzScheduler2) [3877c2ef] Command 
>> 'org.ovirt.engine.core.bll.InitVdsOnUpCommand' failed: EngineException: 
>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
>> VDSGenericException: VDSNetworkException: Message timeout which can be 
>> caused by communication issues (Failed with error VDS_NETWORK_ERROR and code 
>> 5022)
>> 2016-10-27 13:48:24,887 ERROR 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>> (DefaultQuartzScheduler2) [3877c2ef] Correlation ID: 3877c2ef, Call Stack: 
>> null, Custom Event ID: -1, Message: Failed to fetch gluster peer list from 
>> server glusterp1 on Cluster Default.
>> 2016-10-27 13:48:24,908 INFO  
>> [org.ovirt.engine.core.bll.HandleVdsVersionCommand] 
>> (DefaultQuartzScheduler2) [6083469d] Running command: 
>> HandleVdsVersionCommand internal: true. Entities affected :  ID: 
>> 260c0a92-2856-4cd6-a784-01ac95fc41d5 Type: VDS
>> 2016-10-27 13:48:24,959 INFO  [org.ovirt.engine.core.vdsbroker.VdsManager] 
>> (org.ovirt.thread.pool-8-thread-42) [3877c2ef] Server failed to respond, 
>> vds_id='260c0a92-2856-4cd6-a784-01ac95fc41d5', vds_name='glusterp1', 
>> vm_count=0, spm_status='None', non-responsive_timeout (seconds)=60, error: 
>> VDSGenericException: VDSNetworkException: Message timeout which can be 
>> caused by communication issues
>> 2016-10-27 13:48:25,003 ERROR 
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
>> (org.ovirt.thread.pool-8-thread-42) [3877c2ef] Correlation ID: null, Call 
>> Stack: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: 
>> VDSGenericException: VDSNetworkException: Message timeout which can be 
>> caused by communication issues
>> at 
>> org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:188)
>> at 
>> org.ovirt.engine.core.vdsbroker.gluster.AbstractGlusterBrokerCommand.proceedProxyReturnValue(AbstractGlusterBrokerCommand.java:122)
>> at 
>> 

Re: [ovirt-users] failed to activate a (gluster) host. ovirt 4.0.4

[Thing]

from the engine log I see,


2016-10-27 13:45:24,595 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand]
(DefaultQuartzScheduler2) [3877c2ef] START,
GetGlusterHostUUIDVDSCommand(HostName = glusterp1,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'}), log id: 51f83f78
2016-10-27 13:46:15,780 INFO
[org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService]
(DefaultQuartzScheduler3) [] No up server in cluster
2016-10-27 13:47:12,326 INFO
[org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob]
(DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster
'Default' for snapshot monitoring
2016-10-27 13:47:12,329 INFO
[org.ovirt.engine.core.bll.gluster.GlusterSnapshotSyncJob]
(DefaultQuartzScheduler10) [76412dcc] No UP server found in cluster
'Default' for snapshot configurations monitoring
2016-10-27 13:47:15,783 INFO
[org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService]
(DefaultQuartzScheduler4) [27554ab4] No up server in cluster
2016-10-27 13:48:15,785 INFO
[org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService]
(DefaultQuartzScheduler4) [27554ab4] No up server in cluster
2016-10-27 13:48:24,879 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler2) [3877c2ef] Correlation ID: null, Call Stack:
null, Custom Event ID: -1, Message: VDSM glusterp1 command failed: Message
timeout which can be caused by communication issues
2016-10-27 13:48:24,879 ERROR
[org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand]
(DefaultQuartzScheduler2) [3877c2ef] Command
'GetGlusterHostUUIDVDSCommand(HostName = glusterp1,
VdsIdVDSCommandParametersBase:{runAsync='true',
hostId='260c0a92-2856-4cd6-a784-01ac95fc41d5'})' execution failed:
VDSGenericException: VDSNetworkException: Message timeout which can be
caused by communication issues
2016-10-27 13:48:24,879 INFO
[org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand]
(DefaultQuartzScheduler2) [3877c2ef] FINISH, GetGlusterHostUUIDVDSCommand,
log id: 51f83f78
2016-10-27 13:48:24,879 ERROR
[org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler2)
[3877c2ef] Command 'org.ovirt.engine.core.bll.InitVdsOnUpCommand' failed:
EngineException:
org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which can be
caused by communication issues (Failed with error VDS_NETWORK_ERROR and
code 5022)
2016-10-27 13:48:24,887 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQuartzScheduler2) [3877c2ef] Correlation ID: 3877c2ef, Call Stack:
null, Custom Event ID: -1, Message: Failed to fetch gluster peer list from
server glusterp1 on Cluster Default.
2016-10-27 13:48:24,908 INFO
[org.ovirt.engine.core.bll.HandleVdsVersionCommand]
(DefaultQuartzScheduler2) [6083469d] Running command:
HandleVdsVersionCommand internal: true. Entities affected :  ID:
260c0a92-2856-4cd6-a784-01ac95fc41d5 Type: VDS
2016-10-27 13:48:24,959 INFO  [org.ovirt.engine.core.vdsbroker.VdsManager]
(org.ovirt.thread.pool-8-thread-42) [3877c2ef] Server failed to respond,
vds_id='260c0a92-2856-4cd6-a784-01ac95fc41d5', vds_name='glusterp1',
vm_count=0, spm_status='None', non-responsive_timeout (seconds)=60, error:
VDSGenericException: VDSNetworkException: Message timeout which can be
caused by communication issues
2016-10-27 13:48:25,003 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(org.ovirt.thread.pool-8-thread-42) [3877c2ef] Correlation ID: null, Call
Stack: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:
VDSGenericException: VDSNetworkException: Message timeout which can be
caused by communication issues
at
org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase.proceedProxyReturnValue(BrokerCommandBase.java:188)
at
org.ovirt.engine.core.vdsbroker.gluster.AbstractGlusterBrokerCommand.proceedProxyReturnValue(AbstractGlusterBrokerCommand.java:122)
at
org.ovirt.engine.core.vdsbroker.gluster.GetGlusterHostUUIDVDSCommand.executeVdsBrokerCommand(GetGlusterHostUUIDVDSCommand.java:19)
at
org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:110)
at
org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:73)
at
org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:33)
at
org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:451)
at
org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33)
at
org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2171)
at
org.ovirt.engine.core.bll.storage.StorageHandlingCommandBase.runVdsCommand(StorageHandlingCommandBase.java:657)
at
org.ovirt.engine.core.bll.InitVdsOnUpCommand.initGlusterHost(InitVdsOnUpCommand.java:397)
at

[ovirt-users] failed to activate a (gluster) host. ovirt 4.0.4

[Thing]

While trying to figure out how to deploy storage I put 1 host into
maintenance mode, trying to re-activate it and its failed.

It seems to be stuck as neither in activated nor maintenance, so how would
I go about fixing this?

So what log(s) would this be written to?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users