ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Wordpress on Vultr 768

    IT Discussion
    wordpress vultr
    9
    70
    8.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      scottalanmiller
      last edited by

      This might be a silly question but just to be 100% sure.... what is the disk space usage?

      df -h
      A 1 Reply Last reply Reply Quote 0
      • S
        scottalanmiller
        last edited by

        Doesn't look like memory is the problem. You don't have a lot, but it's not being used.

        1 Reply Last reply Reply Quote 0
        • A
          AdamF @scottalanmiller
          last edited by

          @scottalanmiller said in Wordpress on Vultr 768:

          This might be a silly question but just to be 100% sure.... what is the disk space usage?

          df -h

          [root@web01 mariadb]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        15G  3.1G   11G  22% /
devtmpfs        362M     0  362M   0% /dev
tmpfs           371M     0  371M   0% /dev/shm
tmpfs           371M  9.6M  361M   3% /run
tmpfs           371M     0  371M   0% /sys/fs/cgroup
tmpfs            75M     0   75M   0% /run/user/1000
          S 1 Reply Last reply Reply Quote 0
          • S
            scottalanmiller
            last edited by

            This is the bit that matters. InnoDB is freaking out.

            InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes
InnoDB: than specified in the .cnf file 0 8388608 bytes!
InnoDB: Possible causes for this error:
 (a) Incorrect log file is used or log file size is changed
 (b) In case default size is used this log file is from 10.0
 (c) Log file is corrupted or there was not enough disk space
 In case (b) you need to set innodb_log_file_size = 48M
161107 11:05:52 [ERROR] Plugin 'InnoDB' init function returned error.
161107 11:05:52 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
161107 11:05:52 [Note] Plugin 'FEEDBACK' is disabled.
161107 11:05:52 [ERROR] Unknown/unsupported storage engine: InnoDB
161107 11:05:52 [ERROR] Aborting

            And it is not memory that it is complaining about.

            1 Reply Last reply Reply Quote 1
            • S
              scottalanmiller @AdamF
              last edited by

              @fuznutz04 Okay, so plenty of disk space.

              1 Reply Last reply Reply Quote 0
              • S
                scottalanmiller
                last edited by

                Which OS is this? What is the source of MariaDB?

                A 1 Reply Last reply Reply Quote 0
                • A
                  AdamF @scottalanmiller
                  last edited by

                  @scottalanmiller said in Wordpress on Vultr 768:

                  Which OS is this? What is the source of MariaDB?

                  This is CentOS7. I set this server up a few months ago following this guide: https://jaredbusch.com/2014/08/11/how-to-install-wordpress-on-centos-7-minimal/

                  As far as I remember, I don't remember deviating from it.

                  J 1 Reply Last reply Reply Quote 0
                  • S
                    scottalanmiller
                    last edited by

                    I see, so this has been running for a while and only recently started having the problem? It seems like InnoDB is having an issue registering as an engine.

                    A 1 Reply Last reply Reply Quote 1
                    • J
                      JaredBusch @AdamF
                      last edited by

                      @fuznutz04 said in Wordpress on Vultr 768:

                      @scottalanmiller said in Wordpress on Vultr 768:

                      Which OS is this? What is the source of MariaDB?

                      This is CentOS7. I set this server up a few months ago following this guide: https://jaredbusch.com/2014/08/11/how-to-install-wordpress-on-centos-7-minimal/

                      As far as I remember, I don't remember deviating from it.

                      I need to update that guide a bit one of these days.

                      1 Reply Last reply Reply Quote 0
                      • A
                        AdamF @scottalanmiller
                        last edited by

                        @scottalanmiller said in Wordpress on Vultr 768:

                        I see, so this has been running for a while and only recently started having the problem? It seems like InnoDB is having an issue registering as an engine.

                        Yes, it was runnning fine for at least a week, then I abandoned it for a few months, and recently revisited and started having these issues.

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          scottalanmiller @AdamF
                          last edited by

                          @fuznutz04 said in Wordpress on Vultr 768:

                          @scottalanmiller said in Wordpress on Vultr 768:

                          I see, so this has been running for a while and only recently started having the problem? It seems like InnoDB is having an issue registering as an engine.

                          Yes, it was runnning fine for at least a week, then I abandoned it for a few months, and recently revisited and started having these issues.

                          Oh, you hurt it's feelings. That's a standard problem. Talk nice to it for a while.

                          A 1 Reply Last reply Reply Quote 2
                          • A
                            AdamF @scottalanmiller
                            last edited by

                            @scottalanmiller said in Wordpress on Vultr 768:

                            @fuznutz04 said in Wordpress on Vultr 768:

                            @scottalanmiller said in Wordpress on Vultr 768:

                            I see, so this has been running for a while and only recently started having the problem? It seems like InnoDB is having an issue registering as an engine.

                            Yes, it was runnning fine for at least a week, then I abandoned it for a few months, and recently revisited and started having these issues.

                            Oh, you hurt it's feelings. That's a standard problem. Talk nice to it for a while.

                            Could be. It's not a HUGE deal, as I can just blow it away and start over, but it would be nice to find out what's going on for if/when it happens again

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              scottalanmiller @AdamF
                              last edited by

                              @fuznutz04 said in Wordpress on Vultr 768:

                              @scottalanmiller said in Wordpress on Vultr 768:

                              @fuznutz04 said in Wordpress on Vultr 768:

                              @scottalanmiller said in Wordpress on Vultr 768:

                              I see, so this has been running for a while and only recently started having the problem? It seems like InnoDB is having an issue registering as an engine.

                              Yes, it was runnning fine for at least a week, then I abandoned it for a few months, and recently revisited and started having these issues.

                              Oh, you hurt it's feelings. That's a standard problem. Talk nice to it for a while.

                              Could be. It's not a HUGE deal, as I can just blow it away and start over, but it would be nice to find out what's going on for if/when it happens again

                              Agreed. Since it is not mission critical, start with updates if those have not been run. 99% sure that that will not do anything, but you know, worth the test.

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                AdamF @scottalanmiller
                                last edited by

                                @scottalanmiller Yeah, that didn't fix it. I'll just start over. I recall discussion on here previously that the "one click" installs of Wordpress on Vultr are not recommended. I couldn't remember (or find the discussion) why this was the opinion...

                                S 1 Reply Last reply Reply Quote 0
                                • momurdaM
                                  momurda
                                  last edited by

                                  Have you checked to see if these files exist and are correct size? Have you checked the .cnf file
                                  InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes
                                  InnoDB: than specified in the .cnf file 0 8388608 bytes!

                                  Check your cnf file to see that it is correct. Rename/move ib_logfile0, ib_logfile1 (they'll get recreated when the service starts again)

                                  A 1 Reply Last reply Reply Quote 1
                                  • A
                                    AdamF @momurda
                                    last edited by

                                    @momurda said in Wordpress on Vultr 768:

                                    Have you checked to see if these files exist and are correct size? Have you checked the .cnf file
                                    InnoDB: Error: log file ./ib_logfile0 is of different size 0 5242880 bytes
                                    InnoDB: than specified in the .cnf file 0 8388608 bytes!

                                    Check your cnf file to see that it is correct. Rename/move ib_logfile0, ib_logfile1 (they'll get recreated when the service starts again)

                                    I renamed and started the service again, and the files were re-created. The site is online for a few seconds then crashes again. I'm not seeing any configuration file other than /etc/my.cnf, and the file only has a few lines of code in it.

                                    [mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in http://fedoraproject.org/wiki/Systemd

[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

                                    The files in /etc/my.cnf.d have almost nothing in them as well.

                                    momurdaM 1 Reply Last reply Reply Quote 0
                                    • S
                                      scottalanmiller @AdamF
                                      last edited by

                                      @fuznutz04 said in Wordpress on Vultr 768:

                                      @scottalanmiller Yeah, that didn't fix it. I'll just start over. I recall discussion on here previously that the "one click" installs of Wordpress on Vultr are not recommended. I couldn't remember (or find the discussion) why this was the opinion...

                                      That's correct, those are never recommended. Use the OS, not a third party system.

                                      1 Reply Last reply Reply Quote 0
                                      • momurdaM
                                        momurda @AdamF
                                        last edited by

                                        @fuznutz04
                                        I think there should be a bit more lines in that file.
                                        What size files are the recreated innodb files?
                                        What is the contents of /var/log/mariadb/mariadb.log

                                        A 1 Reply Last reply Reply Quote 1
                                        • A
                                          AdamF @momurda
                                          last edited by

                                          @momurda said in Wordpress on Vultr 768:

                                          @fuznutz04
                                          I think there should be a bit more lines in that file.
                                          What size files are the recreated innodb files?
                                          What is the contents of /var/log/mariadb/mariadb.log

                                          5242880 bytes is the size of the new files.

                                          Seems like I'm in a time warp, as it is warning me that my sequence numbers are in the future!

                                          161107 12:17:20  InnoDB: Waiting for the background threads to start
161107 12:17:20  InnoDB: Error: page 348 log sequence number 133743653
InnoDB: is in the future! Current system log sequence number 107618964.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
161107 12:17:21 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended

                                          So following the directions to force innodb into recovery mode, the DB starts, but then the logs say this:

                                          InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.
161107 12:34:37 mysqld_safe Number of processes running now: 0
161107 12:34:37 mysqld_safe mysqld restarted
161107 12:34:40 [Note] /usr/libexec/mysqld (mysqld 5.5.50-MariaDB) starting as process 11049 ...
161107 12:34:40 InnoDB: The InnoDB memory heap is disabled
161107 12:34:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161107 12:34:40 InnoDB: Compressed tables use zlib 1.2.7
161107 12:34:40 InnoDB: Using Linux native AIO
161107 12:34:40 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137756672 bytes) failed; errno 12
161107 12:34:40 InnoDB: Completed initialization of buffer pool
161107 12:34:40 InnoDB: Fatal error: cannot allocate memory for the buffer pool
161107 12:34:40 [ERROR] Plugin 'InnoDB' init function returned error.
161107 12:34:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
161107 12:34:40 [ERROR] mysqld: Out of memory (Needed 128917504 bytes)
161107 12:34:40 [Note] Plugin 'FEEDBACK' is disabled.
161107 12:34:40 [ERROR] Unknown/unsupported storage engine: InnoDB
161107 12:34:40 [ERROR] Aborting
                                          1 Reply Last reply Reply Quote 0
                                          • momurdaM
                                            momurda
                                            last edited by

                                            Just a bit of browsing I find this. You do actually seem to be out of memory, try adding

                                            performance_schema = off

                                            to the [mysqld] section of my.cnf

                                            A 1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 4 / 4
                                            • First post
                                              Last post