found out that MariaDB-server-10.1 does not work.
...
# kolidec
cen
07/18/2018, 10:13 PMfound out that MariaDB-server-10.1 does not work.
updated the database github issue yall got going.
https://github.com/kolide/fleet/issues/1644
any good work around to get me moving? using fleet 1.0.8
Copy code
well. for MariaDB-server-10.1 we get this error @groob
2018/07/18 20:58:55 FAIL 20170306075207_UseUTF8MB.go (alter table file_integrity_monitoring_files: Error 1071: Specified key was too long; max key length is 767 bytes), quitting migration.
did some looking around
found this here
gogs/gogs#4894
Because of mysql 5.6 (includes prior versions) InnoDB max index length is 767 bytes, mysql 5.7.7 is up to 3072 bytes.
If some varchar column's length is 255, when the character format is utf-8 needs 2553=765 bytes for index length, It's OK.
But, an utf8mb needs 2554=1020 bytes for index length.
Solutions:
UPGRADE the mysql to 5.7.7(Mariadb 10.2.2)
Change the utf8mb column length to 191 (191*4=764)
Change the utf8mb to utf8
set innodb_file_format=Barracuda, innodb_large_prefix=on and create table using ROW_FORMAT=DYNAMIC or COMPRESSED (default for 5.7.7)
seems to be the same issuecen
07/19/2018, 5:34 PM@groob
Is there a good work around for this problem?
g
groob
07/19/2018, 5:36 PM
use mysql 5.7 for fleet or submit a pull request
groob
07/19/2018, 5:37 PM
there might be a better answer long term, but AFAIK it’s not an issue anyone is actively working on right now
groob
07/19/2018, 5:37 PM
cc @marpaia
m
marpaia
07/19/2018, 5:38 PMwhat’s the problem? mysql needs to be updated?
c
cen
07/19/2018, 5:38 PMCompany uses Mariadb 10.1 for our managed service db
g
groob
07/19/2018, 5:38 PM
mariadb support
groob
07/19/2018, 5:39 PM
mariadb support and current status of this issue https://github.com/kolide/fleet/issues/1644
c
cen
07/19/2018, 5:43 PMalright. So if submitted a perfect pull request what is the timeline on having it merged and into a version that has the tag
Latest releasem
marpaia
07/19/2018, 6:08 PM@cen if you do it soonish, we can make sure it’s in 2.0.0
marpaia
07/19/2018, 6:09 PMwe’re pretty quick to move PRs along
marpaia
07/19/2018, 6:09 PMit’s just our issue backlog which is long 😅
c
cen
07/19/2018, 6:17 PMwhen is 2.0 planed to be moved to
Latest releasecen
07/19/2018, 6:17 PMright now latest is 1.0.8
m
marpaia
07/19/2018, 6:19 PMwe MAY cut one more release as an rc4, but we are certainly endeavoring to cut 2.0.0 soon if master is stable for everyone
marpaia
07/19/2018, 6:19 PMwe may cut an 2.0.0-rc4 and then re-release it as 2.0.0
marpaia
07/19/2018, 6:19 PMbut soon hopefully
marpaia
07/19/2018, 6:20 PMbut if this doesn’t make it, we can always cut 2.0.1 and mark it latest
marpaia
07/19/2018, 6:20 PMso nbd
c
cen
07/19/2018, 6:28 PMSo my director wants a production ready instance of fleet by 8/15
problem is we don't use mysql (mariadb) and we don't use redis(MeghaCache). Im starting think this might be impossible.
m
marpaia
07/19/2018, 6:35 PMi don’t know what megacache is.. are there problems with it?
marpaia
07/19/2018, 6:37 PMand can you update mariadb? it seems like there’s a bug and the latest version of maridb fixes the bug according to this github issue
c
cen
07/19/2018, 6:41 PMredis(MeghaCache)sorry i ment Memcached
cen
07/19/2018, 6:41 PMand can you update mariadbNo I can not
m
marpaia
07/19/2018, 6:42 PMoh, memcached, yeah, that’s gonna be complicated because we also use redis as the pubsub broker for live query result streaming
marpaia
07/19/2018, 6:43 PMwhich idk if memcached can do
marpaia
07/19/2018, 6:43 PMbut if it can, we would accept a patch for memcached support, it should be easy to setup a local instance
c
cen
07/19/2018, 6:48 PMThank you. You guys are great. I need to reevaluate this and see how my leadership wants to handle this.
m
marpaia
07/19/2018, 6:48 PMyeah, let me know. we also have a SaaS if that’s an option: https://kolide.com/product
3 Views