That was it.
Everything works after reboot.
My new Lines:
36 restart: unless-stopped
142 # - "~/.docker/config.json:/config.json" # optional, for authentication if you have a Docker Hub account
Thanks to all.
That was it.
Everything works after reboot.
My new Lines:
36 restart: unless-stopped
142 # - "~/.docker/config.json:/config.json" # optional, for authentication if you have a Docker Hub account
Thanks to all.
Here's the Yml code
version: '3.5'
# Example Docker Compose config file for PhotoPrism (Linux / AMD64)
#
# Note:
# - Running PhotoPrism on a server with less than 4 GB of swap space or setting a memory/swap limit can cause unexpected
# restarts ("crashes"), for example, when the indexer temporarily needs more memory to process large files.
# - If you install PhotoPrism on a public server outside your home network, please always run it behind a secure
# HTTPS reverse proxy such as Traefik or Caddy. Your files and passwords will otherwise be transmitted
# in clear text and can be intercepted by anyone, including your provider, hackers, and governments:
# https://docs.photoprism.app/getting-started/proxies/traefik/
#
# Setup Guides:
# - https://docs.photoprism.app/getting-started/docker-compose/
# - https://docs.photoprism.app/getting-started/raspberry-pi/
# - https://www.photoprism.app/kb/activation
#
# Troubleshooting Checklists:
# - https://docs.photoprism.app/getting-started/troubleshooting/
# - https://docs.photoprism.app/getting-started/troubleshooting/docker/
# - https://docs.photoprism.app/getting-started/troubleshooting/mariadb/
#
# CLI Commands:
# - https://docs.photoprism.app/getting-started/docker-compose/#command-line-interface
#
# All commands may have to be prefixed with "sudo" when not running as root.
# This will point the home directory shortcut ~ to /root in volume mounts.
services:
photoprism:
## Use photoprism/photoprism:preview for testing preview builds:
image: photoprism/photoprism:latest
## Don't enable automatic restarts until PhotoPrism has been properly configured and tested!
## If the service gets stuck in a restart loop, this points to a memory, filesystem, network, or database issue:
## https://docs.photoprism.app/getting-started/troubleshooting/#fatal-server-errors
# restart: unless-stopped
stop_grace_period: 10s
depends_on:
- mariadb
security_opt:
- seccomp:unconfined
- apparmor:unconfined
ports:
- "2342:2342" # HTTP port (host:container)
environment:
PHOTOPRISM_ADMIN_USER: "admin" # admin login username
PHOTOPRISM_ADMIN_PASSWORD: "***********" # initial admin password (8-72 characters)
PHOTOPRISM_AUTH_MODE: "password" # authentication mode (public, password)
PHOTOPRISM_SITE_URL: "http://192.168.2.9:2342/" # server URL in the format "http(s)://domain.name(:port)/(path)"
PHOTOPRISM_ORIGINALS_LIMIT: 5000 # file size limit for originals in MB (increase for high-res video)
PHOTOPRISM_HTTP_COMPRESSION: "gzip" # improves transfer speed and bandwidth utilization (none or gzip)
PHOTOPRISM_LOG_LEVEL: "info" # log level: trace, debug, info, warning, error, fatal, or panic
PHOTOPRISM_READONLY: "false" # do not modify originals directory (reduced functionality)
PHOTOPRISM_EXPERIMENTAL: "false" # enables experimental features
PHOTOPRISM_DISABLE_CHOWN: "false" # disables updating storage permissions via chmod and chown on startup
PHOTOPRISM_DISABLE_WEBDAV: "false" # disables built-in WebDAV server
PHOTOPRISM_DISABLE_SETTINGS: "false" # disables settings UI and API
PHOTOPRISM_DISABLE_TENSORFLOW: "false" # disables all features depending on TensorFlow
PHOTOPRISM_DISABLE_FACES: "false" # disables face detection and recognition (requires TensorFlow)
PHOTOPRISM_DISABLE_CLASSIFICATION: "false" # disables image classification (requires TensorFlow)
PHOTOPRISM_DISABLE_VECTORS: "false" # disables vector graphics support
PHOTOPRISM_DISABLE_RAW: "false" # disables indexing and conversion of RAW images
PHOTOPRISM_RAW_PRESETS: "false" # enables applying user presets when converting RAW images (reduces performance)
PHOTOPRISM_JPEG_QUALITY: 85 # a higher value increases the quality and file size of JPEG images and thumbnails (25-100)
PHOTOPRISM_DETECT_NSFW: "false" # automatically flags photos as private that MAY be offensive (requires TensorFlow)
PHOTOPRISM_UPLOAD_NSFW: "true" # allows uploads that MAY be offensive (no effect without TensorFlow)
# PHOTOPRISM_DATABASE_DRIVER: "sqlite" # SQLite is an embedded database that doesn't require a server
PHOTOPRISM_DATABASE_DRIVER: "mysql" # use MariaDB 10.5+ or MySQL 8+ instead of SQLite for improved performance
PHOTOPRISM_DATABASE_SERVER: "mariadb:3306" # MariaDB or MySQL database server (hostname:port)
PHOTOPRISM_DATABASE_NAME: "photoprism" # MariaDB or MySQL database schema name
PHOTOPRISM_DATABASE_USER: "photoprism" # MariaDB or MySQL database user name
PHOTOPRISM_DATABASE_PASSWORD: "insecure" # MariaDB or MySQL database user password
PHOTOPRISM_SITE_CAPTION: "AI-Powered Photos App"
PHOTOPRISM_SITE_DESCRIPTION: "" # meta site description
PHOTOPRISM_SITE_AUTHOR: "" # meta site author
## Run/install on first startup (options: update https gpu tensorflow davfs clitools clean):
# PHOTOPRISM_INIT: "https gpu tensorflow"
## Hardware Video Transcoding:
# PHOTOPRISM_FFMPEG_ENCODER: "software" # FFmpeg encoder ("software", "intel", "nvidia", "apple", "raspberry")
# PHOTOPRISM_FFMPEG_BITRATE: "32" # FFmpeg encoding bitrate limit in Mbit/s (default: 50)
## Run as a non-root user after initialization (supported: 0, 33, 50-99, 500-600, and 900-1200):
# PHOTOPRISM_UID: 1000
# PHOTOPRISM_GID: 1000
# PHOTOPRISM_UMASK: 0000
## Start as non-root user before initialization (supported: 0, 33, 50-99, 500-600, and 900-1200):
# user: "1000:1000"
## Share hardware devices with FFmpeg and TensorFlow (optional):
# devices:
# - "/dev/dri:/dev/dri" # Intel QSV
# - "/dev/nvidia0:/dev/nvidia0" # Nvidia CUDA
# - "/dev/nvidiactl:/dev/nvidiactl"
# - "/dev/nvidia-modeset:/dev/nvidia-modeset"
# - "/dev/nvidia-nvswitchctl:/dev/nvidia-nvswitchctl"
# - "/dev/nvidia-uvm:/dev/nvidia-uvm"
# - "/dev/nvidia-uvm-tools:/dev/nvidia-uvm-tools"
# - "/dev/video11:/dev/video11" # Video4Linux Video Encode Device (h264_v4l2m2m)
working_dir: "/photoprism" # do not change or remove
## Storage Folders: "~" is a shortcut for your home directory, "." for the current directory
volumes:
# "/host/folder:/photoprism/folder" # Example
- "/srv/dev-disk-by-uuid-83c77233-238b-4248-94c0-e74a79782ebc/Daten2/Bilder:/photoprism/folder"
- "/srv/dev-disk-by-uuid-83c77233-238b-4248-94c0-e74a79782ebc/Daten2/Bilder:/photoprism/originals" # Original media files (DO NOT REMOVE)
# - "/example/family:/photoprism/originals/family" # *Additional* media folders can be mounted like this
# - "~/Import:/photoprism/import" # *Optional* base folder from which files can be imported to originals
- /srv/dev-disk-by-uuid-d0d0dd9f-1eae-4a4a-90b0-2a6dda9e491e/appdata/photoprism:/photoprism/storage # *Writable* storage folder for cache, database, and sidecar files (DO NOT REMOVE)
## Database Server (recommended)
## see https://docs.photoprism.app/getting-started/faq/#should-i-use-sqlite-mariadb-or-mysql
mariadb:
image: mariadb:10.11
## If MariaDB gets stuck in a restart loop, this points to a memory or filesystem issue:
## https://docs.photoprism.app/getting-started/troubleshooting/#fatal-server-errors
restart: unless-stopped
stop_grace_period: 5s
security_opt: # see https://github.com/MariaDB/mariadb-docker/issues/434#issuecomment-1136151239
- seccomp:unconfined
- apparmor:unconfined
command: mariadbd --innodb-buffer-pool-size=512M --transaction-isolation=READ-COMMITTED --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci --max-connections=512 --innodb-rollback-on-timeout=OFF --innodb-lock-wait-timeout=120
## Never store database files on an unreliable device such as a USB flash drive, an SD card, or a shared network folder:
volumes:
- "./database:/var/lib/mysql" # DO NOT REMOVE
environment:
MARIADB_AUTO_UPGRADE: "1"
MARIADB_INITDB_SKIP_TZINFO: "1"
MARIADB_DATABASE: "photoprism"
MARIADB_USER: "photoprism"
MARIADB_PASSWORD: "insecure"
MARIADB_ROOT_PASSWORD: "insecure"
## Watchtower upgrades services automatically (optional)
## see https://docs.photoprism.app/getting-started/updates/#watchtower
## activate via "COMPOSE_PROFILES=update docker compose up -d"
watchtower:
restart: unless-stopped
image: containrrr/watchtower
profiles: ["update"]
environment:
WATCHTOWER_CLEANUP: "true"
WATCHTOWER_POLL_INTERVAL: 7200 # checks for updates every two hours
volumes:
- "/var/run/docker.sock:/var/run/docker.sock"
- "~/.docker/config.json:/config.json" # optional, for authentication if you have a Docker Hub account
Alles anzeigen
Hello,
photoprism runs very well, but after a reboot of OMV the container stops. (see the screenshot).
Every time I have to press the "up" button again to make it work again.
Here is the message when the container restarts.
docker-compose up -d ...
time="2023-07-07T16:22:33+02:00" level=warning msg="cannot expand '~', because the environment lacks HOME"
Container photoprism-mariadb-1 Running
Container photoprism-photoprism-1 Created
Container photoprism-photoprism-1 Starting
Container photoprism-photoprism-1 Started
END OF LINE
Does somebody has any idea?
The compose shared folder is for the compose files. The container shared folder is for the container data/volumes. You need both.
I probably misunderstand something. I also reinstalled OMV and used this guide for docker. Point 3 says nothing about a "container" folder, which I didn't create.
Nevertheless it works.
Sorry, I found it: In Reset Permission set shared folder to "none", save and reset.
Done.
Jellyfine is now the first container to run.
The next thing to do is set up calibre- web, I hope that goes faster.
Many thanks for the help
Hello, it's me again.
Now I have arrived the point 2 of the Docker instructions.
Under Create symlink /DATA
it says: "In the Destination field write /DATA
(you can use your actual folder name instead of DATA)."
But I get an error message when I use my existing folder.
I guess thunar is another one of your containers.
no, I started my Linux partition, also because I could only access the restored data from Linux.
Now I'm back to windows,
Changing the access rights has no effect, I'm closing for today - I'm a bit frustrated after 7 hours of OMV.
Thanks for the help.
If you have not yet configured anything within Jellyfin, what I would do is reset the permissions of the data folders
Thanks, I'll try, but difficult for someone with little Linux knowledge.
It's something with chmod , I'm learning.
This is a security issue. If the user running the container belongs to the root group, it is as if the container was run by root. The same goes for the adm group. Why did you do that?
You're right, no idea why, I changed it.
uid=1000(myname) gid=100(users) Gruppen=100(users),113(ssh)
Here is the permission from the compose/jellyfin folder.
It is on the same drive where the container is located next to OMV.
root@openmediavault:~# ls -la /srv/dev-disk-by-uuid-ed942d40-5ba0-4008-b1fb-d0ca1b71638d/compose/jellyfin
insgesamt 48
drwxr-xr-x 6 myname users 4096 6. Jun 13:40 .
drwxr-xr-x 3 root root 4096 6. Jun 13:26 ..
drwxr-xr-x 2 myname users 4096 6. Jun 13:26 cache
drwxr-xr-x 7 myname users 4096 6. Jun 13:26 data
drwxr-xr-x 4 myname users 4096 6. Jun 13:26 dlna
-rw-r--r-- 1 myname users 2057 6. Jun 14:26 encoding.xml
drwxr-xr-x 2 myname users 4096 6. Jun 13:26 log
-rw-r--r-- 1 myname users 1362 6. Jun 13:26 logging.default.json
-rw-r--r-- 1 myname users 2181 6. Jun 13:40 migrations.xml
-rw-r--r-- 1 myname users 998 6. Jun 13:40 network.xml
-rw-r--r-- 1 myname users 5656 6. Jun 13:26 system.xml
Alles anzeigen
Thanks for the help but I can't find the mistake, I changed the GID and also moved the config file to the SSD, see new yaml file below.
root@openmediavault:~# ls -la /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media
insgesamt 16
drwxr-xr-x 4 myname users 4096 6. Jun 11:35 .
drwxr-xr-x 9 myname users 4096 6. Jun 14:05 ..
drwxr-xr-x 2 myname users 4096 6. Jun 11:35 Filme
drwxr-xr-x 2 myname users 4096 6. Jun 11:35 Serien
root@openmediavault:~# id myname
uid=1000(myname) gid=100(users) Gruppen=100(users),0(root),4(adm),113(ssh)
New yaml:
---
# https://hub.docker.com/r/linuxserver/jellyfin
version: "2.1"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000
- PGID=100
- TZ=Europe/Berlin
- JELLYFIN_PublishedServerUrl=192.168.2.9 #optional
volumes:
- /srv/dev-disk-by-uuid-ed942d40-5ba0-4008-b1fb-d0ca1b71638d/compose/jellyfin:/config
- /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien:/data/tvshows
- /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme:/data/movies
ports:
- 8096:8096
- 8920:8920 #optional
- 7359:7359/udp #optional
- 1900:1900/udp #optional
restart: unless-stopped
Hello,
I have reinstalled OMV and am working with Docker-Compose for the first time.
Sorry for the question, I can't find the right guide on the web.
Jellyfine is running, but I suspect an error in the yaml file because I can't find any media in Jellyfine's web gui.
Can someone help me please
This is my yaml file:
---
# https://hub.docker.com/r/linuxserver/jellyfin
version: "2.1"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Berlin
- JELLYFIN_PublishedServerUrl=192.168.2.9 #optional
volumes:
- /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/appdata/jellyfin:/config
- /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien:/data/tvshows
- /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme:/data/movies
ports:
- 8096:8096
- 8920:8920 #optional
- 7359:7359/udp #optional
- 1900:1900/udp #optional
restart: unless-stopped
and this the report, if check in Compose
Check compose file for errors ...
name: jellyfin
services:
jellyfin:
container_name: jellyfin
environment:
JELLYFIN_PublishedServerUrl: 192.168.2.9
PGID: "1000"
PUID: "1000"
TZ: Europe/Berlin
image: lscr.io/linuxserver/jellyfin:latest
networks:
default: null
ports:
- mode: ingress
target: 8096
published: "8096"
protocol: tcp
- mode: ingress
target: 8920
published: "8920"
protocol: tcp
- mode: ingress
target: 7359
published: "7359"
protocol: udp
- mode: ingress
target: 1900
published: "1900"
protocol: udp
restart: unless-stopped
volumes:
- type: bind
source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/appdata/jellyfin
target: /config
bind:
create_host_path: true
- type: bind
source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien
target: /data/tvshows
bind:
create_host_path: true
- type: bind
source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme
target: /data/movies
bind:
create_host_path: true
networks:
default:
name: jellyfin_default
END OF LINE
Same problem again this morning. The DNS field was empty, only when I entered a DNS server did it work again.
Is this field blank by default?
From the install guide: "While not visible in the screen capture above, it is recommended that users consider using a public DNS server address."
Unbelievable, the 3rd try today and now everything works. I reloaded the ISO and used a different USB stick.
Thanks very much
And the output of this?
cat /etc/apt/sources.list
Please see my spoiler in the previous post, it was so much text
Are you sure you had a connection during the installation process the second time?
Two other computers in the house were online, my son was playing - he would have reported.
It was an install from a USB stick. The ISO was downloaded from the OMV website.
It was the second attempt as I didn't get a connection the first time during the installation either.
The hardware is an Asrock J3455 with Celeron and 8GB RAM, see screenshot.
Linux OMV 5.16.0-0.bpo.4-amd64 #1 SMP PREEMPT Debian 5.16.12-1~bpo11+1 (2022-03- 08) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jun 4 17:18:03 2023 from 192.168.2.108
root@OMV:~# ^[[200~root@OMV:~# # deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Off icial Snapshot amd64 LIVE/INSTALL Binary 20220426-20:09]/ b ullseye cont rib main non-free
# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/man…ce/ch02.en.html#_updates_ and_backports
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
# deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTA LL Binary 20220426-20:09]/ bullseye cont # see the sources.list(5) manua l.nfigure apt package sources,s.trib non-freetes_and_backports20426-20:09]/ bull seye cont
-bash: deb: Kommando nicht gefunden.
-bash: deb-src: Kommando nicht gefunden.
-bash: deb: Kommando nicht gefunden.
-bash: $'\E[200~root@OMV:~#': Kommando nicht gefunden.
-bash: deb-src: Kommando nicht gefunden.
-bash: root@OMV:~#: Kommando nicht gefunden.
-bash: deb: Kommando nicht gefunden.
-bash: deb-src: Kommando nicht gefunden.
-bash: deb: Kommando nicht gefunden.
-bash: deb-src: Kommando nicht gefunden.
root@OMV:~#
root@OMV:~# # deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd6 4 LIVE/INSTALL Binary 20220426-20:09]/ bullseye cont
# see the sources.l ist(5) manual.nfigure apt package sources,s.trib non-freetes_and_backports20426- 20:09]/ bullseye cont
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: root@OMV:~#: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: root@OMV:~#: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# -bash: deb-src: Kommando nicht gefunden.
-bash: -bash:: Kommando nicht gefunden.
root@OMV:~# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTA LL Binary 20220426-20:09]/ bullseye contrib main non-free
# deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTA LL Binary 20220426-20:09]/ bullseye contrib main non-free
deb http://deb.debian.org/debian/ bullseye main
deb-src http://deb.debian.org/debian/ bullseye main
# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/man…ce/ch02.en.html#_updates_ and_backports
deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
root@OMV:~# sudo apt-get dist-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libmemcachedutil2 proftpd-basic proftpd-core proftpd-mod-crypto proftpd-mod-vroot proftpd-mod-wrap
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden NEUEN Pakete werden installiert:
libnss-resolve libnss-systemd python3-jmespath
Die folgenden Pakete werden aktualisiert (Upgrade):
openmediavault salt-common salt-minion
3 aktualisiert, 3 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 10,0 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 9.704 kB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] j
Fehl:1 http://deb.debian.org/debian bullseye/main amd64 libnss-systemd amd64 247.3-7+deb11u2
»deb.debian.org« konnte nicht aufgelöst werden.
Fehl:2 http://packages.openmediavault.org/public shaitan/main amd64 salt-minion all 3005.1+ds-1
»packages.openmediavault.org« konnte nicht aufgelöst werden.
Fehl:3 http://packages.openmediavault.org/public shaitan/main amd64 salt-common all 3005.1+ds-1
»packages.openmediavault.org« konnte nicht aufgelöst werden.
Fehl:4 http://deb.debian.org/debian bullseye/main amd64 libnss-resolve amd64 247.3-7+deb11u2
»deb.debian.org« konnte nicht aufgelöst werden.
Fehl:5 http://packages.openmediavault.org/public shaitan/main amd64 openmediavault all 6.4.2-1
»packages.openmediavault.org« konnte nicht aufgelöst werden.
Fehl:6 http://deb.debian.org/debian bullseye/main amd64 python3-jmespath all 0.10.0-1
»deb.debian.org« konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://deb.debian.org/debian/p…7.3-7%2bdeb11u2_amd64.deb »deb.debian.or g« konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://deb.debian.org/debian/p…7.3-7%2bdeb11u2_amd64.deb »deb.debian.or g« konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://deb.debian.org/debian/p…jmespath_0.10.0-1_all.deb »deb.debian.org « konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://packages.openmediavault…ion_3005.1%2bds-1_all.deb »packages.ope nmediavault.org« konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://packages.openmediavault…mon_3005.1%2bds-1_all.deb »packages.ope nmediavault.org« konnte nicht aufgelöst werden.
E: Fehlschlag beim Holen von http://packages.openmediavault…ediavault_6.4.2-1_all.deb »packa ges.openmediavault.org« konnte nicht aufgelöst werden.
E: Einige Archive konnten nicht heruntergeladen werden; vielleicht »apt-get update« ausführen oder mit »--fix-missing« probieren?
I just realized that I can't install an extension at all.
Here is the output from systemctl:
root@OMV:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Sun 2023-06-04 16:53:41 CEST; 24min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wi…/systemd/writing-network->
https://www.freedesktop.org/wi…/systemd/writing-resolver>
Main PID: 492 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9059)
Memory: 8.8M
CPU: 166ms
CGroup: /system.slice/systemd-resolved.service
└─492 /lib/systemd/systemd-resolved
Jun 04 16:53:41 OMV systemd[1]: Starting Network Name Resolution...
Jun 04 16:53:41 OMV systemd-resolved[492]: Positive Trust Anchors:
Jun 04 16:53:41 OMV systemd-resolved[492]: . IN DS 20326 8 2 e06d44b80b8f1d39a9>
Jun 04 16:53:41 OMV systemd-resolved[492]: Negative trust anchors: 10.in-addr.a>
Jun 04 16:53:41 OMV systemd-resolved[492]: Using system hostname 'OMV'.
Jun 04 16:53:41 OMV systemd[1]: Started Network Name Resolution.
lines 1-21/21 (END)...skipping...
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>
Active: active (running) since Sun 2023-06-04 16:53:41 CEST; 24min ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wi…/systemd/writing-network->
https://www.freedesktop.org/wi…/systemd/writing-resolver>
Main PID: 492 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9059)
Memory: 8.8M
CPU: 166ms
CGroup: /system.slice/systemd-resolved.service
└─492 /lib/systemd/systemd-resolved
Jun 04 16:53:41 OMV systemd[1]: Starting Network Name Resolution...
Jun 04 16:53:41 OMV systemd-resolved[492]: Positive Trust Anchors:
Jun 04 16:53:41 OMV systemd-resolved[492]: . IN DS 20326 8 2 e06d44b80b8f1d39a9>
Jun 04 16:53:41 OMV systemd-resolved[492]: Negative trust anchors: 10.in-addr.a>
Jun 04 16:53:41 OMV systemd-resolved[492]: Using system hostname 'OMV'.
Jun 04 16:53:41 OMV systemd[1]: Started Network Name Resolution.
This is the output
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=16.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=15.9 ms