Learn about Centmin Mod LEMP Stack today
Register Now

Wordpress unable to complete Wordpress install

Discussion in 'Blogs & CMS usage' started by EckyBrazzz, Nov 30, 2020.

  1. EckyBrazzz

    EckyBrazzz Active Member

    917
    190
    43
    Mar 28, 2018
    >>>>Click here<<<< i'm nearby......
    Ratings:
    +363
    Local Time:
    8:05 PM
    Latest
    Latest
    Code:
    configure autoptimize-gzip https://community.centminmod.com/threads/15314/
    2020-11-29 21:16:50 URL:https://raw.githubusercontent.com/centminmod/autoptimize-gzip/master/autoptimize-gzip.php [573/573] -> "/home/nginx/domains/domain.com.br/public/wp-content/plugins/autoptimize-gzip/autoptimize-gzip.php" [1]
    2020-11-29 21:16:50 URL:https://raw.githubusercontent.com/centminmod/autoptimize-gzip/master/index.html [192/192] -> "/home/nginx/domains/domain.com.br/public/wp-content/plugins/autoptimize-gzip/index.html" [1]
    2020-11-29 21:16:51 URL:https://github.com/centminmod/autoptimize-gzip/blob/master/readme.md [115043] -> "/home/nginx/domains/domain.com.br/public/wp-content/plugins/autoptimize-gzip/readme.md" [1]
    2020-11-29 21:16:51 URL:https://raw.githubusercontent.com/centminmod/autoptimize-gzip/master/LICENSE [18026/18026] -> "/home/nginx/domains/domain.com.br/public/wp-content/plugins/autoptimize-gzip/LICENSE" [1]
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    ------------------------------------------------------------
    ------------------------------------------------------------
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    ------------------------------------------------------------
    ------------------------------------------------------------
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    ------------------------------------------------------------
    ------------------------------------------------------------
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    ------------------------------------------------------------
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    ------------------------------------------------------------


     
  2. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    9:05 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Need more of the wordpress install log as it's possible Wordpress itself failed to download/install and that excerpt doesn't show enough.

    To troubleshoot centmin.sh menu option 22 wordpress installation, you need to check the centmin.sh menu option 22 log located in /root/centminlogs at /root/centminlogs/centminmod_*_wordpress_addvhost.log based log where * is the centminmod version and date timestamp. Edit and mask any actual ftp username/password or wordpress usernames and logins before posting the log contents to Pastebin.com or Gists to share a sanitised version of the contents of the log.

    Example list /root/centminlogs files in date ascending order and grep for wordpress_addvhost.log
    Code (Text):
    ls -lahrt /root/centminlogs | grep wordpress_addvhost.log
    

    example output returns log at /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_wordpress_addvhost.log
    Code (Text):
    ls -lahrt /root/centminlogs | grep wordpress_addvhost.log
    -rw-r--r--  1 root root 2.2M Oct 11 01:40 /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_wordpress_addvhost.log
    

    in SSH use cat to ouput contents of /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_wordpress_addvhost.log. Clear your SSH client window/buffer so only output is the contents of the file
    Code (Text):
    cat /root/centminlogs/centminmod_1.2.3-eva2000.09.001_111016-112321_wordpress_addvhost.log
    

    Then copy and paste into Pastebin.com or Gists entry. If your SSH window scroll buffer isn't that large to get the whole contents of the install log, you can download file manually and copy and paste contents. But makes sure it's sanitised version of the contents without revealing sensitive info. For example you can replace domain name of the wordpress site with generic dummy entry = domain.com if you want and mask site/server IP revealed in the log with generic dummy entry = 111.222.333.444.
     
  3. EckyBrazzz

    EckyBrazzz Active Member

    917
    190
    43
    Mar 28, 2018
    >>>>Click here<<<< i'm nearby......
    Ratings:
    +363
    Local Time:
    8:05 PM
    Latest
    Latest
  4. EckyBrazzz

    EckyBrazzz Active Member

    917
    190
    43
    Mar 28, 2018
    >>>>Click here<<<< i'm nearby......
    Ratings:
    +363
    Local Time:
    8:05 PM
    Latest
    Latest
    @eva2000 I posted the logfile. Can you please have a look at it?
     
  5. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    9:05 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    looks like you hit some kind of memory limit in PHP/WP-CLI
    Code (Text):
    Downloading WordPress 5.5.3 (en_US)...
    Using cached file '/root/.wp-cli/cache/core/wordpress-5.5.3-en_US.tar.gz'...
    PHP Fatal error:  Allowed memory size of 50331648 bytes exhausted (tried to allocate 36864 bytes) in phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Extractor.php on line 101
    Error: This does not seem to be a WordPress installation.
    Pass --path=`path/to/wordpress` or run `wp core download`.
    

    50331648 bytes is very low limit. How much memory does your system have? output for these commands
    Code (Text):
    php -i | grep memory_limit
    

    Code (Text):
    free -mlt

    Code (Text):
    cminfo sar-mem
     
  6. EckyBrazzz

    EckyBrazzz Active Member

    917
    190
    43
    Mar 28, 2018
    >>>>Click here<<<< i'm nearby......
    Ratings:
    +363
    Local Time:
    8:05 PM
    Latest
    Latest
    @eva2000 , thanks, I added more memory and the problem was partaly resolved and also I could upgrade to version 8.0.0.

    Now it gives me a error on the install of the plugins, but they work.

     
  7. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    9:05 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Wordpress 5.5 doesn't support PHP 8.0. You need to wait for next Wordpress 5.6 for PHP 8.0 support
     
  8. Benjamin74

    Benjamin74 Member

    76
    7
    8
    May 2, 2016
    Ratings:
    +18
    Local Time:
    1:05 AM
    Got this error again today, somehow I must have installed CMM a while back on that VPS because it was setup to use 48M for PHP... on a 2GB VPS!! Maybe it was an old VPS that I upgraded so CMM didn't have the opportunity to set the PHP memory to something reasonable for my system.

    Anyway for those that get the same problem I've just edited:

    nano /etc/centminmod/php.d/a_customphp.ini

    And just bump everything to 256M

    upload_max_filesize = 256M
    memory_limit = 256M
    post_max_size = 256M


    I'm not entirely sure what the minimum PHP memory needed by the WP CLI utility but if it's a known value (couldn't find it) maybe we could have CMM check the memory before installing and WP (and yelling if it's below... I don't know 128M maybe ?)

    Cheers,
     
  9. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    9:05 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Instead of editing existing .ini you can create one with filename that overrides any others by ensuring it's name is alphanumerically after other settings files. See example at PHP-FPM - CentminMod.com LEMP Nginx web stack for CentOS

     
  10. eva2000

    eva2000 Administrator Staff Member

    58,893
    12,490
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +19,122
    Local Time:
    9:05 AM
    Nginx 1.31.x
    MariaDB 10.x/11.4+/12.3+
    Currently 123.09beta01 dynamically sets those specific values based on total memory that is actually free and not total memory that is installed.
    Code (Text):
        # dynamic PHP memory_limit calculation
        if [[ "$TOTALMEM_PHP" -le '262144' ]]; then
            ZOLIMIT='32'
            PHP_MEMORYLIMIT='48M'
            PHP_UPLOADLIMIT='48M'
            PHP_REALPATHLIMIT='512k'
            PHP_REALPATHTTL='14400'
        elif [[ "$TOTALMEM_PHP" -gt '262144' && "$TOTALMEM_PHP" -le '393216' ]]; then
            ZOLIMIT='80'
            PHP_MEMORYLIMIT='96M'
            PHP_UPLOADLIMIT='96M'
            PHP_REALPATHLIMIT='640k'
            PHP_REALPATHTTL='21600'
        elif [[ "$TOTALMEM_PHP" -gt '393216' && "$TOTALMEM_PHP" -le '524288' ]]; then
            ZOLIMIT='112'
            PHP_MEMORYLIMIT='128M'
            PHP_UPLOADLIMIT='128M'
            PHP_REALPATHLIMIT='768k'
            PHP_REALPATHTTL='28800'
        elif [[ "$TOTALMEM_PHP" -gt '524288' && "$TOTALMEM_PHP" -le '1049576' ]]; then
            ZOLIMIT='144'
            PHP_MEMORYLIMIT='160M'
            PHP_UPLOADLIMIT='160M'
            PHP_REALPATHLIMIT='768k'
            PHP_REALPATHTTL='28800'
        elif [[ "$TOTALMEM_PHP" -gt '1049576' && "$TOTALMEM_PHP" -le '2097152' ]]; then
            ZOLIMIT='160'
            PHP_MEMORYLIMIT='320M'
            PHP_UPLOADLIMIT='320M'
            PHP_REALPATHLIMIT='1536k'
            PHP_REALPATHTTL='28800'
        elif [[ "$TOTALMEM_PHP" -gt '2097152' && "$TOTALMEM_PHP" -le '3145728' ]]; then
            ZOLIMIT='192'
            PHP_MEMORYLIMIT='384M'
            PHP_UPLOADLIMIT='384M'
            PHP_REALPATHLIMIT='2048k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '3145728' && "$TOTALMEM_PHP" -le '4194304' ]]; then
            ZOLIMIT='224'
            PHP_MEMORYLIMIT='512M'
            PHP_UPLOADLIMIT='512M'
            PHP_REALPATHLIMIT='3072k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '4194304' && "$TOTALMEM_PHP" -le '8180000' ]]; then
            ZOLIMIT='288'
            PHP_MEMORYLIMIT='640M'
            PHP_UPLOADLIMIT='640M'
            PHP_REALPATHLIMIT='4096k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '8180000' && "$TOTALMEM_PHP" -le '16360000' ]]; then
            ZOLIMIT='320'
            PHP_MEMORYLIMIT='800M'
            PHP_UPLOADLIMIT='800M'
            PHP_REALPATHLIMIT='4096k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '16360000' && "$TOTALMEM_PHP" -le '32400000' ]]; then
            ZOLIMIT='480'
            PHP_MEMORYLIMIT='1024M'
            PHP_UPLOADLIMIT='1024M'
            PHP_REALPATHLIMIT='4096k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '32400000' && "$TOTALMEM_PHP" -le '64800000' ]]; then
            ZOLIMIT='600'
            PHP_MEMORYLIMIT='1280M'
            PHP_UPLOADLIMIT='1280M'
            PHP_REALPATHLIMIT='4096k'
            PHP_REALPATHTTL='43200'
        elif [[ "$TOTALMEM_PHP" -gt '64800000' ]]; then
            ZOLIMIT='800'
            PHP_MEMORYLIMIT='2048M'
            PHP_UPLOADLIMIT='2048M'
            PHP_REALPATHLIMIT='8192k'
            PHP_REALPATHTTL='86400'
        fi

    Where total memory (TOTALMEM_PHP) is actually calculated on free available memory and not installed memory to be more accurate. Basing it on total installed memory would be bad as some of that installed memory is already being used most of the time!

    For CentOS 7 non-OpenVZ that free memory calculation is using this formula which takes into account multiple CPU socket numa based memory allocations.
    Code (Text):
            # account for multiple cpu socket numa based memory
            # https://community.centminmod.com/posts/48189/
            GETCPUNODE_COUNT=$(numactl --hardware | awk '/available: / {print $2}')
            if [[ "$GETCPUNODE_COUNT" -ge '2' ]]; then
              FREEMEM_NUMANODE=$(($(numactl --hardware | awk '/free:/ {print $4}' | sort -r | head -n1)*1024))
              FREEMEMCACHED=$(egrep '^Buffers|^Cached' /proc/meminfo | awk '{summ+=$2} END {print summ}' | head -n1)
              FREEMEM=$(($FREEMEM_NUMANODE+$FREEMEMCACHED))
            else
              FREEMEM=$(cat /proc/meminfo | grep MemAvailable | awk '{print $2}')
            fi
    
    TOTALMEM_PHP=$FREEMEM