• Posts

  • Joined

  • Last visited

About VRx

  • Birthday November 30


  • Gender
  • Location

Recent Profile Visitors

661 profile views

VRx's Achievements


Newbie (1/14)



  1. I haven't any, so i cannot test. But with your little help we could install some drivers and libs if it is not working.
  2. It is ok. When You log in to GUI, You can simply create config. When You do that, bind process should start working. You do not need to create config manually before first run.
  3. [Here] is beta plugin, should work like baremetal I think, but it is only agent not agent2, so it can't monitor docker containers.
  4. You can run script on host and write output to file, which could be read by zabbix container. This is the easiest way. Most of templates are not prepared for zabbix-agent contenerized.
  5. Application: Bacula - https://www.bacula.org/ Baculum App - https://www.baculum.app/ Docker Hub: https://hub.docker.com/r/pwa666/bacula-server GitHub: https://github.com/vrx-666/bacula-server Bacula is a client / server backup application. Baculum is a web application that allows you to easily manage the bacula application. This container combines these applications to form a backup tool with a graphical interface. This container can be run in 5 different versions. Bacula server consists of several components: storage daemon - responsible for saving backups to disk or removable media (tape) bacula director - responsible for the entire backup process, contacts agents on client devices, indicates what resources should be backed up, how and where to send them (storage daemon) file daemon - is a bacula client available for many operating systems, responds to requests from bacula director. A relational database is necessary, where the bacula stores all information related to the performed backups. During installation, you can choose Bacula version 9.6 or 11. Version 9.6 allows you to use the mysql or postgresql database as well as sqlite3. Version 11 allows you to use the postgresql or sqlite3 database. The sqlite3-enabled version is not recommended for larger environments, but allows you to run this application without running mysql / postgresql as a separate container or server. If you already have postgresql or mysql running as your VM or docker application, I recommend choosing this version of the application. If you plan to use the PostgreSQL or MySQL version you should first create an empty database named "bacula", create a password user for that database and grant full privileges to this database for the created user.For mySQL: CREATE USER 'USERNAME' @ '%' IDENTIFIED BY 'PASSWORD'; CREATE DATABASE bacula; GRANT ALL PRIVILEGES ON `bacula`. * TO 'USERNAME' @ '%'; flush privileges; For postgreSQL: create user USERNAME with password 'PASSWORD'; create database bacula encoding 'SQL_ASCII' owner "USERNAME" template = template0; When running container there is some mandatory environment variables. Most important is to set up: SD_Host - should define the IP address at which the Bacula Server will be reachable for computers. If you are using a bridge network this parameter should be the ip of your UnRAID. If you set custom bridge, You shuld type in assigned IP. This variable is passed to the Bacula configuration and later during the backup it is passed to the clients so they can communicate with the Bacula server. The following are necessary when using an external database (postgreSQL, mySQL) DB_Host - database ip DB_Port - database port (could be omitted if default) DB_User - database user DB_Password In addition, there are two important ports that must be exposed: 9095 - Bacula Web 9103 - Bacula Storage The first allows access to the webUI Baculum App. The second is used to receive backups by the server from clients / computers. It can be changed, but you have to change the configuration of Storage Daemon and Bacula Director e.g. via webUI. I recommend that you leave these ports unchanged. There are also necessary paths to folders where configuration files, logs and backups will be saved, these variables are transparent in the UnRaid's docker form, I think that they do not need to be described here. If you have any questions, please ask below.
  6. Ciągle o tym zapominałem. Poprawione + kilka innych baboli językowych. Ogólnie ktoś leciał chyba w ciemno translatorem, bez sprawdzania.
  7. Update available: - fixed TZ env - fixed GUI_USER env
  8. Yes You are right, but if someone have for example pihole container or something else what needs dns port... I can't know
  9. find /mnt/user/surveillance_camera/cam[12] -type f -mtime +14 -delete find /mnt/user/surveillance_camera/cam[12] -type d -empty -delete
  10. DNS requests mostly working on UDP, haproxy working on TCP.
  11. You can do this by logging in as root: docker exec -it --user=root zabbix-agent2 /bin/bash Next, edit group file (/etc/group) in vim or sed. If You not familiar with vim, sed will be easier: sed -i "s/docker:x:281:/docker:x:281:zabbix/g" /etc/group Next, type "exit" to exit container shell, then You can restart container from Unraid GUI BTW: Some trick could be used for things that not working from zabbix container, by setting up cron in User Scripts Plugin, this cron could monitor something, and write to file, which could be read by zabbix-agent, for example: my script read parameters from ups tools, writing output to file on cache pool, zabbix-agent read this file and parse output to different items in zabbix.
  12. Because zabbix-agent2 in this container is running by the user without permissions to docker socket. There is a possibility to run this, but You must have basic knowledge about linux shell systems. You must check GID of docker group on Host (Unraid Server). Log in to zabbix-agent2 container as root user (default running "Console" from Unraid GUI made it but as zabbix user) Add group docker (with same gid as on host/unraid server) inside zabbix-agent2 container. Add user zabbix to this group. Restart zabbix-agent2 container. Note: You must do this again after every container update.
  13. From now there will be weekly system update, every Sunday. But every changes in application, as always, will be reported in this thread.
  14. TemplateURL is deprecated: You can simply ignore that error.