• Resolved WIBeditor

    (@wibeditor)


    Not sure what caused this, exactly, but it seemed worth posting here. All was working fine with my self-hosted CDN setup until today, when my webhost contacted me about a bandwidth issue. Their tech spotted several idle FTP connections from localhost. I was stumped at first, but on closer inspection, the runaway server processes traced back to the self-hosted CDN setup within W3 Total Cache:

    lstat64(“/home/XYDOMAIN/public_html/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn/cdn [ETC ETC FOREVER] “, {st_mode=S_IFDIR|0755, st_size=2048, …}) = 0

    Ever seen this before? Ideas?

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: W3 Total Cache] rogue FTP process with self-hosted CDN’ is closed to new replies.