• Just installed WF plugin on an old-fashioned GoDaddy-hosted website on Linux. When I use “Scan”, it runs for a 2-3 minutes but then just spins out and dies. Each time I get the same error message:

    [MAR 13 14:16:09] Error finishing writing value for wfsd_engine (MySQLi error: [1] Can’t create/write to file ‘/var/lib/mysql_logs/3/mysqlbintemp/ML6b4dSG’ (Errcode: 2))

    I can’t find any reference in the documentation on this problem. I turned on Debug but that just shows the same error message.

    What am I missing?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @dccharron

    Looks like you need to check free space on your server and also check server error logs, feel free to ‘tail’ them when you running the Scan task and paste a result here.

    Thread Starter dccharron

    (@dccharron)

    Many thanks for the interest. Still no go. Scan dies with same message as before. I have no control over “free space” on a shared GoDaddy server so don’t think I’ll be able to overcome that. As for the error logs, GoDaddy have some weird setup which I’m trying to work through now but I suspect I’ll have to make a call to get anywhere with it. The Access Logs are available for each day but the Error Logs seem to be completely empty at the moment.

    Aside: I’ve found my hacker by looking at my Access Logs. They were using an IP address from a registrar that I have seen many times over the past few years: a ‘legitimate’ organisation called RIPE in Amsterdam. RIPE must offer a proxy server or VPN service that has become the preferred gateway for hackers. No way to trace the hacker any further back. I’m trying to find the point of intrusion of the malware files but haven’t found it yet. Have spent my day changing passwords. Ho hum.

    Thread Starter dccharron

    (@dccharron)

    I’m stuck. I can’t complete a Scan. It starts normally and then runs normally for a few seconds. But when it reaches Server State level, it runs for a few seconds and then generates:
    [Mar 19 11:16:11] Calling fork() from wordfenceHash with maxExecTime: 15
    [Mar 19 11:16:11] Entered fork()
    [Mar 19 11:16:11] Error finishing writing value for wfsd_engine (MySQLi error: [1] Can’t create/write to file ‘/var/lib/mysql_logs/3/mysqlbintemp/MLjOavJP’ (Errcode: 2))
    My account is an older GoDaddy account (running PHP 5.6 – yes I know this is ancient but GoDaddy are very slow to update PHP for their loyal customers as they are hoping they will die and go away or buy one of their really expensive managed WP accounts). My site is running on Linux using Apache.

    I don’t have access to configure Apache.

    I’ve deactivated all other plugins and tried again but same error at same place.

    I don’t have access to “tmp” files. I can only view “errorlogs” and “accesslogs” but the few error messages I can see are very cryptic and don’t seem to relate to wordfence at all.

    @kalashnikovevg suggested I get more “free space” but I have no idea how to do that. I assume it is an Apache configuration option and I can’t access that.

    Any new help would be great.

    Hi @dccharron
    Please go to (Wordfence > Tools => Diagnostics) and click on “Send Report by Email” button at the top of the page, you can send the report to “alaa [at] wordfence [dot] com”, make sure to include your forum username, I will take a look at this report and let you know my findings.

    Thanks.

    Thread Starter dccharron

    (@dccharron)

    Many thanks. It’s on its way.

    Hi @dccharron,
    This sepecifc MySQL error “mysql can’t create/write to file (errcode 2)” is related to hard drive issues (running out of space) or misconfigured MySQL permissions, check this similar thread here along with this one too, in either cases I recommend reporting this issue to your hosting provider, since the proper solution will be done from the server side.

    Thanks.

    Thread Starter dccharron

    (@dccharron)

    Thanks @wfalaa

    Seems unlikely that GoDaddy would run a server with misconfigured MySQL permissions or a limited space in /tmp but I’ll contact them to see what they say.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Scan doesn’t finish – can’t write to file’ is closed to new replies.