\
; http://php.net/date.sunrise-zenith
\
;date.sunrise_zenith = 90.583333
\
\
; http://php.net/date.sunset-zenith
\
;date.sunset_zenith = 90.583333
\
\
[filter]
\
; http://php.net/filter.default
\
;filter.default = unsafe_raw
\
\
; http://php.net/filter.default-flags
\
;filter.default_flags =
\
\
[iconv]
\
; Use of this INI entry is deprecated, use global input_encoding instead.
\
; If empty, default_charset or input_encoding or iconv.input_encoding is used.
\
; The precedence is: default_charset < input_encoding < iconv.input_encoding
\
;iconv.input_encoding =
\
\
; Use of this INI entry is deprecated, use global internal_encoding instead.
\
; If empty, default_charset or internal_encoding or iconv.internal_encoding is used.
\
; The precedence is: default_charset < internal_encoding < iconv.internal_encoding
\
;iconv.internal_encoding =
\
\
; Use of this INI entry is deprecated, use global output_encoding instead.
\
; If empty, default_charset or output_encoding or iconv.output_encoding is used.
\
; The precedence is: default_charset < output_encoding < iconv.output_encoding
\
; To use an output encoding conversion, iconv's output handler must be set
\
; otherwise output encoding conversion cannot be performed.
\
;iconv.output_encoding =
\
\
[imap]
\
; rsh/ssh logins are disabled by default. Use this INI entry if you want to
\
; enable them. Note that the IMAP library does not filter mailbox names before
\
; passing them to rsh/ssh command, thus passing untrusted data to this function
\
; with rsh/ssh enabled is insecure.
\
;imap.enable_insecure_rsh=0
\
\
[intl]
\
;intl.default_locale =
\
; This directive allows you to produce PHP errors when some error
\
; happens within intl functions. The value is the level of the error produced.
\
; Default is 0, which does not produce any errors.
\
;intl.error_level = E_WARNING
\
;intl.use_exceptions = 0
\
\
[sqlite3]
\
; Directory pointing to SQLite3 extensions
\
; http://php.net/sqlite3.extension-dir
\
;sqlite3.extension_dir =
\
\
; SQLite defensive mode flag (only available from SQLite 3.26+)
\
; When the defensive flag is enabled, language features that allow ordinary
\
; SQL to deliberately corrupt the database file are disabled. This forbids
\
; writing directly to the schema, shadow tables (eg. FTS data tables), or
\
; the sqlite_dbpage virtual table.
\
; https://www.sqlite.org/c3ref/c_dbconfig_defensive.html
\
; (for older SQLite versions, this flag has no use)
\
;sqlite3.defensive = 1
\
\
[Pcre]
\
; PCRE library backtracking limit.
\
; http://php.net/pcre.backtrack-limit
\
;pcre.backtrack_limit=100000
\
\
; PCRE library recursion limit.
\
; Please note that if you set this value to a high number you may consume all
\
; the available process stack and eventually crash PHP (due to reaching the
\
; stack size limit imposed by the Operating System).
\
; http://php.net/pcre.recursion-limit
\
;pcre.recursion_limit=100000
\
\
; Enables or disables JIT compilation of patterns. This requires the PCRE
\
; library to be compiled with JIT support.
\
;pcre.jit=1
\
\
[Pdo]
\
pdo_mysql.default_socket="MySQL"
\
; Whether to pool ODBC connections. Can be one of "strict", "relaxed" or "off"
\
; http://php.net/pdo-odbc.connection-pooling
\
;pdo_odbc.connection_pooling=strict
\
\
;pdo_odbc.db2_instance_name
\
\
[Pdo_mysql]
\
; Default socket name for local MySQL connects. If empty, uses the built-in
\
; MySQL defaults.
\
pdo_mysql.default_socket=
\
\
[Phar]
\
; http://php.net/phar.readonly
\
;phar.readonly = On
\
\
; http://php.net/phar.require-hash
\
;phar.require_hash = On
\
\
;phar.cache_list =
\
\
[mail function]
\
; For Win32 only.
\
; http://php.net/smtp
\
SMTP=localhost
\
; http://php.net/smtp-port
\
smtp_port=25
\
\
; For Win32 only.
\
; http://php.net/sendmail-from
\
;sendmail_from = me@example.com
\
\
; For Unix only. You may supply arguments as well (default: "sendmail -t -i").
\
; http://php.net/sendmail-path
\
;sendmail_path =
\
\
; Force the addition of the specified parameters to be passed as extra parameters
\
; to the sendmail binary. These parameters will always replace the value of
\
; the 5th parameter to mail().
\
;mail.force_extra_parameters =
\
\
; Add X-PHP-Originating-Script: that will include uid of the script followed by the filename
\
mail.add_x_header=Off
\
\
; The path to a log file that will log all mail() calls. Log entries include
\
; the full path of the script, line number, To address and headers.
\
;mail.log =
\
; Log mail to syslog (Event Log on Windows).
\
;mail.log = syslog
\
\
[ODBC]
\
; http://php.net/odbc.default-db
\
;odbc.default_db = Not yet implemented
\
\
; http://php.net/odbc.default-user
\
;odbc.default_user = Not yet implemented
\
\
; http://php.net/odbc.default-pw
\
;odbc.default_pw = Not yet implemented
\
\
; Controls the ODBC cursor model.
\
; Default: SQL_CURSOR_STATIC (default).
\
;odbc.default_cursortype
\
\
; Allow or prevent persistent links.
\
; http://php.net/odbc.allow-persistent
\
odbc.allow_persistent=On
\
\
; Check that a connection is still valid before reuse.
\
; http://php.net/odbc.check-persistent
\
odbc.check_persistent=On
\
\
; Maximum number of persistent links. -1 means no limit.
\
; http://php.net/odbc.max-persistent
\
odbc.max_persistent=-1
\
\
; Maximum number of links (persistent + non-persistent). -1 means no limit.
\
; http://php.net/odbc.max-links
\
odbc.max_links=-1
\
\
; Handling of LONG fields. Returns number of bytes to variables. 0 means
\
; passthru.
\
; http://php.net/odbc.defaultlrl
\
odbc.defaultlrl=4096
\
\
; Handling of binary data. 0 means passthru, 1 return as is, 2 convert to char.
\
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation
\
; of odbc.defaultlrl and odbc.defaultbinmode
\
; http://php.net/odbc.defaultbinmode
\
odbc.defaultbinmode=1
\
\
[Interbase]
\
; Allow or prevent persistent links.
\
ibase.allow_persistent=1
\
\
; Maximum number of persistent links. -1 means no limit.
\
ibase.max_persistent=-1
\
\
; Maximum number of links (persistent + non-persistent). -1 means no limit.
\
ibase.max_links=-1
\
\
; Default database name for ibase_connect().
\
;ibase.default_db =
\
\
; Default username for ibase_connect().
\
;ibase.default_user =
\
\
; Default password for ibase_connect().
\
;ibase.default_password =
\
\
; Default charset for ibase_connect().
\
;ibase.default_charset =
\
\
; Default timestamp format.
\
ibase.timestampformat="%Y-%m-%d %H:%M:%S"
\
\
; Default date format.
\
ibase.dateformat="%Y-%m-%d"
\
\
; Default time format.
\
ibase.timeformat="%H:%M:%S"
\
\
[MySQLi]
\
\
; Maximum number of persistent links. -1 means no limit.
\
; http://php.net/mysqli.max-persistent
\
mysqli.max_persistent=-1
\
\
; Allow accessing, from PHP's perspective, local files with LOAD DATA statements
\
; http://php.net/mysqli.allow_local_infile
\
;mysqli.allow_local_infile = On
\
\
; Allow or prevent persistent links.
\
; http://php.net/mysqli.allow-persistent
\
mysqli.allow_persistent=On
\
\
; Maximum number of links. -1 means no limit.
\
; http://php.net/mysqli.max-links
\
mysqli.max_links=-1
\
\
; Default port number for mysqli_connect(). If unset, mysqli_connect() will use
\
; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the
\
; compile-time value defined MYSQL_PORT (in that order). Win32 will only look
\
; at MYSQL_PORT.
\
; http://php.net/mysqli.default-port
\
mysqli.default_port=3306
\
\
; Default socket name for local MySQL connects. If empty, uses the built-in
\
; MySQL defaults.
\
; http://php.net/mysqli.default-socket
\
mysqli.default_socket=
\
\
; Default host for mysql_connect() (doesn't apply in safe mode).
\
; http://php.net/mysqli.default-host
\
mysqli.default_host=
\
\
; Default user for mysql_connect() (doesn't apply in safe mode).
\
; http://php.net/mysqli.default-user
\
mysqli.default_user=
\
\
; Default password for mysqli_connect() (doesn't apply in safe mode).
\
; Note that this is generally a *bad* idea to store passwords in this file.
\
; *Any* user with PHP access can run 'echo get_cfg_var("mysqli.default_pw")
\
; and reveal this password! And of course, any users with read access to this
\
; file will be able to reveal the password as well.
\
; http://php.net/mysqli.default-pw
\
mysqli.default_pw=
\
\
; Allow or prevent reconnect
\
mysqli.reconnect=Off
\
\
[mysqlnd]
\
; Enable / Disable collection of general statistics by mysqlnd which can be
\
; used to tune and monitor MySQL operations.
\
mysqlnd.collect_statistics=On
\
\
; Enable / Disable collection of memory usage statistics by mysqlnd which can be
\
; used to tune and monitor MySQL operations.
\
mysqlnd.collect_memory_statistics=On
\
\
; Records communication from all extensions using mysqlnd to the specified log
\
; file.
\
; http://php.net/mysqlnd.debug
\
;mysqlnd.debug =
\
\
; Defines which queries will be logged.
\
;mysqlnd.log_mask = 0
\
\
; Default size of the mysqlnd memory pool, which is used by result sets.
\
;mysqlnd.mempool_default_size = 16000
\
\
; Size of a pre-allocated buffer used when sending commands to MySQL in bytes.
\
;mysqlnd.net_cmd_buffer_size = 2048
\
\
; Size of a pre-allocated buffer used for reading data sent by the server in
\
; bytes.
\
;mysqlnd.net_read_buffer_size = 32768
\
\
; Timeout for network requests in seconds.
\
;mysqlnd.net_read_timeout = 31536000
\
\
; SHA-256 Authentication Plugin related. File with the MySQL server public RSA
\
; key.
\
;mysqlnd.sha256_server_public_key =
\
\
[OCI8]
\
\
; Connection: Enables privileged connections using external
\
; credentials (OCI_SYSOPER, OCI_SYSDBA)
\
; http://php.net/oci8.privileged-connect
\
;oci8.privileged_connect = Off
\
\
; Connection: The maximum number of persistent OCI8 connections per
\
; process. Using -1 means no limit.
\
; http://php.net/oci8.max-persistent
\
;oci8.max_persistent = -1
\
\
; Connection: The maximum number of seconds a process is allowed to
\
; maintain an idle persistent connection. Using -1 means idle
\
; persistent connections will be maintained forever.
\
; http://php.net/oci8.persistent-timeout
\
;oci8.persistent_timeout = -1
\
\
; Connection: The number of seconds that must pass before issuing a
\
; ping during oci_pconnect() to check the connection validity. When
\
; set to 0, each oci_pconnect() will cause a ping. Using -1 disables
\
; pings completely.
\
; http://php.net/oci8.ping-interval
\
;oci8.ping_interval = 60
\
\
; Connection: Set this to a user chosen connection class to be used
\
; for all pooled server requests with Oracle 11g Database Resident
\
; Connection Pooling (DRCP). To use DRCP, this value should be set to
\
; the same string for all web servers running the same application,
\
; the database pool must be configured, and the connection string must
\
; specify to use a pooled server.
\
;oci8.connection_class =
\
\
; High Availability: Using On lets PHP receive Fast Application
\
; Notification (FAN) events generated when a database node fails. The
\
; database must also be configured to post FAN events.
\
;oci8.events = Off
\
\
; Tuning: This option enables statement caching, and specifies how
\
; many statements to cache. Using 0 disables statement caching.
\
; http://php.net/oci8.statement-cache-size
\
;oci8.statement_cache_size = 20
\
\
; Tuning: Enables statement prefetching and sets the default number of
\
; rows that will be fetched automatically after statement execution.
\
; http://php.net/oci8.default-prefetch
\
;oci8.default_prefetch = 100
\
\
; Compatibility. Using On means oci_close() will not close
\
; oci_connect() and oci_new_connect() connections.
\
; http://php.net/oci8.old-oci-close-semantics
\
;oci8.old_oci_close_semantics = Off
\
\
[PostgreSQL]
\
; Allow or prevent persistent links.
\
; http://php.net/pgsql.allow-persistent
\
pgsql.allow_persistent=On
\
\
; Detect broken persistent links always with pg_pconnect().
\
; Auto reset feature requires a little overheads.
\
; http://php.net/pgsql.auto-reset-persistent
\
pgsql.auto_reset_persistent=Off
\
\
; Maximum number of persistent links. -1 means no limit.
\
; http://php.net/pgsql.max-persistent
\
pgsql.max_persistent=-1
\
\
; Maximum number of links (persistent+non persistent). -1 means no limit.
\
; http://php.net/pgsql.max-links
\
pgsql.max_links=-1
\
\
; Ignore PostgreSQL backends Notice message or not.
\
; Notice message logging require a little overheads.
\
; http://php.net/pgsql.ignore-notice
\
pgsql.ignore_notice=0
\
\
; Log PostgreSQL backends Notice message or not.
\
; Unless pgsql.ignore_notice=0, module cannot log notice message.
\
; http://php.net/pgsql.log-notice
\
pgsql.log_notice=0
\
\
[bcmath]
\
; Number of decimal digits for all bcmath functions.
\
; http://php.net/bcmath.scale
\
bcmath.scale=0
\
\
[browscap]
\
; http://php.net/browscap
\
browscap="C:\\xampp\\php\\extras\\browscap.ini"
\
\
[Session]
\
; Handler used to store/retrieve data.
\
; http://php.net/session.save-handler
\
session.save_handler=files
\
\
; Argument passed to save_handler. In the case of files, this is the path
\
; where data files are stored. Note: Windows users have to change this
\
; variable in order to use PHP's session functions.
\
;
\
; The path can be defined as:
\
;
\
; session.save_path = "N;/path"
\
;
\
; where N is an integer. Instead of storing all the session files in
\
; /path, what this will do is use subdirectories N-levels deep, and
\
; store the session data in those directories. This is useful if
\
; your OS has problems with many files in one directory, and is
\
; a more efficient layout for servers that handle many sessions.
\
;
\
; NOTE 1: PHP will not create this directory structure automatically.
\
; You can use the script in the ext/session dir for that purpose.
\
; NOTE 2: See the section on garbage collection below if you choose to
\
; use subdirectories for session storage
\
;
\
; The file storage module creates files using mode 600 by default.
\
; You can change that by using
\
;
\
; session.save_path = "N;MODE;/path"
\
;
\
; where MODE is the octal representation of the mode. Note that this
\
; does not overwrite the process's umask.
\
; http://php.net/session.save-path
\
session.save_path="C:\\xampp\\tmp"
\
\
; Whether to use strict session mode.
\
; Strict session mode does not accept an uninitialized session ID, and
\
; regenerates the session ID if the browser sends an uninitialized session ID.
\
; Strict mode protects applications from session fixation via a session adoption
\
; vulnerability. It is disabled by default for maximum compatibility, but
\
; enabling it is encouraged.
\
; https://wiki.php.net/rfc/strict_sessions
\
session.use_strict_mode=0
\
\
; Whether to use cookies.
\
; http://php.net/session.use-cookies
\
session.use_cookies=1
\
\
; http://php.net/session.cookie-secure
\
;session.cookie_secure =
\
\
; This option forces PHP to fetch and use a cookie for storing and maintaining
\
; the session id. We encourage this operation as it's very helpful in combating
\
; session hijacking when not specifying and managing your own session id. It is
\
; not the be-all and end-all of session hijacking defense, but it's a good start.
\
; http://php.net/session.use-only-cookies
\
session.use_only_cookies=1
\
\
; Name of the session (used as cookie name).
\
; http://php.net/session.name
\
session.name=PHPSESSID
\
\
; Initialize session on request startup.
\
; http://php.net/session.auto-start
\
session.auto_start=0
\
\
; Lifetime in seconds of cookie or, if 0, until browser is restarted.
\
; http://php.net/session.cookie-lifetime
\
session.cookie_lifetime=0
\
\
; The path for which the cookie is valid.
\
; http://php.net/session.cookie-path
\
session.cookie_path=/
\
\
; The domain for which the cookie is valid.
\
; http://php.net/session.cookie-domain
\
session.cookie_domain=
\
\
; Whether or not to add the httpOnly flag to the cookie, which makes it
\
; inaccessible to browser scripting languages such as JavaScript.
\
; http://php.net/session.cookie-httponly
\
session.cookie_httponly=
\
\
; Add SameSite attribute to cookie to help mitigate Cross-Site Request Forgery (CSRF/XSRF)
\
; Current valid values are "Lax" or "Strict"
\
; https://tools.ietf.org/html/draft-west-first-party-cookies-07
\
session.cookie_samesite=
\
\
; Handler used to serialize data. php is the standard serializer of PHP.
\
; http://php.net/session.serialize-handler
\
session.serialize_handler=php
\
\
; Defines the probability that the 'garbage collection' process is started on every
\
; session initialization. The probability is calculated by using gc_probability/gc_divisor,
\
; e.g. 1/100 means there is a 1% chance that the GC process starts on each request.
\
; Default Value: 1
\
; Development Value: 1
\
; Production Value: 1
\
; http://php.net/session.gc-probability
\
session.gc_probability=1
\
\
; Defines the probability that the 'garbage collection' process is started on every
\
; session initialization. The probability is calculated by using gc_probability/gc_divisor,
\
; e.g. 1/100 means there is a 1% chance that the GC process starts on each request.
\
; For high volume production servers, using a value of 1000 is a more efficient approach.
\
; Default Value: 100
\
; Development Value: 1000
\
; Production Value: 1000
\
; http://php.net/session.gc-divisor
\
session.gc_divisor=1000
\
\
; After this number of seconds, stored data will be seen as 'garbage' and
\
; cleaned up by the garbage collection process.
\
; http://php.net/session.gc-maxlifetime
\
session.gc_maxlifetime=1440
\
\
; NOTE: If you are using the subdirectory option for storing session files
\
; (see session.save_path above), then garbage collection does *not*
\
; happen automatically. You will need to do your own garbage
\
; collection through a shell script, cron entry, or some other method.
\
; For example, the following script would is the equivalent of
\
; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
\
; find /path/to/sessions -cmin +24 -type f | xargs rm
\
\
; Check HTTP Referer to invalidate externally stored URLs containing ids.
\
; HTTP_REFERER has to contain this substring for the session to be
\
; considered as valid.
\
; http://php.net/session.referer-check
\
session.referer_check=
\
\
; Set to \{nocache,private,public,\} to determine HTTP caching aspects
\
; or leave this empty to avoid sending anti-caching headers.
\
; http://php.net/session.cache-limiter
\
session.cache_limiter=nocache
\
\
; Document expires after n minutes.
\
; http://php.net/session.cache-expire
\
session.cache_expire=180
\
\
; trans sid support is disabled by default.
\
; Use of trans sid may risk your users' security.
\
; Use this option with caution.
\
; - User may send URL contains active session ID
\
; to other person via. email/irc/etc.
\
; - URL that contains active session ID may be stored
\
; in publicly accessible computer.
\
; - User may access your site with the same session ID
\
; always using URL stored in browser's history or bookmarks.
\
; http://php.net/session.use-trans-sid
\
session.use_trans_sid=0
\
\
; Set session ID character length. This value could be between 22 to 256.
\
; Shorter length than default is supported only for compatibility reason.
\
; Users should use 32 or more chars.
\
; http://php.net/session.sid-length
\
; Default Value: 32
\
; Development Value: 26
\
; Production Value: 26
\
session.sid_length=26
\
\
; The URL rewriter will look for URLs in a defined set of HTML tags.
\
; <form> is special; if you include them here, the rewriter will
\
; add a hidden <input> field with the info which is otherwise appended
\
; to URLs. <form> tag's action attribute URL will not be modified
\
; unless it is specified.
\
; Note that all valid entries require a "=", even if no value follows.
\
; Default Value: "a=href,area=href,frame=src,form="
\
; Development Value: "a=href,area=href,frame=src,form="
\
; Production Value: "a=href,area=href,frame=src,form="
\
; http://php.net/url-rewriter.tags
\
session.trans_sid_tags="a=href,area=href,frame=src,form="
\
\
; URL rewriter does not rewrite absolute URLs by default.
\
; To enable rewrites for absolute paths, target hosts must be specified
\
; at RUNTIME. i.e. use ini_set()
\
; <form> tags is special. PHP will check action attribute's URL regardless
\
; of session.trans_sid_tags setting.
\
; If no host is defined, HTTP_HOST will be used for allowed host.
\
; Example value: php.net,www.php.net,wiki.php.net
\
; Use "," for multiple hosts. No spaces are allowed.
\
; Default Value: ""
\
; Development Value: ""
\
; Production Value: ""
\
;session.trans_sid_hosts=""
\
\
; Define how many bits are stored in each character when converting
\
; the binary hash data to something readable.
\
; Possible values:
\
; 4 (4 bits: 0-9, a-f)
\
; 5 (5 bits: 0-9, a-v)
\
; 6 (6 bits: 0-9, a-z, A-Z, "-", ",")
\
; Default Value: 4
\
; Development Value: 5
\
; Production Value: 5
\
; http://php.net/session.hash-bits-per-character
\
session.sid_bits_per_character=5
\
\
; Enable upload progress tracking in $_SESSION
\
; Default Value: On
\
; Development Value: On
\
; Production Value: On
\
; http://php.net/session.upload-progress.enabled
\
;session.upload_progress.enabled = On
\
\
; Cleanup the progress information as soon as all POST data has been read
\
; (i.e. upload completed).
\
; Default Value: On
\
; Development Value: On
\
; Production Value: On
\
; http://php.net/session.upload-progress.cleanup
\
;session.upload_progress.cleanup = On
\
\
; A prefix used for the upload progress key in $_SESSION
\
; Default Value: "upload_progress_"
\
; Development Value: "upload_progress_"
\
; Production Value: "upload_progress_"
\
; http://php.net/session.upload-progress.prefix
\
;session.upload_progress.prefix = "upload_progress_"
\
\
; The index name (concatenated with the prefix) in $_SESSION
\
; containing the upload progress information
\
; Default Value: "PHP_SESSION_UPLOAD_PROGRESS"
\
; Development Value: "PHP_SESSION_UPLOAD_PROGRESS"
\
; Production Value: "PHP_SESSION_UPLOAD_PROGRESS"
\
; http://php.net/session.upload-progress.name
\
;session.upload_progress.name = "PHP_SESSION_UPLOAD_PROGRESS"
\
\
; How frequently the upload progress should be updated.
\
; Given either in percentages (per-file), or in bytes
\
; Default Value: "1%"
\
; Development Value: "1%"
\
; Production Value: "1%"
\
; http://php.net/session.upload-progress.freq
\
;session.upload_progress.freq = "1%"
\
\
; The minimum delay between updates, in seconds
\
; Default Value: 1
\
; Development Value: 1
\
; Production Value: 1
\
; http://php.net/session.upload-progress.min-freq
\
;session.upload_progress.min_freq = "1"
\
\
; Only write session data when session data is changed. Enabled by default.
\
; http://php.net/session.lazy-write
\
;session.lazy_write = On
\
\
[Assertion]
\
; Switch whether to compile assertions at all (to have no overhead at run-time)
\
; -1: Do not compile at all
\
; 0: Jump over assertion at run-time
\
; 1: Execute assertions
\
; Changing from or to a negative value is only possible in php.ini! (For turning assertions on and off at run-time, see assert.active, when zend.assertions = 1)
\
; Default Value: 1
\
; Development Value: 1
\
; Production Value: -1
\
; http://php.net/zend.assertions
\
zend.assertions=1
\
\
; Assert(expr); active by default.
\
; http://php.net/assert.active
\
;assert.active = On
\
\
; Throw an AssertionError on failed assertions
\
; http://php.net/assert.exception
\
;assert.exception = On
\
\
; Issue a PHP warning for each failed assertion. (Overridden by assert.exception if active)
\
; http://php.net/assert.warning
\
;assert.warning = On
\
\
; Don't bail out by default.
\
; http://php.net/assert.bail
\
;assert.bail = Off
\
\
; User-function to be called if an assertion fails.
\
; http://php.net/assert.callback
\
;assert.callback = 0
\
\
; Eval the expression with current error_reporting(). Set to true if you want
\
; error_reporting(0) around the eval().
\
; http://php.net/assert.quiet-eval
\
;assert.quiet_eval = 0
\
\
[COM]
\
; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs
\
; http://php.net/com.typelib-file
\
;com.typelib_file =
\
\
; allow Distributed-COM calls
\
; http://php.net/com.allow-dcom
\
;com.allow_dcom = true
\
\
; autoregister constants of a component's typlib on com_load()
\
; http://php.net/com.autoregister-typelib
\
;com.autoregister_typelib = true
\
\
; register constants casesensitive
\
; http://php.net/com.autoregister-casesensitive
\
;com.autoregister_casesensitive = false
\
\
; show warnings on duplicate constant registrations
\
; http://php.net/com.autoregister-verbose
\
;com.autoregister_verbose = true
\
\
; The default character set code-page to use when passing strings to and from COM objects.
\
; Default: system ANSI code page
\
;com.code_page=
\
\
[mbstring]
\
; language for internal character representation.
\
; This affects mb_send_mail() and mbstring.detect_order.
\
; http://php.net/mbstring.language
\
;mbstring.language = Japanese
\
\
; Use of this INI entry is deprecated, use global internal_encoding instead.
\
; internal/script encoding.
\
; Some encoding cannot work as internal encoding. (e.g. SJIS, BIG5, ISO-2022-*)
\
; If empty, default_charset or internal_encoding or iconv.internal_encoding is used.
\
; The precedence is: default_charset < internal_encoding < iconv.internal_encoding
\
;mbstring.internal_encoding =
\
\
; Use of this INI entry is deprecated, use global input_encoding instead.
\
; http input encoding.
\
; mbstring.encoding_translation = On is needed to use this setting.
\
; If empty, default_charset or input_encoding or mbstring.input is used.
\
; The precedence is: default_charset < input_encoding < mbsting.http_input
\
; http://php.net/mbstring.http-input
\
;mbstring.http_input =
\
\
; Use of this INI entry is deprecated, use global output_encoding instead.
\
; http output encoding.
\
; mb_output_handler must be registered as output buffer to function.
\
; If empty, default_charset or output_encoding or mbstring.http_output is used.
\
; The precedence is: default_charset < output_encoding < mbstring.http_output
\
; To use an output encoding conversion, mbstring's output handler must be set
\
; otherwise output encoding conversion cannot be performed.
\
; http://php.net/mbstring.http-output
\
;mbstring.http_output =
\
\
; enable automatic encoding translation according to
\
; mbstring.internal_encoding setting. Input chars are
\
; converted to internal encoding by setting this to On.
\
; Note: Do _not_ use automatic encoding translation for
\
; portable libs/applications.
\
; http://php.net/mbstring.encoding-translation
\
;mbstring.encoding_translation = Off
\
\
; automatic encoding detection order.
\
; "auto" detect order is changed according to mbstring.language
\
; http://php.net/mbstring.detect-order
\
;mbstring.detect_order = auto
\
\
; substitute_character used when character cannot be converted
\
; one from another
\
; http://php.net/mbstring.substitute-character
\
;mbstring.substitute_character = none
\
\
; overload(replace) single byte functions by mbstring functions.
\
; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(),
\
; etc. Possible values are 0,1,2,4 or combination of them.
\
; For example, 7 for overload everything.
\
; 0: No overload
\
; 1: Overload mail() function
\
; 2: Overload str*() functions
\
; 4: Overload ereg*() functions
\
; http://php.net/mbstring.func-overload
\
;mbstring.func_overload = 0
\
\
; enable strict encoding detection.
\
; Default: Off
\
;mbstring.strict_detection = On
\
\
; This directive specifies the regex pattern of content types for which mb_output_handler()
\
; is activated.
\
; Default: mbstring.http_output_conv_mimetype=^(text/|application/xhtml\\+xml)
\
;mbstring.http_output_conv_mimetype=
\
\
; This directive specifies maximum stack depth for mbstring regular expressions. It is similar
\
; to the pcre.recursion_limit for PCRE.
\
; Default: 100000
\
;mbstring.regex_stack_limit=100000
\
\
[gd]
\
; Tell the jpeg decode to ignore warnings and try to create
\
; a gd image. The warning will then be displayed as notices
\
; disabled by default
\
; http://php.net/gd.jpeg-ignore-warning
\
;gd.jpeg_ignore_warning = 1
\
\
[exif]
\
; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS.
\
; With mbstring support this will automatically be converted into the encoding
\
; given by corresponding encode setting. When empty mbstring.internal_encoding
\
; is used. For the decode settings you can distinguish between motorola and
\
; intel byte order. A decode setting cannot be empty.
\
; http://php.net/exif.encode-unicode
\
;exif.encode_unicode = ISO-8859-15
\
\
; http://php.net/exif.decode-unicode-motorola
\
;exif.decode_unicode_motorola = UCS-2BE
\
\
; http://php.net/exif.decode-unicode-intel
\
;exif.decode_unicode_intel = UCS-2LE
\
\
; http://php.net/exif.encode-jis
\
;exif.encode_jis =
\
\
; http://php.net/exif.decode-jis-motorola
\
;exif.decode_jis_motorola = JIS
\
\
; http://php.net/exif.decode-jis-intel
\
;exif.decode_jis_intel = JIS
\
\
[Tidy]
\
; The path to a default tidy configuration file to use when using tidy
\
; http://php.net/tidy.default-config
\
;tidy.default_config = /usr/local/lib/php/default.tcfg
\
\
; Should tidy clean and repair output automatically?
\
; WARNING: Do not use this option if you are generating non-html content
\
; such as dynamic images
\
; http://php.net/tidy.clean-output
\
tidy.clean_output=Off
\
\
[soap]
\
; Enables or disables WSDL caching feature.
\
; http://php.net/soap.wsdl-cache-enabled
\
soap.wsdl_cache_enabled=1
\
\
; Sets the directory name where SOAP extension will put cache files.
\
; http://php.net/soap.wsdl-cache-dir
\
soap.wsdl_cache_dir="/tmp"
\
\
; (time to live) Sets the number of second while cached file will be used
\
; instead of original one.
\
; http://php.net/soap.wsdl-cache-ttl
\
soap.wsdl_cache_ttl=86400
\
\
; Sets the size of the cache limit. (Max. number of WSDL files to cache)
\
soap.wsdl_cache_limit=5
\
\
[sysvshm]
\
; A default size of the shared memory segment
\
;sysvshm.init_mem = 10000
\
\
[ldap]
\
; Sets the maximum number of open links or -1 for unlimited.
\
ldap.max_links=-1
\
\
[dba]
\
;dba.default_handler=
\
\
[opcache]
\
; Determines if Zend OPCache is enabled\
Zend_extension="php_opcache.dll"\
opcache.enable=1\
\
; Determines if Zend OPCache is enabled for the CLI version of PHP
\
;opcache.enable_cli=0
\
\
; The OPcache shared memory storage size.
\
;opcache.memory_consumption=128
\
\
; The amount of memory for interned strings in Mbytes.
\
;opcache.interned_strings_buffer=8
\
\
; The maximum number of keys (scripts) in the OPcache hash table.
\
; Only numbers between 200 and 1000000 are allowed.
\
;opcache.max_accelerated_files=10000
\
\
; The maximum percentage of "wasted" memory until a restart is scheduled.
\
;opcache.max_wasted_percentage=5
\
\
; When this directive is enabled, the OPcache appends the current working
\
; directory to the script key, thus eliminating possible collisions between
\
; files with the same name (basename). Disabling the directive improves
\
; performance, but may break existing applications.
\
;opcache.use_cwd=1
\
\
; When disabled, you must reset the OPcache manually or restart the
\
; webserver for changes to the filesystem to take effect.
\
;opcache.validate_timestamps=1
\
\
; How often (in seconds) to check file timestamps for changes to the shared
\
; memory storage allocation. ("1" means validate once per second, but only
\
; once per request. "0" means always validate)
\
;opcache.revalidate_freq=2
\
\
; Enables or disables file search in include_path optimization
\
;opcache.revalidate_path=0
\
\
; If disabled, all PHPDoc comments are dropped from the code to reduce the
\
; size of the optimized code.
\
;opcache.save_comments=1
\
\
; Allow file existence override (file_exists, etc.) performance feature.
\
;opcache.enable_file_override=0
\
\
; A bitmask, where each bit enables or disables the appropriate OPcache
\
; passes
\
;opcache.optimization_level=0x7FFFBFFF
\
\
;opcache.dups_fix=0
\
\
; The location of the OPcache blacklist file (wildcards allowed).
\
; Each OPcache blacklist file is a text file that holds the names of files
\
; that should not be accelerated. The file format is to add each filename
\
; to a new line. The filename may be a full path or just a file prefix
\
; (i.e., /var/www/x blacklists all the files and directories in /var/www
\
; that start with 'x'). Line starting with a ; are ignored (comments).
\
;opcache.blacklist_filename=
\
\
; Allows exclusion of large files from being cached. By default all files
\
; are cached.
\
;opcache.max_file_size=0
\
\
; Check the cache checksum each N requests.
\
; The default value of "0" means that the checks are disabled.
\
;opcache.consistency_checks=0
\
\
; How long to wait (in seconds) for a scheduled restart to begin if the cache
\
; is not being accessed.
\
;opcache.force_restart_timeout=180
\
\
; OPcache error_log file name. Empty string assumes "stderr".
\
;opcache.error_log=
\
\
; All OPcache errors go to the Web server log.
\
; By default, only fatal errors (level 0) or errors (level 1) are logged.
\
; You can also enable warnings (level 2), info messages (level 3) or
\
; debug messages (level 4).
\
;opcache.log_verbosity_level=1
\
\
; Preferred Shared Memory back-end. Leave empty and let the system decide.
\
;opcache.preferred_memory_model=
\
\
; Protect the shared memory from unexpected writing during script execution.
\
; Useful for internal debugging only.
\
;opcache.protect_memory=0
\
\
; Allows calling OPcache API functions only from PHP scripts which path is
\
; started from specified string. The default "" means no restriction
\
;opcache.restrict_api=
\
\
; Mapping base of shared memory segments (for Windows only). All the PHP
\
; processes have to map shared memory into the same address space. This
\
; directive allows to manually fix the "Unable to reattach to base address"
\
; errors.
\
;opcache.mmap_base=
\
\
; Enables and sets the second level cache directory.
\
; It should improve performance when SHM memory is full, at server restart or
\
; SHM reset. The default "" disables file based caching.
\
;opcache.file_cache=
\
\
; Enables or disables opcode caching in shared memory.
\
;opcache.file_cache_only=0
\
\
; Enables or disables checksum validation when script loaded from file cache.
\
;opcache.file_cache_consistency_checks=1
\
\
; Implies opcache.file_cache_only=1 for a certain process that failed to
\
; reattach to the shared memory (for Windows only). Explicitly enabled file
\
; cache is required.
\
;opcache.file_cache_fallback=1
\
\
; Enables or disables copying of PHP code (text segment) into HUGE PAGES.
\
; This should improve performance, but requires appropriate OS configuration.
\
;opcache.huge_code_pages=0
\
\
; Validate cached file permissions.
\
;opcache.validate_permission=0
\
\
; Prevent name collisions in chroot'ed environment.
\
;opcache.validate_root=0
\
\
; If specified, it produces opcode dumps for debugging different stages of
\
; optimizations.
\
;opcache.opt_debug_level=0
\
\
[curl]
\
; A default value for the CURLOPT_CAINFO option. This is required to be an
\
; absolute path.
\
curl.cainfo="C:\\xampp\\apache\\bin\\curl-ca-bundle.crt"
\
\
[openssl]
\
; The location of a Certificate Authority (CA) file on the local filesystem
\
; to use when verifying the identity of SSL/TLS peers. Most users should
\
; not specify a value for this directive as PHP will attempt to use the
\
; OS-managed cert stores in its absence. If specified, this value may still
\
; be overridden on a per-stream basis via the "cafile" SSL stream context
\
; option.
\
openssl.cafile="C:\\xampp\\apache\\bin\\curl-ca-bundle.crt"
\
\
; If openssl.cafile is not specified or if the CA file is not found, the
\
; directory pointed to by openssl.capath is searched for a suitable
\
; certificate. This value must be a correctly hashed certificate directory.
\
; Most users should not specify a value for this directive as PHP will
\
; attempt to use the OS-managed cert stores in its absence. If specified,
\
; this value may still be overridden on a per-stream basis via the "capath"
\
; SSL stream context option.
\
;openssl.capath=
\
\
; Local Variables:
\
; tab-width: 4
\
; End:
\
[Syslog]
\
define_syslog_variables=Off
\
[Session]
\
define_syslog_variables=Off
\
[Date]
\
date.timezone=Europe/Berlin
\
[MySQL]
\
mysql.allow_local_infile=On
\
mysql.allow_persistent=On
\
mysql.cache_size=2000
\
mysql.max_persistent=-1
\
mysql.max_link=-1
\
mysql.default_port=3306
\
mysql.default_socket="MySQL"
\
mysql.connect_timeout=3
\
mysql.trace_mode=Off
\
[Sybase-CT]
\
sybct.allow_persistent=On
\
sybct.max_persistent=-1
\
sybct.max_links=-1
\
sybct.min_server_severity=10
\
sybct.min_client_severity=10
\
[MSSQL]
\
mssql.allow_persistent=On
\
mssql.max_persistent=-1
\
mssql.max_links=-1
\
mssql.min_error_severity=10
\
mssql.min_message_severity=10
\
mssql.compatability_mode=Off
\
mssql.secure_connection=Off
\
}
Search found 9178 matches: mysql can%27t start
Searched query: +mysql +can +27t +start
XAMPP Server issues
Below is my my.cnf file . While connection the server my My SQL Database is getting stopped. Please help me
# Example MySQL config file for medium systems.
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /Applications/XAMPP/xamppfiles/var/mysql) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port =3308
socket =/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
default-character-set=utf8mb4
[mysqld]
innodb_force_recovery = 1
user=mysql
port=3308
socket =/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock
key_buffer_size=16M
max_allowed_packet=1M
table_open_cache=64
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=8M
# Where do all the plugins live
plugin_dir=/Applications/XAMPP/xamppfiles/lib/mysql/plugin/
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id =1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Point the following paths to different dedicated disks
tmpdir=/Applications/XAMPP/xamppfiles/temp/mysql
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir=/Applications/XAMPP/xamppfiles/var/mysql/
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_group_home_dir=/Applications/XAMPP/xamppfiles/var/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size=16M
# Deprecated in 5.6
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size=5M
innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_lock_wait_timeout=50
character-set-server=utf8mb4
collation-server=utf8mb4_general_ci
[mysqldump]
max_allowed_packet=16M
[mysql]
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer_size=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M
[myisamchk]
key_buffer_size=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M
[mysqlhotcopy]
# Example MySQL config file for medium systems.
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is /Applications/XAMPP/xamppfiles/var/mysql) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port =3308
socket =/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
default-character-set=utf8mb4
[mysqld]
innodb_force_recovery = 1
user=mysql
port=3308
socket =/Applications/XAMPP/xamppfiles/var/mysql/mysql.sock
key_buffer_size=16M
max_allowed_packet=1M
table_open_cache=64
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=8M
# Where do all the plugins live
plugin_dir=/Applications/XAMPP/xamppfiles/lib/mysql/plugin/
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Replication Master Server (default)
# binary logging is required for replication
# log-bin deactivated by default since XAMPP 1.4.11
#log-bin=mysql-bin
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id =1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Point the following paths to different dedicated disks
tmpdir=/Applications/XAMPP/xamppfiles/temp/mysql
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using BDB tables
#bdb_cache_size = 4M
#bdb_max_lock = 10000
# Comment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir=/Applications/XAMPP/xamppfiles/var/mysql/
innodb_data_file_path=ibdata1:10M:autoextend
innodb_log_group_home_dir=/Applications/XAMPP/xamppfiles/var/mysql/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size=16M
# Deprecated in 5.6
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size=5M
innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
innodb_lock_wait_timeout=50
character-set-server=utf8mb4
collation-server=utf8mb4_general_ci
[mysqldump]
max_allowed_packet=16M
[mysql]
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[isamchk]
key_buffer_size=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M
[myisamchk]
key_buffer_size=20M
sort_buffer_size=20M
read_buffer=2M
write_buffer=2M
[mysqlhotcopy]
- 10. June 2024 12:33
- Forum: XAMPP for macOS
- Topic: XAMPP Server issues
- Replies: 0
- Views: 292
XAAMPP Update
Ich bräuchte bitte Hilfe!
Ich wollte mein XAMPP auf den neuesten Stand bringen und habe es gemäß Anweisung deinstalliert, die neue Version 8.2.12 heruntergeladen und installiert. Hat auch funktioniert, aber MYSQL lässt sich nicht mehr starten.
Da ich bereits 82 Jahre alt bin und mit Beschäftigung am lokalen Server meinn Gehirn möglichst fit halten möchte, würde ich Hilfe sehr begrüßen. Ich vermute, dass ich den Port frei machen müsste, weiß aber nicht, wie das geht.
Schon mal vielen Dank im Voraus!!!
Hier die Meldung im Control Center:
13:08:00 [mysql] Fehler: MySQL wurde unerwartet beendet
13:08:00 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
13:08:00 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
13:08:00 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
13:08:00 [mysql] im Windows Event Viewer für weitere Hinweise
13:08:00 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
13:08:00 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.
und hier die Log-Datei
2024-06-07 13:07:11 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7884
2024-06-07 13:07:11 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:11 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:11 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:11 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:11 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:11 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:11 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:11 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-06-07 13:07:11 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:11 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-06-07 13:07:11 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:11 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:11 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:11 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:11 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-06-07 13:07:11 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:11 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:11 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:11 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:11
2024-06-07 13:07:11 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:11 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:11 0 [ERROR] Aborting
2024-06-07 13:07:43 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8112
2024-06-07 13:07:43 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:43 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:43 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:43 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:43 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:43 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:43 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:43 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:43 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:43 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:43 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:43 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:44 0 [Note] InnoDB: 10.4.32 started; log sequence number 300306; transaction id 170
2024-06-07 13:07:44 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:44 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:44 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:44
2024-06-07 13:07:44 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:44 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:44 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:44 0 [ERROR] Aborting
2024-06-07 13:07:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13672
2024-06-07 13:07:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:58 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:58 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:58 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:58 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:58 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 300315; transaction id 170
2024-06-07 13:07:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:58 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:58
2024-06-07 13:07:58 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:58 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:58 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:58 0 [ERROR] Aborting
Ich wollte mein XAMPP auf den neuesten Stand bringen und habe es gemäß Anweisung deinstalliert, die neue Version 8.2.12 heruntergeladen und installiert. Hat auch funktioniert, aber MYSQL lässt sich nicht mehr starten.
Da ich bereits 82 Jahre alt bin und mit Beschäftigung am lokalen Server meinn Gehirn möglichst fit halten möchte, würde ich Hilfe sehr begrüßen. Ich vermute, dass ich den Port frei machen müsste, weiß aber nicht, wie das geht.
Schon mal vielen Dank im Voraus!!!
Hier die Meldung im Control Center:
13:08:00 [mysql] Fehler: MySQL wurde unerwartet beendet
13:08:00 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
13:08:00 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
13:08:00 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
13:08:00 [mysql] im Windows Event Viewer für weitere Hinweise
13:08:00 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
13:08:00 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.
und hier die Log-Datei
2024-06-07 13:07:11 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7884
2024-06-07 13:07:11 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:11 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:11 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:11 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:11 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:11 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:11 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:11 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-06-07 13:07:11 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:11 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-06-07 13:07:11 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:11 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:11 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:11 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:11 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-06-07 13:07:11 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:11 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:11 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:11 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:11
2024-06-07 13:07:11 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:11 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:11 0 [ERROR] Aborting
2024-06-07 13:07:43 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8112
2024-06-07 13:07:43 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:43 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:43 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:43 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:43 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:43 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:43 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:43 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:43 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:43 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:43 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:43 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:44 0 [Note] InnoDB: 10.4.32 started; log sequence number 300306; transaction id 170
2024-06-07 13:07:44 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:44 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:44 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:44
2024-06-07 13:07:44 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:44 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:44 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:44 0 [ERROR] Aborting
2024-06-07 13:07:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13672
2024-06-07 13:07:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-06-07 13:07:58 0 [Note] InnoDB: Uses event mutexes
2024-06-07 13:07:58 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-06-07 13:07:58 0 [Note] InnoDB: Number of pools: 1
2024-06-07 13:07:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-06-07 13:07:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-06-07 13:07:58 0 [Note] InnoDB: Completed initialization of buffer pool
2024-06-07 13:07:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-06-07 13:07:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-06-07 13:07:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-06-07 13:07:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-06-07 13:07:58 0 [Note] InnoDB: Waiting for purge to start
2024-06-07 13:07:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 300315; transaction id 170
2024-06-07 13:07:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-06-07 13:07:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-06-07 13:07:58 0 [Note] InnoDB: Buffer pool(s) load completed at 240607 13:07:58
2024-06-07 13:07:58 0 [Note] Server socket created on IP: '::'.
2024-06-07 13:07:58 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 10013: Der Zugriff auf einen Socket war aufgrund der Zugriffsrechte des Sockets unzulässig.
2024-06-07 13:07:58 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2024-06-07 13:07:58 0 [ERROR] Aborting
- 07. June 2024 12:45
- Forum: XAMPP für Windows
- Topic: XAAMPP Update
- Replies: 1
- Views: 576
Re: mysql is not working on my xampp control panel.
I don't know if's related,iwas trying to upgrade the mysql(mariadb) inside of xampp but allways crash or not connect with error 10061,or if connect mariadb crash in server.dll with query timeout upon connection
After a lot of test upgrade it to only 11.0.2.
I change this fom cmd with "mysql -u user -p" "SET GLOBAL connect_timeout = 1800;" "SET GLOBAL wait_timeout = 1800;"
"SET GLOBAL interactive_timeout = 1800;", and got it working to the latest version in one pc,but the same zipped mysql inother not(i updated the ini before the start )
In resume, i increase the timeout of certain variables, unlock the files relevant(check by right click and properties), testing many locations, checkif the firewall allow mariadbd or mysqld to pass.
problems related to firewall, timeouts, or default data dir location error, or windows thinking the files are downloadedfrom the internet
After a lot of test upgrade it to only 11.0.2.
I change this fom cmd with "mysql -u user -p" "SET GLOBAL connect_timeout = 1800;" "SET GLOBAL wait_timeout = 1800;"
"SET GLOBAL interactive_timeout = 1800;", and got it working to the latest version in one pc,but the same zipped mysql inother not(i updated the ini before the start )
In resume, i increase the timeout of certain variables, unlock the files relevant(check by right click and properties), testing many locations, checkif the firewall allow mariadbd or mysqld to pass.
problems related to firewall, timeouts, or default data dir location error, or windows thinking the files are downloadedfrom the internet
- 03. June 2024 04:47
- Forum: XAMPP for Windows
- Topic: mysql is not working on my xampp control panel.
- Replies: 1
- Views: 607
PHP not writing to error log
Hi All, same for me. In the log files, I have this :
---
2024-05-14 12:55:06 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5532
2024-05-14 12:55:06 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-14 12:55:06 0 [Note] InnoDB: Uses event mutexes
2024-05-14 12:55:06 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-14 12:55:06 0 [Note] InnoDB: Number of pools: 1
2024-05-14 12:55:06 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-14 12:55:06 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-14 12:55:06 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-14 12:55:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-05-14 12:55:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-14 12:55:07 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-14 12:55:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-14 12:55:07 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-14 12:55:07 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-14 12:55:07 0 [Note] InnoDB: Waiting for purge to start
2024-05-14 12:55:07 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-05-14 12:55:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-14 12:55:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-14 12:55:07 0 [Note] Server socket created on IP: '::'.
2024-05-14 12:55:07 0 [Note] InnoDB: Buffer pool(s) load 2024-05-14 16:29:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14816
2024-05-14 16:29:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-14 16:29:25 0 [Note] InnoDB: Uses event mutexes
2024-05-14 16:29:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-14 16:29:25 0 [Note] InnoDB: Number of pools: 1
2024-05-14 16:29:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-14 16:29:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-14 16:29:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-14 16:29:25 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300306
2024-05-14 16:29:26 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2024-05-14 16:29:26 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-14 16:29:26 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-14 16:29:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-14 16:29:26 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-14 16:29:26 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-14 16:29:26 0 [Note] InnoDB: Waiting for purge to start
2024-05-14 16:29:26 0 [Note] InnoDB: 10.4.32 started; log sequence number 300675; transaction id 193
2024-05-14 16:29:26 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-14 16:29:26 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-14 16:29:26 0 [Note] InnoDB: Buffer pool(s) load completed at 240514 16:29:26
2024-05-14 16:29:26 0 [Note] Server socket created on IP: '::'.
2024-05-16 10:55:34 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8924
2024-05-16 10:55:34 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 20% 30%
Got error 176 when executing record redo_insert_row_head
2024-05-16 10:55:34 0 [ERROR] mysqld.exe: Aria engine: Redo phase failed
tables to flush: 2 1 0
2024-05-16 10:55:34 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2024-05-16 10:55:34 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2024-05-16 10:55:34 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 10:55:34 0 [Note] InnoDB: Uses event mutexes
2024-05-16 10:55:34 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 10:55:34 0 [Note] InnoDB: Number of pools: 1
2024-05-16 10:55:34 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 10:55:34 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 10:55:34 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 10:55:34 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=7857198
2024-05-16 10:55:34 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 10:55:34 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 10:55:34 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 10:55:34 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 10:55:34 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 10:55:34 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 10:55:34 0 [Note] InnoDB: 10.4.32 started; log sequence number 7857207; transaction id 6496
2024-05-16 10:55:34 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 10:55:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 10:55:34 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2024-05-16 10:55:34 0 [ERROR] Failed to initialize plugins.
2024-05-16 10:55:34 0 [ERROR] Aborting
2024-05-16 10:55:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8984
2024-05-16 10:55:50 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 20%
Table '.\mysql\db' is crashed, skipping it. Please repair it with aria_chk -r
30% 46% 60% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-16 10:55:50 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-16 10:55:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 10:55:50 0 [Note] InnoDB: Uses event mutexes
2024-05-16 10:55:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 10:55:50 0 [Note] InnoDB: Number of pools: 1
2024-05-16 10:55:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 10:55:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 10:55:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 10:55:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 10:55:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 10:55:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 10:55:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 10:55:50 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 10:55:50 0 [Note] InnoDB: 10.4.32 started; log sequence number 7857216; transaction id 6496
2024-05-16 10:55:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 10:55:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 10:55:50 0 [Note] InnoDB: Buffer pool(s) load completed at 240516 10:55:50
2024-05-16 10:55:50 0 [Note] Server socket created on IP: '::'.
2024-05-19 16:29:46 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7832
2024-05-19 16:29:46 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-19 16:29:46 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-19 16:29:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-19 16:29:46 0 [Note] InnoDB: Uses event mutexes
2024-05-19 16:29:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-19 16:29:46 0 [Note] InnoDB: Number of pools: 1
2024-05-19 16:29:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-19 16:29:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-19 16:29:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-19 16:29:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=34787403
2024-05-19 16:29:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-19 16:29:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-19 16:29:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-19 16:29:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-19 16:29:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-19 16:29:46 0 [Note] InnoDB: Waiting for purge to start
2024-05-19 16:29:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 34787412; transaction id 42487
2024-05-19 16:29:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-19 16:29:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-19 16:29:46 0 [Note] Server socket created on IP: '::'.
2024-052024-05-19 16:31:23 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13628
2024-05-19 16:31:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-19 16:31:23 0 [Note] InnoDB: Uses event mutexes
2024-05-19 16:31:23 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-19 16:31:23 0 [Note] InnoDB: Number of pools: 1
2024-05-19 16:31:23 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-19 16:31:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-19 16:31:23 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-19 16:31:23 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=34787403
2024-05-19 16:31:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-19 16:31:23 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-19 16:31:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-19 16:31:23 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-19 16:31:23 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-19 16:31:23 0 [Note] InnoDB: Waiting for purge to start
2024-05-19 16:31:23 0 [Note] InnoDB: 10.4.32 started; log sequence number 34787412; transaction id 42487
2024-05-19 16:31:23 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-19 16:31:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-19 16:31:23 0 [Note] Server socket created on IP: '::'.
2024-05-25 13:11:09 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4264
2024-05-25 13:11:09 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-25 13:11:09 0 [Note] InnoDB: Uses event mutexes
2024-05-25 13:11:09 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-25 13:11:09 0 [Note] InnoDB: Number of pools: 1
2024-05-25 13:11:09 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-25 13:11:09 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-25 13:11:09 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-25 13:11:09 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=87790645
2024-05-25 13:11:09 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-25 13:11:09 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-25 13:11:09 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-25 13:11:09 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-25 13:11:09 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-25 13:11:09 0 [Note] InnoDB: Waiting for purge to start
2024-05-25 13:11:09 0 [Note] InnoDB: 10.4.32 started; log sequence number 87790654; transaction id 79686
2024-05-25 13:11:09 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-25 13:11:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-25 13:11:09 0 [Note] InnoDB: Buffer pool(s) load completed at 240525 13:11:09
2024-05-25 13:11:09 0 [Note] Server socket created on IP: '::'.
2024-05-30 11:30:32 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14024
2024-05-30 11:30:32 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 22% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-30 11:30:32 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-30 11:30:32 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 11:30:32 0 [Note] InnoDB: Uses event mutexes
2024-05-30 11:30:32 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 11:30:32 0 [Note] InnoDB: Number of pools: 1
2024-05-30 11:30:32 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 11:30:32 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 11:30:32 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 11:30:32 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733484
2024-05-30 11:30:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 11:30:33 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 11:30:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 11:30:33 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 11:30:33 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 11:30:33 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 11:30:33 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733493; transaction id 88879
2024-05-30 11:30:33 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 11:30:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 11:30:33 0 [Note] InnoDB: Buffer pool(s) load completed at 240530 11:30:33
2024-05-30 11:30:33 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:27:21 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3996
2024-05-30 16:27:21 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:27:21 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:27:21 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:27:21 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:27:21 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:27:21 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:27:21 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:27:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:27:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:27:21 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:27:21 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:27:21 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:27:21 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733518; transaction id 88879
2024-05-30 16:27:21 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:27:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:27:21 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:27:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4356
2024-05-30 16:27:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:27:58 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:27:58 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:27:58 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:27:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:27:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:27:58 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:27:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:27:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:27:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:27:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:27:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733527; transaction id 88879
2024-05-30 16:27:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:27:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:27:58 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:30:46 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2036
2024-05-30 16:30:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:30:46 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:30:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:30:46 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:30:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:30:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:30:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:30:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:30:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:30:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:30:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:30:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733536; transaction id 88879
2024-05-30 16:30:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:30:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:30:46 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:32:36 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8940
2024-05-30 16:32:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:32:36 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:32:36 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:32:36 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:32:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:32:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:32:36 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:32:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:32:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:32:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:32:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:32:36 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:32:36 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733545; transaction id 88879
2024-05-30 16:32:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:32:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:32:36 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:40:49 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2380
2024-05-30 16:40:49 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:40:49 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:40:49 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:40:49 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:40:49 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:40:49 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:40:49 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:40:49 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733545
2024-05-30 16:40:49 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:40:49 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 16:40:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:40:49 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:40:49 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:40:49 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:40:49 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733554; transaction id 88879
2024-05-30 16:40:49 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:40:49 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:40:49 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:44:40 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3796
2024-05-30 16:44:40 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:44:40 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:44:40 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:44:40 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:44:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:44:40 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:44:40 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:44:40 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733545
2024-05-30 16:44:40 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 99733545, less than the log sequence number in the first system tablespace file header, 99733563.
2024-05-30 16:44:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:44:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 16:44:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:44:41 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:44:41 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:44:41 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:44:41 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733563; transaction id 88879
2024-05-30 16:44:41 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:44:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:44:41 0 [Note] Server socket created on IP: '::'.
2024-052024-05-30 16:44:48 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2636
2024-05-30 16:44:48 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:44:48 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:44:48 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:44:48 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:44:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:44:48 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:44:48 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:44:48 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:44:48 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:44:48 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:44:48 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:44:48 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:44:48 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733572; transaction id 88879
2024-05-30 16:44:48 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:44:48 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:44:48 0 [Note] Server socket created on IP: '::'.
2024-05-30 18:33:19 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5352
2024-05-30 18:33:19 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 18:33:19 0 [Note] InnoDB: Uses event mutexes
2024-05-30 18:33:19 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 18:33:19 0 [Note] InnoDB: Number of pools: 1
2024-05-30 18:33:19 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 18:33:19 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 18:33:19 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 18:33:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 18:33:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 18:33:19 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 18:33:19 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 18:33:19 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 18:33:19 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733581; transaction id 88879
2024-05-30 18:33:19 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 18:33:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 18:33:19 0 [Note] Server socket created on IP: '::'.
---
Thank you for help
---
2024-05-14 12:55:06 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5532
2024-05-14 12:55:06 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-14 12:55:06 0 [Note] InnoDB: Uses event mutexes
2024-05-14 12:55:06 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-14 12:55:06 0 [Note] InnoDB: Number of pools: 1
2024-05-14 12:55:06 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-14 12:55:06 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-14 12:55:06 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-14 12:55:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-05-14 12:55:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-14 12:55:07 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-14 12:55:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-14 12:55:07 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-14 12:55:07 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-14 12:55:07 0 [Note] InnoDB: Waiting for purge to start
2024-05-14 12:55:07 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-05-14 12:55:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-14 12:55:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-14 12:55:07 0 [Note] Server socket created on IP: '::'.
2024-05-14 12:55:07 0 [Note] InnoDB: Buffer pool(s) load 2024-05-14 16:29:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14816
2024-05-14 16:29:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-14 16:29:25 0 [Note] InnoDB: Uses event mutexes
2024-05-14 16:29:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-14 16:29:25 0 [Note] InnoDB: Number of pools: 1
2024-05-14 16:29:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-14 16:29:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-14 16:29:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-14 16:29:25 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300306
2024-05-14 16:29:26 0 [Note] InnoDB: Starting final batch to recover 1 pages from redo log.
2024-05-14 16:29:26 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-14 16:29:26 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-14 16:29:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-14 16:29:26 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-14 16:29:26 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-14 16:29:26 0 [Note] InnoDB: Waiting for purge to start
2024-05-14 16:29:26 0 [Note] InnoDB: 10.4.32 started; log sequence number 300675; transaction id 193
2024-05-14 16:29:26 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-14 16:29:26 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-14 16:29:26 0 [Note] InnoDB: Buffer pool(s) load completed at 240514 16:29:26
2024-05-14 16:29:26 0 [Note] Server socket created on IP: '::'.
2024-05-16 10:55:34 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8924
2024-05-16 10:55:34 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 20% 30%
Got error 176 when executing record redo_insert_row_head
2024-05-16 10:55:34 0 [ERROR] mysqld.exe: Aria engine: Redo phase failed
tables to flush: 2 1 0
2024-05-16 10:55:34 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
2024-05-16 10:55:34 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2024-05-16 10:55:34 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 10:55:34 0 [Note] InnoDB: Uses event mutexes
2024-05-16 10:55:34 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 10:55:34 0 [Note] InnoDB: Number of pools: 1
2024-05-16 10:55:34 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 10:55:34 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 10:55:34 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 10:55:34 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=7857198
2024-05-16 10:55:34 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 10:55:34 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 10:55:34 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 10:55:34 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 10:55:34 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 10:55:34 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 10:55:34 0 [Note] InnoDB: 10.4.32 started; log sequence number 7857207; transaction id 6496
2024-05-16 10:55:34 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 10:55:34 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 10:55:34 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2024-05-16 10:55:34 0 [ERROR] Failed to initialize plugins.
2024-05-16 10:55:34 0 [ERROR] Aborting
2024-05-16 10:55:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8984
2024-05-16 10:55:50 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 20%
Table '.\mysql\db' is crashed, skipping it. Please repair it with aria_chk -r
30% 46% 60% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-16 10:55:50 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-16 10:55:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 10:55:50 0 [Note] InnoDB: Uses event mutexes
2024-05-16 10:55:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 10:55:50 0 [Note] InnoDB: Number of pools: 1
2024-05-16 10:55:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 10:55:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 10:55:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 10:55:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 10:55:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 10:55:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 10:55:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 10:55:50 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 10:55:50 0 [Note] InnoDB: 10.4.32 started; log sequence number 7857216; transaction id 6496
2024-05-16 10:55:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 10:55:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 10:55:50 0 [Note] InnoDB: Buffer pool(s) load completed at 240516 10:55:50
2024-05-16 10:55:50 0 [Note] Server socket created on IP: '::'.
2024-05-19 16:29:46 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7832
2024-05-19 16:29:46 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-19 16:29:46 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-19 16:29:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-19 16:29:46 0 [Note] InnoDB: Uses event mutexes
2024-05-19 16:29:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-19 16:29:46 0 [Note] InnoDB: Number of pools: 1
2024-05-19 16:29:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-19 16:29:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-19 16:29:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-19 16:29:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=34787403
2024-05-19 16:29:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-19 16:29:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-19 16:29:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-19 16:29:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-19 16:29:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-19 16:29:46 0 [Note] InnoDB: Waiting for purge to start
2024-05-19 16:29:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 34787412; transaction id 42487
2024-05-19 16:29:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-19 16:29:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-19 16:29:46 0 [Note] Server socket created on IP: '::'.
2024-052024-05-19 16:31:23 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13628
2024-05-19 16:31:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-19 16:31:23 0 [Note] InnoDB: Uses event mutexes
2024-05-19 16:31:23 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-19 16:31:23 0 [Note] InnoDB: Number of pools: 1
2024-05-19 16:31:23 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-19 16:31:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-19 16:31:23 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-19 16:31:23 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=34787403
2024-05-19 16:31:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-19 16:31:23 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-19 16:31:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-19 16:31:23 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-19 16:31:23 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-19 16:31:23 0 [Note] InnoDB: Waiting for purge to start
2024-05-19 16:31:23 0 [Note] InnoDB: 10.4.32 started; log sequence number 34787412; transaction id 42487
2024-05-19 16:31:23 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-19 16:31:23 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-19 16:31:23 0 [Note] Server socket created on IP: '::'.
2024-05-25 13:11:09 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4264
2024-05-25 13:11:09 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-25 13:11:09 0 [Note] InnoDB: Uses event mutexes
2024-05-25 13:11:09 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-25 13:11:09 0 [Note] InnoDB: Number of pools: 1
2024-05-25 13:11:09 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-25 13:11:09 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-25 13:11:09 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-25 13:11:09 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=87790645
2024-05-25 13:11:09 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-25 13:11:09 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-25 13:11:09 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-25 13:11:09 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-25 13:11:09 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-25 13:11:09 0 [Note] InnoDB: Waiting for purge to start
2024-05-25 13:11:09 0 [Note] InnoDB: 10.4.32 started; log sequence number 87790654; transaction id 79686
2024-05-25 13:11:09 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-25 13:11:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-25 13:11:09 0 [Note] InnoDB: Buffer pool(s) load completed at 240525 13:11:09
2024-05-25 13:11:09 0 [Note] Server socket created on IP: '::'.
2024-05-30 11:30:32 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14024
2024-05-30 11:30:32 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0% 22% 100% (0.0 seconds); tables to flush: 1 0
(0.0 seconds);
2024-05-30 11:30:32 0 [Note] mysqld.exe: Aria engine: recovery done
2024-05-30 11:30:32 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 11:30:32 0 [Note] InnoDB: Uses event mutexes
2024-05-30 11:30:32 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 11:30:32 0 [Note] InnoDB: Number of pools: 1
2024-05-30 11:30:32 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 11:30:32 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 11:30:32 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 11:30:32 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733484
2024-05-30 11:30:33 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 11:30:33 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 11:30:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 11:30:33 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 11:30:33 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 11:30:33 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 11:30:33 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733493; transaction id 88879
2024-05-30 11:30:33 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 11:30:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 11:30:33 0 [Note] InnoDB: Buffer pool(s) load completed at 240530 11:30:33
2024-05-30 11:30:33 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:27:21 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3996
2024-05-30 16:27:21 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:27:21 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:27:21 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:27:21 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:27:21 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:27:21 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:27:21 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:27:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:27:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:27:21 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:27:21 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:27:21 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:27:21 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733518; transaction id 88879
2024-05-30 16:27:21 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:27:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:27:21 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:27:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4356
2024-05-30 16:27:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:27:58 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:27:58 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:27:58 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:27:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:27:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:27:58 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:27:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:27:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:27:58 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:27:58 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:27:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733527; transaction id 88879
2024-05-30 16:27:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:27:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:27:58 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:30:46 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2036
2024-05-30 16:30:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:30:46 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:30:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:30:46 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:30:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:30:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:30:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:30:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:30:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:30:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:30:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:30:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733536; transaction id 88879
2024-05-30 16:30:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:30:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:30:46 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:32:36 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 8940
2024-05-30 16:32:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:32:36 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:32:36 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:32:36 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:32:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:32:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:32:36 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:32:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:32:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:32:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:32:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:32:36 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:32:36 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733545; transaction id 88879
2024-05-30 16:32:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:32:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:32:36 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:40:49 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2380
2024-05-30 16:40:49 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:40:49 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:40:49 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:40:49 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:40:49 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:40:49 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:40:49 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:40:49 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733545
2024-05-30 16:40:49 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:40:49 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 16:40:49 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:40:49 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:40:49 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:40:49 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:40:49 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733554; transaction id 88879
2024-05-30 16:40:49 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:40:49 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:40:49 0 [Note] Server socket created on IP: '::'.
2024-05-30 16:44:40 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3796
2024-05-30 16:44:40 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:44:40 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:44:40 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:44:40 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:44:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:44:40 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:44:40 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:44:40 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=99733545
2024-05-30 16:44:40 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 99733545, less than the log sequence number in the first system tablespace file header, 99733563.
2024-05-30 16:44:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:44:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-30 16:44:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:44:41 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:44:41 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:44:41 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:44:41 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733563; transaction id 88879
2024-05-30 16:44:41 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:44:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:44:41 0 [Note] Server socket created on IP: '::'.
2024-052024-05-30 16:44:48 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2636
2024-05-30 16:44:48 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 16:44:48 0 [Note] InnoDB: Uses event mutexes
2024-05-30 16:44:48 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 16:44:48 0 [Note] InnoDB: Number of pools: 1
2024-05-30 16:44:48 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 16:44:48 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 16:44:48 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 16:44:48 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 16:44:48 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 16:44:48 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 16:44:48 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 16:44:48 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 16:44:48 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733572; transaction id 88879
2024-05-30 16:44:48 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 16:44:48 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 16:44:48 0 [Note] Server socket created on IP: '::'.
2024-05-30 18:33:19 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5352
2024-05-30 18:33:19 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-30 18:33:19 0 [Note] InnoDB: Uses event mutexes
2024-05-30 18:33:19 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-30 18:33:19 0 [Note] InnoDB: Number of pools: 1
2024-05-30 18:33:19 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-30 18:33:19 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-30 18:33:19 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-30 18:33:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-30 18:33:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-30 18:33:19 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-30 18:33:19 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-30 18:33:19 0 [Note] InnoDB: Waiting for purge to start
2024-05-30 18:33:19 0 [Note] InnoDB: 10.4.32 started; log sequence number 99733581; transaction id 88879
2024-05-30 18:33:19 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-30 18:33:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-30 18:33:19 0 [Note] Server socket created on IP: '::'.
---
Thank you for help
- 30. May 2024 19:43
- Forum: XAMPP for Windows
- Topic: PHP not writing to error log
- Replies: 0
- Views: 697
Re: corrution of aria table
Run (start & stop) the MySQL Server as a Windows Service (a little cross in the corresponding entry of the starting dialog). in most cases this resolves the issue.
Due to ease of use you should also run Apache as a Windows Service.
Starting and especially stopping MySQL manually via Xampp Control Dialog may lead to inconsistent data (for an unknown reason, probably uncleaned cache or similar).
Keep in mind, that a Windows Service is executed by System User (different from logged in user). That may affect certain rights (depending on your environment).
Due to ease of use you should also run Apache as a Windows Service.
Starting and especially stopping MySQL manually via Xampp Control Dialog may lead to inconsistent data (for an unknown reason, probably uncleaned cache or similar).
Keep in mind, that a Windows Service is executed by System User (different from logged in user). That may affect certain rights (depending on your environment).
- 30. May 2024 18:47
- Forum: XAMPP for Windows
- Topic: corrution of aria table
- Replies: 1
- Views: 1541
Re: Error: MySQL shutdown unexpectedly
Windows Event Viewer > Windows Logs > Application shows 3 Error messages and 18 Information messages
all messages show Source= MariaDB, Event ID= 100, Task Category= None
3 Error messages (shown in chronological order):
mysqld.exe: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
Fatal error: Can't open and lock privilege tables: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
Aborting
(following fix did not help)
[https://stackoverflow.com/questions/59410692/xampp-windows-mariadb-not-starting]
With the help of @RiggsFolly, the following solved my issue.
1. Open cmd.
2. In cmd, go to xampp/mysql/data folder.
In my case, I did the following cd C:\xampp\mysql\data
3. Run aria_chk -r in that directory for all .MAI tables in the mysql subfolder.
In my case, ..\bin\aria_chk -r mysql\*.MAI
4. Delete all aria_log.######## files. They are present in the C:\xampp\mysql\data folder.
I just renamed them for just in case (added old_ in the beginning of their names).
5. Start xampp again and it should be working.
-------
I followed these five steps.
c:\xampp\mysql\data>C:\xampp\mysql\bin\aria_chk -r
C:\xampp\mysql\bin\aria_chk Ver 1.2 for Win64 on AMD64
Used without options all tables on the command will be checked for errors
Usage: aria_chk [OPTIONS] tables[.MAI]
:
(verbose output)
:
c:\xampp\mysql\data>C:\xampp\mysql\bin\aria_chk
C:\xampp\mysql\bin\aria_chk Ver 1.2 for Win64 on AMD64
:
(verbose output)
:
c:\xampp\mysql\data>dir aria*
Volume in drive C has no label.
Directory of c:\xampp\mysql\data
2024-05-29 23:47 24,576 aria_log.00000001
2024-05-29 23:47 52 aria_log_control
c:\xampp\mysql\data>del aria*
c:\xampp\mysql\data>exit
Restart Xampp...
XAMPP Control Panel v3.3.0
12:16:37 AM [main] Initializing Control Panel
12:16:37 AM [main] Windows Version: Enterprise 64-bit
12:16:37 AM [main] XAMPP Version: 8.2.12
12:16:37 AM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
12:16:37 AM [main] Running with Administrator rights - good!
12:16:37 AM [main] XAMPP Installation Directory: "c:\xampp\"
12:16:37 AM [main] Checking for prerequisites
12:16:37 AM [main] All prerequisites found
12:16:37 AM [main] Initializing Modules
12:16:37 AM [main] Starting Check-Timer
12:16:37 AM [main] Control Panel Ready
12:16:52 AM [Apache] Attempting to start Apache app...
12:16:52 AM [Apache] Status change detected: running
12:17:04 AM [mysql] Attempting to start MySQL app...
12:17:04 AM [mysql] Status change detected: running
12:17:05 AM [mysql] Status change detected: stopped
12:17:05 AM [mysql] Error: MySQL shutdown unexpectedly.
12:17:05 AM [mysql] This may be due to a blocked port, missing dependencies,
12:17:05 AM [mysql] improper privileges, a crash, or a shutdown by another method.
12:17:05 AM [mysql] Press the Logs button to view error logs and check
12:17:05 AM [mysql] the Windows Event Viewer for more clues
12:17:05 AM [mysql] If you need more help, copy and post this
12:17:05 AM [mysql] entire log window on the forums
(fix did not help)
all messages show Source= MariaDB, Event ID= 100, Task Category= None
3 Error messages (shown in chronological order):
mysqld.exe: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
Fatal error: Can't open and lock privilege tables: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
Aborting
(following fix did not help)
[https://stackoverflow.com/questions/59410692/xampp-windows-mariadb-not-starting]
With the help of @RiggsFolly, the following solved my issue.
1. Open cmd.
2. In cmd, go to xampp/mysql/data folder.
In my case, I did the following cd C:\xampp\mysql\data
3. Run aria_chk -r in that directory for all .MAI tables in the mysql subfolder.
In my case, ..\bin\aria_chk -r mysql\*.MAI
4. Delete all aria_log.######## files. They are present in the C:\xampp\mysql\data folder.
I just renamed them for just in case (added old_ in the beginning of their names).
5. Start xampp again and it should be working.
-------
I followed these five steps.
c:\xampp\mysql\data>C:\xampp\mysql\bin\aria_chk -r
C:\xampp\mysql\bin\aria_chk Ver 1.2 for Win64 on AMD64
Used without options all tables on the command will be checked for errors
Usage: aria_chk [OPTIONS] tables[.MAI]
:
(verbose output)
:
c:\xampp\mysql\data>C:\xampp\mysql\bin\aria_chk
C:\xampp\mysql\bin\aria_chk Ver 1.2 for Win64 on AMD64
:
(verbose output)
:
c:\xampp\mysql\data>dir aria*
Volume in drive C has no label.
Directory of c:\xampp\mysql\data
2024-05-29 23:47 24,576 aria_log.00000001
2024-05-29 23:47 52 aria_log_control
c:\xampp\mysql\data>del aria*
c:\xampp\mysql\data>exit
Restart Xampp...
XAMPP Control Panel v3.3.0
12:16:37 AM [main] Initializing Control Panel
12:16:37 AM [main] Windows Version: Enterprise 64-bit
12:16:37 AM [main] XAMPP Version: 8.2.12
12:16:37 AM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
12:16:37 AM [main] Running with Administrator rights - good!
12:16:37 AM [main] XAMPP Installation Directory: "c:\xampp\"
12:16:37 AM [main] Checking for prerequisites
12:16:37 AM [main] All prerequisites found
12:16:37 AM [main] Initializing Modules
12:16:37 AM [main] Starting Check-Timer
12:16:37 AM [main] Control Panel Ready
12:16:52 AM [Apache] Attempting to start Apache app...
12:16:52 AM [Apache] Status change detected: running
12:17:04 AM [mysql] Attempting to start MySQL app...
12:17:04 AM [mysql] Status change detected: running
12:17:05 AM [mysql] Status change detected: stopped
12:17:05 AM [mysql] Error: MySQL shutdown unexpectedly.
12:17:05 AM [mysql] This may be due to a blocked port, missing dependencies,
12:17:05 AM [mysql] improper privileges, a crash, or a shutdown by another method.
12:17:05 AM [mysql] Press the Logs button to view error logs and check
12:17:05 AM [mysql] the Windows Event Viewer for more clues
12:17:05 AM [mysql] If you need more help, copy and post this
12:17:05 AM [mysql] entire log window on the forums
(fix did not help)
- 30. May 2024 05:19
- Forum: XAMPP for Windows
- Topic: Error: MySQL shutdown unexpectedly
- Replies: 2
- Views: 1341
Error: MySQL shutdown unexpectedly
I cannot find this problem in this forum (search is "not available at this time"). Note Apache and MySQL were running fine up until tonight.
Tonight when I try to Start MySQL, I get this error "MySQL shutdown unexpectedly". Here are the pertinent logs. Please can someone point me to documentation on how to fix this problem? TIA
Installed XAMPP for Windows 8.2.12 on May 26. Used Apache and MySQL just fine until tonight (May 29).
Reboot Windows 10 Pro version 22H2 OS Build 19045.4412
XAMPP Control Panel v3.3.0
10:52:35 PM [main] Initializing Control Panel
10:52:35 PM [main] Windows Version: Enterprise 64-bit
10:52:35 PM [main] XAMPP Version: 8.2.12
10:52:35 PM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
10:52:35 PM [main] Running with Administrator rights - good!
10:52:35 PM [main] XAMPP Installation Directory: "c:\xampp\"
10:52:35 PM [main] Checking for prerequisites
10:52:38 PM [main] All prerequisites found
10:52:38 PM [main] Initializing Modules
10:52:38 PM [main] Starting Check-Timer
10:52:38 PM [main] Control Panel Ready
10:52:54 PM [Apache] Attempting to start Apache app...
10:52:54 PM [Apache] Status change detected: running
10:53:08 PM [mysql] Attempting to start MySQL app...
10:53:08 PM [mysql] Status change detected: running
10:53:10 PM [mysql] Status change detected: stopped
10:53:10 PM [mysql] Error: MySQL shutdown unexpectedly.
10:53:10 PM [mysql] This may be due to a blocked port, missing dependencies,
10:53:10 PM [mysql] improper privileges, a crash, or a shutdown by another method.
10:53:10 PM [mysql] Press the Logs button to view error logs [see below]
10:53:10 PM [mysql] and check the Windows Event Viewer for more clues
10:53:10 PM [mysql] If you need more help, copy and post this
10:53:10 PM [mysql] entire log window on the forums [this post!]
mysql_error.log
2024-05-29 22:53:08 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 716
2024-05-29 22:53:08 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-29 22:53:08 0 [Note] InnoDB: Uses event mutexes
2024-05-29 22:53:08 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-29 22:53:08 0 [Note] InnoDB: Number of pools: 1
2024-05-29 22:53:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-29 22:53:08 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-29 22:53:08 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-29 22:53:08 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-29 22:53:08 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-29 22:53:08 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-29 22:53:08 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-29 22:53:08 0 [Note] InnoDB: Waiting for purge to start
2024-05-29 22:53:09 0 [Note] InnoDB: 10.4.32 started; log sequence number 408752; transaction id 348
2024-05-29 22:53:09 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-29 22:53:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-29 22:53:09 0 [Note] Server socket created on IP: '::'.
Tonight when I try to Start MySQL, I get this error "MySQL shutdown unexpectedly". Here are the pertinent logs. Please can someone point me to documentation on how to fix this problem? TIA
Installed XAMPP for Windows 8.2.12 on May 26. Used Apache and MySQL just fine until tonight (May 29).
Reboot Windows 10 Pro version 22H2 OS Build 19045.4412
XAMPP Control Panel v3.3.0
10:52:35 PM [main] Initializing Control Panel
10:52:35 PM [main] Windows Version: Enterprise 64-bit
10:52:35 PM [main] XAMPP Version: 8.2.12
10:52:35 PM [main] Control Panel Version: 3.3.0 [ Compiled: Apr 6th 2021 ]
10:52:35 PM [main] Running with Administrator rights - good!
10:52:35 PM [main] XAMPP Installation Directory: "c:\xampp\"
10:52:35 PM [main] Checking for prerequisites
10:52:38 PM [main] All prerequisites found
10:52:38 PM [main] Initializing Modules
10:52:38 PM [main] Starting Check-Timer
10:52:38 PM [main] Control Panel Ready
10:52:54 PM [Apache] Attempting to start Apache app...
10:52:54 PM [Apache] Status change detected: running
10:53:08 PM [mysql] Attempting to start MySQL app...
10:53:08 PM [mysql] Status change detected: running
10:53:10 PM [mysql] Status change detected: stopped
10:53:10 PM [mysql] Error: MySQL shutdown unexpectedly.
10:53:10 PM [mysql] This may be due to a blocked port, missing dependencies,
10:53:10 PM [mysql] improper privileges, a crash, or a shutdown by another method.
10:53:10 PM [mysql] Press the Logs button to view error logs [see below]
10:53:10 PM [mysql] and check the Windows Event Viewer for more clues
10:53:10 PM [mysql] If you need more help, copy and post this
10:53:10 PM [mysql] entire log window on the forums [this post!]
mysql_error.log
2024-05-29 22:53:08 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 716
2024-05-29 22:53:08 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-29 22:53:08 0 [Note] InnoDB: Uses event mutexes
2024-05-29 22:53:08 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-29 22:53:08 0 [Note] InnoDB: Number of pools: 1
2024-05-29 22:53:08 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-29 22:53:08 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-29 22:53:08 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-29 22:53:08 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-29 22:53:08 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-29 22:53:08 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-29 22:53:08 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-29 22:53:08 0 [Note] InnoDB: Waiting for purge to start
2024-05-29 22:53:09 0 [Note] InnoDB: 10.4.32 started; log sequence number 408752; transaction id 348
2024-05-29 22:53:09 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-29 22:53:09 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-29 22:53:09 0 [Note] Server socket created on IP: '::'.
- 30. May 2024 04:34
- Forum: XAMPP for Windows
- Topic: Error: MySQL shutdown unexpectedly
- Replies: 2
- Views: 1341
Re: Running as a non-admin user
Ernestfady33 wrote:Why cant you run the database 24/7?
Because they WANT(!) to use the "manager-osx" (a tool delivered from Xampp), which is a GUI for starting/stopping the related servers. And there every single user has to login/logout (on a daily base at least), which means a shutdown of all related servers. Its not a technical issue, neither a bug. Its simply missing knowledge how to stop/start all the servers (including Apache, MySQL) by an admin via boot scripts or similar instead of using "manager-osx". Its that easy.
- 28. May 2024 14:52
- Forum: XAMPP for macOS
- Topic: Running as a non-admin user
- Replies: 7
- Views: 3614
Re: Re-instating copies of htdocs and mysql data
Thank you very much for answer.
I am just trying to repare local install (I know I can reinstall xampp, create clean local wordpress install and than migrate back to local from my live site).
I am using local install which is than migrated to live web from time to time using wordpress migrate plugin. I have made some changes in local posts, but next day when trying to start xampp mysql there was above mentioned error before sync to web.
I wonder if (how) I could avoid this in the future, my idea was to sync relevant xampp folders to external drive, which could be quite fast to recover (in case of such error simple rewrite from last folders sync).
I am just trying to repare local install (I know I can reinstall xampp, create clean local wordpress install and than migrate back to local from my live site).
I am using local install which is than migrated to live web from time to time using wordpress migrate plugin. I have made some changes in local posts, but next day when trying to start xampp mysql there was above mentioned error before sync to web.
I wonder if (how) I could avoid this in the future, my idea was to sync relevant xampp folders to external drive, which could be quite fast to recover (in case of such error simple rewrite from last folders sync).
- 22. May 2024 10:23
- Forum: XAMPP for Windows
- Topic: Re-instating copies of htdocs and mysql data
- Replies: 2
- Views: 767
mysql wird ständig beendet
2024-05-22 9:41:46 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7260
2024-05-22 9:41:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 9:41:46 0 [Note] InnoDB: Uses event mutexes
2024-05-22 9:41:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 9:41:46 0 [Note] InnoDB: Number of pools: 1
2024-05-22 9:41:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 9:41:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 9:41:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 9:41:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 9:41:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 9:41:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 9:41:46 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 9:41:46 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607938; transaction id 1468
2024-05-22 9:41:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 9:41:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 9:41:46 0 [Note] Server socket created on IP: '::'.
2024-05-22 9:45:45 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13672
2024-05-22 9:45:45 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 9:45:45 0 [Note] InnoDB: Uses event mutexes
2024-05-22 9:45:45 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 9:45:45 0 [Note] InnoDB: Number of pools: 1
2024-05-22 9:45:45 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 9:45:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 9:45:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 9:45:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 9:45:45 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 9:45:45 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 9:45:45 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 9:45:45 4 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607947; transaction id 1468
2024-05-22 9:45:45 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 9:45:45 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 9:45:45 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:04:53 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6568
2024-05-22 10:04:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:04:53 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:04:53 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:04:53 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:04:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:04:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:04:53 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:54 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:04:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:04:54 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:04:54 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:04:54 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:04:54 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:54 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:54 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607956; transaction id 1468
2024-05-22 10:04:54 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:04:54 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:04:54 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:16:18 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3332
2024-05-22 10:16:18 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:16:18 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:16:18 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:16:18 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:16:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:16:18 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:16:18 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:16:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:16:19 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:16:19 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:16:19 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:16:19 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:19 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:19 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607965; transaction id 1468
2024-05-22 10:16:19 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:16:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:16:19 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:17:20 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5924
2024-05-22 10:17:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:17:20 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:17:20 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:17:20 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:17:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:17:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:17:20 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:17:21 0 [Note] InnoDB: The log sequence number 2607974 in the system tablespace does not match the log sequence number 2607965 in the ib_logfiles!
2024-05-22 10:17:21 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=57] with future log sequence number 2613791
2024-05-22 10:17:21 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=321] with future log sequence number 2613791
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:17:21 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-22 10:17:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:17:21 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:17:21 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:17:21 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:17:21 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607965; transaction id 1468
2024-05-22 10:17:21 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:17:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:17:21 0 [Note] Server socket created on IP: '::'.
Das sind die Errors aus dem Log ich bräuchte bitte hilfe damit ich wieder schnelst möglich an meinem server arbeiten kann.
MfG. Simon
2024-05-22 9:41:46 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 9:41:46 0 [Note] InnoDB: Uses event mutexes
2024-05-22 9:41:46 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 9:41:46 0 [Note] InnoDB: Number of pools: 1
2024-05-22 9:41:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 9:41:46 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 9:41:46 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 9:41:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 9:41:46 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 9:41:46 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 9:41:46 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 9:41:46 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607947.
2024-05-22 9:41:46 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:41:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607938; transaction id 1468
2024-05-22 9:41:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 9:41:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 9:41:46 0 [Note] Server socket created on IP: '::'.
2024-05-22 9:45:45 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 13672
2024-05-22 9:45:45 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 9:45:45 0 [Note] InnoDB: Uses event mutexes
2024-05-22 9:45:45 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 9:45:45 0 [Note] InnoDB: Number of pools: 1
2024-05-22 9:45:45 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 9:45:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 9:45:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 9:45:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 9:45:45 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 9:45:45 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 9:45:45 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 9:45:45 4 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607956.
2024-05-22 9:45:45 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 9:45:45 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607947; transaction id 1468
2024-05-22 9:45:45 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 9:45:45 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 9:45:45 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:04:53 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6568
2024-05-22 10:04:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:04:53 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:04:53 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:04:53 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:04:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:04:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:04:53 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:53 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:54 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:04:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:04:54 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:04:54 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:04:54 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:04:54 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607965.
2024-05-22 10:04:54 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:04:54 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607956; transaction id 1468
2024-05-22 10:04:54 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:04:54 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:04:54 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:16:18 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3332
2024-05-22 10:16:18 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:16:18 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:16:18 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:16:18 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:16:18 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:16:18 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:16:18 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:18 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:19 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:16:19 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:16:19 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:16:19 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:16:19 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:16:19 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607974.
2024-05-22 10:16:19 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:16:19 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607965; transaction id 1468
2024-05-22 10:16:19 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:16:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:16:19 0 [Note] Server socket created on IP: '::'.
2024-05-22 10:17:20 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 5924
2024-05-22 10:17:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-22 10:17:20 0 [Note] InnoDB: Uses event mutexes
2024-05-22 10:17:20 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-22 10:17:20 0 [Note] InnoDB: Number of pools: 1
2024-05-22 10:17:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-22 10:17:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-22 10:17:20 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-22 10:17:21 0 [Note] InnoDB: The log sequence number 2607974 in the system tablespace does not match the log sequence number 2607965 in the ib_logfiles!
2024-05-22 10:17:21 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=57] with future log sequence number 2613791
2024-05-22 10:17:21 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=321] with future log sequence number 2613791
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=316] log sequence number 2608276 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=317] log sequence number 2608688 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=319] log sequence number 2609186 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 2611511 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 2611511 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 2613791 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=321] log sequence number 2613791 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 2616141 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=323] log sequence number 2616141 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 2618482 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=324] log sequence number 2618482 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 2620878 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=325] log sequence number 2620878 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 2621358 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=326] log sequence number 2621358 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 2622318 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=328] log sequence number 2622318 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 2622803 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 2622803 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 2623304 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Page [page id: space=0, page number=331] log sequence number 2623304 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-22 10:17:21 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-22 10:17:21 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-22 10:17:21 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-22 10:17:21 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-22 10:17:21 0 [Note] InnoDB: Waiting for purge to start
2024-05-22 10:17:21 3 [ERROR] InnoDB: Page [page id: space=85, page number=3] log sequence number 2623324 is in the future! Current system log sequence number 2607974.
2024-05-22 10:17:21 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-22 10:17:21 0 [Note] InnoDB: 10.4.32 started; log sequence number 2607965; transaction id 1468
2024-05-22 10:17:21 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-22 10:17:21 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-22 10:17:21 0 [Note] Server socket created on IP: '::'.
Das sind die Errors aus dem Log ich bräuchte bitte hilfe damit ich wieder schnelst möglich an meinem server arbeiten kann.
MfG. Simon
- 22. May 2024 09:30
- Forum: XAMPP für Windows
- Topic: mysql wird ständig beendet
- Replies: 1
- Views: 837
Re-instating copies of htdocs and mysql data
Hi, I cannot start mysql server. Have tried to change port numbers, which did not help.
I decided to backup the whole xampp folder to externral disc, unistall and install xampp again (which solved port/sql server start issue).
Would it be possible to somehow "copy" to this new installation my wordpress site located in htdocs/* and mysql/data* folders?
Thank you very much.
I decided to backup the whole xampp folder to externral disc, unistall and install xampp again (which solved port/sql server start issue).
Would it be possible to somehow "copy" to this new installation my wordpress site located in htdocs/* and mysql/data* folders?
Thank you very much.
- 22. May 2024 08:58
- Forum: XAMPP for Windows
- Topic: Re-instating copies of htdocs and mysql data
- Replies: 2
- Views: 767
Hi i have a problem
I need to download Xampp to start using MySQL Workbench at school, but for some reason, whenever I want to use it, I can't because Xampp downloads the 32-bit version even though I have the 64-bit installer. I have downloaded it multiple times from different versions, but whenever I start the download, it installs the 32-bit version instead of the 64-bit one. Can help me? I'm just starting university with this ;— pls pls pls
Does anyone know how to fix that problem? or another way to
use MySQL workbench without Xampp?
Does anyone know how to fix that problem? or another way to
use MySQL workbench without Xampp?
- 21. May 2024 10:27
- Forum: XAMPP for Windows
- Topic: Hi i have a problem
- Replies: 1
- Views: 840
Re: Error: Apache shutdown unexpectedly.
Altrea wrote:what is the output of the apache_start.bat script?
Hi there!
Sorry for the late reply. I was struggling a long time with this, but I found out what was the issue. What I did was the following:
1) I downloaded the XAMPP portable version as a zip file
2) I unzipped the file and placed the folder in some custom folder structure
3) I couldn't understand why I got these error messages when I tried to start Apache / MySQL
4) I did try to start Apache and MySQL from the Control Panel. After some troubleshooting I tried to start the two modules with the apache_start.bat and mysql_start.bat files directly instead. Then I got a clue that the paths defined in the configuration files was not correct.
5) I ran the setup_xampp.bat, so the folder settings was configured to point at the custom folder ... and voila everything worked as it should.
If anyone else reads this; As far as I have understood this, the portable version comes with some default paths set in the configuration files. If you run the installer those paths will probably (?) be set during that process. If you just download the .zip file instead and does not run the software from the default location, you need to run the setup_xampp.bat file first.
I am pretty sure this is a common misunderstanding for several people using XAMPP, so hopefully my post can also help someone else that had missed this detail.
Cheers.
- 20. May 2024 01:52
- Forum: XAMPP for Windows
- Topic: Error: Apache shutdown unexpectedly.
- Replies: 3
- Views: 1448
MySQL Error
Unable to Run XAMPP Control Panel on my Windows 64bit OS ( XAMPP Version:8.2.12
I am getting MySQL error ( Error:MySQL shutdown unexpectedly. This may be due to a blocked port, missing dependencies)
I tried replacing the corrupted data file with a new one still not working.I have the Log errors which is pasted below:-
Would appreciate a reply
2024-05-16 18:50:57 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14020
2024-05-16 18:50:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:50:57 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:50:57 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:50:57 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:50:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:50:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:50:57 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:50:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-05-16 18:50:57 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 300288, less than the log sequence number in the first system tablespace file header, 300522.
2024-05-16 18:50:57 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:50:57 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:50:57 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:50:57 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:50:57 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:50:57 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-05-16 18:50:57 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:50:57 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:50:57 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: Buffer pool(s) load completed at 240516 18:50:57
2024-05-16 18:50:57 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 11044
2024-05-16 18:51:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300306; transaction id 170
2024-05-16 18:51:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:04 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 9324
2024-05-16 18:51:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:04 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:04 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:04 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:04 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:04 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:04 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:04 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:04 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] InnoDB: 10.4.32 started; log sequence number 300315; transaction id 170
2024-05-16 18:51:05 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:12 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2360
2024-05-16 18:51:12 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:12 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:12 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:12 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:12 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:12 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:12 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:12 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:12 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:12 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:12 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] InnoDB: 10.4.32 started; log sequence number 300324; transaction id 170
2024-05-16 18:51:12 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:15 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4868
2024-05-16 18:51:15 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:15 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:15 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:15 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:15 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:15 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:15 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:15 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:15 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:15 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] InnoDB: 10.4.32 started; log sequence number 300333; transaction id 170
2024-05-16 18:51:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6888
2024-05-16 18:51:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:25 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:25 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:25 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:25 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:25 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:25 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] InnoDB: 10.4.32 started; log sequence number 300342; transaction id 170
2024-05-16 18:51:25 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:45 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 12396
2024-05-16 18:51:45 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:45 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:45 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:45 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:45 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:45 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:45 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:45 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7060
2024-05-16 18:51:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:50 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:50 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:50 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:51:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:50 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:53 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6548
2024-05-16 18:51:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:53 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:53 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:53 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:53 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:53 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:53 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:53 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] InnoDB: 10.4.32 started; log sequence number 300360; transaction id 170
2024-05-16 18:51:54 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:54 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3908
2024-05-16 18:51:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:59 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:59 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:59 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:59 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:59 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:59 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] InnoDB: 10.4.32 started; log sequence number 300369; transaction id 170
2024-05-16 18:51:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 17684
2024-05-16 18:52:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300378; transaction id 170
2024-05-16 18:52:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:36 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18332
2024-05-16 18:52:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:36 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:36 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:36 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:36 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:36 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] InnoDB: 10.4.32 started; log sequence number 300387; transaction id 170
2024-05-16 18:52:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] Server socket created on IP: '::'.
I am getting MySQL error ( Error:MySQL shutdown unexpectedly. This may be due to a blocked port, missing dependencies)
I tried replacing the corrupted data file with a new one still not working.I have the Log errors which is pasted below:-
Would appreciate a reply
2024-05-16 18:50:57 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 14020
2024-05-16 18:50:57 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:50:57 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:50:57 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:50:57 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:50:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:50:57 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:50:57 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:50:57 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2024-05-16 18:50:57 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 300288, less than the log sequence number in the first system tablespace file header, 300522.
2024-05-16 18:50:57 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:50:57 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:50:57 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:50:57 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:50:57 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:50:57 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: 10.4.32 started; log sequence number 300297; transaction id 170
2024-05-16 18:50:57 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:50:57 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:50:57 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300306.
2024-05-16 18:50:57 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:50:57 0 [Note] InnoDB: Buffer pool(s) load completed at 240516 18:50:57
2024-05-16 18:50:57 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 11044
2024-05-16 18:51:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300306; transaction id 170
2024-05-16 18:51:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300315.
2024-05-16 18:51:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:04 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 9324
2024-05-16 18:51:04 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:04 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:04 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:04 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:04 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:04 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:04 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:04 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:04 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:04 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:04 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:04 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:04 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] InnoDB: 10.4.32 started; log sequence number 300315; transaction id 170
2024-05-16 18:51:05 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300324.
2024-05-16 18:51:05 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:05 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:12 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2360
2024-05-16 18:51:12 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:12 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:12 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:12 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:12 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:12 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:12 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:12 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:12 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:12 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:12 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] InnoDB: 10.4.32 started; log sequence number 300324; transaction id 170
2024-05-16 18:51:12 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300333.
2024-05-16 18:51:12 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:12 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:15 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 4868
2024-05-16 18:51:15 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:15 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:15 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:15 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:15 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:15 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:15 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:15 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:15 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:15 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:15 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] InnoDB: 10.4.32 started; log sequence number 300333; transaction id 170
2024-05-16 18:51:15 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300342.
2024-05-16 18:51:15 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:15 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:25 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6888
2024-05-16 18:51:25 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:25 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:25 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:25 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:25 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:25 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:25 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:25 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:25 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:25 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:25 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:25 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] InnoDB: 10.4.32 started; log sequence number 300342; transaction id 170
2024-05-16 18:51:25 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300351.
2024-05-16 18:51:25 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:25 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:45 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 12396
2024-05-16 18:51:45 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:45 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:45 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:45 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:45 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:45 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:45 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:45 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:45 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:45 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:45 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:45 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:45 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:46 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:46 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:46 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:50 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 7060
2024-05-16 18:51:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:50 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:50 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:50 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:50 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:50 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2024-05-16 18:51:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:50 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] InnoDB: 10.4.32 started; log sequence number 300351; transaction id 170
2024-05-16 18:51:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:50 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300360.
2024-05-16 18:51:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:50 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:53 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 6548
2024-05-16 18:51:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:53 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:53 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:53 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:53 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:53 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:53 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:53 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:53 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] InnoDB: 10.4.32 started; log sequence number 300360; transaction id 170
2024-05-16 18:51:54 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:54 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300369.
2024-05-16 18:51:54 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:54 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:51:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 3908
2024-05-16 18:51:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:51:59 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:51:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:51:59 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:51:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:51:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:51:59 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:51:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:51:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:51:59 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:51:59 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:51:59 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 4 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] InnoDB: 10.4.32 started; log sequence number 300369; transaction id 170
2024-05-16 18:51:59 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:51:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300378.
2024-05-16 18:51:59 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:51:59 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:02 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 17684
2024-05-16 18:52:02 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:02 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:02 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:02 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:02 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:02 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:02 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:02 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] InnoDB: 10.4.32 started; log sequence number 300378; transaction id 170
2024-05-16 18:52:02 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300387.
2024-05-16 18:52:02 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:02 0 [Note] Server socket created on IP: '::'.
2024-05-16 18:52:36 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 18332
2024-05-16 18:52:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-05-16 18:52:36 0 [Note] InnoDB: Uses event mutexes
2024-05-16 18:52:36 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-05-16 18:52:36 0 [Note] InnoDB: Number of pools: 1
2024-05-16 18:52:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-05-16 18:52:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-05-16 18:52:36 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-16 18:52:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-05-16 18:52:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-05-16 18:52:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-05-16 18:52:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-05-16 18:52:36 0 [Note] InnoDB: Waiting for purge to start
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 257117461 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 257117401 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] InnoDB: 10.4.32 started; log sequence number 300387; transaction id 170
2024-05-16 18:52:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-05-16 18:52:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 41555624 is in the future! Current system log sequence number 300396.
2024-05-16 18:52:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-05-16 18:52:36 0 [Note] Server socket created on IP: '::'.
- 16. May 2024 14:47
- Forum: XAMPP for Windows
- Topic: MySQL Error
- Replies: 2
- Views: 1072