Hi Pnuke, there is no dmesg attache, but since you added rules I assume you have no denies anymore (can only guess).
Your log holds some warnigns which could be misconfiguration: 2018-01-31T23:14:55.066207Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000) 2018-01-31T23:14:55.066271Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000) 2018-01-31T23:14:55.217858Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). But not sure about that. Further down the log then comes this: 23:14:55 UTC - mysqld got signal 11 ; 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76385 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... stack_bottom = 0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8f29b] /usr/sbin/mysqld(handle_fatal_signal+0x489)[0x787029] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7feb9edd5390] /lib/x86_64-linux-gnu/libc.so.6(+0x14e045)[0x7feb9e2a7045] /usr/sbin/mysqld(_Z22find_or_create_programP10PFS_thread16enum_object_typePKcjS3_j+0x439)[0x11ccee9] /usr/lib/mysql/plugin/auth_pam.so(+0x238b)[0x7feb8430938b] /usr/sbin/mysqld[0xc70134] /usr/sbin/mysqld[0xc766ef] /usr/sbin/mysqld(_Z36plugin_register_dynamic_and_init_allPiPPci+0xf6)[0xc782e6] /usr/sbin/mysqld[0x77f4bb] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xa29)[0x780e49] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7feb9e179830] /usr/sbin/mysqld(_start+0x29)[0x7772d9] 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. This is mysql crashing hard on something. It has plugin registration in the stack, so you might disable all of them [1] and switch them on one by one to spot the failing one. Could be e.g. a manually built plugin which no more matches the upgraded version Also in general more details about your configuration might be interesting to understand what is failing. [1]: https://dev.mysql.com/doc/refman/5.7/en/mysql-plugin.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746620 Title: mysql-server-5.7: after upgrade apparmor and invalidargument errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1746620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
