Re: [ovirt-users] Node issues

2014-11-30 Thread Doron Fediuck
Hi Juan.
it seems as you have connectivity issues with the storage:

> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Failed to connect Host node3 to
> the Storage Domains node1_image.

And-

> 2014-11-29 23:40:05,691 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: The error message for connection
> node1.monalisa.com.py:/nfs/image returned by VDSM was: Problem while trying
> to mount target
> 2014-11-29 23:40:05,695 ERROR
> [org.ovirt.engine.core.bll.storage.NFSStorageHelper]
> (DefaultQuartzScheduler_Worker-79) [be7203c] The connection with details
> node1.monalisa.com.py:/nfs/image failed because of error code 477 and error
> message is: problem while trying to mount target

You should verify your configuration first. If it looks fine consider selinux
issues as well.

Doron

- Original Message -
> From: "Juan Carlos YJ. Lin" 
> To: users@ovirt.org
> Sent: Sunday, November 30, 2014 4:57:30 AM
> Subject: [ovirt-users] Node issues
> 
> OVirt 3.5 hosted, installed new node, centos 6.5 minumal, updated, ovirt3.5
> repos,
> 
> with ovirt interface, create on default datacenter try to add second host
> the system installs and then occurs error
> 
> the host cannot be up
> 
> engine.log
> 
> 2014-11-29 23:37:57,719 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-48) Activate finished. Lock released.
> Monitoring can run now for host node3 from data-center Default
> 2014-11-29 23:37:57,730 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-48) Correlation ID: 7cf0e41a, Job ID:
> f4e3d0cb-e7f7-4c91-8fcd-f3323848d53a, Call Stack: null, Custom Event ID: -1,
> Message: Host node3 was activated by admin.
> 2014-11-29 23:37:57,762 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (org.ovirt.thread.pool-8-thread-48) Lock freed to object EngineLock
> [exclusiveLocks= key: 447f5911-07b7-4b10-9eb6-15a5e06e535a value: VDS
> , sharedLocks= ]
> 2014-11-29 23:38:00,369 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
> (DefaultQuartzScheduler_Worker-79) START, GetHardwareInfoVDSCommand(HostName
> = node3, HostId = 447f5911-07b7-4b10-9eb6-15a5e06e535a,
> vds=Host[node3,447f5911-07b7-4b10-9eb6-15a5e06e535a]), log id: 737e2224
> 2014-11-29 23:38:00,382 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand]
> (DefaultQuartzScheduler_Worker-79) FINISH, GetHardwareInfoVDSCommand, log
> id: 737e2224
> 2014-11-29 23:38:00,417 INFO
> [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand]
> (DefaultQuartzScheduler_Worker-79) [d948749] Running command:
> HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected :
> ID: 447f5911-07b7-4b10-9eb6-15a5e06e535a Type: VDS
> 2014-11-29 23:38:00,431 INFO [org.ovirt.engine.core.bll.InitVdsOnUpCommand]
> (DefaultQuartzScheduler_Worker-79) [2abcada9] Running command:
> InitVdsOnUpCommand internal: true. Entities affected : ID:
> 0002-0002-0002-0002-0101 Type: StoragePool
> 2014-11-29 23:38:00,445 INFO
> [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand]
> (DefaultQuartzScheduler_Worker-79) [be7203c] Running command:
> ConnectHostToStoragePoolServersCommand internal: true. Entities affected :
> ID: 0002-0002-0002-0002-0101 Type: StoragePool
> 2014-11-29 23:38:00,453 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand]
> (DefaultQuartzScheduler_Worker-79) [be7203c] START,
> ConnectStorageServerVDSCommand(HostName = node3, HostId =
> 447f5911-07b7-4b10-9eb6-15a5e06e535a, storagePoolId =
> 0002-0002-0002-0002-0101, storageType = NFS, connectionList = [{
> id: 2fc02401-37e2-4169-83e4-c302ac1e0eb2, connection:
> 192.168.1.90:/mnt/storage1/ovirt_share/exports, iqn: null, vfsType: null,
> mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };{
> id: 4454ad4c-be93-49e6-ab77-87befc141b21, connection:
> node1.monalisa.com.py:/nfs/image, iqn: null, vfsType: null, mountOptions:
> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id:
> 653cab22
> 2014-11-29 23:40:05,676 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Failed to connect Host node3 to
> the Storage Domains node1_image.
> 2014-11-29 23:40:05,678 

[ovirt-users] Node issues

2014-11-29 Thread Juan Carlos YJ. Lin
OVirt 3.5 hosted, installed new node, centos 6.5 minumal, updated, ovirt3.5 
repos, 

with ovirt interface, create on default datacenter try to add second host 
the system installs and then occurs error 

the host cannot be up 

engine.log 

2014-11-29 23:37:57,719 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] 
(org.ovirt.thread.pool-8-thread-48) Activate finished. Lock released. 
Monitoring can run now for host node3 from data-center Default 
2014-11-29 23:37:57,730 INFO 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(org.ovirt.thread.pool-8-thread-48) Correlation ID: 7cf0e41a, Job ID: 
f4e3d0cb-e7f7-4c91-8fcd-f3323848d53a, Call Stack: null, Custom Event ID: -1, 
Message: Host node3 was activated by admin. 
2014-11-29 23:37:57,762 INFO [org.ovirt.engine.core.bll.ActivateVdsCommand] 
(org.ovirt.thread.pool-8-thread-48) Lock freed to object EngineLock 
[exclusiveLocks= key: 447f5911-07b7-4b10-9eb6-15a5e06e535a value: VDS 
, sharedLocks= ] 
2014-11-29 23:38:00,369 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] 
(DefaultQuartzScheduler_Worker-79) START, GetHardwareInfoVDSCommand(HostName = 
node3, HostId = 447f5911-07b7-4b10-9eb6-15a5e06e535a, 
vds=Host[node3,447f5911-07b7-4b10-9eb6-15a5e06e535a]), log id: 737e2224 
2014-11-29 23:38:00,382 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] 
(DefaultQuartzScheduler_Worker-79) FINISH, GetHardwareInfoVDSCommand, log id: 
737e2224 
2014-11-29 23:38:00,417 INFO 
[org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] 
(DefaultQuartzScheduler_Worker-79) [d948749] Running command: 
HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : 
ID: 447f5911-07b7-4b10-9eb6-15a5e06e535a Type: VDS 
2014-11-29 23:38:00,431 INFO [org.ovirt.engine.core.bll.InitVdsOnUpCommand] 
(DefaultQuartzScheduler_Worker-79) [2abcada9] Running command: 
InitVdsOnUpCommand internal: true. Entities affected : ID: 
0002-0002-0002-0002-0101 Type: StoragePool 
2014-11-29 23:38:00,445 INFO 
[org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] 
(DefaultQuartzScheduler_Worker-79) [be7203c] Running command: 
ConnectHostToStoragePoolServersCommand internal: true. Entities affected : ID: 
0002-0002-0002-0002-0101 Type: StoragePool 
2014-11-29 23:38:00,453 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
(DefaultQuartzScheduler_Worker-79) [be7203c] START, 
ConnectStorageServerVDSCommand(HostName = node3, HostId = 
447f5911-07b7-4b10-9eb6-15a5e06e535a, storagePoolId = 
0002-0002-0002-0002-0101, storageType = NFS, connectionList = [{ 
id: 2fc02401-37e2-4169-83e4-c302ac1e0eb2, connection: 
192.168.1.90:/mnt/storage1/ovirt_share/exports, iqn: null, vfsType: null, 
mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };{ id: 
4454ad4c-be93-49e6-ab77-87befc141b21, connection: 
node1.monalisa.com.py:/nfs/image, iqn: null, vfsType: null, mountOptions: null, 
nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 653cab22 
2014-11-29 23:40:05,676 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: null, Call Stack: 
null, Custom Event ID: -1, Message: Failed to connect Host node3 to the Storage 
Domains node1_image. 
2014-11-29 23:40:05,678 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] 
(DefaultQuartzScheduler_Worker-79) [be7203c] FINISH, 
ConnectStorageServerVDSCommand, return: 
{4454ad4c-be93-49e6-ab77-87befc141b21=477, 
2fc02401-37e2-4169-83e4-c302ac1e0eb2=0}, log id: 653cab22 
2014-11-29 23:40:05,691 ERROR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: null, Call Stack: 
null, Custom Event ID: -1, Message: The error message for connection 
node1.monalisa.com.py:/nfs/image returned by VDSM was: Problem while trying to 
mount target 
2014-11-29 23:40:05,695 ERROR 
[org.ovirt.engine.core.bll.storage.NFSStorageHelper] 
(DefaultQuartzScheduler_Worker-79) [be7203c] The connection with details 
node1.monalisa.com.py:/nfs/image failed because of error code 477 and error 
message is: problem while trying to mount target 
2014-11-29 23:40:05,697 INFO 
[org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] 
(DefaultQuartzScheduler_Worker-79) [be7203c] Host node3 storage connection was 
failed 
2014-11-29 23:40:05,708 WARN 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(DefaultQuartzScheduler_Worker-79) [be7203c] Correlation ID: be7203c, Call 
Stack: null, Custom Event ID: -1, Message: Failed to connect Host node3 to 
Storage Servers 
2014-11-29 23:40:05,725 INFO 
[org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] 
(org.ovirt.thread.pool-8-thread-19) START, 
ConnectStoragePoolVDSCommand(HostName = node3, HostId =