rmdir messages in debug log

@sbelding – does it say what line in wp-cache-phase2.php that warning happens on?

You’re getting 404 errors in wp-admin? Do they happen in the WP Super Cache settings pages? The plugin shouldn’t do any caching in wp-admin.

Hi Donncha:

There are actually two errors that occur in succession (been going on for a long time, according to the debug file), They are:

rmdir():Directory not empty in…/wp-super-cache/wp-cache-phase2.php on line 987

unlink():No such file or directory in…/wp-super-cache/wp-cache.php on line 3556

A third error that frequently pops up is: gzuncompress(): data error in…/wp-super-cache/wp-cache-phase2.php on line 367

I’m not sure how they relate to the weird and annoying backend thing, unless they are both symptoms of something else. I was thinking it might be memory, but I’ve upgraded a number of months ago and it had no impact.

They’re nothing to worry about:

1. the rmdir() error happens because your server has created a cached file in a directory that the plugin had just cleared out and was about to delete. rmdir() won’t delete a directory if there are any files in it.
2. That unlink() removes a temporary file that was removed earlier in the function. I presume you saw it during preloading?
3. This error happens when a page is not compressed, when it should have been, and is supposed to be served uncompressed. It’s harmless as it’s checked afterwards.

The odd thing is, all these warnings aren’t supposed to show because I’ve used “@” to suppress the warning messages. Are you using a custom error handler to log the errors on your site?

Thanks Donncha. Nope I’m not using anything special that I’m aware of for debugging.

It’s still odd, though, that these errors are coinciding with the backend 404s…

Some plugin you have installed may be doing the logging. Look for the command “set_error_handler”, and the function name that’s passed as a parameter to it may have an error_log command that logs errors.

Maybe that plugin causes the 404 errors when it detects the warnings you noticed.

You could also disable plugins one by one and try and replicate what causes the 404 and logging of warnings to see if they happen.

Hello @sbelding

It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!