latest update failed in the dracut command

The latest software update (Friday Nov 18th, 2022) failed on two commands during the dracut kernal update process.

localhost:/home/owner # /usr/bin/dracut -f /boot/initrd-5.14.21-150400.24.33-default 5.14.21-150400.24.33-default
dracut: Executing: /usr/bin/dracut -f /boot/initrd-5.14.21-150400.24.33-default 5.14.21-150400.24.33-default
dracut: dracut module ‘memstrack’ will not be installed, because command ‘memstrack’ could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module ‘memstrack’ will not be installed, because command ‘memstrack’ could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: *** Including module: systemd ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: rngd ***
dracut: *** Including module: i18n ***
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
/usr/lib/plymouth/plymouth-populate-initrd: line 450: +: command not found
dracut: *** Including module: btrfs ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: kernel-modules-extra ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: suse-btrfs ***
dracut: *** Including module: suse-xfs ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: biosdevname ***
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: haveged ***
dracut: *** Including module: ostree ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including module: suse ***
dracut: *** Including module: suse-initrd ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies ***
dracut: *** Installing kernel module dependencies done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done ***
dracut: *** Hardlinking files ***
dracut: Mode: real
dracut: Files: 1105
dracut: Linked: 1 files
dracut: Compared: 0 xattrs
dracut: Compared: 156 files
dracut: Saved: 692 B
dracut: Duration: 0.007164 seconds
dracut: *** Hardlinking files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing GenuineIntel.bin ***
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut: rd.driver.pre=btrfs
dracut: root=UUID=c39847c8-a96b-4977-a909-47b19192521c rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=256,subvol=/@,subvol=@
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Creating image file ‘/boot/initrd-5.14.21-150400.24.33-default’ ***
dracut: *** Creating initramfs image file ‘/boot/initrd-5.14.21-150400.24.33-default’ done ***
localhost:/home/owner #

I brought up the yast2 software configurater but both memstrack and procps-n executables could NOT be found.

Can someone kindly point me to the appropriate openSuse Leap 15.4 software repository where these 2 commands are found, so that I can install them on my system and re-execute the dracut command?? I believe that this is important while updating the kernel.

P.S. I have noticed lately that the dracut command is expecting some commands to be on the user’s system, but they are NOT there Perhaps the routine can be fixed so that necessary executables can be checked before running the dracut command and getting warnings ???

I ignore these messages:

**erlangen:~ #** journalctl -b -g 'please install' 
Nov 18 05:25:05 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
Nov 18 05:25:05 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
Nov 18 05:25:09 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
Nov 18 05:25:10 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
Nov 18 05:25:14 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
Nov 18 05:25:14 erlangen zypper[22839]: dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng 
**erlangen:~ #** 

I have more in the dracut command, but the initrd is build and all is working fine:

.
.
.
.
.
dracut: dracut module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found!
dracut: dracut module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found!
dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found!
dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsiadm' could not be found!
dracut: dracut module 'iscsi' will not be installed, because command 'iscsid' could not be found!
dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found!
dracut: memstrack is not available
dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng
dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found!
dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found!

The man pages for dracut are a good starting point to understand the whole concept.

https://man7.org/linux/man-pages/man…modules.7.html

dracut creates an initial image used by the kernel for preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem.

dracut uses a modular system to build and extend the initramfs image.

Adding dracut Modules
Some dracut modules are turned off by default and have to be activated manually. You can do this by adding the dracut modules to the configuration file
/etc/dracut.conf or /etc/dracut.conf.d/myconf.conf. See dracut.conf(5). You can also add dracut modules on the command line by using the -a or --add
option:

Only modules that are needed for your hardware/software setup are installed and get loaded. So absolutely nothing is “failing” on your system as it works as intended.

I went to git and did this command

git clone https://aur.archlinux.org/packages/memstrack/

The I ran “make” and “make install” under root privileges.
Redoing the dracut command executed with no warnings.

Normally make should under user install as root