• Resolved ronmeyn

    (@ronmeyn)


    Whilst I have stated the version of WP is 4.7, I really cannot tell which version it is. I could not find a suitable entry in the Mysql tables that may give me an indication of version & my wp-admin URL appears to be down with the same issue as the base URL.

    a few days ago the /wp-admin URL stopped working and now the site itself is down.

    I believe that the Error_log reveals that wp-load.php is called twice somehow, and the error comes up as the first function is attempted to be redeclared?

    To verify this, I altered the name of the function, and the error log would report the same error with the newly named function. So this proves to me that somehow the wp-load.php file is being attempted twice.

    PHP Fatal error: Cannot redeclare login_header() (previously declared in /home/mymy2116/public_html/wp-load.php:30) in /home/mymy2116/public_html/wp-load.php on line 30

    the website has been working for a few years being hosted in Australia in a netregistry space, but my client recently reported ho could not log on.

    The thing that throws me is that I cannot get into Admin to try anything. It also seems to me that the error_log file in the wp-admin folder and the base Url folder seem to be linked? I “think” that from either URL I cam getting the error logged.

    I have also tried renaming the plugins sub-folder (under the wp-content folder) to no avail.

    Website base URL is https://mybootid.com.au

    please help ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • Did you try renaming the themes folder too?

    Thread Starter ronmeyn

    (@ronmeyn)

    Thanks shariqkhan2012, Just gave that a crack to no avail.

    So I’ve changed both back.

    I have also since worked out that the Error_Log files are in fact unique in each folder, but reporting the Exact same error message when I attempt the relevant URL.

    • This reply was modified 7 years, 11 months ago by ronmeyn.
    Thread Starter ronmeyn

    (@ronmeyn)

    Not sure if this is also part of the bigger issue, but there are log entries from around 24 hours ago that refer to “out of Memory” issues.

    My client first reported issues before 9th March, but the initial problem could have occurred on 7th Feb to render the wp-admin URL unusable, and the memory issues on 9th March could have impacted the website itself?

    See Log Entries below……

    [07-Feb-2017 16:58:44 UTC] PHP Warning: array_unshift() expects parameter 1 to be array, null given in /home/mymy2116/public_html/wp-includes/class-wp-xmlrpc-server.php on line 580
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 20971520) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-includes/media.php on line 2318
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 23855104) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/akismet/class.akismet.php on line 505
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 20971520) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-includes/media.php on line 2318
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 39321600) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/modules/theme-tools/infinite-scroll.php on line 31
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 29884416) (tried to allocate 7680 bytes) in /home/mymy2116/public_html/wp-includes/widgets/class-wp-widget-recent-comments.php on line 170
    [09-Mar-2017 13:39:10 UTC] PHP Fatal error: Out of memory (allocated 27525120) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/class.media-summary.php on line 90
    [09-Mar-2017 13:39:11 UTC] PHP Fatal error: Out of memory (allocated 23855104) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/akismet/class.akismet.php on line 505
    [09-Mar-2017 13:39:11 UTC] PHP Fatal error: Out of memory (allocated 27787264) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/class.photon.php on line 260
    [09-Mar-2017 13:39:11 UTC] PHP Fatal error: Out of memory (allocated 27262976) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/class.jetpack-post-images.php on line 363
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 41418752) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/modules/sharedaddy/sharing-service.php on line 709
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 29622272) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-includes/widgets/class-wp-widget-archives.php on line 157
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 25165824) (tried to allocate 7680 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/class.jetpack.php on line 3875
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 23592960) (tried to allocate 122880 bytes) in /home/mymy2116/public_html/wp-includes/vars.php on line 87
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 39845888) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/modules/custom-post-types/nova.php on line 244
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 40632320) (tried to allocate 71 bytes) in /home/mymy2116/public_html/wp-includes/post.php on line 1305
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 40632320) (tried to allocate 32 bytes) in /home/mymy2116/public_html/wp-includes/post.php on line 1305
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 24379392) (tried to allocate 30720 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/class.jetpack.php on line 813
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 41943040) (tried to allocate 7680 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/modules/sharedaddy/sharing-sources.php on line 1628
    [06-Apr-2017 10:09:31 UTC] PHP Fatal error: Out of memory (allocated 40108032) (tried to allocate 7680 bytes) in /home/mymy2116/public_html/wp-content/plugins/jetpack/modules/custom-post-types/nova.php on line 1147
    [08-Apr-2017 18:49:08 Australia/Melbourne] PHP Deprecated: Automatically populating $HTTP_RAW_POST_DATA is deprecated and will be removed in a future version. To avoid this warning set ‘always_populate_raw_post_data’ to ‘-1’ in php.ini and use the php://input stream instead. in Unknown on line 0

    Is there a probablity that the client tried changing the login url by the use of some plugins?
    Try having a look at the .htaccess file.
    Probably, there would be a line which rewrites the admin url.

    There HAS to be some hint there.

    Thread Starter ronmeyn

    (@ronmeyn)

    My understanding of this is pretty scratchy, but I think this is “vanilla”. This is what it currently looks like…

    Am I right in saying that the “RewriteBase /” command is always forcing to the public_html folder?

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    [Moderator note: code fixed. Please wrap code in the backtick character or use the code button.]

    • This reply was modified 7 years, 11 months ago by ronmeyn.
    • This reply was modified 7 years, 11 months ago by bdbrown.

    I too dont have much knowledge about .htaccess, but what you posted looks fine. No funny business going on there.

    So, we have ruled out a faulty plugin (by renaming the plugin folder)
    And similarly any faulty theme.
    And the htaccess too.

    That’s not good.

    Quick question: Did you rename the entire themes directory or just the theme which you were using?
    Try both the approaches.

    And could you try setting WP_DEBUG to true in w-config.php?

    change the wp-config.php file. Where it says define( 'WP_DEBUG', false ); change that to define( 'WP_DEBUG', true );

    Thread Starter ronmeyn

    (@ronmeyn)

    We’ve just been told by the hosting organisation that they reckon the site has been compromised.

    I’ve placed the burden on them for now as I had subscribed to paying for a security service directly with them, which has failed to protect my site, AND failed to make us aware of the problems.

    With any luck, I’ll have a backup copy of the site running shortly.

    I thank you for your interest and attention to my problem.

    That’s bad.
    I hope the damage is not extensive and that the site is back at the earliest.
    Have a good day!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘site and wp-admin no longer work, log entry “Cannot redeclare login_header()”’ is closed to new replies.