• Posts

  • Joined

  • Last visited

About VRx

  • Birthday November 30


  • Gender
  • Location

Recent Profile Visitors

2179 profile views

VRx's Achievements


Rookie (2/14)



  1. @chaosratt "You may write a command that retrieves the data you need and include it in the user parameter in the agent configuration file ('UserParameter' configuration parameter)." docs "Allowed volumes for the Zabbix agent container /etc/zabbix/zabbix_agentd.d The volume allows include *.conf files and extend Zabbix agent using UserParameter feature." more info So You should add another docker volume /etc/zabbix/zabbix_agentd.d And make some .conf files inside
  2. @autumnwalker try to set /mnt/user as Host path
  3. @b0m541 there is alpha version with vchanger compiled: bacula-server:11-sq3-vchanger bacula-server:11-pg-vchanger You can test it, but remember that You must mount disk into docker container as path, and use path in the vchanger config, and it will be better for You if You make config file in the bacula config path instead every path in the container filesystem.
  4. @eagle470 You can run one as master, and second as slave dns. Master after zone modification can send query to slaves, then slaves know that they must get update from master.
  5. Postgres Client v14.5 at the next update
  6. From now Privileged mode is default off in the template. Everyone can switch it on if there is a need.
  7. This is not as clear cut as you say, it depends on the configuration. The assignment of the ip address to the container is the use of the macvlan driver. This assigns the mac address to the container and binds it to the physical network. This is a very different situation to the one you describe and is much closer to computers than containers. How can I help You? This is how bridged and macvlan networks are working in docker environment. It is not my fault and it is also not the fault of the unRAID developers. Quite simply, docker was created for something other than what is used by many. For many reasons, a container should represent one service / process, meanwhile, we build containers that include a database, an application or several applications. Probably if you build one image containing the agent server and zabbix web it will work according to your expectations. I am not in favor of duplicating applications since they already exist in the image repository. Unfortunately, but applications such as zabbix server should be run in a host or virtual machine, not in a container, it will not cause such problems. Try looking for a solution on the zabbix community forum
  8. You could try to bind /proc/net/dev to /host/proc/net/dev inside container. But You need also to instruct zabbix agent it should monitor /host/proc/net/dev. I have not tried this solution.
  9. I omit the technical possibilities but do you think it logical that two containers should use the same ip? Do you also assign the same ip for two computers in the network? https://forums.docker.com/t/container-read-host-proc-net-dev/3439
  10. Activating plugins may not have sense since the docker container does not have full access to the host operating system. First of all, you need to consider what plugins you want to activate, whether they will be able to collect any data You could try to configure path for agent conf file, and after this edit it. You must carefully read previous posts
  11. Email notification added, please read first post (Update section):
  12. I know this, the permission problem, because you confirmed that you are breaking this container with your own configuration, I already had a fix prepared so that further analysis could be carried out. Will come out in the next version. No, it's not useless. If you had read carefully what I wrote earlier, you would have known that I was in the process of preparing a container version with email notification functionality. Previously, the container was built from packages available in the bacula repository, but this repository has stopped working. There was no image update for a month. To avoid this in the future, I started building an image using the source code to build binaries. That's when you started to insist that the most important thing is that the vchanger should be added. But I am writing this for the third time. You can set any hostname in the container, including fqdn, but not with hostname command. And it's not a problem that I blocked it in some way. This is a simple smtp client, not a mail relay. It does not have the option of authorization, but it has the function of configuring what the bacula should send, e.g. what logs should be attached to the e-mail and you do not need to use any scripts to cut a fragment of the log file, as you would have to do in postfix. Really? Then watch this [email protected]:/# which apt /usr/bin/apt [email protected]:/# apt install psutils Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: dbus fontconfig-config fonts-droid-fallback fonts-noto-mono fonts-urw-base35 ghostscript libapparmor1 libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libdbus-1-3 libdeflate0 libfontconfig1 libfreetype6 libgs9 libgs9-common libidn11 libijs-0.35 libjbig0 libjbig2dec0 libjpeg62-turbo liblcms2-2 libopenjp2-7 libpaper-utils libpaper1 libpng16-16 libtiff5 libwebp6 poppler-data Suggested packages: default-dbus-session-bus | dbus-session-bus fonts-noto fonts-freefont-otf | fonts-freefont-ttf fonts-texgyre ghostscript-x cups-common liblcms2-utils poppler-utils fonts-japanese-mincho | fonts-ipafont-mincho fonts-japanese-gothic | fonts-ipafont-gothic fonts-arphic-ukai fonts-arphic-uming fonts-nanum The following NEW packages will be installed: dbus fontconfig-config fonts-droid-fallback fonts-noto-mono fonts-urw-base35 ghostscript libapparmor1 libavahi-client3 libavahi-common-data libavahi-common3 libcups2 libdbus-1-3 libdeflate0 libfontconfig1 libfreetype6 libgs9 libgs9-common libidn11 libijs-0.35 libjbig0 libjbig2dec0 libjpeg62-turbo liblcms2-2 libopenjp2-7 libpaper-utils libpaper1 libpng16-16 libtiff5 libwebp6 poppler-data psutils 0 upgraded, 31 newly installed, 0 to remove and 2 not upgraded. Need to get 17.1 MB of archives. After this operation, 62.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bullseye/main amd64 libapparmor1 amd64 2.13.6-10 [99.3 kB] Get:2 http://deb.debian.org/debian bullseye/main amd64 libdbus-1-3 amd64 1.12.20-2 [219 kB] Get:3 http://deb.debian.org/debian bullseye/main amd64 dbus amd64 1.12.20-2 [239 kB] Get:4 http://deb.debian.org/debian bullseye/main amd64 fonts-droid-fallback all 1:6.0.1r16-1.1 [1807 kB] Get:5 http://deb.debian.org/debian bullseye/main amd64 poppler-data all 0.4.10-1 [1602 kB] Get:6 http://deb.debian.org/debian bullseye/main amd64 fonts-urw-base35 all 20200910-1 [6367 kB] Get:7 http://deb.debian.org/debian bullseye/main amd64 fontconfig-config all 2.13.1-4.2 [281 kB] Get:8 http://deb.debian.org/debian bullseye/main amd64 fonts-noto-mono all 20201225-1 [402 kB] Get:9 http://deb.debian.org/debian bullseye/main amd64 libgs9-common all 9.53.3~dfsg-7+deb11u2 [734 kB] Get:10 http://deb.debian.org/debian bullseye/main amd64 libavahi-common-data amd64 0.8-5 [124 kB] Get:11 http://deb.debian.org/debian bullseye/main amd64 libavahi-common3 amd64 0.8-5 [58.4 kB] Get:12 http://deb.debian.org/debian bullseye/main amd64 libavahi-client3 amd64 0.8-5 [62.1 kB] Get:13 http://deb.debian.org/debian bullseye/main amd64 libcups2 amd64 2.3.3op2-3+deb11u2 [350 kB] Get:14 http://deb.debian.org/debian bullseye/main amd64 libpng16-16 amd64 1.6.37-3 [294 kB] Get:15 http://deb.debian.org/debian bullseye/main amd64 libfreetype6 amd64 2.10.4+dfsg-1+deb11u1 [418 kB] Get:16 http://deb.debian.org/debian bullseye/main amd64 libfontconfig1 amd64 2.13.1-4.2 [347 kB] Get:17 http://deb.debian.org/debian bullseye/main amd64 libidn11 amd64 1.33-3 [116 kB] Get:18 http://deb.debian.org/debian bullseye/main amd64 libijs-0.35 amd64 0.35-15 [16.4 kB] Get:19 http://deb.debian.org/debian bullseye/main amd64 libjbig2dec0 amd64 0.19-2 [67.2 kB] Get:20 http://deb.debian.org/debian bullseye/main amd64 libjpeg62-turbo amd64 1:2.0.6-4 [151 kB] Get:21 http://deb.debian.org/debian bullseye/main amd64 liblcms2-2 amd64 2.12~rc1-2 [150 kB] Get:22 http://deb.debian.org/debian bullseye/main amd64 libopenjp2-7 amd64 2.4.0-3 [172 kB] Get:23 http://deb.debian.org/debian bullseye/main amd64 libpaper1 amd64 1.1.28+b1 [21.6 kB] Get:24 http://deb.debian.org/debian bullseye/main amd64 libdeflate0 amd64 1.7-1 [53.1 kB] Get:25 http://deb.debian.org/debian bullseye/main amd64 libjbig0 amd64 2.1-3.1+b2 [31.0 kB] Get:26 http://deb.debian.org/debian bullseye/main amd64 libwebp6 amd64 0.6.1-2.1 [258 kB] Get:27 http://deb.debian.org/debian bullseye/main amd64 libtiff5 amd64 4.2.0-1+deb11u1 [289 kB] Get:28 http://deb.debian.org/debian bullseye/main amd64 libgs9 amd64 9.53.3~dfsg-7+deb11u2 [2245 kB] Get:29 http://deb.debian.org/debian bullseye/main amd64 ghostscript amd64 9.53.3~dfsg-7+deb11u2 [98.0 kB] Get:30 http://deb.debian.org/debian bullseye/main amd64 libpaper-utils amd64 1.1.28+b1 [18.3 kB] Get:31 http://deb.debian.org/debian bullseye/main amd64 psutils amd64 1.17.dfsg-4 [59.1 kB] Fetched 17.1 MB in 1s (16.3 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package libapparmor1:amd64. (Reading database ... 16918 files and directories currently installed.) Preparing to unpack .../00-libapparmor1_2.13.6-10_amd64.deb ... Unpacking libapparmor1:amd64 (2.13.6-10) ... Selecting previously unselected package libdbus-1-3:amd64. Preparing to unpack .../01-libdbus-1-3_1.12.20-2_amd64.deb ... Unpacking libdbus-1-3:amd64 (1.12.20-2) ... Selecting previously unselected package dbus. Preparing to unpack .../02-dbus_1.12.20-2_amd64.deb ... Unpacking dbus (1.12.20-2) ... Selecting previously unselected package fonts-droid-fallback. Preparing to unpack .../03-fonts-droid-fallback_1%3a6.0.1r16-1.1_all.deb ... Unpacking fonts-droid-fallback (1:6.0.1r16-1.1) ... Selecting previously unselected package poppler-data. Preparing to unpack .../04-poppler-data_0.4.10-1_all.deb ... Unpacking poppler-data (0.4.10-1) ... Selecting previously unselected package fonts-urw-base35. Preparing to unpack .../05-fonts-urw-base35_20200910-1_all.deb ... Unpacking fonts-urw-base35 (20200910-1) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../06-fontconfig-config_2.13.1-4.2_all.deb ... Unpacking fontconfig-config (2.13.1-4.2) ... Selecting previously unselected package fonts-noto-mono. Preparing to unpack .../07-fonts-noto-mono_20201225-1_all.deb ... Unpacking fonts-noto-mono (20201225-1) ... Selecting previously unselected package libgs9-common. Preparing to unpack .../08-libgs9-common_9.53.3~dfsg-7+deb11u2_all.deb ... Unpacking libgs9-common (9.53.3~dfsg-7+deb11u2) ... Selecting previously unselected package libavahi-common-data:amd64. Preparing to unpack .../09-libavahi-common-data_0.8-5_amd64.deb ... Unpacking libavahi-common-data:amd64 (0.8-5) ... Selecting previously unselected package libavahi-common3:amd64. Preparing to unpack .../10-libavahi-common3_0.8-5_amd64.deb ... Unpacking libavahi-common3:amd64 (0.8-5) ... Selecting previously unselected package libavahi-client3:amd64. Preparing to unpack .../11-libavahi-client3_0.8-5_amd64.deb ... Unpacking libavahi-client3:amd64 (0.8-5) ... Selecting previously unselected package libcups2:amd64. Preparing to unpack .../12-libcups2_2.3.3op2-3+deb11u2_amd64.deb ... Unpacking libcups2:amd64 (2.3.3op2-3+deb11u2) ... Selecting previously unselected package libpng16-16:amd64. Preparing to unpack .../13-libpng16-16_1.6.37-3_amd64.deb ... Unpacking libpng16-16:amd64 (1.6.37-3) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../14-libfreetype6_2.10.4+dfsg-1+deb11u1_amd64.deb ... Unpacking libfreetype6:amd64 (2.10.4+dfsg-1+deb11u1) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../15-libfontconfig1_2.13.1-4.2_amd64.deb ... Unpacking libfontconfig1:amd64 (2.13.1-4.2) ... Selecting previously unselected package libidn11:amd64. Preparing to unpack .../16-libidn11_1.33-3_amd64.deb ... Unpacking libidn11:amd64 (1.33-3) ... Selecting previously unselected package libijs-0.35:amd64. Preparing to unpack .../17-libijs-0.35_0.35-15_amd64.deb ... Unpacking libijs-0.35:amd64 (0.35-15) ... Selecting previously unselected package libjbig2dec0:amd64. Preparing to unpack .../18-libjbig2dec0_0.19-2_amd64.deb ... Unpacking libjbig2dec0:amd64 (0.19-2) ... Selecting previously unselected package libjpeg62-turbo:amd64. Preparing to unpack .../19-libjpeg62-turbo_1%3a2.0.6-4_amd64.deb ... Unpacking libjpeg62-turbo:amd64 (1:2.0.6-4) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../20-liblcms2-2_2.12~rc1-2_amd64.deb ... Unpacking liblcms2-2:amd64 (2.12~rc1-2) ... Selecting previously unselected package libopenjp2-7:amd64. Preparing to unpack .../21-libopenjp2-7_2.4.0-3_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.4.0-3) ... Selecting previously unselected package libpaper1:amd64. Preparing to unpack .../22-libpaper1_1.1.28+b1_amd64.deb ... Unpacking libpaper1:amd64 (1.1.28+b1) ... Selecting previously unselected package libdeflate0:amd64. Preparing to unpack .../23-libdeflate0_1.7-1_amd64.deb ... Unpacking libdeflate0:amd64 (1.7-1) ... Selecting previously unselected package libjbig0:amd64. Preparing to unpack .../24-libjbig0_2.1-3.1+b2_amd64.deb ... Unpacking libjbig0:amd64 (2.1-3.1+b2) ... Selecting previously unselected package libwebp6:amd64. Preparing to unpack .../25-libwebp6_0.6.1-2.1_amd64.deb ... Unpacking libwebp6:amd64 (0.6.1-2.1) ... Selecting previously unselected package libtiff5:amd64. Preparing to unpack .../26-libtiff5_4.2.0-1+deb11u1_amd64.deb ... Unpacking libtiff5:amd64 (4.2.0-1+deb11u1) ... Selecting previously unselected package libgs9:amd64. Preparing to unpack .../27-libgs9_9.53.3~dfsg-7+deb11u2_amd64.deb ... Unpacking libgs9:amd64 (9.53.3~dfsg-7+deb11u2) ... Selecting previously unselected package ghostscript. Preparing to unpack .../28-ghostscript_9.53.3~dfsg-7+deb11u2_amd64.deb ... Unpacking ghostscript (9.53.3~dfsg-7+deb11u2) ... Selecting previously unselected package libpaper-utils. Preparing to unpack .../29-libpaper-utils_1.1.28+b1_amd64.deb ... Unpacking libpaper-utils (1.1.28+b1) ... Selecting previously unselected package psutils. Preparing to unpack .../30-psutils_1.17.dfsg-4_amd64.deb ... Unpacking psutils (1.17.dfsg-4) ... Setting up liblcms2-2:amd64 (2.12~rc1-2) ... Setting up libpaper1:amd64 (1.1.28+b1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.) debconf: falling back to frontend: Readline Creating config file /etc/papersize with new version Setting up libapparmor1:amd64 (2.13.6-10) ... Setting up fonts-noto-mono (20201225-1) ... Setting up libijs-0.35:amd64 (0.35-15) ... Setting up libdeflate0:amd64 (1.7-1) ... Setting up libpaper-utils (1.1.28+b1) ... Setting up fonts-urw-base35 (20200910-1) ... Setting up libjbig0:amd64 (2.1-3.1+b2) ... Setting up poppler-data (0.4.10-1) ... Setting up libjpeg62-turbo:amd64 (1:2.0.6-4) ... Setting up libjbig2dec0:amd64 (0.19-2) ... Setting up libidn11:amd64 (1.33-3) ... Setting up libavahi-common-data:amd64 (0.8-5) ... Setting up libdbus-1-3:amd64 (1.12.20-2) ... Setting up dbus (1.12.20-2) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Setting up libpng16-16:amd64 (1.6.37-3) ... Setting up libwebp6:amd64 (0.6.1-2.1) ... Setting up libopenjp2-7:amd64 (2.4.0-3) ... Setting up libtiff5:amd64 (4.2.0-1+deb11u1) ... Setting up fonts-droid-fallback (1:6.0.1r16-1.1) ... Setting up psutils (1.17.dfsg-4) ... Setting up libgs9-common (9.53.3~dfsg-7+deb11u2) ... Setting up fontconfig-config (2.13.1-4.2) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.) debconf: falling back to frontend: Readline Setting up libavahi-common3:amd64 (0.8-5) ... Setting up libfreetype6:amd64 (2.10.4+dfsg-1+deb11u1) ... Setting up libfontconfig1:amd64 (2.13.1-4.2) ... Setting up libavahi-client3:amd64 (0.8-5) ... Setting up libcups2:amd64 (2.3.3op2-3+deb11u2) ... Setting up libgs9:amd64 (9.53.3~dfsg-7+deb11u2) ... Setting up ghostscript (9.53.3~dfsg-7+deb11u2) ... Processing triggers for libc-bin (2.31-13+deb11u3) ... [email protected]:/# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 28916 19664 ? Ss Aug01 0:44 /usr/bin/python3 /usr/bin/supervisord -n -c /etc/supervisord.conf bacula 174 0.0 0.0 885804 4516 ? Ssl Aug01 0:05 /opt/bacula/bin/bacula-sd -u bacula -g tape -v -c /opt/bacula/etc root 181 0.0 0.0 277116 1988 ? Ssl Aug01 0:03 /opt/bacula/bin/bacula-fd -v -c /opt/bacula/etc/bacula-fd.conf bacula 188 0.0 0.0 1236664 7240 ? Ssl Aug01 0:02 /opt/bacula/bin/bacula-dir -u bacula -g bacula -v -c /opt/bacula/ root 199 0.0 0.0 2420 524 ? S Aug01 0:00 /bin/sh /usr/sbin/apache2ctl -D FOREGROUND root 201 0.0 0.0 209304 20292 ? S Aug01 0:14 /usr/sbin/apache2 -D FOREGROUND www-data 202 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND www-data 203 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND www-data 204 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND www-data 205 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND www-data 206 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND root 7398 0.0 0.0 4100 3292 pts/0 Ss+ Aug01 0:00 bash root 17717 0.0 0.0 4100 3496 pts/1 Ss 12:19 0:00 bash root 19475 0.0 0.0 6700 3012 pts/1 R+ 12:45 0:00 ps aux www-data 22127 0.0 0.0 209384 8856 ? S Aug01 0:00 /usr/sbin/apache2 -D FOREGROUND [email protected]:/# Since the last change in this image, I have been working for my employer 12-14 hours a day to finish the project and be able to go on vacation calmly and forgive me for taking into account several dozen people who wanted to migrate the entire virtual environment to the new hypervisor as soon as possible and it was a bit more urgent than implementing the email notification service in this docker, which you have been ignoring so far. Forgive me also that I want to spend my vacation with my family in exchange for the last weeks, when I didn't have time for them. Also, forgive me that your need to implement vchanger will be postponed, because after returning to work, an interesting project to implement ceph storage in my organization awaits. Forgive me for being teased too, but I don't like someone trying to lecture me but proving that they have no idea about it. This is my hobby, I don't have to do it, I can stop writing back to you like some other docker developers. And you can stop using this docker, it is your choice. I answered your every problem and even if I came home late from work, I found the strength and time to analyze your problem. And you without a second thought, google check, you say that I blocked to use apt in the container as well as the hostname settings. Regards
  13. @b0m541 try this version pwa666/bacula-server:11-postgresql-b0m It is a liitle bigger, because I made it from previous image with some permission fixes. Tell me if it can run longer then "6 minutes". Try to not make any backups, because if I remember You have mounted backup disks outside /mnt/bacula, and could be some permission issues. I only want to know if it can run longer, and without "segmentantion error"
  14. Lots of text but little useful information. If the Timemachine does not have the same ip address that the bacula server uses, the timemachine configuration is irrelevant to me. If the bacula-dir process crashes it is normal for bconsole not to connect, no matter if it is on localhost or called by fqdn. This change is completely pointless, localhost will always be a local connection within this container, unless you intend to separate bconsole and bacula-dir but that won't be part of the container support anymore. First of all, what you have in "Path where bacula's logs will be stored on Host disk", the log should contain information about what caused the bacula process to crash. Otherwise, within the container, you need to run the process in debug mode: /opt/bacula/bin/bacula-dir -u bacula -g bacula -v -d 1 if you know that the problem will occur within 6 minutes, then after 6 minutes you will see the following error in the console. And fyi, bacula-fd does not connect to bacula-dir, it is always bacula-dir that connects. bacula-fd can make connections to bacula-sd.