Scan still hanging on a litespeed server

I have had no joy with getting a scan to complete on a LiteSpeed server either. The first few times it was doing about four things at once (core, themes, plugins, malware) but not saying anything about progress with files in the details. By telling it not to do themes or plugins and various reducing the execution time to 15 seconds and playing with both increasing and decreasing memory size I got it to tell me it was scanning files and eventually it built up to 1400 files but that is it. There are no errors to be seen anywhere that I have access to, it just seems to stop making any progress.

More info:

I am running with the medium security setting.

My shared hosting is configured for a maximum execution time of 30 seconds and 128 Mb of memory. Running the memory test says 90 Mb was requested and it was able to get 82.5 Mb which it seemed quite happy about.

If I leave the execution time blank at the default the logs report:

getMaxExecutionTime() returning half ini value: 15
Got max_execution_time value from ini: 30

The scan then runs for 15 seconds and stops showing anything else happening.

If I set the execution time to 29 seconds then I get:

getMaxExecutionTime() returning config value: 29
Got value from wf config maxExecutionTime: 29

The scan then runs for 29 seconds and stops showing anything else.

It doesn’t seem to make a significant amount of difference whether I reduce the memory option to 75 Mb or double it to 512 Mb (I wouldn’t expect the latter to make a difference as presumably the internal limits are detected). 75 Mb actually words a tad better than 82.5 Mb but neither work as well as leaving the default alone.

Turning off ‘Scan for signatures of known malicious files’ allows the scan to process more files but it just means it is doing more in the time it has available.

To me it seems like something is going wrong when a new process is being forked but whatever that something is doesn’t show in the activity log. For all I know, it being a shared server, the scan could be chugging along quite happily but not updating the activity log so I don’t know about it.

Sorry, I didn’t intend to hijack the thread by the way, I just inadvertently breached etiquette and then it seemed less damaging to widen the breach with some hopefully useful information.

G.

I have had no joy with getting a scan to complete on a LiteSpeed server either. I have loaded v5.0.7.

The first few times it was doing about four things at once (core, themes, plugins, malware) but not saying anything about progress with files in the details.

Scan Summary:
Scan hangs here, with these four just spinning.
Comparing core WordPress files against originals in repository
Comparing open source themes against www.ads-software.com originals
Comparing plugins against www.ads-software.com originals
Scanning for known malware files

Scan Detailed Activity
Scan hangs here,
[May 16 05:20:32] Analyzed 200 files containing 2.07 MB of data so far

There are no errors to be seen anywhere that I have access to, it just seems to stop making any progress.

We all appear to be having the same problem. At least we know we are not alone.

Interestingly increasing the update time in the options tab increases the number of files scanned reported before the hang.

Update time – Default
[May 17 12:10:08] Analyzed 900 files containing 10.67 MB of data so far

Update time – 16
[May 17 12:11:24] Analyzed 1400 files containing 16.52 MB of data so far

It just occurred to me:
Are you guys hosting in the UK? Maybe we are with the same company.

I suspect we aren’t but my installation is on EZPZhosting, who are CPanel based using LiteSpeed, and I’m in the Kent data centre.

G.

Duplicate post …

Yep, I’m with EZPZ as well.

Hi all,

We successfully run Wordfence on a LiteSpeed server in our lab.

There’s a debug option at the bottom of Wordfence options which you can enable to see where it stops.

Check your litespeed error log if you have access to that to find out if the process is being killed or there’s some other issue.

Post what you find and I”ll try to help.

Regards,

Mark.

Hello.

I am both a new to WP and to Wordfence. I have a scan that had been running for 3 hours. I killed it and started again, this time scanning plugins and themes.

Firstly, is it normal to take this long?

Secondly, how do I check what platform I am on – Lightspeed or something else?

Thanks!

John

Mark,

I’ve been using the debug options. After the initial setup all it shows is a list of files being scanned and that list just stops updating. The scan starts at e.g. May 21 11:49:12 and stops updating at May 21 11:49:41. That’s 29 seconds which is the process execution limit I have set. Had I left it to default it would stop after 15 seconds.

The scan summary shows the ‘in progress’ indicators as if something is happening but I don’t know what controls the display of those.

I only have access to the CPanel error log and that shows absolutely nothing of interest. I don’t know if there are other logs I wouldn’t get to see.

G.

Hi @nosnurg

Please use the link below the second yellow box to view your activity log.

If you have debug enabled you should see something like “Entered fork”. It will look like:

[May 21 14:52:01:1400683921.417540:4:info] Entered fork()

Post the lines above and below that. Around 20 lines above and below will do. I want to see if Wordfence is able to fork correctly.

Regards,

Mark.

I don’t have anything saying ‘entered fork’. The closest I have is ‘Scan process ended after forking’ (see https://pastebin.com/9jG9jEqy ).

Graham

I had this problem. it was fixed by my host. Here are the instructions they gave me. If it works for you give credit to Stablehost. Stablehost is fantastic in every way..

Compliments of https://www.Stablehost.com
———————————–
It is a combination of 3 things.

1) Modify the .htaccess of that specific site and make it have this rule –

How do I disable the connection timeout?

The connection timeout is meant to stay on, however if you need to turn it off temporary, you can do so by creating an .htaccess in your public_html folder and placing this line on the very top of it:

<IfModule litespeed>
RewriteRule .* – [E=noabort:1]
</IfModule>

2 Go to your cPanel -> Software -> PHP Settings -> Switch to PHP settings -> change both execution times to -1 , then hit save.

3) Remove unused themes to avoid timeouts.

Hope it works for you..