VMware Cloud Community
AlexZZ
Contributor
Contributor

ESXi 5.5. "The ramdisk 'root' is full. As a result, the file /var/run/vmware/tickets/vmtck XXXXXX could not be written. error XXXXXXXX"

Every 5-10 minites I have error

The ramdisk 'root' is full.  As a result, the file /var/run/vmware/tickets/vmtck-XXXXXXXXX could not be written.

Supermicro X9DR3-F + VMware-VMvisor-Installer-5.5.0-1331820.x86_64.iso

addons:

net-igb-5.0.5.1-1OEM.550.0.0.1198611.x86_64.vib

scsi-megaraid-sas-6.601.56.00-1vmw.500.0.0.472560.x86_64.vib

LSI_bootbank_lsiprovider_500.04.V0.39-0006.vib

/vmfs/volumes # df -h

Filesystem   Size   Used Available Use% Mounted on

VMFS-5     893.0G 703.9G    189.1G  79% /vmfs/volumes/XXX1

VMFS-5       5.4T   1.4T      4.1T  25% /vmfs/volumes/XXX2

vfat         4.0G  17.9M      4.0G   0% /vmfs/volumes/XXX3

vfat       249.7M 166.6M     83.1M  67% /vmfs/volumes/XXX4

vfat       249.7M 166.6M     83.1M  67% /vmfs/volumes/XXX5

vfat       285.8M 191.3M     94.6M  67% /vmfs/volumes/XXX6

Tags (3)
Reply
0 Kudos
4 Replies
admin
Immortal
Immortal

Hi,

your root directory is filled up and its not able to update the log entries the /var/run/vmware/tickets/vmtck-XXXXXXXXX could not be written is actually a HP log.

run the df-h at the root.

cd /

df -h

It would show up with the location that is completely filled up or may be move the logs or files that are filled to a different location like a datastore and your Host should be back fine.  or you could reboot the host and It would clear out all the Ram disk


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203307...


Regards,

Avinash

Reply
0 Kudos
AlexZZ
Contributor
Contributor

SNMP disabled and not used.

~ # vdf -h

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M       32M        0B 100% --

etc                        28M      168K       27M   0% --

tmp                       192M        4K      191M   0% --

hostdstats                803M        6M      796M   0% --

How can it be resolved?

Reply
0 Kudos
admin
Immortal
Immortal

can you cd into the root folder and see what are the files available..?

AlexZZ
Contributor
Contributor

I'll remove some files (log files from root - MegaSAS.log) and problem resolved. Smiley Happy

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M      852K       31M   2% --

etc                        28M      168K       27M   0% --

tmp                       192M        4K      191M   0% --

hostdstats                803M        6M      796M   0% --

And stiil one problem resolved -  console access to VMs "unable to connect to the MKS internal error"