Peter Kuykendall

UPDATE: I walked through the code for drblpush and found it calls another program drbl-get-dnsserver. That code includes the following: # On Ubuntu, dnsmasq with network-manager, the result might 127.0.0.1. We use nm-tool to get the real one # Ubuntu >= 17.10 or Debian >= 9, use "systemd-resolve --status" The problem is that Ubuntu 22 systemd-resolv has been replaced by resolvectl. This info is per https://askubuntu.com/questions/1409726/systemd-resolve-command-not-found-in-ubuntu-22-04-desktop For...

Hi. I've been running a Clonezilla server forever, but it was stuck at Ubuntu 12, so I decided to build a new one. It's in a VM based on Ubuntu 22.04 server. I set up the LAN NIC as 192.168.56.1 static. WAN NIC is DHCP. When I run drblpush -i it fails with the nameserver unset message. I've added the nameserver line to /etc/drbl/drblpush.conf but it didn't help. I then added it to /etc/resolv.conf and that didn't help either. Here's the output: root@cz05:/home/pete# drblpush -i ******************************************************...

UPDATE: I walked through the code for drblpush and found it calls another program drbl-get-dnsserver. That code includes the following: # On Ubuntu, dnsmasq with network-manager, the result might 127.0.0.1. We use nm-tool to get the real one # Ubuntu >= 17.10 or Debian >= 9, use "systemd-resolve --status" The problem is that Ubuntu 22 systemd-resolv has been replaced by resolvectl. This info is per https://askubuntu.com/questions/1409726/systemd-resolve-command-not-found-in-ubuntu-22-04-desktop For...

Hi. I've been running a Clonezilla server forever, but it was stuck at Ubuntu 12, so I decided to build a new one. It's in a VM. I set up the LAN NIC as 192.168.56.1 static. WAN NIC is DHCP. When I run drblpush -i it fails with the nameserver unset message. I've added the nameserver line to /etc/drbl/drblpush.conf but it didn't help. I then added it to /etc/resolv.conf and that didn't help either. Here's the output: root@cz05:/home/pete# drblpush -i ******************************************************...

Adding denyhosts.conf

Running but not acting on invalid users

Interesting info on the BT method, thanks. I think my first step will be to clone the disk image of my Clonezilla VM's virtual disk to a physical disk in a physical machine. From there I will try running my Clonezilla server as a physical machine, rather than a VM. That should be a pretty easy test to run and will allow me to quickly see if ditching the problematic Virtualbox fixes it or not. If it doesn't fix it I'll explore other paths. I don't want to mess with the OS configuration if I can help...

This problem was intermittent for us. Now it has reappeared and I've spent some time running tests and gathering data. I'm getting closer to root cause. I stuck with NFS because it disappeared before I could switch to SSH. As it turns out, NFS isn't the problem. I'm running Clonezilla Server in a virtual machine on Ubuntu 12.04. The host is running CentOS release 6.9 (Final), hosting with VirtualBox 5.1.22r115126. It has a gigabit Ethernet interface to the LAN. When we are restoring images to random...