irishjd

All, the answer to my question is found in thread #48983

To do a 180, how would I shrink the size of the docker image file?

Me again... so, even though the warning is being displayed in the graylog log file, this is actually a elasticsearch issue. I believe I know how to fix it kind of. To get rid of this warning, I need to add a couple of lines to the elasticsearch.yml configuration file. The problem is, this file is not located in persistent storage (i.e. /appdata/), as it is located at: /usr/share/elasticsearch/config/elasticsearch.yml. Can anyone tell me how I can make persistent changes to this file? Specifically, I need to add these two lines: xpack.security.enabled: true discovery.type: single-node

Has anyone had any luck upgrading Elasticsearch using this template? I was able to get it updated to v7.17.8 by simply changing the Repository: field to: elasticsearch:7.17.8. Although this successfully updated the image, I am now being inundated with warnings in the logs. Specifically: 2022-12-29 08:17:33,366 WARN : org.graylog.shaded.elasticsearch7.org.elasticsearch.client.RestClient - request [GET http://192.168.100.69:9200/_cluster/health?master_timeout=60s&level=cluster&timeout=60s&local=true] returned 1 warnings: [299 Elasticsearch-7.17.8-120eabe1c8a0cb2ae87cffc109a5b65d213e9df1 "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html to enable security."] I am new to Docker, so I am not exactly sure how to correct this, but if I figure it out, I will post it back here.

I'm giving checkmk a look...

Have you had any luck getting WMI working with Observium?

@maybertsUnfortunatly, I did not. I gave up on LibreNMS and I am looking for something else.

@Mattaton instead of me trying and failing to provide you with decent instructions Take a look at this video: This is what I used to setup up my SearXNG https environment. If you happen to use CloudFlare as well, take a look at this too: This makes it super simple to enable https on any self-hosted app/site.

@Mattaton, yes, I did get this working. I’ll do a write-up of my solution tomorrow and post it here.

So, I got this fixed on my install. I had to; 'rm -fR /boot/config/plugins/snmp' and reboot. After that, I was able to install the plugin with no issues. I think my problem was that I had it installed before and customized the snmpd.conf file. I don't believe that the plugin likes it when you do that. Hope this helps.

@dgaglioni I am having the exact same issue.

Trying to get the last of the issues resolved on my LibreNMS install. When I validate the config, I see the following three errors: FAIL: No active polling method detected FAIL: No active python wrapper pollers found FAIL: ServerName is set incorrectly for your webserver, update your webserver config. 192.168.100.69 parse failure (/validate/results) If i run "/opt/librenms/cronic /opt/librenms/poller-wrapper.py 16"manually, it runs without any issues, so I am not sure where the problem is. As far as the server name goes, I'm still trying to figure out where that is set at. I have it set in the Web GUI, but obviously I need to change a config file as well.

Can anyone tell me how to utilize plugins in adminer? I see it mentioned in several Ibracorp videos, but I see no mention off how to enable/use the plugins.

Ahh, that makes sense...

I went back to the config and told it to generate a random password, but it does not appear to be doing so: 2022-10-15 11:14:16 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ... 2022-10-15 11:14:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-10-15 11:14:16 0 [Note] InnoDB: Number of transaction pools: 1 2022-10-15 11:14:16 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-10-15 11:14:16 0 [Note] InnoDB: Using liburing 2022-10-15 11:14:16 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB 2022-10-15 11:14:16 0 [Note] InnoDB: Completed initialization of buffer pool 2022-10-15 11:14:16 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) 2022-10-15 11:14:16 0 [Note] InnoDB: 128 rollback segments are active. 2022-10-15 11:14:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2022-10-15 11:14:16 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2022-10-15 11:14:16 0 [Note] InnoDB: log sequence number 273003; transaction id 325 2022-10-15 11:14:16 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-10-15 11:14:16 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2022-10-15 11:14:16 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. 2022-10-15 11:14:16 0 [Note] Server socket created on IP: '0.0.0.0'. 2022-10-15 11:14:16 0 [Note] Server socket created on IP: '::'. 2022-10-15 11:14:16 0 [Note] InnoDB: Buffer pool(s) load completed at 221015 11:14:16 2022-10-15 11:14:16 0 [Note] mariadbd: ready for connections. Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2022-10-15 11:14:15-05:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started. 2022-10-15 11:14:16-05:00 [Note] [Entrypoint]: MariaDB upgrade not required