[Users] XML RPC error in command
Rami Vaknin
rvaknin at redhat.com
Tue Feb 7 01:24:14 EST 2012
On 02/07/2012 12:59 AM, justin potts wrote:
> Getting the following error after a successful install and reboot:
>
> 19:24:50,662 INFO
> [org.ovirt.engine.core.utils.hostinstall.MinaInstallWrapper]
> (pool-5-thread-8) RunSSHCommand returns true
> 19:24:50,662 INFO [org.ovirt.engine.core.bll.VdsInstaller]
> (pool-5-thread-8) FinishCommand ended:true
> 19:24:50,662 INFO [org.apache.sshd.client.session.ClientSessionImpl]
> (pool-5-thread-8) Closing session
> 19:24:50,716 INFO [org.ovirt.engine.core.bll.InstallVdsCommand]
> (pool-5-thread-8) After Installation pool-5-thread-8
> 19:24:50,752 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (pool-5-thread-8) START, SetVdsStatusVDSCommand(vdsId =
> 250f8cda-4a0f-11e1-a961-5254
> 003fe1e9, status=Reboot, nonOperationalReason=NONE), log id: 72e555cc
> 19:24:50,797 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (pool-5-thread-8) FINISH, SetVdsStatusVDSCommand, log id: 72e555cc
> 19:24:50,820 INFO [org.ovirt.engine.core.bll.VdsCommand]
> (pool-5-thread-9) Waiting 300 seconds, for server to finish reboot
> process.
> 19:28:04,397 INFO
> [org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand]
> (pool-5-thread-10) Lock Acquired to object EngineLock [exclusiveLocks=
> key: org.ov
> irt.engine.core.bll.storage.FenceVdsManualyCommand value:
> 250f8cda-4a0f-11e1-a961-5254003fe1e9
> , sharedLocks= ]
> 19:28:04,398 INFO
> [org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand]
> (pool-5-thread-10) Running command: FenceVdsManualyCommand internal:
> false. Entiti
> es affected : ID: 250f8cda-4a0f-11e1-a961-5254003fe1e9 Type: VDS
> 19:28:04,436 INFO
> [org.ovirt.engine.core.bll.ClearNonResponsiveVdsVmsCommand]
> (pool-5-thread-10) Running command: ClearNonResponsiveVdsVmsCommand
> internal: tru
> e. Entities affected : ID: 250f8cda-4a0f-11e1-a961-5254003fe1e9 Type: VDS
> 19:28:04,457 INFO
> [org.ovirt.engine.core.vdsbroker.UpdateVdsVMsClearedVDSCommand]
> (pool-5-thread-10) START, UpdateVdsVMsClearedVDSCommand(vdsId =
> 250f8cda-4a0f
> -11e1-a961-5254003fe1e9), log id: c232386
> 19:28:04,461 INFO
> [org.ovirt.engine.core.vdsbroker.UpdateVdsVMsClearedVDSCommand]
> (pool-5-thread-10) FINISH, UpdateVdsVMsClearedVDSCommand, log id:
> c232386
> 19:28:04,504 INFO
> [org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand]
> (pool-5-thread-10) Lock freed to object EngineLock [exclusiveLocks=
> key: org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand value:
> 250f8cda-4a0f-11e1-a961-5254003fe1e9
> , sharedLocks= ]
> 19:29:50,822 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (pool-5-thread-9) START, SetVdsStatusVDSCommand(vdsId =
> 250f8cda-4a0f-11e1-a961-5254003fe1e9, status=NonResponsive,
> nonOperationalReason=NONE), log id: 2e1f48b4
> 19:29:50,847 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (pool-5-thread-9) FINISH, SetVdsStatusVDSCommand, log id: 2e1f48b4
> 19:30:09,652 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
> (QuartzScheduler_Worker-100) XML RPC error in command
> GetCapabilitiesVDS ( Vds: ovirtnode.grims.com ), the error was:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 19:30:14,679 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
> (QuartzScheduler_Worker-42) XML RPC error in command
> GetCapabilitiesVDS ( Vds: ovirtnode.grims.com ), the error was:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 19:30:17,687 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
> (QuartzScheduler_Worker-38) XML RPC error in command
> GetCapabilitiesVDS ( Vds: ovirtnode.grims.com ), the error was:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 19:30:20,695 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
> (QuartzScheduler_Worker-40) XML RPC error in command
> GetCapabilitiesVDS ( Vds: ovirtnode.grims.com ), the error was:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
> 19:30:25,735 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand]
> (QuartzScheduler_Worker-45) XML RPC error in command
> GetCapabilitiesVDS ( Vds: ovirtnode.grims.com ), the error was:
> java.util.concurrent.ExecutionException:
> java.lang.reflect.InvocationTargetException
>
> Neither the engine host nor the node are firewalled. Communicated has
> been verified between them. Ovirt bridge is up on the node and IP'd.
> No VDSM processes are running on the node however.
That's the reason, Engine expect the node's vdsm to respond to
getVdsCapabilities command 5 minutes after installation's reboot has
started.
You can check why vdsm didn't start by running the service manually from
command line (without using the systemctl command), it might also be one
of its needed service that failed to start like the following iscsid
issue described in:
https://bugzilla.redhat.com/show_bug.cgi?id=786174
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
--
Thanks,
Rami Vaknin, QE @ Red Hat, TLV, IL.
More information about the Users
mailing list