• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Very large sps-runtime.log.stderr log file

Duncan Epping · Jul 6, 2021 ·

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.

Related

Server vcenter server, vcsa

Reader Interactions

Comments

  1. Chris says

    6 July, 2021 at 19:19

    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.

    • Duncan Epping says

      7 July, 2021 at 09:14

      Thanks for that pointer, I hadn’t seen the log entries of this customer, but it could indeed be the same issue!

    • Petr says

      20 July, 2021 at 14:57

      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

  2. anonymous german says

    20 August, 2021 at 16:22

    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

    • anonymous german says

      20 August, 2021 at 16:24

      sorry, here the Menu-Path: “Your vCenter” – “Configure” – “Storage Providers”

      • Duncan Epping says

        24 August, 2021 at 13:31

        thanks

  3. Matt Heldstab says

    3 September, 2021 at 20:41

    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.

Primary Sidebar

About the author

Duncan Epping is a Chief Technologist in the Office of CTO of the Cloud Platform BU at VMware. He is a VCDX (# 007), the author of the "vSAN Deep Dive", the “vSphere Clustering Technical Deep Dive” series, and the host of the "Unexplored Territory" podcast.

Upcoming Events

May 24th – VMUG Poland
Aug 21st – VMware Explore
Sept – VMUG Slovenia (virtual)
Oct – VMUG Sweden
Nov 6th – VMware Explore
Nov 23rd – UK VMUG
Dec 7th – Swiss German VMUG

Recommended Reads

Sponsors

Want to support Yellow-Bricks? Buy an advert!

Advertisements

Copyright Yellow-Bricks.com © 2023 · Log in