charlescng / docker-containers Goto Github PK

An email from a user

I noticed that discovery is currently scheduled this way in /etc/cron.d/observium :

33  */6   * * *   root    /opt/observium/discovery.php -h all >> /dev/null 2>&1
*/5 *     * * *   root    /opt/observium/discovery.php -h new >> /dev/null 2>&1

This is obsolete as shown in [Observium's documentation](https://docs.observium.org/discovery/#cron) and should be :

33  */6   * * *   root    /opt/observium/observium-wrapper discovery >> /dev/null 2>&1
*/5 *     * * *   root    /opt/observium/observium-wrapper discovery --host new >> /dev/null 2>&1

The issue is that if one device fails to be discovered with the old method (./discovery.php -h new), the next new devices in the list are not discovered (ignored).
observium-wrapper prevents this from happening.

Hi,

Tried to run this behind a reserve-proxy (traefik 2.0)

Some files are trying to add always the default port to the dns
https://observium.containers.mycompany.com:**8668**/js/jquery.min.js?v=20.9.10731

instead of

https://observium.containers.mycompany.com/js/jquery.min.js?v=20.9.10731

Is there a way to pass in the host dns/port ? Similar to this one:
https://github.com/somsakc/docker-observium#a-manual-run-containers

The old image from Zuhkov/observium is running Observium CE 0.14.11.6000 with MariaDB 5.5.42
The new image is running Observium CE 18.9.1 with MariaDB 10.3

Trying to reuse the database will fail with the following schema update error:

[2018/10/06 23:15:01 -0400] discovery.php(298): ====== Schema update 183 -> 184 ==============
[2018/10/06 23:15:01 -0400] discovery.php(298): Query: UPDATE eventlog SET severity = 5 WHERE message REGEXP ' [.(.]by (user|cron|console)';
[2018/10/06 23:15:01 -0400] discovery.php(298): Error: (1139) Got error 'POSIX collating elements are not supported at offset1' from regexp

A new community edition release has just happened. Please could you rebuild the container with it and tag the version on docker hub. Thanks :-)

Hello,

I just upgraded to v 6.0.0 from 5.0.0 and am now unable to log in with observium/observium. The log files seem to indicate that observium is otherwise working ok.

Thanks,
Tom

Hello sir,

I have a graph:

and after editing the log format to show the timezone:

The image creation is not the same as the logfile..

From 1:15 to 3:45 the power was out the graph shows 6:15, which would be UTC (I'm EST -5 atm)

Timezones info

o Date Wednesday, 15-Dec-21 07:51:46 EST
o PHP -05:00
o MariaDB -05:00

./poller.php -d shows that it should be correct..

TZ was/is set correctly in the docker-compose for observium and when I enter the container it is also appearing correctly in env

Suggestions?

Hello sir,

Trying to get started.. but I don't think I have enough legs underneath me yet..

*** Running /etc/my_init.d/firstrun.sh...
Using existing PHP database config file.
Dec  8 20:09:58 db3406aabc73 syslog-ng[12]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
warning: commands will be executed using /bin/sh
job 1 at Wed Dec  8 20:10:00 2021
warning: commands will be executed using /bin/sh
job 2 at Wed Dec  8 20:10:00 2021
ln: failed to create symbolic link '/opt/observium/config.php': File exists
Dec  8 20:09:58 db3406aabc73 syslog-ng[12]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
Dec  8 20:09:58 db3406aabc73 syslog-ng[12]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'

This is how I started..

docker run -d --name observium -v /home/docker/observium/config:/config -v /home/docker/observium/logs:/opt/observium/logs -v /home/docker/observium/rrd:/opt/observium/rrd -e TZ="America/New_York" -p 8668:8668 uberchuckie/observium 

Open to any suggestions

Server Version: 20.10.11, fedora 35, xanmod-tt kernel

starting the image I can get into the container, but I need to comment out the syslog entry in config.php then it all starts..

setting it to zero didn't change anything..

// End config.php
// $config['enable_syslog'] = 0;

But then it looks like it's listening anyway..

root@fedora-d51108 ~# docker ps -a 
CONTAINER ID   IMAGE                      COMMAND                  CREATED          STATUS                PORTS                                                                                                      NAMES
db3406aabc73   uberchuckie/observium      "/sbin/my_init"          11 minutes ago   Up 2 minutes          514/udp, 0.0.0.0:8668->8668/tcp, :::8668->8668/tcp                                                         observium

Thanks in advance..

The latest uberchuckie/observium image was uploaded to Docker hub on October 23rd, 2023. Meanwhile the most recent commit made to this repo was 7 months ago.

Is this repo still the source of the uberchuckie/observium docker image?

Hello, my colleague and I would like to migrate to Docker. Our Observium version is 19.8. We would like to use the same version for the migration initially. But the image in version 2.1.1 is not available on Docker Hub. Is there a way to get the old version?

Just installed the https://hub.docker.com/r/uberchuckie/observium container.

Observium started, but I could only add one device. After some digging i found out the db was missing auto_increment on the device_id column.

alter table devices change column device_id device_id int(11) not null auto_increment;

fixed it. Perhaps something to take along?

Could you release an updated container with the latest Observium CE? 22.5 (25th May 2022)
Thanks :)

I'm not able to build/run the Observium CE.
this is the errors

2023-07-11 11:06:29 230711 11:06:29 mysqld_safe Logging to '/config/databases/890fd2297f10.err'
2023-07-11 11:05:53 230711 11:05:53 mysqld_safe A mysqld process already exists
2023-07-11 11:05:57 230711 11:05:56 mysqld_safe A mysqld process already exists
2023-07-11 11:06:00 230711 11:06:00 mysqld_safe A mysqld process already exists
2023-07-11 11:06:04 230711 11:06:04 mysqld_safe A mysqld process already exists
2023-07-11 11:06:07 230711 11:06:07 mysqld_safe A mysqld process already exists
2023-07-11 11:06:11 230711 11:06:11 mysqld_safe A mysqld process already exists
2023-07-11 11:06:15 230711 11:06:15 mysqld_safe A mysqld process already exists
2023-07-11 11:06:18 230711 11:06:18 mysqld_safe A mysqld process already exists
2023-07-11 11:06:22 230711 11:06:22 mysqld_safe A mysqld process already exists
2023-07-11 11:06:25 230711 11:06:25 mysqld_safe A mysqld process already exists
2023-07-11 11:06:29 230711 11:06:29 mysqld_safe A mysqld process already exists
2023-07-11 11:06:33 230711 11:06:33 mysqld_safe A mysqld process already exists
2023-07-11 11:06:36 230711 11:06:36 mysqld_safe A mysqld process already exists
2023-07-11 11:06:40 230711 11:06:40 mysqld_safe A mysqld process already exists
2023-07-11 11:06:43 230711 11:06:43 mysqld_safe A mysqld process already exists
2023-07-11 11:06:47 230711 11:06:47 mysqld_safe A mysqld process already exists
2023-07-11 11:06:51 230711 11:06:51 mysqld_safe A mysqld process already exists
2023-07-11 11:06:54 230711 11:06:54 mysqld_safe A mysqld process already exists
2023-07-11 11:06:58 230711 11:06:58 mysqld_safe A mysqld process already exists
2023-07-11 11:07:01 230711 11:07:01 mysqld_safe A mysqld process already exists
2023-07-11 11:07:05 230711 11:07:05 mysqld_safe A mysqld process already exists
2023-07-11 11:07:09 230711 11:07:09 mysqld_safe A mysqld process already exists
2023-07-11 11:07:12 230711 11:07:12 mysqld_safe A mysqld process already exists
2023-07-11 11:07:16 230711 11:07:16 mysqld_safe A mysqld process already exists
2023-07-11 11:07:19 230711 11:07:19 mysqld_safe A mysqld process already exists
2023-07-11 11:07:23 230711 11:07:23 mysqld_safe A mysqld process already exists
2023-07-11 11:07:27 230711 11:07:27 mysqld_safe A mysqld process already exists
2023-07-11 11:07:30 230711 11:07:30 mysqld_safe A mysqld process already exists
2023-07-11 11:07:34 230711 11:07:34 mysqld_safe A mysqld process already exists
2023-07-11 11:07:38 230711 11:07:38 mysqld_safe A mysqld process already exists
2023-07-11 11:07:41 230711 11:07:41 mysqld_safe A mysqld process already exists

and also
2023-07-11 11:13:56 Fixing file permissions.
2023-07-11 11:14:00 Starting MariaDB...
2023-07-11 11:14:00 230711 11:14:00 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:00 Database exists.
2023-07-11 11:14:00 Fixing file permissions.
2023-07-11 11:14:04 Starting MariaDB...
2023-07-11 11:14:04 230711 11:14:04 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:04 Database exists.
2023-07-11 11:14:04 Fixing file permissions.
2023-07-11 11:14:07 Starting MariaDB...
2023-07-11 11:14:07 230711 11:14:07 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:07 Database exists.
2023-07-11 11:14:07 Fixing file permissions.
2023-07-11 11:14:11 Starting MariaDB...
2023-07-11 11:14:11 230711 11:14:11 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:11 Database exists.
2023-07-11 11:14:11 Fixing file permissions.
2023-07-11 11:14:14 Starting MariaDB...
2023-07-11 11:14:15 230711 11:14:15 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:15 Database exists.
2023-07-11 11:14:15 Fixing file permissions.
2023-07-11 11:14:18 Starting MariaDB...
2023-07-11 11:14:18 230711 11:14:18 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:18 230711 11:14:18 mysqld_safe A mysqld process already exists
2023-07-11 11:14:18 Database exists.
2023-07-11 11:14:18 Fixing file permissions.
2023-07-11 11:14:22 Starting MariaDB...
2023-07-11 11:14:22 230711 11:14:22 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:22 230711 11:14:22 mysqld_safe A mysqld process already exists
2023-07-11 11:14:22 Database exists.
2023-07-11 11:14:22 Fixing file permissions.
2023-07-11 11:14:25 Starting MariaDB...
2023-07-11 11:14:25 230711 11:14:25 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:25 230711 11:14:25 mysqld_safe A mysqld process already exists
2023-07-11 11:14:25 Database exists.
2023-07-11 11:14:25 Fixing file permissions.
2023-07-11 11:14:29 Starting MariaDB...
2023-07-11 11:14:29 230711 11:14:29 mysqld_safe Logging to '/config/databases/890fd2297f10.err'.
2023-07-11 11:14:29 230711 11:14:29 mysqld_safe A mysqld process already exists
2023-07-11 11:14:29 Database exists.
2023-07-11 11:14:29 Fixing file permissions.

I believe this might be a similar issue to when MariaDB upgraded from 10.14 to 10.15

Like stated, this is a new docker image build, and I do get the WebGUI but i'm not able to login with the default user/password.
I even ran adduser.php and created a new user successfully but still not able to login
deleted error files to see if that would work, still no go.

this is also in the install logs
023-07-11 11:01:46 CMD[/usr/bin/mysql -u'observium' -p'kCytMBqI4PLnS2WJI1OxVBP26ozzpobU' -h'localhost' -D 'observium' < '/opt/observium/update/db_schema_mysql.sql']
2023-07-11 11:01:46
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:46 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:46 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:47 Jul 11 11:01:47 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:48 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:49 Jul 11 11:01:48 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:49 Jul 11 11:01:49 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:49 Jul 11 11:01:49 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:49 Jul 11 11:01:49 890fd2297f10 syslog-ng[13]: Child program exited, restarting; cmdline='/opt/observium/syslog.php', status='0'
2023-07-11 11:01:56 CMD EXITCODE[0]
2023-07-11 11:01:56 CMD RUNTIME[10.3653s]
2023-07-11 11:01:56 STDOUT[
2023-07-11 11:01:56
2023-07-11 11:01:56 ]

From what I can see there is no syslog collection support in the docker image. (please correct me if I am wrong and let me know how to use it!).

Is this a feature you are likely to add?
Would you accept a PR that added it?

Hello, is possible to somehow use email notification in Observium container?
I'm getting /usr/sbin/sendmail: not found
when trying test_alert.hhp

Thanks