This documentation is only valid for older versions of Wordfence. If you are using Wordfence 7 or later, please visit our new documentation.

My scan is stuck. What does fseek() function.fseek: stream does not support seeking mean?

From Wordfence Documentation
Jump to: navigation, search

If you get this error when trying to do a scan:

Dec 10 20:10:23] fseek() [function.fseek]: stream does not support seeking (2) File: /home/xxxxxxx/public_html/wp-content/plugins/wordfence/lib/wfUtils.php Line: 502
Remember the paths and dates in you errors could be different

What this means is the scan stopped because it hit a file it was having trouble scanning, like a symbolic link.

The way to fix this is to enable debugging mode for your wordfence scans. Look for it on the Wordfence Tools page on the Diagnostics tab, near the bottom. Since this increases database load, we recommend you do this off peak hours. Start a new scan. When your scan completes, you want to view the activity log and look for where the scan hangs up.

Also note that the activity log shows you entries in reverse chronological order, so the latest entries are on top (see below)

[Dec 11 23:10:46:1418339446.057756:2:info] Checking 30 URLs from 13 sources.
[Dec 11 23:10:46:1418339446.053623:2:info] Done host key check.
[Dec 11 23:10:45:1418339445.576363:2:info] Checking 496 host keys against Wordfence scanning servers.
[Dec 11 23:10:45:1418339445.571489:2:info] Asking Wordfence to check URL's against malware list.
[Dec 11 23:10:45:1418339445.571060:2:info] Scanned contents of 1199 additional files at 84.89 per second
[Dec 11 23:10:45:1418339445.563845:4:info] Scanning contents: wp-content/wfcache/leadershipforum.scrippsnetworks.com_/~~~~_wfcache.html_gzip (Size:10565B Mem:32.0M)
[Dec 11 23:10:45:1418339445.510521:4:info] Scanning contents: wp-content/wfcache/leadershipforum.scrippsnetworks.com_/~~~~_wfcache.html (Size:72147B Mem:31.8M)
[Dec 11 23:10:45:1418339445.509550:4:info] Scanning contents: wp-content/wfcache/clear.lock (Size:0B Mem:31.8M)
[Dec 11 23:10:45:1418339445.176027:2:info] Scanned contents of 1196 additional files at 87.12 per second
[Dec 11 23:10:44:1418339444.279646:4:info] Scanning contents: wp-content/uploads/2012/09/ (Size:2.67M Mem:32.0M)
[Dec 11 23:10:44:1418339444.164650:4:info] Scanning contents: wp-content/uploads/.htaccess (Size:112B Mem:32.0M)
[Dec 11 23:10:44:1418339444.155998:4:info] Scanning contents: wp-content/themes/twentythirteen/fonts/genericons.css (Size:22487B Mem:32.0M)
[Dec 11 23:10:44:1418339444.150750:4:info] Scanning contents: wp-content/themes/twentythirteen/fonts/genericons-regular-webfont.woff (Size:12156B Mem:32.0M)
[Dec 11 23:10:44:1418339444.143610:4:info] Scanning contents: wp-content/themes/twentythirteen/fonts/genericons-regular-webfont.ttf (Size:19864B Mem:32.0M)
[Dec 11 23:10:44:1418339444.128041:4:info] Scanning contents: wp-content/themes/twentythirteen/fonts/genericons-regular-webfont.svg (Size:27517B Mem:32.0M)

You'll likely notice a file it hangs on and this is what we'll need to know when you open a ticket in the premium ticket system or the free forums.

Make sure and turn off debugging mode after capturing the information.

(More on the debugging option can be found HERE)