Posts by KlausR

Had 3 downs/ups meanwhile, and mac address stays stable. But thanx for the option.

In case, anyone should face same prob:

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

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?

# >>> [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]

Quote from macom

Do you have both clones attached at the same time? That causes issues. Only one of the drives should be connected.

Cloned just docker-ssd. And attached only the clone. (beside swap ssd and other hardware)

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!

Quote from votdev

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.

journalctl --disk-usage

Archived and active journals take up 1.3G in the file system.

journalctl -e works without probs. So really seems to be a prob of failing extractation. But i got no clue how to solve it. Anyone?

Quote from votdev

In the diagnostic section you can get the the old syslog which is extracting the info from the journal.

I tried, but i failed. after upgrading from OMV6... just Error 502/504, no further informations.

Is it possible that extractions fails due to large journal?

Due to these informations

Where is some os logs in Debian 12

It seems that some of the system log files (/var/log/syslog, /var/log/auth.log, /var/log/kern.log, ...) have been removed in the latest version of Debian,…

serverfault.com

debian cancelled syslog and uses journald instead. Is there any way to reach journald in webgui?

Thank you for hints in advance!

Is there a way to get journald instead? In Web-gui?

Maybe it´s better to open a new thread with this topic.

I guess i can close this thread, seems as is syslog has been cancelled by debian-

Where is some os logs in Debian 12

It seems that some of the system log files (/var/log/syslog, /var/log/auth.log, /var/log/kern.log, ...) have been removed in the latest version of Debian,…

serverfault.com

But, is there any way to get journald in webgui?

Quote

# dpkg -l | grep openm

ii libopenmpt0:arm64 0.6.9-1 arm 64 module music library based on OpenMPT -- shared library

ii openmediavault 7.3.0-4 all openmediavault - The open network attached storage solution

ii openmediavault-apttool 7.1.1 all apt tool plugin for OpenMediaVault.

ii openmediavault-backup 7.1.4 all backup plugin for OpenMediaVault.

ii openmediavault-compose 7.2.1 all OpenMediaVault compose plugin

ii openmediavault-cputemp 7.0.2 all cpu temperature plugin for openmediavault

ii openmediavault-fail2ban 7.0.1 all OpenMediaVault Fail2ban plugin

ii openmediavault-flashmemory 7.0.1 all folder2ram plugin for openmediavault

ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive

ii openmediavault-omvextrasorg 7.0 all OMV-Extras.org Package Repositories for OpenMediaVault

ii openmediavault-resetperms 7.1 all Reset Permissions

ii openmediavault-sftp 7.0.3 all sftp server

ii openmediavault-sharerootfs 7.0-1 all openmediavault share root filesystem plugin

ii openmediavault-symlinks 7.0 all OpenMediaVault symlinks plugin

Display More

sudo omv-salt deploy run collectd webgui

Quote from Soma

Did you try all I posted?

Deleted browser's cache, yes

Quote

sudo omv-salt deploy run collectd webgui

The message is too long, must be under 10,000 characters.

too long...

Quote

----------

ID: webgui_document_root_perms_recursive

Function: cmd.run

Name: chown -R 'openmediavault-webgui:openmediavault-webgui' '/var/www/openmediavault'

Result: True

Comment: Command "chown -R 'openmediavault-webgui:openmediavault-webgui' '/var/www/openmediavault'" run

Started: 20:26:26.126171

Duration: 38.305 ms

Changes:

----------

pid:

36413

retcode:

0

stderr:

stdout:

Summary for raspberrypi

-------------

Succeeded: 35 (changed=29)

Failed: 0

-------------

Total states run: 35

Total run time: 81.864 s

Display More

That is the tail....

Quote

# sudo omv-salt deploy run collectd workbench

ERROR: The state 'workbench' does not exist

502 and 504 in switch