Hey together,

FYI: I solved the issue by adding following dependencies to the client 
(auth61 machine)      

   -  python3-requests
   -  python3-urllib3
   -  python3-pyvmomi

+ adding Plugin Directory/Name 
to /etc/bareos/bareos-fd.d/client/myself.conf:

# 
# Ansible managed 
# 

Client { 
 Name = "auth-test61.DOMAIN.local" 
 Messages = "Standard" 
 Plugin Directory = /usr/lib64/bareos/plugins 
 Plugin Names = python3 
}

I thought until this hour that the vmware plugin worked "agentless" in a 
matter of not needing to define anything but the filedaemon on the client 
machine,.

I appreciate all your help.

Best Regards
Max
Max schrieb am Donnerstag, 23. Mai 2024 um 15:12:19 UTC+2:

> Hey,
>
> I added the Plugin Dir & Name Parameter to the bareos-sd.conf and 
> bareos-dir.conf and the Plugin seems to be referenced correctly on a local 
> level. (the fatal error went away)
> However, if I start the Backup it gets stuck in a endless loop and the 
> trace says:
>
> 23-Mai-2024 15:07:27.228320 storage-test01.DOMAIN.local (100): 
> lib/bsock_tcp.cc:217-13 Current host[ipv6;::1;9103]  All 
> host[ipv6;::1;9103] host[ipv4;192.168.
> 6.34;65535]  
> 23-Mai-2024 15:07:27.228400 storage-test01.DOMAIN.local (100): 
> lib/bsock_tcp.cc:217-13 Current host[ipv4;192.168.6.34;9103]  All 
> host[ipv6;::1;9103] host[ipv4
> ;192.168.6.34;9103]  
> 23-Mai-2024 15:07:27.228432 storage-test01.DOMAIN.local (100): 
> lib/bsock_tcp.cc:116-13 Unable to connect to Storage daemon on 
> storage-test01.DOMAIN.local:9103
> . ERR=Verbindungsaufbau abgelehnt
>
>
> it seems that the python3 is not loaded as it should be:
>
> *status client=auth-test61-fd 
> Connecting to Client auth-test61-fd at auth-test61.DOMAIN.local:9102 
> Handshake: Immediate TLS, Encryption: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 
>
> auth-test61.DOMAIN.local Version: 23.0.3~pre112.7df7ba8e1 (14 May 2024) 
>  Red Hat Enterprise Linux release 9.1 (Plow) 
> Daemon started 23-Mai-24 14:44. Jobs: run=0 running=0, Bareos community 
> binary 
> Sizeof: boffset_t=8 size_t=8 debug=0 trace=0 bwlimit=0kB/s 
>
> Running Jobs: 
> storage-test01.Domain.local (director) connected at: 23-Mai-24 15:09 
> No Jobs running. 
> ==== 
>
> Best regards
> Max
>
> Andreas Rogge schrieb am Donnerstag, 23. Mai 2024 um 14:07:59 UTC+2:
>
>> Am 23.05.24 um 14:01 schrieb Max: 
>> > Hey Andreas, 
>> [...] 
>> > and i still got the fatal error of the Plugin Dir not found. What 
>> itches 
>> > me is that the myself.conf names calls specifically  python3 while the 
>> > Plugin Definition in the FileSet says "python" as the docs say, is that 
>> > correct? 
>>
>> Does a status client for that client list the python3 plugin as loaded? 
>>
>> -- 
>> Andreas Rogge [email protected] 
>> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> 
>> http://www.bareos.com 
>>
>> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 
>> Komplementär: Bareos Verwaltungs-GmbH 
>> Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/a6939a89-8311-4538-a7a8-b2ada4348976n%40googlegroups.com.

Reply via email to