Failed to connect to remote backup service Veeam - veeam

Backup veeam failled .
07/10/2022 08:11:14 :: Error: Failed to connect to remote backup service.
07/10/2022 08:11:30 :: Processing finished with errors at 07/10/2022 08:11:30
07/10/2022 11:23:33 :: Failed to send backup job configuration to Error: Failed to update backup job
Managed by agent job ID: 96539a-6eae-54-8a8e7c2f.
Managed by agent job name: Backup_PC.
Invalid job configuration.
Failed to connect to remote backup service.

Related

How to connect QEMU qmp-shell to a VM via unix socket?

I followed this tutorial to connect qmp-shell to a QEMU VM instance.
1. Start QMP on a unix socket
# qemu-system-aarch64 -M virt -qmp unix:./qmp-sock,server,wait=off
2. Run the script
# qmp-shell ./qmp-sock
3. You should get the following prompt
(QEMU)
But step 2 gives below error:
ERROR: Couldn't connect to ./qmp-sock: Failed to establish connection: [Errno 2] No such file or directory
What could be wrong?

Cannot start minishift on mac Catalina

I tried a couple of time to install uninstall and reinstall openshift on 2 macs with os Catalina 10.15.7 but it never starts.
I read Minishift cannot start in macOS and installed the var as described. but I still get the error below. Did anybody manage to install it on Catalyna and managed to resolve these errors?
kind regards
Markus
-- Starting Minishift VM ........ FAIL E0423 15:57:02.814314 21785 start.go:499] Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: /usr/local/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
. Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error in driver during machine creation: Error setting up host only network on machine start: /usr/local/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
It seens a virtualbox configuration error about network access deniying. Try this:
Access or create file /etc/vbox/networks.conf (or where your vbox configuration file is located)
Change the content to: *0.0.0.0/0 ::/0

Couchbase server Restore

I am trying to restore a couchbase base from the backup file. I used the following command:
./cbrestore
/backup/2019-02-06T121650Z-full
http://127.0.0.1:8091
-u Administrator -p password
–bucket-source=my_bucket
–bucket-destination=my_bucket
When I run the command I get the following error:
s0 error: async operation: error: conn.send() exception:
[Errno 32] Broken pipe on sink: http://10.128.0.2:8091(my_bucket#10.128.0.2:8091)
error: conn.send() exception: [Errno 32] Broken pipe
I used:
couchbase-server5.1.1 community edition
My backup has the sync_gateways sync data also:
couchbase-sync-gateway 1.5.1 version

Recurring "Can't connect to MySQL server .. Temporary failure in name resolution" in GKE cluster

I deployed MySQL server using mysql:5.7 image on my GKE cluster. Its deployed with one replica and exposed with a ClusterIP service named "mysql-server".
In the last few hours I'm experiencing recurring flaky errors from other pods that are running Python servers:
sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'mysql-server' ([Errno -3] Temporary failure in name resolution)")
I've gone over Kubernetes DNS debugging and found no errors or other issues, except for CoreDNS not running at all in any of my clusters.
When executing nslookup mysql-server on another pod, I'm getting an healthy output.
Server: 10.39.240.10
Address: 10.39.240.10#53
Name: mysql-server.default.svc.cluster.local
Address: 10.39.245.88
However, ping mysql-server never returns, don't know if its relevant.
PING mysql-server.default.svc.cluster.local (10.39.245.88) 56(84) bytes of data.
^C
--- mysql-server.default.svc.cluster.local ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2039ms
Would this be an issue on mysql or GKE? How can I debug it further?

Getting error: operation failed: Failed to connect to remote libvirt error when I try doing kvm migration using virsh on debian

I am getting the error message
error: operation failed: Failed to connect to remote libvirt URI qemu+ssh://mytargethostname.mydomain.com/system: Cannot recv data: Host key verification failed.: Connection reset by peer
when I try to run the kvm migration command like this
virsh migrate --verbose --live --p2p --tunnelled hosttomigrate qemu+ssh://mytargethostname.mydomain.com/system
I can successfully view the running vms on the target host when I run
virsh -c qemu+ssh://mytargethostname.mydomain.com/system list --all
Is there some special configuration that I may need for kvm ?