Quantcast
Channel: VMware Communities: Message List - vCenter™ Server
Viewing all 15787 articles
Browse latest View live

Custom alarm for esx.problem.visorfs.ramdisk.full

$
0
0

Hello,

 

We are running ESXi 6.7 U1 (13004448) and VCSA 6.7 U1b.

 

A few days ago I noticed our regular firmware backups which run Get-VMHostFirmware were not getting executed. In the hostd log, I saw the error esx.problem.visorfs.ramdisk.full and noted ams-bbUsg.txt taking up pretty much all of the space in /tmp. After removing that file, everything worked fine again. We did not get any notifications or snmp traps the /tmp directory was full.

 

To my question: Is it possible to create a custom alarm in vCenter to fire on this event? I tried going into vCenter => Alarm Definitions => Add => Target type = Hosts, and then simply entering esx.problem.visorfs.ramdisk.full in the Alarm rule, but I can't enter the full string into the textbox. I'm probably doing something wrong!

 

I'm attaching a picture of how I'm trying to add the custom alarm for clarity, and below is the full error from the hostd log.

 

Thanks in advance.

 

/Gustav Andersson

 

customAlarm1.png

2020-04-24T21:42:43.852Z info hostd[2104254] [Originator@6876 sub=Vimsvc.TaskManager opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] Task Created : haTask--vim.host.FirmwareSystem.backupConfiguration-6348273

2020-04-24T21:42:43.854Z info hostd[2104254] [Originator@6876 sub=SysCommandPosix opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] ForkExec(/sbin/firmwareConfig.sh) 6249455

2020-04-24T21:42:44.095Z info hostd[2099846] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {

--> key = 111,

--> chainId = -1,

--> createdTime = "1970-01-01T00:00:00Z",

--> userName = "",

--> datacenter = (vim.event.DatacenterEventArgument) null,

--> computeResource = (vim.event.ComputeResourceEventArgument) null,

--> host = (vim.event.HostEventArgument) {

--> name = "10-0-xxx-xx.local.xxx.xx",

--> host = 'vim.HostSystem:ha-host'

--> },

--> vm = (vim.event.VmEventArgument) null,

--> ds = (vim.event.DatastoreEventArgument) null,

--> net = (vim.event.NetworkEventArgument) null,

--> dvs = (vim.event.DvsEventArgument) null,

--> fullFormattedMessage = <unset>,

--> changeTag = <unset>,

--> eventTypeId = "esx.problem.visorfs.ramdisk.full",

--> severity = <unset>,

--> message = <unset>,

--> arguments = (vmodl.KeyAnyValue) [

--> (vmodl.KeyAnyValue) {

--> key = "1",

--> value = "tmp"

--> },

--> (vmodl.KeyAnyValue) {

--> key = "2",

--> value = "/tmp/firmware-backup.6249455.lck"

--> }

--> ],

--> objectId = "ha-host",

--> objectType = "vim.HostSystem",

--> objectName = <unset>,

--> fault = (vmodl.MethodFault) null

--> }


2020-04-24T21:42:44.096Z info hostd[2099846] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 45621 : The ramdisk 'tmp' is full. As a result, the file /tmp/firmware-backup.6249455.lck could not be written.


2020-04-24T21:43:44.133Z error hostd[2104254] [Originator@6876 sub=Default opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] SysCmd [/sbin/firmwareConfig.sh --backup /usr/lib/vmware/hostd/docroot/downloads/524e04be-4d82-4d9e-03ea-db4dfb052267] failed with exit code [1] and output:

--> lockfile: Sorry, giving up on "/tmp/firmware-backup.6249455.lck"

-->

2020-04-24T21:43:44.134Z info hostd[2104254] [Originator@6876 sub=Default opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] AdapterServer caught exception: N5Vmomi5Fault11SystemError9ExceptionE(Fault cause: vmodl.fault.SystemError

--> )

--> [context]zKq7AVICAgAAAKBuxgAOaG9zdGQAAEy4NWxpYnZtYWNvcmUuc28AAFDKGwCwuhcBg/ViaG9zdGQAAek2ZQFXy3aCEq0nAWxpYnZpbS10eXBlcy5zbwABWQvCAVEUwgD1TigA01IoAAsuNgM7fQBsaWJwdGhyZWFkLnNvLjAABB2bDmxpYmMuc28uNgA=[/context]

2020-04-24T21:43:44.138Z info hostd[2104254] [Originator@6876 sub=Vimsvc.TaskManager opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] Task Completed : haTask--vim.host.FirmwareSystem.backupConfiguration-6348273 Status error

2020-04-24T21:43:44.138Z info hostd[2104254] [Originator@6876 sub=Solo.Vmomi opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] Activation [N5Vmomi10ActivationE:0x0000006f2a5f19b0] : Invoke done [backupConfiguration] on [vim.host.FirmwareSystem:ha-firmwareSystem]

2020-04-24T21:43:44.138Z info hostd[2104254] [Originator@6876 sub=Solo.Vmomi opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] Throw vmodl.fault.SystemError

2020-04-24T21:43:44.138Z info hostd[2104254] [Originator@6876 sub=Solo.Vmomi opID=1800d84d-1f-6df3 user=vpxuser:VSPHERE.LOCAL\Administrator] Result:

--> (vmodl.fault.SystemError) {

--> faultCause = (vmodl.MethodFault) null,

--> faultMessage = <unset>,

--> reason = "Internal error"

--> msg = ""

--> }


 

 



New VCenter - cannot add host

$
0
0

Running VCenter 7.0 and I am trying to add an ESXi-7.0.0-15843807-standard host. I enter all the correct credentials and addition process starts but then abruptly ends with:

 

A specified parameter was not correct: info.productVersion

 

Anybody seen this and know why this is occurring and a possible fix?

 

 

Re: VCSA v7.0 Storage Use

$
0
0

I basically agree with you. The partition sizes (or should I call it disk space reservation) are most likely massive overkill for most use cases. It's similar to ESXi 7.0 itself, where a fresh installation will use up to ~128GB on the installation disk. Anyway, most modern storage systems support thin provisioning, zero detection, and other things, so that the whole disk space is not going to be used up front. For storage system without thin provisioning options, thin provisioned virtual disks may be an option.


André

Re: New VCenter - cannot add host

$
0
0

Please do not create multiple posts. You already have one here with responses.

Re: New VCenter - cannot add host

$
0
0

Moderator: Please do not post duplicate threads. Locking this one.

vCenter server linked mode issue

$
0
0

I had a vCenter server vCenter02 with 6.5 version(recently upgraded from 6.0 to 6.5).

After upgraded, i have installed new vcenter(VCSA02) and added to the existing domain(SSO) for linked mode. After completion when i connect to the Old vCEnter server(vCEnter02).

 

i am not able to see the new vcenter server under inventory as below.

 

but when i connect to VCSA02 vcenter(new vcenter), i am able to access the both the vcenter servers as shown below.

 

When i checked the system configuration from VCSA02, i am able to see both the nodes active state when i connect from VCSA02.

But when i connect to old vCenter(vCenter02), under the nodes its showing as degrade state.

 

 

Note: Both i have logged in with vsphere.local administrator account only,

What might be the cause of issue and why its not showing both the vcenter servers.

Re: vCenter server linked mode issue

$
0
0

This issue can occur if you do not have Administrator privileges on the server. Are both vCenter is appliance or one on windows platform and other one VCSA appliance? And the one showing degraded what it is shows? Also, Can share the complete screenshot and both vCenter version and build number..

Re: Custom alarm for esx.problem.visorfs.ramdisk.full


Re: vCenter server linked mode issue

$
0
0

Both are vcenter appliance, embedded PSC. and i logged in using local domain(vsphere.local administrator).

Both has same username and password.

 

While connecting from old vcenter, i am facing issue. but from new vcsa, i am able to see the both.

Re: vCenter server linked mode issue

$
0
0

Verify DNS using nslookup, Correct any invalid DNS entries for the vCenter Server.

Re: Custom alarm for esx.problem.visorfs.ramdisk.full

$
0
0

Thanks for your reply!

 

I have already read that post. I can see 2 different solutions being presented.

 

One being creating a custom alarm in vCenter. The guy who posted writes he did not succeed in making it work for vSphere 6.7. The solution might perhaps have worked for ESXi 5.0? Could you perhaps elaborate on how I should do it in vSphere 6.7?

 

The other is done with PowerCLI. While that seems to work, I would prefer if I could get a notification from vCenter without creating a script on a VM and running it regularly.

 

/Gustav

VCSA 6.7 to 7.0 migration failure

$
0
0

I am trying to upgrade my lab VCSA 6.7.0.43000 to 7.0. It always fails on the migration part. It fails on firstboot starting the sps service.

 

I attached the log from sms_spbm_firstboot.py_35481_stderr.log. It does not seem to help very much I have searched several KB errors for failing to start SPS but no luck. This lab is out of my Vmug account so I'm not entitled to support however, my company I work for does have support so it may be a gray area of actually getting support from vmware. I normally test things in my lab before doing things in production.

 

Any Ideas or any other logs needed just let me know.

Re: VCSA v7.0 Storage Use

$
0
0

Hi Benedikt,

 

I know that. What I'd love is the ability to define my own HD sizes, mem use and CPU.

 

Having this much storage use on a home lab is crippling.

 

Thanks.

Re: VCSA v7.0 Storage Use

$
0
0

For the homelab there is always the thin provisioning ;-)

Re: VCSA 6.7 to 7.0 migration failure


Re: VCSA 6.7 to 7.0 migration failure

$
0
0

I came across that KB also but it didn't seem to help. I was unable to locate the cmfirstboot.py_####_stderr.log file. My analytics_firstboot.py_####_stderr.log is empty and the stdout says: "2020-04-25T07:32:07.793Z  VMware Analytics Service firstboot finished". My vpxd_firstboot.py_####_stdout.log has no error the last line is: 2020-04-25T07:37:09.140Z  VirtualCenter firstboot successfully finished. My pschealth-firstboot.py_#####_stderr.log has some items but doesn't really say error:

2020-04-25 07:34:00,666 INFO 71 PSCHealth FBActions.FIRSTBOOT

 

2020-04-25 07:34:00,679 INFO 73 SCA Registration completed successfully

2020-04-25 07:34:02,029 INFO 115 Done with pschealth firstboot

 

Obviously then the sms_spbm_firstboot.py_####_stderr.log has the errors and that's when it seems the installer blows out.

 

 

vmafdd-syslog.log Shows no error and the last line is: 2020-04-25T07:29:16.021Z  VMAFD Boot Succeeded

 

vapi_firstboot.py_####_stderr.log error file is blank stdout:

2020-04-25T07:32:51.928Z  Successfully started vapi-endpoint service

 

2020-04-25T07:32:51.928Z  Done with vapi firstboot

 

mgmt-firstboot.py_####_stderr.log is empty, stdout:

2020-04-25T07:37:27.759Z  Successfully started applmgmt service

 

2020-04-25T07:37:27.759Z  Service setup completed successfully

 

scafirstboot.py_####_stderr.log is empty, stdout:

 

2020-04-25T07:32:38.310Z  Successfully started sca service

2020-04-25T07:32:38.310Z  Done with sca firstboot

 

updatemgr-firstboot.py_6012_stderr.log does not exist.

 

ngc_firstboot.py_####_stderr.log does not exist.

 

fbInstall.json

 

   "start_time": "2020-04-25T07:27:57.541Z",

 

   "end_time": "2020-04-25T07:50:39.726Z"

 

vCenter host name change

$
0
0

Hi all,

 

I have to change the FQDN of my vCenter server 6.0 under windows server 2016.

How can I do this?

 

After change of hostname the windows system could be migrated successfully but the VMWare services don't start and vCenter webclient cannot be open.

 

I'm assuming I have to adapt the vCenter network configuration in order to assign the new FQDN. Do you have any idea which changes in vCenter are required?

Re: vCenter host name change

Re: vCenter server linked mode issue

$
0
0

AFter the reboot of both the vcenter servers fixed the issue

vCenter Standard Linux GUI & CLI deploy failure

$
0
0

VMware-VCSA-all-6.7.0-10244745.iso

VMware-VCSA-all-6.7.0-13010631.iso

VMware-VCSA-all-6.7.0-15976714.iso

VMware-VCSA-all-6.7.0-8217866.iso

 

On Fedora 31 (Workstation Edition) Linux 5.6.6-200.fc31.x86_64

 

Originally I tried deploying the vCSA via gui as i have in the past however when i got to the storage selection part the gui would throw an error about a json or the main one at select deployment size where everything is blank(nothing selectable or seable)

Tried all 4 versions with the oldest one not even launching complaining about some binary starting with an h(also tried on a usb stick fedora live image). Anyways, so I looked up how todo the cli deploy and I also met failure.

Any suggestions? Seems like a problem with ovftool and executing the right binary.

Viewing all 15787 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>