Oleg Sigida

I had a similar problem `--include='{__name__!~"cadvisor_.+"}` didn't actually work Got errors like `parse error at char 19: vector selector must contain at least one non-empty matcher` Had to move negation...

same issue here, does not run inside a docker container (tested alpine and debian) failed with: ``` [main] WARN ru.yandex.qatools.embed.postgresql.PostgresProcess - Possibly failed to run initdb: initdb: cannot be run...

to workaround the issue I had to - create a new user in the build container - expose it via USER command in the docker file - update the CI...

@apacukaa you may try to brute-force the password, something tells me it should be something simple.

@dandymsk, if you do have telnet access, try to install 1.5.4 FW as explained here: https://github.com/zvldz/mgl03_fw/tree/main/firmware#the-easy-way

@dandymsk I saw two options, login `admin` and either no password at all or `admin` as the password

@p1ratrulezzz dare to run some brute-force script? I have 3 gateways, one had no password (some old fw), other 2 were on 1.5.5.006 with the password `admin`

Maybe a dictionary then? I doubt it is random. I also found `app` as user name and no password on some forum as an option

I've found out that something set queueSize to 10000, this value will be reused as ringBufferSize. so if I set queueSize: 8192 it works, but still not clear where 10000...

here is the test for the case ``` @Test public void testQueueSize() throws Exception { final LogstashTcpAppenderFactory logstashTcpAppenderFactory = new LogstashTcpAppenderFactory(); Assert.assertEquals(AbstractLogstashTcpSocketAppender.DEFAULT_QUEUE_SIZE, logstashTcpAppenderFactory.getQueueSize()); } ```