-
-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mysql cannot working with fs=ramfs #975
Comments
i found the root cause, is that when use ramfs , all the file permission is change to "777", it works when i modify the mysql code to not adjust the permission, key_buffer_size=16384 Thread pointer: 0xffff80013dc2c040 Trying to get some variables. [backtrace] " |
Your second report is a different issue, and you please try to reproduce it without any "fs=..." parameter, and report it as a separate issue? It will be hard to solve this without debugging mysql and trying to understand if mysql itself has a bug, or somehow got misled by OSv (note that the crash is in mysql code, not in OSv code). We did test mysql on OSv in the past and didn't see these errors, but since then all of mysql, OSv and the compilers, have changed, so there may have been some regression. |
@yuwang888 I think this issue can be closed. We have fixed number of ramfs bugs that may have caused this crash: Also I have added
|
i use fs=ramfs to build the mysql
#./scripts/build image=mysql fs=ramfs
#./scripts/run.py -nv
but mysql can not work well
#mysql -h 192.168.122.76 -u root
ERROR 1130 (HY000): Host '192.168.122.1' is not allowed to connect to this MySQL server
the log i found
Warning: World-writable config file '/etc/my.cnf' is ignored
but ls -l /etc/my.cnf is 644
"
Warning: World-writable config file '/etc/my.cnf' is ignored
2018-05-22 12:45:11 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-05-22 12:45:11 0 [Note] Plugin 'FEDERATED' is disabled.
2018-05-22 12:45:11 0 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-05-22 12:45:11 0 [Note] InnoDB: The InnoDB memory heap is disabled
2018-05-22 12:45:11 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-22 12:45:11 0 [Note] InnoDB: Memory barrier is not used
2018-05-22 12:45:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-05-22 12:45:11 0 [Note] InnoDB: Using CPU crc32 instructions
2018-05-22 12:45:11 0 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-05-22 12:45:11 0 [Note] InnoDB: Completed initialization of buffer pool
WARNING: fcntl(F_SETLK) stubbed
2018-05-22 12:45:11 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-05-22 12:45:11 0 [Note] InnoDB: 128 rollback segment(s) are active.
2018-05-22 12:45:11 0 [Note] InnoDB: 5.6.21 started; log sequence number 1625997
2018-05-22 12:45:11 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: f74e65b2-5dbd-11e8-80cd-525400123456.
2018-05-22 12:45:11 0 [Note] Server hostname (bind-address): '*'; port: 3306
2018-05-22 12:45:11 0 [Note] IPv6 is not available.
2018-05-22 12:45:11 0 [Note] - '0.0.0.0' resolves to '0.0.0.0';
2018-05-22 12:45:11 0 [Note] Server socket created on IP: '0.0.0.0'.
2018-05-22 12:45:11 0 [Note] Event Scheduler: Loaded 0 events
2018-05-22 12:45:11 0 [Note] /usr/bin/mysqld: ready for connections.
Version: '5.6.21' socket: '' port: 3306 Source distribution
2018-05-22 12:45:57 0 [Warning] IP address '192.168.122.1' could not be resolved: Name does not resolve
"
The text was updated successfully, but these errors were encountered: