asked on

Cannot access vCenter anymore after disk space issue

Hi,
I am using vCenter ESXi 6.0.
Since I ran out of space on VCSA due to very big audit.log file, I followed this URL:
https://kb.vmware.com/s/article/2149278

I changed root password, and rebooted vCenter Appliance.
I am unable to access through vcsa.
In web interface, I get error:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7f9ab7e2ac40] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)

Even with vSphere client (the server could not interpret client's request)

How can I solve this?
Thank you

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Did you expand the disks ?

Armitage318

ASKER

not yet, but I do have free space now:

vcsa:~ # df -h
Filesystem                            Size  Used Avail Use% Mounted on
/dev/sda3                              19G  8.5G  9.2G  48% /
udev                                  7.9G  164K  7.9G   1% /dev
tmpfs                                 7.9G   40K  7.9G   1% /dev/shm
/dev/sda1                             128M   38M   84M  31% /boot
/dev/mapper/core_vg-core               50G 1022M   46G   3% /storage/core
/dev/mapper/log_vg-log                 20G   11G  7.8G  59% /storage/log
/dev/mapper/db_vg-db                  9.9G  326M  9.1G   4% /storage/db
/dev/mapper/dblog_vg-dblog            5.0G  203M  4.5G   5% /storage/dblog
/dev/mapper/seat_vg-seat               25G  900M   23G   4% /storage/seat
/dev/mapper/netdump_vg-netdump       1001M   18M  932M   2% /storage/netdump
/dev/mapper/autodeploy_vg-autodeploy  9.9G  151M  9.2G   2% /storage/autodeploy
/dev/mapper/invsvc_vg-invsvc          9.9G  643M  8.8G   7% /storage/invsvc

Open in new window

Armitage318

ASKER

anyway, I just removed an 8 GB audit.log file.
I noticed something strange.
I used vSphere to access the host on which vcsa is running, it shows me a 200 GB hard disk.
I don't see such space in df -h output..
vcsa.png

Armitage318

ASKER

Hi, solved.
I noticed these errors in /var/log/vmware/vmdird/vmdird-syslog.log

2019-01-17T14:51:08.061900+00:00 err vmdird  t@139899088922368: SASLSessionStep: sasl error (-13)(SASL(-13): authentication failure: client evidence does not match what we cal
culated. Probably a password error)
2019-01-17T14:51:08.061923+00:00 err vmdird  t@139899088922368: VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL step failed.)), (0) socket ([3] 127.0.0.1:3
89<-127.0.0.1:55244)
2019-01-17T14:51:08.061930+00:00 err vmdird  t@139899088922368: Bind Request Failed ([3] 127.0.0.1:389<-127.0.0.1:55244) error 49: Protocol version: 3, Bind DN: "cn=vcsa.company
.it,ou=Domain Controllers,dc=vsphere,dc=company", Method: SASL
2019-01-17T14:51:08.073215+00:00 err vmdird  t@139899088922368: SASLSessionStep: sasl error (-13)(SASL(-13): authentication failure: client evidence does not match what we cal
culated. Probably a password error)
2019-01-17T14:51:08.073544+00:00 err vmdird  t@139899088922368: VmDirSendLdapResult: Request (Bind), Error (49), Message ((49)(SASL step failed.)), (0) socket ([3] 192.168.250
.11:389<-192.168.250.11:45313)

Open in new window

so I used /usr/lib/vmware-vmdir/bin/vdcadmintool and reset credentials (option 3).
After vcsa reboot, all went fine.

ASKER CERTIFIED SOLUTION

Armitage318

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial