On VMTN someone hit a situation where the sps-runtime.log.stderr log file grew extremely large on their vCenter Server Appliance (7.0 in this case). I have seen this before, and sizes over 10GB are not uncommon. The sps-runtime.log.stderr file belongs to the service that provides the Policy-Based Storage capabilities. You can of course stop the service and then delete the files, and restart the service again. However, you could also empty the file by simply doing the following on the command-line:
cat /dev/null > /storage/log/vmware/vmware-sps/sps-runtime.log.stderr
This results in a 0kb file immediately.
I ran into this issue recently. Logs were full of complaints about cert issues from hosts that didn’t exist anymore. Storage providers for hosts all showed offline. Had to go through storage MOB and unregister all the providers. Restarting vmware-sps then re-registered the attached hosts and everything was online and working as expected.
Thanks for that pointer, I hadn’t seen the log entries of this customer, but it could indeed be the same issue!
Hi Chris, could you write it down a bit and describe exactly what needs to be done? I have the same problem after upgrading from vCentrum 6.5 to 7.0u2
You can check for that in the vCenter GUI under:
The following KB describes how to fix it: https://kb.vmware.com/s/article/76633
sorry, here the Menu-Path: “Your vCenter” – “Configure” – “Storage Providers”
thanks
Thanks, Duncan. We ran into this issue on one of our vCenters as well. It was after migrating from one storage platform to another. GSS told us that it wasn’t anything we did, but it is something they see every once-in-a-while. It sounds like VMware has an internal script and process to fix the problem and the un-registration of the old storage providers was completed in short order.