14:13:50 jperkin: did you had the time to look into the mariadb missing innodb issue? Just wanted to know before the next update round :-) 14:14:17 Is it really missing or did people just hit the same as me I wonder 14:14:59 https://github.com/omniosorg/omnios-extra/commit/39de7a8862426e6d8fa57e855fd8459d3625eb83 14:14:59 → GitHub commit : (committed) 14:16:00 There is a workaround in the my.cnf too. They changed a default value in a minor release which makes the innodb engine try to mmap a very large amount of memory, assuming Linux semantics. 14:22:41 andyf: I got the error "Unknown/unsupported storage engine: innodb". But innodb is the main storage engine. 14:23:29 If you got the same as me - https://paste.omnios.org/?5d43a09365c6aecb#4NAz6i8MGx3C1YDJU5xnfchdPjRMRs8r1bwGTnUhS5CR - then it's the new default innodb_buffer_pool_size_max 14:24:19 https://jira.mariadb.org/browse/MDEV-38671 - I already dropped a note in there. 14:27:37 Thx a lot for sharing! I will take a look into it. And maybe jperkin can include the patch in the mean time? 14:38:24 ah thanks, no sorry I didn't get a chance to look yet (August is very flaky for me, and there are issues with the NetBSD repo conversion at the moment) - I'll pull in andy's patch 14:39:26 andyf: Looked into the log again and yes it is the exact same error output as yours. So I will try to fix it by setting innodb_buffer_pool_size_max to a lower value. Maybe I do not understand it right, but it should work if I set it to 80% of the swap (currently 32G)? 14:40:24 I just set it to 2G, and innodb_buffer_pool_size to 1G - but this was on a smallish server. Maybe just look at what the current size is with `show global variables like...` and set both to that value. It just means you can't dynamically grow it with the server running. 14:43:08 I really wish projects would not make changes like this in minor releases. 14:44:37 andyf: yes so true! But this is more and more the case.