jchonig / docker-mmonit Goto Github PK

View Code? Open in Web Editor NEW

10.0 10.0 4.0 39 KB

A container to run M/Monit

License: Creative Commons Zero v1.0 Universal

Dockerfile 82.03% Shell 17.97%

docker-mmonit's Introduction

Jeffrey Honig

About me

I mostly work on system Configuration Management projects (Puppet, Ansible).

Many of these repos are dockerized versions of system services I run on my home systems.

I really like building containers based on the s6-overlay base images developed by LinuxServer.io.

My Organizations

Name	Description
Copilot	This organization provides access to Copilot for some accounts.
HYPE - FRC 5254
The Things Network Ithaca	Building a free, open source community-owned IoT network for Ithaca and Tompkins County, NY
The Things Network New York	Deploying The Things Network in New York City

Repositories

Repositories I own

Name	Description	Stars
docker-bind9	A container to run named	0
docker-conman	A docker container to run https://github.com/dun/conman	0
docker-dhcpd	Run ISC DHCP server in a docker container. Based on Linuxserver.io containers	1
docker-g10k	G10k and webhook in a container	0
docker-kea	Alpine container to run Kea DHCP server	0
docker-meetup-slack	Post notices about Meetup events in a Slack channel	0
docker-mmonit	A container to run M/Monit	10
docker-monit	A container to run monit	1
docker-nut-cgi	Nut CGI in a container	8
docker-postfix	Postfix running in a container	2
docker-rsnapshot	Run rsnapshot in a container	0
docker-spideroak	SpiderOakONE in a container	0
docker-webhook	A container to run adnanh/webhook under lsio's s6 overlay containers	0
homebrew-conman	Homebrew formula	0
hubitat	Hubitat apps and drivers	0
hubitat-pushbullet	Pushbullet support for Hubitat	0
jchonig	A special repository to automatically generate my GitHub README.md	0
jchonig.github.io	jchonig.github.io	0
mlinux-be	Containerized build environment for MultiTech mLinux	2
named_docker	Run bind in a Docker container	0
pfsense_scripts	pfSense support scripts	2
pushbullet	A small python script to send pushbullet notifications	4
rak7200_config	A tool to configure a RAK7200	6
tempest_influx	Go program to convert WeatherFlow Tempest WX UDP broadcasts to influx wire protocol	1
things-nyc.github.io	Website for TheThingsNetwork NYC	2

Repositories I forked

Name	Description	Parent
Catena-Sketches	Top-level Arduino sketches for the MCCI Catena family of IoT LPWA Devices	mcci-catena/Catena-Sketches
conduit-mfg	Manufacturing instructions for deploying Conduits with Ansible	terrillmoore/conduit-mfg
home-assistant	🏡 Open source home automation that puts local control and privacy first	home-assistant/core
homebrew-core	🍻 Default formulae for the missing package manager for macOS (or Linux)	Homebrew/homebrew-core
hubitat-1	None	augoisms/hubitat
RAK811-tracker	RAK811 ultra fast TTN Mapper node example	jpmeijers/RAK811-tracker

How this works.

docker-mmonit's People

Contributors

Stargazers

Watchers

Forkers

sseide barcar alexander-potemkin hpcmtint

docker-mmonit's Issues

3.7.14 coming ?

Hi
Do you plan to upgarde the docker image to 3.7.14 due to OpenSSL defects:
CVE-2023-0286
CVE-2023-0215
CVE-2022-4450
CVE-2022-4304
?
br, Richard
;-)

Fix custom scripts locations

https://info.linuxserver.io/issues/2022-11-29-custom-files/

Document migrating from sqlite to mysql (and postgresql?)

Example container?

Steps to take.

Sample script?

MMonit 4.1.1

MMonit is updated to new releases version :-).
This version contains some fixes for Sqlite database in regard to the memory size.

https://mmonit.com/wiki/MMonit/Release4-1-1

br, Richard

Add periodic backups

Add periodic backups for at least sqlite3 database.

Add support for backing up mysql database

Clean up older versions of config directory

This should work:

olddirs=$(ls -1d mmonit-* | grep -E '^mmonit-([0-9.]+)(-(alpine|ubuntu))?$' | sort --version-sort --field-separator=- --key=2,2 -r | tail -n +3)
find ${olddirs} -prune -mtime +30 -ls

When it has proved to work for a few versions, add a -exec rmdir {} to the end.

"latest" tag?

Pulling for the first time and I was surprised that there was no latest tag on dockerhub. can this be implemented?

Migrate Docker on Synolgy from 3.7.15 to 4.0.0

i am running your docker container on a synology NAS.
upgrade to 4.0.0 dont work. container doesnt start.
the manually command...
"/volume1/docker/mmonit/mmonit-4.0.0/upgrade/upgrade -p /volume1/docker/mmonit/mmonit-3.7.15"
ends with the error: "/volume1/docker/mmonit/mmonit-4.0.0/upgrade/upgrade: No such file or directory"
but the file ist there ?!?!?
can you please help how to migrate from 3.x to 4.x on a synology NAS ?
thx !, Richard

Mmonit 4.2.2 resolves performance issues

Please upgrade the docker container to 4.2.2.
Changes:

we significantly improved the speed of statistics aggregation (the slower aggregation speed was the main performance difference between 4.0.2 and 4.1.0-4.2.0)
we have increased the aggregation granularity and reduced the number of default datapoints in the analytics report from ~60 to ~30 for default timeframes, to reduce the data volume and load time when large number of statistics is to be displayed (e.g. the 'all hosts' selection). The higher precision can be displayed via a selection in the chart.

thx a lot !!
br, Richard

Timezone TZ not used by M/Monit

We recently switched from "traditional hosting" of M/Monit to the docker container. But there is one issue which previously worked, so it is not a bug in M/Monit itself.

The dates in alert mails M/Monit is sending are in UTC instead of our set timezone. The TZ param seems to have no influence on M/Monit. We have set the following in a docker-compose.yml:

environment:
  - TZ=Europe/Berlin
image: jchonig/mmonit:3.7.15
…

4.2.2 is not starting ... error.log is full with "Unsupported database schema version: 22"

Coming from 4.0.2 ... waiting here for about 45min and 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)

should i wait longer ??
br, Richard

See the full log here:
Mmonit (3).csv

Add support for backing up postgresql databases

Mmonit 4.2.0 very slow in use ....

As described above, I have updated on the Synology from 4.0.2 to 4.2.0. The container starts after a long "PRAGMA check" ... but the whole system responds very slow !! ... it takes minutes to load the different pages :-(

Alerts hostname?

Hi - where can I set the hostname used in alerts?

Mmonit 4.02 crashes regularly ?

Hi
Since 4.02 my Mmonit Docker crashes regularly. Here is the error log. Is there anything to recognise?
br Richard

2024-01-18 10:04:18 mmonit 4.0.2 is shutting down.. (please wait)
2024-01-18 10:04:38 mmonit 4.0.2 started
2024-01-18 10:28:44 [client 172.17.0.1] could not read request body -- read timed out
2024-01-18 10:35:49 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-18 11:16:00 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-18 13:18:02 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-18 14:27:57 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 8 statistics
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 8 statistics
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 1114 statistics
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 94 statistics
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 1114 statistics
2024-01-19 03:00:05 SQLException: database is locked when storing hostid 733 statistics
2024-01-19 04:00:00 Scheduler: task StatisticsManager cleanup: SQLException: database is locked
2024-01-19 04:00:00 StatisticsManager events aggregation: SQLException: database is locked
2024-01-19 08:54:51 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-19 08:55:49 [client 172.17.0.1] HTTP 408 Request Timeout
2024-01-19 09:10:31 mmonit 4.0.2 is shutting down.. (please wait)
2024-01-19 09:10:57 mmonit 4.0.2 started

Upgrade from MMonit 3.x to 4.0 does not work

i tried to upgrade my 3.5 version of the MMonit system to the current 4.0 version.
During the upgrade the necessary database upgrade is not running therefor MMonit does no start up.

I think the problem is due to the order of the startup steps done. It seems the database upgrade is tried first and afterwards the new configuration files are created. Due to this the new MMonit 4.x upgrade script is executed with an invalid (old 3.x) license and does not run.

The second start up MMonit (after config file upgrade) is correctly using the new 4.x license and logs error messages only for having the wrong db table versions.

Full Log output of the startup:

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 

  Based on images from linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

Environment init-mmonit-upgrade:
    PUID=
    PGID=
    TZ=UTC
    MMONIT_LIMIT_FD=4096
    MMONIT_OS=alpine
    MMONIT_VERSION=4.0.0
[custom-init] No custom files found, skipping...
crond[148]: crond (busybox 1.36.1) started, log level 7
Upgrading from 3.7.15-alpine to 4.0.0
Upgrading M/Monit from /config/mmonit-3.7.15-alpine to /config/mmonit-4.0.0 ...

***WARNING*** please wait and DO NOT INTERRUPT the process (the upgrade can take some time if your database is large)

Reading license in '/config/mmonit-3.7.15-alpine/conf/server.xml'
Starting Reactor using epoll (max concurrent connections = 1048476)
Copying configuration files from /config/mmonit-3.7.15-alpine/conf/ to /config/mmonit-4.0.0/conf/ ... done
Copying uploaded files from /config/mmonit-3.7.15-alpine/docroot/uploads/ to /config/mmonit-4.0.0/docroot/uploads/ ... done
Reactor stopped
+------------------------------------------------------------------------------+
| LICENSE EXPIRED                                                              |
|                                                                              |
| This is M/Monit version 4.0.0, released, November 17, 2023. Your license was |
| registred on April 15, 2015. Please renew your license to upgrade to this    |
| version of M/Monit.                                                          |
|                                                                              |
| When you renew your license, you'll get a year of updates for M/Monit. Once  |
| that year is up, you can renew again or continue forever using the last      |
| version of M/Monit you updated to.                                           |
|                                                                              |
| Please go to https://mmonit.com/user to renew your M/Monit license and       |
| paste your renewed license below or enter q to abort this upgrade process.   |
+------------------------------------------------------------------------------+

New License key>
crond[148]: USER root pid 161 cmd run-parts /etc/periodic/15min


Please enter a valid M/Monit license to upgrade.
init-mmonit-upgrade done
Environment init-mmonit:
    PUID=
    PGID=
    TZ=UTC
    MMONIT_LIMIT_FD=4096
    MMONIT_OS=alpine
    MMONIT_VERSION=4.0.0
Unsetting TLS version

init-mmonit done
Starting mmonit 4.0.0
mmonit    | AssertException: Unsupported database schema version: 16 -- please run database upgrade script(s) to update M/Monit to version 4.0.0 (database schema version 19)
...