Error Creating Ramdisk For Ha Agent Configuration
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESX 4 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 1 2 Previous Next 17 Replies Latest reply: Oct 17, 2011 4:01 PM by cho9045 ESXi 4.1 HA configure error!!! linglong768 Sep 26, 2010 6:58 PM I have 2 esxi 4.1 hosts ,when configure the HA ,the error apears bellow:HA agent on xx.xx.xx.xx in cluster xx in xx has an error:cmd addnode failed for primary node:error creating ramdisk for HA agent configuration,:unknown HA errorbut other 2 esx 4.1 host is ok in this cluster 14007Views Tags: none (add) This content has been marked as final. Show 17 replies 1. Re: ESXi 4.1 HA configure error!!! FrisoAkkerman Sep 27, 2010 12:56 AM (in response to linglong768) Hi, what you can try is to disable HA and DRS at the cluster level and when that's finished enable it again. Like Show 0 Likes (0) Actions 2. Re: ESXi 4.1 HA configure error!!! Maximenu Sep 27, 2010 1:32 AM (in response to linglong768) Hi linglongTry this solution.Remove the HA from the cluster and then re-apply HA to it again. When all ESX hosts in the cluster have had HA re-enabled you should see that the HA error previously seen has now gone. And try to disconnect the server (The HA agent will be remove) and re-connect. Like Show 0 Likes (0) Actions 3. Re: ESXi 4.1 HA configure error!!! linglong768 Sep 28, 2010 7:15 PM (in response to Maximenu) thank you for both of you , i have tried it,no worked. any idears? Like Show 0 Likes (0) Actions 4. Re: ESXi 4.1 HA configure error!!! chadwickking Sep 28, 2010 7:47 PM (in response to linglong768) Unjoin the host from vcenter - SSH to server and run: (technical support mode)service mgmt-vmware stopservice vmware-aam stopservice vmware-vpxa stopRejoin the host back to vCenter - it should reinstall the agents. I had this problem today and this fixed. If it gets tougher there are alternatives.Stopping servics see:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490Worse case scenario:Right-click on the ESXi host and click Disconnect. This disconnects the ESXi host from the VirtualCenter Inventory. Log in to ESXi Troubleshooting Mode. For more information, see Tech Support Mode for Emergency Support (1003677). Uninstall the vpxa and aam components from the VMware ESXi host using the following commands:/opt/vmware/uninstallers/VMware-vpxa-uninstall.sh/opt/vmware/uninstallers/VMware-aam-ha-uninsta
noticed a couple of people reported this problem in the last two months so I figured a blog post would be useful. This thread on VMTN triggered this article. If your ESXi host is disconnected from vCenter (even 5.0 and 5.1 appear to be impacted by this) and you see error http://www.yellow-bricks.com/2013/01/07/esxi-5-x-host-disconnected-from-vcenter/ messages in your log files about free space like these: WARNING: VisorFSObj: xxxx: Cannot create file /var/spool/snmp/xxxxxxxx_x_ x_xxxx.trp for process hostd-worker because the inode table of its ramdisk (root) is full. VmkCtl Locking (/etc/vmware/esx.conf) : Unable to http://docs.openstack.org/kilo/config-reference/content/ch_configuring-openstack-bare-metal.html create or open a LOCK file. Failed with reason: No space left on device This could be caused by the fact that ESXi is running out of inodes. You can simply check that on the command line by error creating using the following command: stat -f / The outcome of this command will look as follows: File: "/" ID: 1 Namelen: 127 Type: visorfs Block size: 4096 Blocks: Total: 449852 Free: 324368 Available: 324368 Inodes: Total: 8192 Free: 55 As you can see the amount of "free" inodes is low and this is causing the experienced issues. In some cases it is reported (by vdsyn in this case) that "/var/spool/snmp/" is full and needs to error creating ramdisk be cleaned out. In this KB Article "/var/run/sfcb/" is explicitly called out and also explains what you can delete and how. So make sure to look at those two directories when an ESXi host is disconnected from vCenter. Share it:TweetPocket Related Filed Under: ServerComments JunTan says 7 January, 2013 at 11:47 Hi Epping, you can also use command df -i to check the inode useage of the filesystem. In the *nix environment, the inode allocation is based on the filesystem. Duncan Epping says 7 January, 2013 at 12:04 Euuh, there is no "df -i" on ESXi? Pat Erler says 7 January, 2013 at 13:44 Hi, as you are on rare problems with esxi, I have a problem on several servers, not being able to connect via ssh to the esxi console. Problem is, I almost find no reference to it in vmware's forum (strangly some references in centOS forums and at HP, not related to esx at all). Here is what happens: ssh yourserver.com Server refused to allocate pty you can login with ssh -T yourserver.com though (you don't get a prompt, but can issue commands and receive the results) I suspect somehow, that this may be related to putty and strange hang ups I got, when using putty with a management tool (http://www.visionapp.com/germany/solutions/asg-remote-desktop.html) which I just recently solved by specifying http://screencast.com/t/veLMANQM
is capable of managing and provisioning physical machines. The configuration file of this module is /etc/ironic/ironic.conf.The following tables provide a comprehensive list of the Bare metal service configuration options. Table 1.1. Description of agent configuration options Configuration option = Default value Description [agent] agent_api_version = v1 (StrOpt) API version to use for communicating with the ramdisk agent. agent_erase_devices_priority = None (IntOpt) Priority to run in-band erase devices via the Ironic Python Agent ramdisk. If unset, will use the priority set in the ramdisk (defaults to 10 for the GenericHardwareManager). If set to 0, will not run during cleaning. agent_pxe_append_params = nofb nomodeset vga=normal (StrOpt) Additional append parameters for baremetal PXE boot. agent_pxe_bootfile_name = pxelinux.0 (StrOpt) Neutron bootfile DHCP parameter. agent_pxe_config_template = $pybasedir/drivers/modules/agent_config.template (StrOpt) Template file for PXE configuration. heartbeat_timeout = 300 (IntOpt) Maximum interval (in seconds) for agent heartbeats. manage_tftp = True (BoolOpt) Whether Ironic will manage TFTP files for the deploy ramdisks. If set to False, you will need to configure your own TFTP server that allows booting the deploy ramdisks. Table 1.2. Description of AMQP configuration options Configuration option = Default value Description [DEFAULT] control_exchange = openstack (StrOpt) The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option. notification_driver = [] (MultiStrOpt) Driver or drivers to handle sending notifications. notification_topics = notifications (ListOpt) AMQP topic used for OpenStack notifications. transport_url = None (StrOpt) A URL representing the messaging driver to use and its full configuration. If not set, we fall back to the rpc_backend option and driver specific configuration. Table 1.3. Description of AMT configuration options Configuration option = D