Re: [Bacula-users] Now it is the Docker plugin....
Hello Radosław, Everyone, Yes, bacula-fd service is running as root user, as well as the docker services, while other docker processes are running under my user-id instead. Both bacula and docker using standard installation configurations with minimal tweeks, if any. The funny bits are the different results from the "/usr/bin/docker image ls ..." command to list my containers - just 1 container at this moment. When I run the command "docker image ls ...", I get nothing. Only AFTER I start the docker desktop application I get to see my container. But when the command is run by bacula-fd (under the root user), docker does not show any containers - it misses my container!! Same thing happens when I run "sudo docker image ls..." Nothing is listed. It seems that docker desktop is like a "private user docker" instance, distinct from a "system docker" that bacula tries to connect to. So, I'll try to find an answer for that from the docker users group, and I'll report back here. Any suggestions? Cheers, Ismael ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: Failure to run proxied backup job from behind a firewall/NAT gateway using Client Initiated Backup feature
I'm trying to use the feature explained in the Bacula Community Main Users Guide section 3.3 "Client Behind NAT Support with the Connect To Director Directive". The FD behind the NAT appears convinced the Director invoking the run request is running in Monitor mode - I have tried in the client's bacula-fd.conf to add "Monitor = no" directive, and restart the bacula-fd service, but to no avail. I tried adding "Remote = yes" and "Monitor = no" to the bacula-dir.conf Client directive referenced by the job I'm invoking, but these fields are apparently not allowed and were rejected by the software so I reverted them and restarted the director. I am trying to launch the job both via the Bacularis web interface and via the bconsole remote proxy interface, with the same immediate failure after 2 seconds (shown in red below) I am reading the documentation, but I'm really down to trial and error here, any suggestions ? Thanks, On 2024-03-12 6:41 a.m., Myles Dear wrote: > Update : Here are the bacula logs from the server side when I attempt a > client initiated backup from the client. > > Any ideas on what this error means, and how to resolve this? > > 12-Mar 11:22 cloud-dir JobId 241: Start Backup JobId 241, > Job=KhapBackupVcuClient1.2024-03-12_11.22.15_31 > 12-Mar 11:22 cloud-dir JobId 241: Connected to Storage "File1" at orb:9103 > with TLS > 12-Mar 11:22 cloud-dir JobId 241: Using Device "FileChgr1-Dev1" to write. > 12-Mar 11:22 cloud-dir JobId 241: Connected to Client "vcuproject2030-fd" at > localhost:9104 with TLS > 12-Mar 11:22 cloud-dir JobId 241: Fatal error: File daemon "baremetal-fd" > rejected Job command: 2997 Invalid command for a Director with Monitor > directive enabled. > > 12-Mar 11:22 orb-dir JobId 241: Fatal error: No Job status returned from FD. > 12-Mar 11:22 orb-dir JobId 241: Error: Bacula Enterprise orb-dir 13.0.3 > (02May23): > Build OS: x86_64-pc-linux-gnu-bacula-enterprise ubuntu 22.04 > JobId: 241 > Job: MyBackupJob.2024-03-12_11.22.15_31 > Backup Level: Full > Client: "baremetal-fd" 13.0.3 (02May23) > x86_64-pc-linux-gnu-bacula-enterprise,ubuntu,22.04 > FileSet: "Full Set" 2024-01-18 06:23:13 > Pool: "File" (From Job resource) > Catalog: "MyCatalog" (From Client resource) > Storage: "File1" (From Job resource) > Scheduled time: 12-Mar-2024 11:22:13 > Start time: 12-Mar-2024 11:22:17 > End time: 12-Mar-2024 11:22:18 > Elapsed time: 1 sec > Priority: 10 > FD Files Written: 0 > SD Files Written: 0 > FD Bytes Written: 0 (0 B) > SD Bytes Written: 0 (0 B) > Rate: 0.0 KB/s > Software Compression: None > Comm Line Compression: None > Snapshot/VSS: no > Encryption: no > Accurate: yes > Volume name(s): > Volume Session Id: 16 > Volume Session Time: 1709388420 > Last Volume Bytes: 2,809,442,893 (2.809 GB) > Non-fatal FD errors: 1 > SD Errors: 0 > FD termination status: Error > SD termination status: Waiting on FD > Termination: *** Backup Error ***___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Now it is the Docker plugin....
Hello, Please reply to bacula-users list, so all can help you or benefit from our discussion. pon., 11 mar 2024 o 02:38 Ismael Matos napisał(a): > Hello Radosław. > > *This is the console output from a freshly restarted system.* > *From the bacula trace, I've found that the docker plugin uses a > variation of "docker ps -a" command.* > *While the 2 docker services are up automatically after the system > restart, but the "docker ps -a" command says different. * > > > im@imcserv24:~$ /usr/bin/docker ps -a --no-trunc=true > Cannot connect to the Docker daemon at > unix:///home/im/.docker/desktop/docker.sock. Is the docker daemon running? > What user bacula-fd is running on? Is it "im"? If not then this test is useless. You need to check it on the user which runs bacula-fd. In most cases it is a "root". im@imcserv24:~$ sudo systemctl status docker* > [sudo] password for im: > ● docker.service - Docker Application Container Engine > Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: > enabled) > Active: active (running) since Mon 2024-03-11 00:05:37 GMT; 1min 24s > ago > TriggeredBy: ● docker.socket >Docs: https://docs.docker.com >Main PID: 1674 (dockerd) > Tasks: 10 > Memory: 105.4M > CPU: 715ms > CGroup: /system.slice/docker.service > └─1674 /usr/bin/dockerd -H fd:// > --containerd=/run/containerd/containerd.sock > > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.092629876Z" level=info msg="Starting up" > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.108840311Z" level=info msg="detected 127.0.0.53 > nameserver, ass> > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.435263475Z" level=info msg="[graphdriver] using > prior storage d> > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.440764468Z" level=info msg="Loading containers: > start." > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:37.107855184Z" level=info msg="Default bridge > (docker0) is assigne> > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:37.199167737Z" level=info msg="Loading containers: > done." > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:37.269123107Z" level=info msg="Docker daemon" > commit=061aa95 conta> > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:37.270738445Z" level=info msg="Daemon has completed > initialization" > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:37.342865821Z" level=info msg="API listen on > /run/docker.sock" > Mar 11 00:05:37 imcserv24.imc systemd[1]: Started docker.service - Docker > Application Container Engine. > > ● docker.socket - Docker Socket for the API > Loaded: loaded (/lib/systemd/system/docker.socket; enabled; preset: > enabled) > Active: active (running) since Mon 2024-03-11 00:05:28 GMT; 1min 33s > ago >Triggers: ● docker.service > Listen: /run/docker.sock (Stream) > Tasks: 0 (limit: 19048) > Memory: 0B > CPU: 1ms > CGroup: /system.slice/docker.socket > > Mar 11 00:05:28 imcserv24.imc systemd[1]: Starting docker.socket - Docker > Socket for the API... > Mar 11 00:05:28 imcserv24.imc systemd[1]: Listening on docker.socket - > Docker Socket for the API. > > > *Just after the previous command: * > > > im@imcserv24:~$ /usr/bin/docker ps -a --no-trunc=true > Cannot connect to the Docker daemon at > unix:///home/im/.docker/desktop/docker.sock. Is the docker daemon running? > > > *After a few minutes. Still the same results:* > > > im@imcserv24:~$ /usr/bin/docker ps -a --no-trunc=true > Cannot connect to the Docker daemon at > unix:///home/im/.docker/desktop/docker.sock. Is the docker daemon running? > im@imcserv24:~$ sudo systemctl status docker* > ● docker.service - Docker Application Container Engine > Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: > enabled) > Active: active (running) since Mon 2024-03-11 00:05:37 GMT; 5min ago > TriggeredBy: ● docker.socket >Docs: https://docs.docker.com >Main PID: 1674 (dockerd) > Tasks: 10 > Memory: 104.0M > CPU: 799ms > CGroup: /system.slice/docker.service > └─1674 /usr/bin/dockerd -H fd:// > --containerd=/run/containerd/containerd.sock > > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.092629876Z" level=info msg="Starting up" > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.108840311Z" level=info msg="detected 127.0.0.53 > nameserver, ass> > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.435263475Z" level=info msg="[graphdriver] using > prior storage d> > Mar 11 00:05:36 imcserv24.imc dockerd[1674]: > time="2024-03-11T00:05:36.440764468Z" level=info msg="Loading containers: > start." > Mar 11 00:05:37 imcserv24.imc dockerd[1674]: >
