VMware Cloud Community
sibsbt
Enthusiast
Enthusiast

shell.set unknown command

Hi,

I have a problem after rebooting  i am getting shell.set unknown command  error

How to fix it

pastedImage_0.png

Thanks

8 Replies
virtualg_uk
Leadership
Leadership

Hi Sibsbt,

This may be due to a non-clean shutdown of the VCSA.

Please see this post for details: fsck of vCenter Server Appliance 6.0 partitions - CormacHogan.com


Graham | User Moderator | https://virtualg.uk
RajeevVCP4
Expert
Expert

Do not reboot

Do the clean shut down then power on , issue will resolve

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
sibsbt
Enthusiast
Enthusiast

Hi,

Yes it was a clean shutdown  BY pressing  F12 in the console

I tried couple of times  , it worked once 

again gone to the same situation

Thanks

Reply
0 Kudos
sibsbt
Enthusiast
Enthusiast

Hi,

I think the below link is for  "boot failure " ?

Please correct me if i am wrong

Thanks

Reply
0 Kudos
sibsbt
Enthusiast
Enthusiast

Hi,

If in case it does not work , I have a clone of  vcenter . Can I use this machine ?

After this clone taken I have created vm's in the dc ,Does it matter ?

Thanks

Reply
0 Kudos
virtualg_uk
Leadership
Leadership

When you boot the VCSA, see if you spot any FAILED red errors on the right in relation to "file system not accessible", if you do (and even if the VCSA loads up, you may still have this issue in the blog post I mentioned)


Graham | User Moderator | https://virtualg.uk
IRIX201110141
Champion
Champion

This happens when the / Filesystems reached 100%. The existing services may running but spawning new processes or creating files are not working any more. A reboot cant fix this problem because the linux try to create new files or append to the existing logs... but with no space left on the device you cant bypass the vmware shell wapper.

You can boot into the SUSE linux by following this VMware Knowledge Base

Try a "df -h" and you see maybe /var/log with 5.xGB. Free up some space be deleting  rm -rf *.bz2 files.

Enter into this dir and type in "du -sh *"

Free up some space be deleting  rm -rf *.bz2 files

Than check for the big one... most likly its audit/audit.log. YOu can override it by "> audit.log" and reboot the VCSA.

For the non US keyboard user which have problems with a "du -sh * | more" try   "du -sh * > asa" and than less asa or vi asa and scroll within the listing.

Regards,

Joerg

BaijuParambil
Contributor
Contributor

Appliance Shell commands depends on applmgmt service in VCSA.. In this situation, looks like applmgmt service is not starting during server boot which results in error "error connecting to the server". Changing default shell for root will help if login works atleast once. You can change the default shell for root to /bin/bash using command "chsh -s /bin/bash root" or change it in /etc/passwd file by booting in single user mode (modify "root:x:0:0:root:/root:/bin/appliancesh" to "root:x:0:0:root:/root:/bin/bash")

Thanks