stevenshiau / drbl Goto Github PK

It looks like the SSH key generation on a drblpush is done one by one. On systems with large subnets assigned, this can take a considerable amount of time. I would really like to see the key generation run in parallel.

parallel -j 32 cat /dev/zero | ssh-keygen -q -t rsa -N '' {}

Any way to have both BIOS and EFI support without having to change the pxelinux config, thus making it mutually exclusive?

Hi everyone
I'm having trouble using ip_start option with drblpush
I had an eye into the code and see that this value appear to be never used.
Probably I'm wrong and missing something so if somebody culd explain I'd appreciate!

systemd 227[0] enforces that /etc/mtab isn't a regular file and freezes the system during boot if it is. This is only a temporary issue as the behavior is patched[1] away in the next version of systemd.

A temporary workaround is to create a symlink instead in init.drbl:

diff --git a/setup/files/misc/init.drbl b/setup/files/misc/init.drbl
index 73ea98a..f8e5e8d 100755
--- a/setup/files/misc/init.drbl
+++ b/setup/files/misc/init.drbl
@@ -352,11 +352,7 @@ maybe_break drbl_postnfs
 rm -f /etc/mtab /etc/mtab~ /etc/mtab~~ /etc/nologin

 # if, for any reason, mtab was not synced with what it should be, Sync it.
-while read ilist; do
-  # skip the "rootfs / rootfs rw 0 0" 
-  [ -n "$(echo $ilist | grep -E "^rootfs \/ rootfs .*")" ] && continue
-  echo $ilist >> /etc/mtab
-done < /proc/mounts
+ln -sf /proc/mounts /etc/mtab

 # umount the useless /initrd/proc and /initrd if they exist.
 for i in /initrd/proc /initrd; do

I'm not familiar enough with the internals to know if this creates any issues (due to rootfs not being removed), but it works in our current setup.

systemd 227 is currently used in Debian Stretch and Sid.

[0] http://lists.freedesktop.org/archives/systemd-devel/2015-October/034509.html
[1] systemd/systemd@5dea1c1

I'm using latest stable version of drbl, booted from ISO.
I have only one NIC and as I clone in a isolated network, I'm trying NOT to configure an alias.
During config phase of "start DRBL", I answer no, neverthelesee, the alias is created.
Beside this, is there a way to "reset" all network config, so I can try again without rebooting the whole system ?
Thx for the great work btw.

Hi Steve;
Back in 2012 I did a working env of the DRBL, now my requirement is not imaging over LAN or a terminal from the server. But the ability to give the thins a graphical environment with their remote home dirs which include personal chrooted dirs saved at the server.
An example could be like a puppy linux + some customized apps inside this image plus the home dirs of users which are saved at the server side. The application of this project could be for offices that maintain a high level of cost-control and efficiency while users data is not lost and the source image is loaded from the server to the diskless clients.
Reading recently found out that there is little regarding the users dir and how to mount them in the working env of a projected image to the thin client. Can you provide me some guideline and direction
Very much appreciate it. Thanks

Hi, I'm trying to set up a DRBL server to do network backups of all my PCs, but I'm having trouble setting up the NICs.

My setup is this: the PC is a virtual machine running on TrueNAS CORE and the OS is Ubuntu Server 23.10. The network service running on it is netplan. The virtual machine has two NICs and they show in Ubuntu as different network interfaces. When I try to run "drblpush -i" the setup stops after setting the client hostname prefix saying "You did NOT setup any Internet network settings for the network cards for the clients (such as the IP address of eth1, eth2, ...), or something wrong!"

If I list the network interfaces, they don't show as ethx, but as enp0sx.

Does drbl expect to find networks named ethx? Or am I missing something?
Can you give me some hints?

Thank You in advance for your time.

Specifically this.
Is it still performing grub config file check?
If not, why is such an "altering" option enabled by default in Clonezilla?

And is it normal the parameter in sourced is called "msg_ocs_onthefly_param_g" even though (at least in disk_to_local_disk mode) it is called "-g auto" then? Like here but with the aforementioned description.

Dear @stevenshiau,

It is planned to have a new version after several years?

Latest news: 2016-11-01 https://sourceforge.net/p/drbl/news/

https://sourceforge.net/projects/drbl/files/

• live testing: 2.6.2-1 (2019-12-10)
• stable: 2.25.10 (2017-08-03)
• live stable: 2.5.1-16 (2017-03-28)

Thanks in advance.

I have an MPI cluster I do some work on at home.

My DRBL server is hosted as VM on my NAS, and is more powerful than my compute nodes. Ideally, I want it to be a part of the cluster after it has served the clients their OS and file system.

I found that when I run
mpiexec -np 12 -hostfile /mirror/cluster_machines python /mirror/approx_pi.py
I get the following:
[proxy:0:0@cn1] HYDU_sock_connect (utils/sock/sock.c:145): unable to connect from "cn1" to "drbl" (connection refused)
[proxy:0:0@cn1] main (pm/pmiserv/pmip.c:183): unable to connect to server drbl at port 42597 (check for firewalls!)
[proxy:0:1@cn2] HYDU_sock_connect (utils/sock/sock.c:145): unable to connect from "cn2" to "drbl" (connection refused)
[proxy:0:1@cn2] main (pm/pmiserv/pmip.c:183): unable to connect to server drbl at port 42597 (check for firewalls!)

But when I run it on cn1 alone, using just cn1 and cn2 as workers, they talk to each other and run fine.

I also noticed I can ssh into cn1. I get the prompt:
node@cn1:~$
and from there I can ssh into cn2, and get the correct prompt:
node@cn2:~$
but if I try to ssh into drbl from a client, it seems to log in fine, but the prompt stays the same as the client I tried to log in from. Additionally, when I type "exit" and get out of the ssh session, it says:
logout Connection to drbl closed.
although it doesn't seem to have ever really logged in..

Can someone help me with the firewall settings so I can add my DRBL server into my cluster?

Hello. Could you please add p7zip-full in your project for unpacking 7-zip archives?

That would avoid me to run a linux image in virtualbox just to do that.

I m creating a custom service in /srv/cluster/bin/ and linking to /tftpboot/nodes/10.1.1.1/etc/init.d/ with:

ln -s /srv/cluster/bin/node_service /tftpboot/nodes/10.1.1.1/etc/init.d/node_service

When use:

drbl-client-service node_service on

not create /rc0.d /rc1.d ... bindings in /tftpboot/nodes/10.1.1.1/etc/.

Where from drbl-client-service copy the services?

Then i modify de file /usr/sbin/drbl-client-service. I m using debian jessie and insserv.

In switch 'on' option, in line

chroot $ihost/ insserv $service &> /dev/null

i rewrite to

insserv -p $ihost/etc/init.d/ $service

Then the bindings works and image templates were created.

I m creating a custom service in /srv/cluster/bin/ and linking to /tftpboot/nodes/10.1.1.1/etc/init.d/ with:

ln -s /srv/cluster/bin/node_service /tftpboot/nodes/10.1.1.1/etc/init.d/node_service

When use:

drbl-client-service node_service on

not create /rc0.d /rc1.d ... in bindings /tftpboot/nodes/10.1.1.1/etc/.

Then i modify de file /usr/sbin/drbl-client-service. I m using debian jessie and insserv.

In switch on option, in line

chroot $ihost/ insserv $service &> /dev/null

i rewrite to

insserv -p $ihost/etc/init.d/ $service

Then the bindings works and image templates were created.

Whether I put files manualy using insserv -p /tftpboot/nodes/10.1.1.1/etc/init.d/ node_service, these are cleaned when I use dcs. Why?

I using DRBL to create a cluster in shared computer labs. I need to add the service in startup to all nodes.

I do not understand that files need stay in node_root or nodes. Whether I using ssi, why the files not stay on node_root only?

Sorry, I dont speak english.

I am trying to load a new systemd service on Ubuntu 18.04 and it's not working. On the client, I see the systemd file, but it's showing as inactive.

When using resolvconf, the systemd service does not load and DNS queries are broken.

DRBL: drbl-4.5.16-drbl1.noarch.rpm

Operating System: Fedora Linux 37 (Server Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:37
Kernel: Linux 6.1.8-200.fc37.x86_64
Architecture: x86-64
Hardware Vendor: Dell Computer Corporation
Hardware Model: PowerEdge SC1425
Firmware Version: A03

SELINUX=disabled

*****************************************************.
Installing DRBL for RedHat/Fedora Linux...
Your OS version is:: FC37
*****************************************************.
Do you want to set up the proxy server?
[y/N] N

*****************************************************.
No yum repository setting found!
You must set the yum repository in /etc/yum.repos.d/!
*****************************************************.

Program terminated!

Why would a yum repository be needed?

I'm using DRBL as the base of a PXE-based testing and imaging platform (Panucci, if you're interested in what it is), and every morning, I have to power on the server, wait for it to power on, and then run drblpush with our existing configuration.

How do I make it so that I can start up the necessary services without creating the images every time, or at least without making the user hit enter each time?