Mmonit 4.2.2 resolves performance issues about docker-mmonit HOT 12 CLOSED

do you mean 4.2.1? 4.2.2 is not release by now it seems:

https://mmonit.com/wiki/MMonit/Releases

Or is there an additional release coming these days?

from docker-mmonit.

I got this link from mmonit support:

https://mmonit.com/tmp/mmonit-4.2.2-linux-x64.tar.gz

so i think 4.2.2 is coming soon
br richard

from docker-mmonit.

ok, thanks - but i think 4.2.1 docker image should be created non the less (if the new version has some other issues).

@jchonig can you please create a 4.2.1 docker image release? Thanks a lot.

from docker-mmonit.

I have merged your PR (thanks) and am also building 4.2.2.

from docker-mmonit.

I am unable to build 4.2.2 without changes to the container that I do not have time for at the moment. Maybe later this weekend.

from docker-mmonit.

Reopening

from docker-mmonit.

As v4.2.1 is available as docker image now (thanks!) and its release notes also mention some performance improvements, it is probably fine to wait until 4.2.2 is officially released. And than everything should work as before without changes needed...

from docker-mmonit.

M/Monit 4.2.2 was released today and I built the 4.2.2 tag.

The upgrade took quite a long time, but it is up and running for me.

from docker-mmonit.

Waiting here for about 45min an Mmonit is not starting ... the logs are full with:

2024-05-09 06:42:09,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

2024-05-09 06:42:09,stdout,Starting mmonit 4.2.2

2024-05-09 06:42:08,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

2024-05-09 06:42:07,stdout,Starting mmonit 4.2.2

2024-05-09 06:42:06,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

2024-05-09 06:42:06,stdout,Starting mmonit 4.2.2

2024-05-09 06:42:05,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

2024-05-09 06:42:05,stdout,Starting mmonit 4.2.2

2024-05-09 06:42:05,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

2024-05-09 06:42:04,stdout,Starting mmonit 4.2.2

2024-05-09 06:42:03,stdout,AssertException: Unsupported database schema version: 22 -- please run database upgrade script(s) to update M/Monit to version 4.2.2 (database schema version 23)

from docker-mmonit.

from docker-mmonit.

Did you interrupt the first start because it was taking too long? My first start probably took an hour (I didn't time it) with lots of:

mmonit_mmonit  | Upgrading M/Monit from /config/mmonit-4.2.1-alpine to /config/mmonit-4.2.2 ...
mmonit_mmonit  |
mmonit_mmonit  | ***WARNING*** please wait and DO NOT INTERRUPT the process (the upgrade can take some time if your database is large)
mmonit_mmonit  |
mmonit_mmonit  | Reading license in '/config/mmonit-4.2.1-alpine/conf/server.xml'
mmonit_mmonit  | Starting Reactor using epoll (max concurrent connections = 4096)
mmonit_mmonit  | Copying database file from /config/mmonit-4.2.1-alpine/db/mmonit.db to /config/mmonit-4.2.2/db/ ... Reactor stopped
mmonit_mmonit  | Connecting to sqlite:///config/mmonit-4.2.2/db/mmonit.db?synchronous=full&
mmonit_mmonit  | Upgrading schema version 22 to 23
mmonit_mmonit  | 	Add analytics table with 2m precision
mmonit_mmonit  | CREATE TABLE statistics_aggregate_2m (
mmonit_mmonit  |   statisticsid INTEGER,
mmonit_mmonit  |   collectedsec INTEGER NOT NULL,
mmonit_mmonit  |   value_avg REAL,
mmonit_mmonit  |   count INTEGER,
mmonit_mmonit  |   CONSTRAINT statistics_aggregate_2m_statisticsid_fk FOREIGN KEY(statisticsid) REFERENCES statistics(id) ON DELETE CASCADE
mmonit_mmonit  | );
mmonit_mmonit  |

I can probably figure out some way to see if the first start was interrupted and cause the upgrade to be re-run on the next start.

from docker-mmonit.

for me the solution was 4.0.2 -> 4.2.1 -> 4.2.2 ... that worked for me :-)
br, Richard

from docker-mmonit.