Posts by webman

webman · Installation

Hi!
I am reading invoke-rc.d: could not determine current runlevel already on my last install
and faceing it at my current install again. So I have two setups with this error and I do not
know, where to look for it.
I am not a specialist, but one mentioned (together with other hints):

The service’s startup script is not working properly.

https://hatchjs.com/invoke-rc-d-could-n … -runlevel/
The message is in bootlog and appears between:

Starting Setting kernel variables: sysctl.
Starting: AppArmorLoading AppArmor profiles...done.
.
Configuring network interfaces...invoke-rc.d: could not determine current runlevel
invoke-rc.d: could not determine current runlevel
done.
Cleaning up temporary files....

And a mysterious DOT in a single line - WHO logs????
The network is ok.

The first computer does not start my LXC (container) which is set to autostart.
At this box, I tracked the occurence better (and I am just in an eraly state after
the networked setup) and it appears, after I installed some firmware packages
(amd64-microcode firmware-amd-graphics firmware-linux firmware-linux-free firmware-linux-nonfree firmware-realtek)
But the error persists if I remove (including purge) the packages and reboot.

For the first box, the problem may cause this:

$ ls /var/lib/lxcfs
ls: cannot access '/var/lib/lxcfs/sys': Input/output error
ls: cannot access '/var/lib/lxcfs/cgroup': Input/output error
total 0
dr-xr-xr-x 2 root root 0 2024-07-19 09:23:27 proc/
?????????? ? ?    ?    ?                   ? cgroup
?????????? ? ?    ?    ?                   ? sys

I am using fresh network install of devuan daedalus with kernel 6.1.0-23-amd64
Can someone help?
Thanks,
Manfred

webman · Hardware & System Configuration

Hi!

Just stumpled over this ...
Yes, I told them!

Regards,
Manfred

webman · Hardware & System Configuration

Hi!

Thanks for your investigation.
Not sure, if bridge-utils are really need, but I use them because its an easier way then "ip-link".
I usually use 'ifquery' ether with '--list' or '--state' but it does not show my second bridge, even
though 'ip link' shows it.
I know the problem with the member ports and on my current workstation the solution was to
give it a dummy address ("0.0.0.0"). The bridges are for containers and LXC, so there is no
definitiv port at computer start - which was never a problem to me.
But there is "/etc/network/if-pre-up.d/bridge -> /lib/bridge-utils/ifupdown.sh*"
which should solve the problem (that ip link is not persistent) and read "interfaces".
I have two comparable computers (hardware and VM), both Devuan5. If I look into /var/log/boot:

Starting: AppArmorLoading AppArmor profiles...done.
Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts ... (warning).
invoke-rc.d: could not determine current runlevel
if-up.d/mountnfs[eth1]: waiting for interface lanbr before doing NFS mounts ... (warning).
invoke-rc.d: could not determine current runlevel

Note: waiting for interface lanbr ....
I am even not capable to write everthing, I saw. But a internet search for

"2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP>"

Exactly this is part of my experience, were the bridge and even sometime
a hardware inferace shows this strange status!
This earch gives tons of similar messages, a hint of apparmor bug, of Kernel 6.1 bug and more.
You remove a VF from a dual-nic and suddenly, the other(!) port does not get carrier! I changed the NIC with the exact same from another computer (shown in the log-excerpt above) with not changes and the other box does not have that problem.
The whole story started with unexpected behavior of a kvm-guest, which had no traffic. But then I made the same, step-by-step on this host itself (create bridge, create macvlan) and everythings works - repeated this using LXC, works.
I made a port mirror on the hardware-switch - no packages came out, if the VM runs ..... but you see the packets on the host.
Something drops them. Due to the probability, this could be some of the "same subnet" things, I used a complete different, 10.10.10. ... (have enough free port on other computers). No change.
Now I removed systemtap, xtables-common, libvirt*, qemu*, xrdp, x2go, xfce4. Upgraded to kernel 6.5 - no changes.
There is no wait-message for the bridge and the assigned interface does not become member (can be done manually, after login). Even "/etc/network/interfaces.d/" is not read (was successful with: "/etc/network/if-pre-up.d/lanbr"
(my script with name of the bridge - but the membership problem remains). So the bridge can be created, but get no member ports.
Time to reinstall and hope.
I remember, what was the first fault on this box:
On shutdown, after the first boot (zfs on root), installed the usual way using chroot (like one of the other
boxes from the logs above, were the same things works), I got:
~ "cannot unmount /var/log" .....

Thanks anyway and
best regards,
Manfred

webman · Hardware & System Configuration

Thanks!

Was not the whole truth so, but probably the most important pointer!
Had to remove everything named apparmor so,
the boot was error-free and new install too!

Regards,
Manfred

webman · Hardware & System Configuration

Hello!

After I had some problems with KMV - in this context I saw apparmor errors
about KVM - I thought to remove apparmor temporarely. The docs does not
show me, how to disable (tried: /etc/init.d/apparmor stop), so I uninstalled it.
But the errors (while starting a VM) continue.
So I re-installed apparmor and another pain begins, which my bootlog shows (datetime column removed):

 Starting: AppArmorLoading AppArmor profiles...AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.man at line 53: Could not open 'local/usr.bin.man'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper at line 75: Could not open 'local/usr.lib.libvirt.virt-aa-helper'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.libvirtd at line 144: Could not open 'local/usr.sbin.libvirtd'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/sbin.dhclient at line 74: Could not open 'local/sbin.dhclient'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.ntpd at line 86: Could not open 'local/usr.sbin.ntpd'
 AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.bin.tcpdump at line 68: Could not open 'local/usr.bin.tcpdump'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lsb_release: File exists
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lightdm-guest-session: File exists
 AppArmor parser error for /etc/apparmor.d/sbin.dhclient in profile /etc/apparmor.d/sbin.dhclient at line 74: Could not open 'local/sbin.dhclient'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/nvidia_modprobe: File exists
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/usr.bin.lxc-start: File exists
 AppArmor parser error for /etc/apparmor.d/usr.bin.man in profile /etc/apparmor.d/usr.bin.man at line 53: Could not open 'local/usr.bin.man'
 AppArmor parser error for /etc/apparmor.d/usr.bin.tcpdump in profile /etc/apparmor.d/usr.bin.tcpdump at line 68: Could not open 'local/usr.bin.tcpdump'
 AppArmor parser error for /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper in profile /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper at line 75: Could not open 'local/usr.lib.libvirt.virt-aa-helper'
 AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in profile /etc/apparmor.d/usr.sbin.libvirtd at line 144: Could not open 'local/usr.sbin.libvirtd'
 AppArmor parser error for /etc/apparmor.d/usr.sbin.ntpd in profile /etc/apparmor.d/usr.sbin.ntpd at line 86: Could not open 'local/usr.sbin.ntpd'
 Error: Could not load profile /var/cache/apparmor/201d1af9.0/lxc-containers: File exists
 /sbin/apparmor_parser: Unable to add "/usr/bin/lxc-start".  Profile already exists
 /sbin/apparmor_parser: Unable to add "lsb_release".  Profile already exists
 /sbin/apparmor_parser: Unable to add "kmod".  Profile already exists
 /sbin/apparmor_parser: Unable to add "nvidia_modprobe".  Profile already exists
 /sbin/apparmor_parser: Unable to add "chromium".  Profile already exists
 /sbin/apparmor_parser: Unable to add "/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session".  Profile already exists
 /sbin/apparmor_parser: Unable to add "lxc-container-default".  Profile already exists
 At least one profile failed to load ... failed!
 failed.

I do not know, why this hapens and how to repair it!

Thanks,
Manfred

webman · Hardware & System Configuration

Until debian buster, I have had never a problem to create and or use bridges,
but - so far I remember correctly - this came with bullseye.
Since then, I had to issue (example) "ip link add mybr type bridge" once and the
bridge could be configured in the interfaces file, but only for some bridges, not all ....
Now, on Daedalus,I had this with my bridge for my (k)VMs - to avoid complexity,
I started again using a usual lan-bridge:
ip link add lanbr type bridge
Then I edit 'interfaces'

auto lanbr
iface lanbr inet static
address 10.0.0.1/24
gateway 10.0.0.254

#bridge_stp off
#bridge_waitport 0
#bridge_fd 0

bride_ports eif0

But the bridge does not come up after boot and bootlog tells me:

Cannot find device "lanbr"
Sat Jul  6 23:20:03 2024: ifup: failed to bring up lanbr
Sat Jul  6 23:20:03 2024: invoke-rc.d: could not determine current runlevel

Looks like, someone forgot the 'lanbr' interface.
This is something I never had seen before.
What is a - reproducable - list of steps to setup a bridge?
I try to avoid - for this message - that KVM has the same
problem and does not find (the other bridge).
Something strange!
Please help!

Regards,
Manfred

webman · Installation

Hi!

You need to use Devuan's debootstrap (not Debian's).

LXC is not debootstrap and is intended to install containers for
different OS, like Ubuntu, Arch etc.
Thanks to @fsmithred's:

ln -s ceres daedalus

it works like a charm now (at least setup, not configured and runned it).
So the messages about "NN signatures not checked due to missing keys"
may be a conseqence of the missing reference.

Anyway, regards,
Manfred

webman · Installation

Hi!
For the vm, after upgrading from zfs from 2.1.11 to 2.2.4 I used two ssh session:
One for shutting down, the other running "dmesg -Tw", which shows the catastrophe:

The system is going down for system halt NOW!
[Wed Jun 26 15:29:46 2024] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[Wed Jun 26 15:29:46 2024] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[Wed Jun 26 15:29:46 2024] device-mapper: uevent: version 1.0.3
[Wed Jun 26 15:29:46 2024] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[Wed Jun 26 15:29:46 2024] ------------[ cut here ]------------
[Wed Jun 26 15:29:46 2024] kobject: '(null)' (00000000ae4d8a76): is not initialized, yet kobject_put() is being called.
[Wed Jun 26 15:29:46 2024] WARNING: CPU: 0 PID: 2114 at lib/kobject.c:726 kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:46 2024] Modules linked in: dm_mod nfnetlink_log nfnetlink binfmt_misc sha512_generic cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache netfs snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec drm_ttm_helper snd_hda_core ttm iTCO_wdt intel_pmc_bxt snd_hwdep drm_kms_helper snd_pcm pcspkr snd_timer vmw_vsock_virtio_transport serio_raw iTCO_vendor_support vmw_vsock_virtio_transport_common joydev snd watchdog soundcore evdev virtio_rng drm vsock virtio_balloon virtio_console qemu_fw_cfg button zfs(POE-) spl(OE) ext4 crc16 mbcache jbd2 crc32c_generic sg hid_generic sd_mod t10_pi usbhid crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_common hid ahci libahci virtio_scsi libata ehci_pci uhci_hcd psmouse i2c_i801 ehci_hcd virtio_net net_failover failover scsi_mod i2c_smbus lpc_ich scsi_common usbcore usb_common virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio virtio_ring
[Wed Jun 26 15:29:47 2024] CPU: 0 PID: 2114 Comm: rmmod Tainted: P           OE      6.1.0-21-amd64 #1  Debian 6.1.90-1
[Wed Jun 26 15:29:47 2024] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
[Wed Jun 26 15:29:47 2024] RIP: 0010:kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024] Code: 00 4c 89 ef e8 84 8b 8e ff 48 85 db 74 9a f6 43 3c 01 0f 85 78 ff ff ff 48 8b 33 48 89 da 48 c7 c7 e0 a1 20 b4 e8 83 1b 6e ff <0f> 0b e9 5f ff ff ff c3 cc cc cc cc 4d 89 f1 49 c7 c0 30 59 f5 b3
[Wed Jun 26 15:29:47 2024] RSP: 0018:ffffad0bc077bd08 EFLAGS: 00010286
[Wed Jun 26 15:29:47 2024] RAX: 0000000000000000 RBX: ffff968f0478a6d0 RCX: c0000000ffffefff
[Wed Jun 26 15:29:47 2024] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000001
[Wed Jun 26 15:29:47 2024] RBP: 00000000ffffffff R08: 0000000000000000 R09: ffffad0bc077bb80
[Wed Jun 26 15:29:47 2024] R10: 0000000000000003 R11: ffffffffb48d4448 R12: 0000000000000800
[Wed Jun 26 15:29:47 2024] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[Wed Jun 26 15:29:47 2024] FS:  00007f90abfb2040(0000) GS:ffff968f7dc00000(0000) knlGS:0000000000000000
[Wed Jun 26 15:29:47 2024] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Wed Jun 26 15:29:47 2024] CR2: 00007f90ab867c10 CR3: 00000000047ac000 CR4: 00000000000006f0
[Wed Jun 26 15:29:47 2024] Call Trace:
[Wed Jun 26 15:29:47 2024]  <TASK>
[Wed Jun 26 15:29:47 2024]  ? __warn+0x7d/0xc0
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  ? report_bug+0xe2/0x150
[Wed Jun 26 15:29:47 2024]  ? handle_bug+0x41/0x70
[Wed Jun 26 15:29:47 2024]  ? exc_invalid_op+0x13/0x60
[Wed Jun 26 15:29:47 2024]  ? asm_exc_invalid_op+0x16/0x20
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  zfs_sysfs_fini+0x116/0x190 [zfs]
[Wed Jun 26 15:29:47 2024]  openzfs_fini+0x5/0x7df [zfs]
[Wed Jun 26 15:29:47 2024]  __do_sys_delete_module+0x1d5/0x320
[Wed Jun 26 15:29:47 2024]  do_syscall_64+0x55/0xb0
[Wed Jun 26 15:29:47 2024]  ? __handle_mm_fault+0x660/0xfa0
[Wed Jun 26 15:29:47 2024]  ? handle_mm_fault+0xdb/0x2d0
[Wed Jun 26 15:29:47 2024]  ? do_user_addr_fault+0x1b0/0x580
[Wed Jun 26 15:29:47 2024]  ? exit_to_user_mode_prepare+0x44/0x1f0
[Wed Jun 26 15:29:47 2024]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[Wed Jun 26 15:29:47 2024] RIP: 0033:0x7f90ab928a67
[Wed Jun 26 15:29:47 2024] Code: 73 01 c3 48 8b 0d 99 83 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 69 83 0c 00 f7 d8 64 89 01 48
[Wed Jun 26 15:29:47 2024] RSP: 002b:00007ffe277cc818 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0
[Wed Jun 26 15:29:47 2024] RAX: ffffffffffffffda RBX: 0000561de39f1780 RCX: 00007f90ab928a67
[Wed Jun 26 15:29:47 2024] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 0000561de39f17e8
[Wed Jun 26 15:29:47 2024] RBP: 0000000000000000 R08: 1999999999999999 R09: 0000000000000000
[Wed Jun 26 15:29:47 2024] R10: 00007f90ab99bac0 R11: 0000000000000206 R12: 00007ffe277cca60
[Wed Jun 26 15:29:47 2024] R13: 00007ffe277cce16 R14: 0000561de39f12a0 R15: 00007ffe277cca70
[Wed Jun 26 15:29:47 2024]  </TASK>
[Wed Jun 26 15:29:47 2024] ---[ end trace 0000000000000000 ]---
[Wed Jun 26 15:29:47 2024] ------------[ cut here ]------------

Its followed by a second block with "same" content, probably, one for each CPU (the VM has two).

Regards,
Manfred

webman · Installation

Hi!
Thanks!

This is nearly, what I usually do (have only SSHD and some networking tools - I usually keep this as
a bootable installation on first partition as "repair-inst", with the same version of ZFS which I'll use
to setup zfs on root (onto anohter disk). Using ether netinstall, or, naturallay, for zfs on root the
debootstrap tool, how it is described. One different thing is, that I first install DKMS separately and
the wanted kernel with headers.

And you describe exactly ("image1"), what I am experiencing. What you see

"I didn't look further what error it was (sorry)."

is a dependency problem, which left a part uninitialized, which becomes "repaired" if you repeat the
step - independently, that you' made it a little differently (which is not neccessary, because all this
is in dependencies).

I have the (already) described problem with shutdown. If I add pools, they dont have a problem
and working properly like your's.

But I am not keeping installations, which have improperly behavior on stutdown (or startup).
For my ZFS-VMs (which are KVM/QEMU), I initiate a shutdown from inside and keep the
mouse-pointer (on the host) on the pause button, which I press at the moment, the red errorline appears.
On a new hardware, this is the same - but I cannot stop the display .... and they dont appear in logs,
and for my other cases, it is theit is the root-filesystem on unmount!

My older (and running) installations dont have errors or this behavior.
On my day-work machine (which ist Debian Bullseye, ZFS on root), no errors appear, wether
at startup or shutdown (and even my fileserver, staying on Debian Buster, ZFS on root, is error-free).

The 2.4 version (in backports), which I need due to the block-copy feature, is even crashing
hard at shutdown.

Usually, zfs-setup is easy (except for on root) and causes no errors - I am using it since
2012 (not on root at that time).

Regards,
Manfred

webman · Installation

Hi!
On my VM, I removed backports and ZFS and started from scratch
(was a bit tricky to remove 'grub-pc' from backports).
Installation of ZFS 2.1.11 went smootly, no errors.
But, with the "cannot unmount /var/log" from my hardware in mind,
I looked at shutdown and the I see this:

Stopping ZFS Event Daemon
Unloading modules rmmod: ERROR: Module zcommon is in use by icp
rmmod ERROR: Module znvpais is in use by: zcommon
rmmod: ERROR: Module spl is in use by: icp zstd znvpair zcommon
FAILED!

Packages:

Stopping ZFS Event Daemon
Unloading modules rmmod: ERROR: Module zcommon is in use by icp
rmmod ERROR: Module znvpais is in use by: zcommon
rmmod: ERROR: Module spl is in use by: icp zstd znvpair zcommon
FAILED!

zfsutils-linux:
  Installed: 2.1.11-1
  Candidate: 2.1.11-1
  Version table:
 *** 2.1.11-1 500
        500 http://deb.devuan.org/merged daedalus/contrib amd64 Packages
        100 /var/lib/dpkg/status
zfs-dkms:
  Installed: 2.1.11-1
  Candidate: 2.1.11-1
  Version table:
 *** 2.1.11-1 500
        500 http://deb.devuan.org/merged daedalus/contrib amd64 Packages
        100 /var/lib/dpkg/status

$ uname -a
Linux devu5base 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

There are NO pools, but an extra disk, which contains a pool (which has not und should not be importet)

With this VM, using zfs 2.4, I created two clones (on ZFS volumes for VMs) and they have the same error
like the hardware installation:

Unsharing ZFS filesystems.
Stopping ZFS Event Daemon.
Unmounting ZFS filesystems cannot unmount '/var/pool': pool or dataset is busy
cannot unmount 'var/log': pool or dataset is busy
cannot unmount '/root': pool or dataset is busy

Lost my hope!

Regards,
Manfred

webman · Installation

Hello!
I try to migrate things to Devuan and so, even on Debian (Bullseye), I start new things with Devuan.
So I came to lxc-setup and here starts a problem:

lxc-create devu5-ct1 --bdev zfs --zfsroot=zfspool/lxc -t devuan -- -r daedalus

which fails miserably:

debootstrap is /usr/sbin/debootstrap
Checking cache download in /var/cache/lxc/devuan/rootfs-daedalus-amd64 ... 
gpg: keybox '/etc/apt/trusted.gpg.d/devuan-archive-keyring.gpg' created
gpg: key 94532124541922FB: 6 signatures not checked due to missing keys
gpg: key 94532124541922FB: public key "Devuan Repository (Primary Devuan signing key) <repository@devuan.org>" imported
gpg: key BB23C00C61FC752C: 6 signatures not checked due to missing keys
gpg: key BB23C00C61FC752C: public key "Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org>" imported
gpg: key 010291FF0AECE9B9: 5 signatures not checked due to missing keys
gpg: key 010291FF0AECE9B9: public key "Devuan Repository (Amprolla) <repository@devuan.org>" imported
gpg: key 0022D0AB5275F140: 4 signatures not checked due to missing keys
gpg: key 0022D0AB5275F140: public key "Devuan Release Signing (Daedalus) <repository@devuan.org>" imported
gpg: key B3982868D104092C: 4 signatures not checked due to missing keys
gpg: key B3982868D104092C: public key "Devuan Release Signing (Excalibur) <repository@devuan.org>" imported
gpg: key 55C470D57732684B: 3 signatures not checked due to missing keys
gpg: key 55C470D57732684B: public key "Devuan Release Signing (Freia) <repository@devuan.org>" imported
gpg: Total number processed: 6
gpg:               imported: 6
gpg: no ultimately trusted keys found
Downloading devuan minimal ...
E: No such script: /usr/share/debootstrap/scripts/daedalus
Failed to download the rootfs, aborting.
Failed to download 'devuan base'
failed to install devuan
lxc-create: devu5-ct1: lxccontainer.c: create_run_template: 1616 Failed to create container from template
lxc-create: devu5-ct1: tools/lxc_create.c: main: 319 Failed to create container devu5-ct1

I know (only "in the dust") that one can specify an URL at the end of the command, but
would not know, which that might be! The tipping point is probably this:

E: No such script: /usr/share/debootstrap/scripts/daedalus

Every tips is welcome!
BTW, astoundingly, in the cover of lxc-create, devuan signing keys were properly importet.
(I always export a http-proxy for lxc-setup). This is not the case for a chroot setup (tried
to install devuan in a chroot -- failed, because gpg "does not understand proxy" ....).
Regards,
Manfred

webman · Installation

Hi!
Exactly, what I did (just not listed lile "headers-$(uname -r), but my real kernel version).
Additionally, I required the version form backports (because I need the block-copy feature).
From my first failed setup, I have to add: Use grub-pc from backports too, it may otherwise
fail after pool snapshots!
But it remains problematic and I am unsure, to continue:
- In my real hardware setup, I am getting an error message at each shutdown (postet this here).
- In another kvm/qemu setup, where NO pools are in use, but just ZFS setup, it crashes at each shutdown.
May be, there is an undiscovered problem with non-systemd systems - worked perfectly for me on debian.
Regards,
Manfred

webman · Hardware & System Configuration

Thank you very much!
--br,
Manfred

webman · Hardware & System Configuration

Hello!
Thanks, will try that!
--br,
Manfred

webman · Installation

Hello All!

Thanks, @fsmithred!
I followed this advice, event though it shows another theme!
My problem was not old/new naming convention, but changing interface names between boot - not daily though
and a quick reboot is not an answer. But I looked at this kernel commandline option and it seems not to have any effect!
But I found 70-persistent-net.rules, something, I've not regarded before.
Astroundingly, the mapping, applied in this file, does NOT fit the reality completely, there is an exception for one interface.
Then I changed the rules/names, but the problem persists. Then I enabled udev debug logging and saw, that the interface,
which hasnt followed the rule, was renamed two times: From eth0 to eth2, the from eth2 to eth3.
"Predictbale interface names" .....
Anyway, which kernel commandline applied.
Additionally, I found, that there COULD be "net.naming-scheme=v250", according to this thread:
udevd produce same ID_NET_NAME_SLOT for different NIC, so break rename #28929 :
https://github.com/systemd/systemd/issues/28929
But from this thread, I found a hint: "udevadm test-builtin" and I used it like this:

$ udevadm test-builtin net_id /sys/class/net/gif0 (where gif0 is now my 10GbE-IF)
calling: test-builtin
=== trie on-disk ===
tool version:          3
file size:         9709412 bytes
header size             80 bytes
strings            2419020 bytes
nodes              7290312 bytes
Load module index
ID_NET_NAME_MAC=enx001999c13f23
ID_OUI_FROM_DATABASE=Fujitsu Technology Solutions GmbH
ID_NET_NAME_PATH=enp4s0f0
Unload module index

This <enp4s0f0> (under: ID_NET_NAME_PATH) is probably the original IF-name and could explain, why
the "70-persistent-net.rules" cannot work:
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" - because they trigger (not!) on interface
names, which do not exist?
After I enabled udev debug logging, I have to look deeper at systemstart in the next days.
So wether "net.naming-scheme=v250" nor "net.ifnames=1" made something!
To udev logging: The shown output ("=== trie on-disk ===") appears in LSPCI too:

08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
=== trie on-disk ===
tool version:          3
file size:         9709412 bytes
header size             80 bytes
strings            2419020 bytes
nodes              7290312 bytes

at the end of the list of network cards.

For the moment, I choosed a completely different set of names (eno0 for MoBo-IF, eif<N>
for the ethernet (better: 1Gbe) and gif<N> for the 10GbE interfaces. And these coming - at least
for the moment - up with exactly this names without any problem.

The drama will probably start, if I now start setting the "sriov_numvfs"
variable to get man VFs (asked a question in another part of this forum).

webman · Hardware & System Configuration

Hello All!
Just a very simple script and where and how to install it would help
me getting started!

Thanks,
Manfred

webman · Hardware & System Configuration

Hello!
How can I send sound from scripts or services, running at root?
Know not much about this, but pulseaudio seems to be a problem.
Although I found this:

pulseaudio --start --log-target=syslog --system

BUT, this is systemd, or not?
The man file says:

--system[=BOOL]
              Run as system-wide instance instead of per-user. Please note that this disables
             certain features of ..... (without mentioning them!)

So it is unclear about this!
Just an "aplay <file>" would enough for me!

Probably remove pulse and install pipewire?
Woudl they run without something like the
xdg-desktop(-portal) and can I remove these?

Thanks,
Manfred

webman · Hardware & System Configuration

Hi!
As long as I was on debian (bullseye so far), virtual functions
(VF) from SR-IOV interfaces have had a relation to its physical
part (PF), like here from an Intel X710:

enp66s0f0	PF
enp66s10f80v0   VF
enp66s10f81v1	VF
....

This seems no longer the case, at least for my daedalus setup
and even the "80/81" (in the names above) are really ugly.
If I have 5 physical inferfaces, they are named from eth0 to eth4.
If I issue "echo 8 cat /sys/class/net/<IFACE>/device/sriov_numvfs"
this generates a sequence of new interfaces (VFS), just as numbered
as eth<N> and after my existing ifaces, so starting with eth5 ....
Then I repeat this for the second NIC and the chaos
is complete and they should be applied to QEMU and LCC without
pooling, I must be able to map a VF to a PF (for example, to end up
on a 10GbE port/VF).

I made a script for this (the same, the sets the sriov_numvfs
value). So, if eth5 is my 10GbE port0 (in 0-1), then I create
the names for the new IFs like:
eth5-00 - eth5-07 and the same for the second NIC.

I have not tried it in "rc.local" just now, but this is,
what I di on my debian (rename not done).
But is there a better place, I am not just en par with
sysv-int? And other hint about the interface naming
are reallay welcome!

Thanks,
Manfred

webman · Installation

Hello!
I have no clue, what causes this, but the network interface names are changing often.
So, for this cases, there were no software or hardware changes applied.
I am using daedalus, devuan5, with ZFS on root, using kernel:

6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux

on a ASRock X570M Pro4.
The situation is to see, if one looks into '/sys/class/net', here two examples.

##Previous boot:

##eth0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/net/eth0    <==
##eth1 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.0/net/eth1
##eth2 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.1/net/eth2
##eth3 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:06.0/0000:08:00.0/net/eth3
##eth4 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.1/net/eth4

##Current boot:

eth0 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.0/net/eth0/
eth1 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:04.0/0000:06:00.1/net/eth1/
eth2 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:06.0/0000:08:00.0/net/eth2/
eth3 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0/net/eth3/   <==
eth4 -> ../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.1/net/eth4/

How can this be fixed?
BTW, the 0000:08:00.0 is the mainboard interface, which I use as basic interface for LAN access.
I could list the pci-device order (and have saved it), but there are never changes.
This is not a desktop, and this behavior makes ssh access impossible!

Regards,
Manfred

webman · Installation

Installed qemu-guest-agent, but found it disfunctional, at
least, cut&paste from host to guest does not work.
Then I saw, it has not been started - whyever.

/etc/init.d/qemu-guest-agent start
qemu-ga: transport endpoint not found, not starting ... (warning).

Then I saw a newer version in backports and installed this.

qemu-guest-agent:
  Installed: 1:7.2+dfsg-7+deb12u5
  Candidate: 1:7.2+dfsg-7+deb12u5
  Version table:
     1:8.2.1+ds-1~bpo12+1 100
        100 http://deb.devuan.org/merged daedalus-backports/main amd64 Packages
 *** 1:7.2+dfsg-7+deb12u5 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
        100 /var/lib/dpkg/status

But at the end of this setup, the same error appeard:

Setting up qemu-guest-agent (1:8.2.1+ds-1~bpo12+1) ...
qemu-ga: transport endpoint not found, not starting ... (warning).
Processing triggers for man-db (2.11.2-2) ...

And the service says it:

# /etc/init.d/qemu-guest-agent status
qemu-ga is not running ... failed!

Regards,
Manfred

webman · Installation

Hello!
I just - for testing - setup ZFS in a kvm guest.
If fails miserably, because the package has left off dependencies.
I am listing the problem messages here (and a bad solution further down).

apt install zfsutils-linux -t daedalus-backports

Setting up zfs-dkms (2.2.4-1~bpo12+1) ...
Loading new zfs-2.2.4 DKMS files...
Building for 6.1.0-15-amd64
Module build for kernel 6.1.0-15-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.
....
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
invoke-rc.d: initscript zfs-import, action "start" failed.
dpkg: error processing package zfsutils-linux (--configure):
 installed zfsutils-linux package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-15-amd64
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Next, I installed the headers mentioned above.

apt install linux-headers-6.1.0-15-amd64

went through a while ....

Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.1.0-15-amd64..........................................................................
...............................................................................................................
................................................................
Signing module /var/lib/dkms/zfs/2.2.4/build/module/zfs.ko
Signing module /var/lib/dkms/zfs/2.2.4/build/module/spl.ko

Running the post_build script:
Cleaning build area...

zfs.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.1.0-15-amd64/updates/dkms/

 ....

dkms: autoinstall for kernel: 6.1.0-15-amd64.
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

The same story as for my first installation attempt.
From this, I know, how to continue:

apt install zfsutils-linux -t daedalus-backports

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
zfsutils-linux is already the newest version (2.2.4-1~bpo12+1).
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/spl.ko 
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/zfs.ko 
Mounting ZFS filesystem(s) .
Load ZFS filesystem(s) keys.
Sharing ZFS filesystems .
Setting up zfs-zed (2.2.4-1~bpo12+1) ...
Starting ZFS Event Daemon .

The zfs packages are in an invalid state, which has to be fixed!

Regards,
Manfred

webman · Installation

Hello!
At shutdown, I get the message:

Unmounting ZFS filesystems cannot unmount 'var/log/': pool or dataset is busy ...failed!

What to do about this error and situation?

Thanks,
Manfred

webman · Installation

Created a base chimeara setup on one disk and setup zfs.
Works, can create/destroy pools and filesystems.
Then create a bootstrap setup, following the instruction for debian bookworm(!!!), ignoring
just the systemd part. In a first glance, everything was ok, installed simple software and
rebooted several times - until I snapshotted the rpool and bpool (syspool/bootpool for me).
Found grub bug description and mounted the pools, upgraded to grub from backport.
After bottable again, a lot of error coming up, which may have to do with mount-orde.

Configuring network interfaces...if-up.d/mountnfs[eth3]: waiting for interface eth1 before doing NFS
 mounts ... (warning).

 Starting enhanced syslogd: rsyslogdrsyslogd: $WorkDirectory: /var/spool/rsyslog can not be accessed,
 probably does not exist - directive ignored [v8.2302.0 try https://www.rsyslog.com/e/2181 ]

>dir exist (perms: root/root)

Sharing ZFS filesystems failed to lock /etc/exports.d/zfs.exports.lock: No such file or directory

uups! dont understand!
>Can import/export pools and are mounts are like set in the installtion.

configfs not found in /proc/mount: exiting!

rsyslog does not accept messages from logger (but after restarting it),
same for ulogd2.

I just shortly made a "recommendation" in the ZFS group to provide detailed instructions for
sysv init systems - but his if future ....
Other instructions I found on Galaxy, skip the setup of the filesystems with its individual mount,
which are probably the root of the problem.

Have had a look for the configfs - I dont understand it. Looked at two other devuan installations
(live and standard [in KVM]) and there, it is at least not mounted.

Here are my zfs mounts

$ zfs list -r -o name,canmount,mounted,overlay,mountpoint
NAME                 CANMOUNT  MOUNTED  OVERLAY   USED  MOUNTPOINT
bootpool             off       no       on        112M  /boot
bootpool/BOOT        off       no       on        111M  none
bootpool/BOOT/devu5  on        yes      on        111M  /boot
syspool              off       no       on       6.86G  /
syspool/ROOT         off       no       on       1.35G  none
syspool/ROOT/devu5   noauto    yes      on       1.35G  /
syspool/home         on        yes      on       5.35G  /home
syspool/home/root    on        yes      on       5.35G  /root
syspool/ops          on        yes      on       2.55M  /ops
syspool/ops/tools    on        yes      on       2.32M  /ops/tools
syspool/opt          on        yes      on         96K  /opt
syspool/srv          on        yes      on         96K  /srv
syspool/tmp          on        yes      on        188K  /tmp
syspool/var          off       no       on        149M  /var
syspool/var/cache    on        yes      on        147M  /var/cache
syspool/var/lib      off       no       on         96K  /var/lib
syspool/var/log      on        yes      on        884K  /var/log
syspool/var/mail     on        yes      on         96K  /var/mail
syspool/var/spool    on        yes      on        192K  /var/spool

Any help would be really great!

++Manfred

webman · Installation

But why does it work in Debian itself?
As I wrote: Made comparable installs (all via netsetup).
Regards,
Manfred

webman · Hardware & System Configuration

Hello!

Wondering, why my DNS log (dnsmasq) is that large and took an tcpdump.
Easy to see, that my new devuan daedalus (running in KVM) causes this,
but the root cause is not easy to find.

Now, that I have Systemtap made running, this is a snip.

stap /ops/monits/watchport53.stp 
exim4[15354] sent packet to 192.168.26.254:53
exim4[15354] sent packet to 192.168.26.254:53
exim4[15364] sent packet to 192.168.26.254:53

So, exim4 ist the beast - dnsmasq shows:

04:55:07 dnsmasq[236175]: 3981 192.168.99.58/35315 query[AAAA] devu5test.home.local from 192.168.26.58
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/35315 config devu5test.home.local is NODATA-IPv6
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/36463 query[AAAA] devu5test1kvm from 192.168.26.58
04:55:07 dnsmasq[236175]: 3981 192.168.99.58/36463 config devu5test1kvm is NODATA-IPv6

The hit to this is the fact, that it queries for its own host, which
does not have any ipv6 address (disabled by kernel commandline)
and no ipv6 addresses in hosts.
The other importent problem with this is, that it makes dns-log checks a pain.

Note (later added): I've removed the ipv6 address from exim's config.

How can I stop this dirty packet flood?

Thanks,
Manfred

The officially official Devuan Forum!

#1 Installation » After installing firmware, runlevel is unknown » 2024-07-21 17:36:26

#2 Re: Hardware & System Configuration » Systemtap packaging error - cannot be used » 2024-07-08 14:11:28

#3 Re: Hardware & System Configuration » Looking for the RIGHT way to create a bridge » 2024-07-07 21:17:33

#4 Re: Hardware & System Configuration » How to repair APPARMOR? » 2024-07-07 20:53:21

#5 Hardware & System Configuration » How to repair APPARMOR? » 2024-07-06 21:55:36

#6 Hardware & System Configuration » Looking for the RIGHT way to create a bridge » 2024-07-06 21:46:30

#7 Re: Installation » How to install devuan lxc-container on debian? » 2024-06-26 18:10:53

#8 Re: Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-26 16:49:39

#9 Re: Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-26 13:53:17

#10 Re: Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-26 03:29:30

#11 Installation » How to install devuan lxc-container on debian? » 2024-06-25 14:38:06

#12 Re: Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-25 14:25:24

#13 Re: Hardware & System Configuration » sysv-init: Looking for example/run a script permanently, like service? » 2024-06-19 21:52:00

#14 Re: Hardware & System Configuration » Need acoustic signalling (sound) where only root account is present » 2024-06-15 20:39:37

#15 Re: Installation » daedalus: network interface names changing with (nearly) each boot » 2024-06-15 00:18:36

#16 Hardware & System Configuration » sysv-init: Looking for example/run a script permanently, like service? » 2024-06-13 19:26:01

#17 Hardware & System Configuration » Need acoustic signalling (sound) where only root account is present » 2024-06-13 19:22:26

#18 Hardware & System Configuration » How handle network interface naming for SOME interfaces (VF/SR-IOV) » 2024-06-13 19:03:58

#19 Installation » daedalus: network interface names changing with (nearly) each boot » 2024-06-13 18:44:40

#20 Installation » qemu-guest-agent - dysfunctional package » 2024-06-13 18:15:17

#21 Installation » zfs setup package - missing dependencies leads to failed setup » 2024-06-13 17:57:52

#22 Installation » zfs on root successfully installed - but unmount problem at shutdown » 2024-06-13 17:34:39

#23 Installation » chimaera: Stucking with zfs on root - mount and other errors » 2024-05-06 03:22:48

#24 Re: Installation » packagemanagement and dependencies - xfce4 setup does not install xorg » 2024-01-11 22:41:50

#25 Hardware & System Configuration » exim4 floods dns (and its log) with AAAA queries, though NO ipv6 avail » 2024-01-09 04:02:33

Board footer