BFA - 1. Database issue.

Request/Answer help topics.
Post Reply
User avatar
Katsuhito
Posts: 2

BFA - 1. Database issue.

Post by Katsuhito » Sun Aug 25, 2019 12:08 pm

So this is really annoying me....

Following the step by step in the newest BFA Repack/SPP and when trying the database, i keep hitting errors before it closes, this is what i could quickly grab before it shut down



08-25 13:03:13 26836 [Note] H:\WoW-BFA Main\SPP-BFA\SPP-BFA\Server\Database\bin\mysqld (mysqld 10.1.36-MariaDB) starting as process 26568 ...
2019-08-25 13:03:13 26836 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-08-25 13:03:13 26836 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-08-25 13:03:13 26836 [Note] InnoDB: The InnoDB memory heap is disabled
2019-08-25 13:03:13 26836 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-08-25 13:03:13 26836 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-08-25 13:03:13 26836 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-08-25 13:03:13 26836 [Note] InnoDB: Using generic crc32 instructions
2019-08-25 13:03:13 26836 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-08-25 13:03:13 26836 [Note] InnoDB: Completed initialization of buffer pool
2019-08-25 13:03:13 68d4 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/ ... codes.html
InnoDB: Operation close to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 2493
2019-08-25 13:03:13 26836 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
190825 13:03:13 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.36-MariaDB
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2196544 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


Any help would be nice please :/



User avatar
conan513
Site Admin
Posts: 123
Location: Hungary
x 27
Conan’s avatar
Online

Re: BFA - 1. Database issue.

Post by conan513 » Sun Aug 25, 2019 6:32 pm

Umm are you using Windows 64 bit version?

User avatar
Katsuhito
Posts: 2

Re: BFA - 1. Database issue.

Post by Katsuhito » Mon Aug 26, 2019 2:02 am

I do use that aye

Edited: I would add a DxDiag but cant add txt or word documents as attachments and to copy and paste its too long for the reply box to hold lol

Post Reply