Posts by KlausR

    und das journal im txt Anhang


    Kann es sein, dass ein bluetooth adapter aktiviert sein muss?

    Ich meinte die Annoucements andere geräte im Netz. Gefunden werden der Router, der Repeater und ein esphome ble Gerät. Von dem omv Rechner aber eben keines davon...

    Hallo,

    ich habe zu meinem Problem zwar den thread mDNS resolution stopped working within last month gefunden, meine Kenntnisse reichen aber nicht, um mir zu einer Lösung zu verhelfen. Vielleicht hat jemand einen Rat?


    Kurze Beschreibung:

    # avahi-browse -a findet nichts, ein ping auf 224.0.0.251 hat 100% loss.

    # Die Konfiguration des Routers (inkl Nutzung von pihole und unbound) kann ich vermutlich ausschliessen, ein anderer Linux-Rechner zeigt dieses Problem nicht, avahi-browse -a wird fündig.

    # nano /etc/avahi/avahi-daemon/.conf zeigt mir, diese Datei ist komplett leer? Ist das möglicherweise die Ursache?

    # Den Rat von votdev aus o.g. thread habe ich schon befolgt,

    Code
    omv-salt deploy run avahi

    keine Veränderung damit.

    # Die ports in der Firewall 6052-6053 TCP für esphome und 5353 UDP für mDNS sind natürlich freigegeben.


    Besten Dank vorab!

    This is the original up to now

    Code
    deb http://deb.debian.org/debian bookworm main contrib non-free
    deb http://deb.debian.org/debian bookworm-updates main contrib non-free
    # Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
    # deb-src http://deb.debian.org/debian bookworm main contrib non-free
    # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free

    As i wrote, i added a 3rd line, so i got

    Code
    deb http://deb.debian.org/debian bookworm main contrib non-free
    deb http://deb.debian.org/debian bookworm-updates main contrib non-free
    deb https://deb.debian.org/debian bookworm main non-free-firmware
    # Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
    # deb-src http://deb.debian.org/debian bookworm main contrib non-free
    # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free

    resulting in multiple times configuration notice


    If i got you right, it has to look..

    Code
    deb https://deb.debian.org/debian bookworm main non-free-firmware
    deb http://deb.debian.org/debian bookworm-updates main contrib non-free
    # Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
    # deb-src http://deb.debian.org/debian bookworm main contrib non-free
    # deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free

    Right?

    i almost had try. I added

    Code
    deb https://deb.debian.org/debian bookworm main non-free-firmware

    but apt update then gives me

    Code
    W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc               /apt/sources.list:3
    W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc               /apt/sources.list:3
    W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/a               pt/sources.list:3
    W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /e               tc/apt/sources.list:3
    W: Target Packages (main/binary-arm64/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc               /apt/sources.list:3
    W: Target Packages (main/binary-armhf/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc               /apt/sources.list:3
    W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:1 and /etc/a               pt/sources.list:3
    W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list:1 and /e               tc/apt/sources.list:3

    Do i have to edit sources.list:3 also? But can`t find it at all

    Hi everybody,

    apt update gives following notice:

    Quote

    1 package can be upgraded. Run 'apt list --upgradable' to see it.

    N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'

    N: More information about this can be found online in the Release notes at: https://www.debian.org/release…ation.html#non-free-split

    i read the Release notes mentioned. Do i get this right, i have to edit /etc/apt/sources.list to correct this issue?


    Thank you in advance!

    In case, anyone should face same prob:


    Solution: You can set fixed mac adress instead of random by editing compose file like this:



    Code
    services:
      pihole:
        mac_address: xx:xx:xx:xx:xx:xx  # choose yourself
        container_name: pihole
        image: pihole/pihole:latest
        ..
        ..

    Hello, as i noticed every new start of each or both containers creates new mac addresses. Router´s list of accepted devices (AVM FB 7490) is running full.

    Is that a "normal" behaviour or may i change to fixed mac addresses?


    Both containers are using same macvlan network with /30, so just 2 IPs usable.


    Thanx in advance!

    I noticed an entry in fstab concerning docker-ssd. Both existent partitions are there. Can one or another parameter cause my issue?


    Code
    # >>> [openmediavault]
    /dev/disk/by-uuid/766cfdbc-cd12-4123-b685-eb33f4de60f3        /srv/dev-disk-by-uuid-766cfdbc-cd12-4123-b685-eb33f4de60f3    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
    /dev/disk/by-uuid/140F-2EC9        /srv/dev-disk-by-uuid-140F-2EC9    vfat    defaults,nofail    0 2
    # <<< [openmediavault]

    Hello and Good Morning,


    i made a dd-copy of my docker-ssd for security reasons. It`s now attached, mounted, file systems are ok, shared folders for docker are in use (see storage). But there are some strange behaviours.


    1. 3 containers started with omv on their own


    2. These containers are not stoppable under compose, they aren´t listed there under files (as some else). Had a try with portainer, everything ok there, could stop and start


    3. Dashboard shows them 3 running, and they are in deed (tested, of course). But even compose-services are blank


    compose configuration:

    compose files in /dev/sdb2, /compose

    data: none

    compose backups in /dev/sdb2, /compose.backup

    docker location: /srv/dev-disk-by-uuid-766cfdbc-cd12-4123-b685-eb33f4de60f3/docker


    What i tried:

    # checked for updates

    # checked /compose: all directories existent, rights are the same for each directory(root/root 0775) and file (root/root 0664)

    # checked: /var/lib/docker is empty

    # checked: /etc/docker has daemon.json

    # Reinstalled docker


    Has anyone an idea for this issue? Thank you in advance!

    I have never owned a Raspi, but i think to remember that the forum has several posts that such hardware has no RTC so the Debian time infra/packages can not store the correct time at shutdown and restore it on bootup.


    I've checked the bootup process and collectd is started after rrdcached which is started after chrony has synced the time via NTP. So i have no idea why there should be a problem.

    ah, ok, thank you. So i might buy a rtc module for rpi to solve it. In the meantime, can i stop rrdgraph? If i am right it´s purpose is to show a graph for cpu under diagnostics.

    I´m facing probs with rrdtool too, after upgrade from 6 to 7. Very high cpu usage every 15min. I had my router as ntp server before, changed to "2.europe.pool.ntp.org" now, finally omv-firstaid again, but it doesn´t solve it. In my case there is no battery to check, it is a Rpi with. OS/OMV on SSD. Is there another item to be checked to solve this prob?

    It seems to be rather a stroke of luck to get an answer from the experts. Thank you for your help.


    Perhaps it will be of interest to anyone else who has the same problem. I jumped in at the deep end and deleted most of the files in /var/log/journal/(dir with 32characters).


    It was probably really the size. Syslog and messages under Diagnostics are working again.