Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Trying to manually run an upgrade from ESXi 5.0 to ESXi 5.1. My image bundle is stored on the first datastore /vmfs/volumes/datastore1/ESXi-5.1.0-799733-standard, I am running the command esxcli software profile update -d /vmfs/volumes/datastore1/ -p ESXi-5.1.0-799733-standard.

The system responds with Got no data from process /usr/lib/vmware/esxcli-software profile.update

I have read some similar posts, but nothing that seems to be in the same boat as me.

share|improve this question
up vote 1 down vote accepted

Found the solution. This is caused by the ESXi host not having a static scratch storage. Even though the system creates a temporary self storage, it leaves a strange descriptor in place for the log file: /dev/log, and of course the python scripts fail to write to /dev/log causing all esxcli commands to fail with "Got no data".

Adding a static scratch fix my problem.

ESXi 5.1 is faaast.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.