thirstyjon

Well.

So much for that.

The scans are failing again.

I’m pretty sure they are being cut short by Dreamhost’s procwatch daemon.

https://help.dreamhost.com/hc/en-us/articles/216540488-Why-did-procwatch-kill-processes-on-my-Shared-server-

Do you know of anyone who is successfully running Wordfence on a Dreamhost shared hosting site? (I’m not talking about their premium Dreampress hosting).

I think I solved this problem.

I did two major things. I am not sure which of the two fixed this problem, but here is what they are.

1) I talked to Dreamhost support and ended up moving the 3 sites that I have hosted on one account to three different ftp/php users within that account instead of all being on one. They told me that this would allow me to use the maximum resources available to my shared hosting account, whereas all three on one user could only use half.

2) BEFORE I switched two of the sites to new “users” I completely deleted wordfence and all of it’s database tables, etc. I deleted the created .user.ini file. I completely obliterated wordfence. Then I did completely fresh installs of wordfence AFTER moving to the new users.

Now the scan is working without apparent problem on all three sites, including the one I started this thread for: worldwideawakening.org

I am going to run at least 1 scan a day for a few days.

If the scans keep working without problem I will come back and mark this thread resolved.

• This reply was modified 7 years ago by thirstyjon. Reason: typo

Disabling scanning for backdoors, etc. ended here:

[Nov 19 14:16:48:1511119008.370639:4:info] Scan process ended after forking.

After a bit of time I also saw this error message in red:

Scan Failed

The current scan looks like it has failed. Its last status update was 5 mins ago. You may continue to wait in case it resumes or cancel and restart the scan. Some sites may need adjustments to run scans reliably. Click here for steps you can try.

• This reply was modified 7 years ago by thirstyjon.

Thanks wyfann. I am trying those two things now.

You did notice my previous post where I said this, right?:

I switched it back to 15 and the activity log ended with this:

[Nov 16 16:07:55] Scan process ended after forking.

chongop1, what is with the spam?

Resolved.

Resolved.

Thanks for updating this.

This is a great plugin.

Now I can use it without my security plugin always warning me that there is an abandoned plugin on my site.

??

You didn’t forget me, did you?

I seem to have stopped getting blitzed today.

And I see that the plugin page now has the option to subscribe again.

Did you fix this? Did it fix itself? If you did, thanks.

How can I avoid this in the future? Must I decline to ever subscribe to plugins?

I am afraid to use the forum now. ??

I switched it back to 15 and the activity log ended with this:

[Nov 16 16:07:55] Scan process ended after forking.

Scan appears to have failed.

This is all I see in the activity log:

[Nov 16 16:04:47] Ajax request received to start scan.
[Nov 16 16:04:47] Entering start scan routine
[Nov 16 16:04:47] Got value from wf config maxExecutionTime: 10
[Nov 16 16:04:47] getMaxExecutionTime() returning config value: 10
[Nov 16 16:05:50] Scan kill request received.

Then it appears that the scan is doing nothing.

Howdy wyfann.

I don’t recall any specific errors other than the notice that it seemed to have not completed.

I adjusted the max execution time according to the help docs, but they never suggested LOWERING that time. They suggested INCREASING it.

I’ll try it right now with 10.

Howdy Samuel!

I just got back home and forwarded two to you.

I saved them as .eml files and attached copies as well because it was the only way I could be reasonably sure you would get the headers.

Thanks for jumping in to help me before I pull all of my hair out. ??

Let me know if you got these (or didn’t) and what the answer to this mystery is.

Thanks,

Jon
ThirstyJon on www.remarpro.com

Every email from that plugin to which I CANNOT unsubscribe has this at the bottom:

You are receiving this email because you are subscribed to a plugin.

Login and visit the topic to unsubscribe from these emails.

This is getting more maddening by the day.