[Cloudflare DNS Proxy, Swag und Bitwarden - teilerfolg]

Was du auch noch probieren könntest (Port ergänzen): 

 

proxy_pass http://bitwarden:PORT;

ODER 

proxy_pass http://IP:PORT;

[[SOLVED] Wie funktioniert SnapRAID?]

7 hours ago, mgutt said:

Trotzdem muss man bei BTRFS nach einem Stromausfall oder harter Abschaltung des Servers immer einen Scrub ausführen. Macht man das nicht, kann es sein, dass Daten später nicht mehr zu reparieren sind. Leider macht Unraid das nicht automatisch. Der Nutzer muss selbst daran denken.

 

Wie würde man so etwas machen?

[Transcoding]

4 hours ago, guybrush2012 said:

Ich bin mit Jellyfin sehr zufriden. Es geht nicht um die Lizenzkosten sondern um die Privacy.

 

Schließe mich hier an. 

Ebenfalls sehr zufrieden. 

[rclone: OneDrive Konfiguration bringt einen http 401 Fehler]

37 minutes ago, mgutt said:

Da Google Drive das Änderungsdatum übernehmen sollte, dürfte sich "--min-age" auf das Erstelldatum beziehen oder?

Soweit ich weiß ist es das Erstellungsdatum.

[rclone: OneDrive Konfiguration bringt einen http 401 Fehler]

Falls jemand Interesse hat. 
Ich führe meine Backups über folgendes Script täglich um 03:00 Uhr automatisiert aus. 
 

Quote

#!/bin/bash

 

####### MAIN SETTINGS #######
JobName="GDrive daily upload" # choose a job name
RcloneCommand="sync" # choose your rclone command e.g. move, copy, sync
RcloneRemoteName="googledrive_encrypted" # choose your remote name
Notification=1 # Enables a notification to the Unraid WebGui
BackupRetention="30d" # How long to keep deleted sync files suffix ms|s|m|h|d|w|M|y
source_paths=(
    "backup"
    "Medien"
    "Musik"
    "Nextcloud"
)

####### Bandwidth limits #######
# specify the desired bandwidth in kBytes/s, or use a suffix b|k|M|G. Or 'off' or '0' for unlimited.  The script uses --drive-stop-on-upload-limit which stops the script if the 750GB/day limit is achieved, so you no longer have to slow 'trickle' your files all day if you don't want to e.g. could just do an unlimited job overnight.
BWLimit1Time="15:30"
BWLimit1="2048k"
BWLimit2Time="22:00"
BWLimit2="off"

 

####### Jobs per Share #######
for source_path in "${source_paths[@]}"; do
    #######  Job Settings ##########
    LocalFilesShare="/mnt/user/$source_path" # choose local location for opload files
    RcloneMountShare="Shares/$source_path/Current" # choose remote location for upload files
    BackupRemoteLocation="Shares/$source_path/Archive" # choose remote location for backup files
    
    #######  Create backup path if it doesn't already exist  ##########
    rclone mkdir $RcloneRemoteName:$BackupRemoteLocation

 

    #######  Upload files  ##########
    echo "$(date "+%d.%m.%Y %T") INFO: *** Start upload files from $LocalFilesShare to $RcloneRemoteName:$RcloneMountShare."
    rclone -v $RcloneCommand $LocalFilesShare $RcloneRemoteName:$RcloneMountShare \
    --backup-dir $RcloneRemoteName:$BackupRemoteLocation \
    --bwlimit "${BWLimit1Time},${BWLimit1} ${BWLimit2Time},${BWLimit2}" \
    --drive-stop-on-upload-limit \
    --fast-list \
    --transfers 4 \
    --checkers 8 \
    --drive-chunk-size 128M \
    --min-age 15m \
    --exclude /Filme/** \
    --exclude /Serien/**

 

    #######  Delete old synced files from archive  ##########
    echo "$(date "+%d.%m.%Y %T") INFO: *** Removing files older than ${BackupRetention} from ${BackupRemoteLocation} for ${RcloneRemoteName}."
    rclone -v delete $RcloneRemoteName:$BackupRemoteLocation --min-age $BackupRetention
    rclone -v rmdirs $RcloneRemoteName:$BackupRemoteLocation --leave-root
   
    #######  Add a notification to the Unraid WebGui  ##########
    if [ "$Notification" = "1" ]; then
        /usr/local/emhttp/webGui/scripts/notify -i normal -s "Backup done." -d "Job $JobName $LocalFilesShare successfully finished."
    fi
done
    
echo "$(date "+%d.%m.%Y %T") INFO: Script complete."

exit

 

[[Support] Natcoso9955 - Loki]

Can anyone help me?

Unfortunately, no data from Promtail and Loki arrive at Grafana.

Here are my configurations:

 

Promtail config.yml in /mnt/user/appdata/promtail/config.yml

Quote

server:
  http_listen_port: 9080
  grpc_listen_port: 0

positions:
  filename: /tmp/positions.yaml

clients:
  - url: http://[IP]:3100/loki/api/v1/push

scrape_configs:
- job_name: system
  static_configs:
  - targets:
      - localhost
    labels:
      job: varlogs
      agent: promtail
      __path__: /var/log/*log
- job_name: nginx
  static_configs:
  - targets:
      - localhost
    labels:
      job: nginx
      host: swag
      __path__: /mnt/user/appdata/swag/log/nginx/*log

 

 

Loki local-config.yaml in /mnt/user/appdata/loki/conf/local-config.yaml

Quote

auth_enabled: false

server:
  http_listen_port: 3100
  grpc_listen_port: 9096

ingester:
  wal:
    enabled: true
    dir: /tmp/wal
  lifecycler:
    address: 127.0.0.1
    ring:
      kvstore:
        store: inmemory
      replication_factor: 1
    final_sleep: 0s
  chunk_idle_period: 1h       # Any chunk not receiving new logs in this time will be flushed
  max_chunk_age: 1h           # All chunks will be flushed when they hit this age, default is 1h
  chunk_target_size: 1048576  # Loki will attempt to build chunks up to 1.5MB, flushing first if chunk_idle_period or max_chunk_age is reached first
  chunk_retain_period: 30s    # Must be greater than index read cache TTL if using an index cache (Default index read cache TTL is 5m)
  max_transfer_retries: 0     # Chunk transfers disabled

schema_config:
  configs:
    - from: 2020-10-24
      store: boltdb-shipper
      object_store: filesystem
      schema: v11
      index:
        prefix: index_
        period: 24h

storage_config:
  boltdb_shipper:
    active_index_directory: /tmp/loki/boltdb-shipper-active
    cache_location: /tmp/loki/boltdb-shipper-cache
    cache_ttl: 24h         # Can be increased for faster performance over longer query periods, uses more disk space
    shared_store: filesystem
  filesystem:
    directory: /tmp/loki/chunks

compactor:
  working_directory: /tmp/loki/boltdb-shipper-compactor
  shared_store: filesystem

limits_config:
  reject_old_samples: true
  reject_old_samples_max_age: 168h

chunk_store_config:
  max_look_back_period: 0s

table_manager:
  retention_deletes_enabled: false
  retention_period: 0s

ruler:
  storage:
    type: local
    local:
      directory: /tmp/loki/rules
  rule_path: /tmp/loki/rules-temp
  alertmanager_url: http://localhost:9093
  ring:
    kvstore:
      store: inmemory
  enable_api: true

 

[App >Network Browser< Zugriff auf shares via Handy]

11 hours ago, Hoddl said:

@Anym001

wie schaffst du die Verbindung zu dem Unraidmount? Ich würde auch gerne einen Ordner in Nextcloud haben um die Nextcloud so zu sagen als Suchmaschine zu benutzen... 

Was muss ich noch einstellen im Unraid das die Verbindung funktioniert?

 

Danke 

 

Zuerst musst du den gewünschten Pfad bei deinem Nextcloud Container hinzufügen. 

Dazu gehst du unter "Edit" ins Docker Template. 

Hier fügst du einen neuen Pfad hinzu. 

 

Config Type = Path

Name = Host Path %

Container Path = /mnt/Unraid/Musik

Host Path = /mnt/user/Musik/                      >> hier deinen gewünschten Share angeben

Access Mode = Read/Write

 

Danach in Nextcloud mit einem Admin Account in den Einstellungen unter "externer Speicher" wie folgt hinzufügen.

Unter "Konfiguration" muss der "Container Path" von oben verwendet werden. 

 

[[SOLVED] Nextcloud performance/ Hardware ausreichend?]

22 hours ago, mgutt said:

Da bekommt man die beste Performance, wenn man Folder statt vDisk wählt.

 

Wenn man auf Folder wechselt, wo sollte man diesen am Besten abspeichern?

Macht es Sinn diesen im appdata Folder zu ergänzen? /mnt/cache/appdata/docker/

[[SOLVED] Nextcloud performance/ Hardware ausreichend?]

6 hours ago, mgutt said:

Ich kenne niemanden, der mit MariaDB ein lahmes Setup hat.

Habe es gleich eingestellt wie von @mgutt beschrieben und keine Performanceprobleme. Nextcloud mit MariaDB läuft wie am Schnürchen.

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

4 hours ago, Hoddl said:

und was ist mit dem Ländercode? Wie bekomme ich den richtig gesetzt?

Bei mir war die Fehlermeldung weg, nachdem ich folgendes in der config.php ergänzt habe.

 

'default_language' => 'de',
'default_locale' => 'de_DE',

'default_phone_region' => 'DE',

 

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

38 minutes ago, Hoddl said:

ist die Nextcloud immer so behäbig?

 

Habe persönlich noch keine Performanceprobleme mit Nextcloud gehabt. 

Upload von zB Bilder läuft zackig. 

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

5 hours ago, Hoddl said:

nun hier die confic ohne Logindaten 🙂

 

Sorry, hatte vergessen zu erwähnen, dass vorher die persönlichen Informationen entfernt werden müssen. 

 

Probier mal bitte folgendes für deine Fehlermeldung:

'overwrite.cli.url' => 'http://192.168.XX.XX',     >>     'overwrite.cli.url' => 'http://192.168.XX.XX:Port',         

ODER komplett weglassen

 

Hier würde ich noch aus Gründen der besseren Lesbarkeit folgendes ändern:

'dbhost' => '192.168.XX.XX:3306',                  >>     'dbhost' => '192.168.XX.XX',

'dbport' => '',                                                >>     'dbport' => '3306',

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

1 hour ago, Hoddl said:

über die ip 🙂

Okay dann schaut die Sache anders aus. 
 

Poste mal bitte den Inhalt deiner config.php

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

2 hours ago, Hoddl said:

wo ist die denn zu finden 🙂

Wie rufst du denn Nextcloud auf?

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

6 minutes ago, Hoddl said:

meine domain ist in dem fall die IP???

Nein deine DDNS Adresse. 
zB nextcloud.domain.goip.de

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

2 minutes ago, Hoddl said:

Kann mir einer helfen dies zu lösen:

 

Müsste funktionieren wenn du folgendes in deiner Nextcloud config.php ergänzt. 

 

  'overwrite.cli.url' => 'https://meine-domain.de',
  'overwritehost' => 'meine-domain.de',
  'overwriteprotocol' => 'https',

 

  'default_language' => 'de',
  'default_locale' => 'de_DE',
  'default_phone_region' => 'DE',

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

Der Grund warum ich mit -u 99 ausführe ist, weil ich folgendes im Nextcloud Template ergänzt habe:

 

Quote

--user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0
&&  docker exec -u 0 Nextcloud /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars'

Ursache war damals ein Rechteproblem bei den Container Ordnern. 

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

2 hours ago, mgutt said:

Ist doch richtig @Anym001?

 

Bei mir ist es:

Quote

#!/bin/bash
docker exec -u 99 Nextcloud php -f /var/www/html/cron.php
exit 0

 

Ausführung alle 30 Minuten.

[Wie arbeitet Ihr mit euren Daten - direkt auf unRaid Server oder lokal?]

10 hours ago, ich777 said:

11 hours ago, MartinG said:

guten Editor wie Notepad++

Der gute alte "Editor" in Windows kann das auch

 

Der eingebaute Editor in Krusader funktioniert auch.

[SWAG SSL Zertifikat für mehrere Domains]

10 hours ago, AliH said:

jedoch wird nur für die "Hauptdomain" ein SSL Cert erstellt.

 

Welche Einstellungen hast du in deinem SWAG Template? (Am besten mal einen Screenshot posten)

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

5 hours ago, i-B4se said:

D.h. entweder man lässt alles mit Bridge oder br0 laufen.

 

Warum bist du überhaupt auf br0 gewechselt?

[Nextcloud Sicherheits- & Einrichtungswarnungen beheben]

11 minutes ago, i-B4se said:

Habe ich etwas übersehen?

 

Was hast du bei Container Port eingestellt? 

 

Laut Template hast du Port 8100 aktiviert.

In der Docker Übersicht sehe ich allerdings Port 80. 

 

Hast du schon mal versucht den Container mit http://192.168.178.15:80 aufzurufen?

[Wie arbeitet Ihr mit euren Daten - direkt auf unRaid Server oder lokal?]

Noch ein Tipp am Rande für SWAG: 

 

Normalerweise liegen die .conf Dateien für die proxy-confs in folgendem Ordner:

/mnt/user/appdata/swag/nginx/proxy-confs

 

 

Habe hier keine Datei "aktiviert", sondern die default Datei im folgenden Verzeichnis bearbeitet und den Inhalt der vorgeschlagenen proxy-confs Dateien eingefügt. -> Somit befinden sich die Einstellungen für alle Proxyweiterleitungen in einer Datei und sind damit bei weitem übersichtlicher. 

/mnt/user/appdata/swag/nginx/site-confs

 

[Syslog Docker Meldungen]

Alles klar, vielen Dank. :)

[Syslog Docker Meldungen]

Hallo, 

 

mir sind seit einiger Zeit komische Meldungen in meinem Syslog aufgefallen. (immer mal wiederkehrend)

Hier mal einen Teil davon:

 

Quote

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered blocking state

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered disabled state

Apr 20 06:26:06 nas kernel: device veth42be60c entered promiscuous mode

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered blocking state

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered forwarding state

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered disabled state

Apr 20 06:26:06 nas kernel: eth0: renamed from veth3f82378

Apr 20 06:26:06 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth42be60c: link becomes ready

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered blocking state

Apr 20 06:26:06 nas kernel: docker0: port 3(veth42be60c) entered forwarding state

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(vethfa4bbd0) entered disabled state

Apr 20 06:38:23 nas kernel: veth6411e32: renamed from eth0

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(vethfa4bbd0) entered disabled state

Apr 20 06:38:23 nas kernel: device vethfa4bbd0 left promiscuous mode

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(vethfa4bbd0) entered disabled state

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered blocking state

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered disabled state

Apr 20 06:38:23 nas kernel: device veth6fbfa37 entered promiscuous mode

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered blocking state

Apr 20 06:38:23 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered forwarding state

Apr 20 06:38:24 nas kernel: eth0: renamed from vethea3db7a

Apr 20 06:38:24 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6fbfa37: link becomes ready

Apr 20 06:38:27 nas kernel: eth0: renamed from veth49132d7

Apr 20 06:38:27 nas kernel: device br0 entered promiscuous mode

Apr 20 06:41:15 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered disabled state

Apr 20 06:41:15 nas kernel: vethea3db7a: renamed from eth0

Apr 20 06:41:15 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered disabled state

Apr 20 06:41:15 nas kernel: device veth6fbfa37 left promiscuous mode

Apr 20 06:41:15 nas kernel: br-de4e767e968b: port 1(veth6fbfa37) entered disabled state

Apr 20 06:41:16 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered blocking state

Apr 20 06:41:16 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered disabled state

Apr 20 06:41:16 nas kernel: device veth0c50a77 entered promiscuous mode

Apr 20 06:41:16 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered blocking state

Apr 20 06:41:16 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered forwarding state

Apr 20 06:41:16 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered disabled state

Apr 20 06:41:17 nas kernel: eth0: renamed from vethceaed97

Apr 20 06:41:17 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0c50a77: link becomes ready

Apr 20 06:41:17 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered blocking state

Apr 20 06:41:17 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered forwarding state

Apr 20 06:49:59 nas kernel: device br0 left promiscuous mode

Apr 20 06:49:59 nas kernel: veth49132d7: renamed from eth0

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered blocking state

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered disabled state

Apr 20 06:50:00 nas kernel: device vethb7a7a0d entered promiscuous mode

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered blocking state

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered forwarding state

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered disabled state

Apr 20 06:50:00 nas kernel: eth0: renamed from veth04271b4

Apr 20 06:50:00 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb7a7a0d: link becomes ready

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered blocking state

Apr 20 06:50:00 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered forwarding state

Apr 20 06:51:31 nas kernel: vethceaed97: renamed from eth0

Apr 20 06:51:31 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered disabled state

Apr 20 06:51:31 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered disabled state

Apr 20 06:51:31 nas kernel: device veth0c50a77 left promiscuous mode

Apr 20 06:51:31 nas kernel: br-de4e767e968b: port 1(veth0c50a77) entered disabled state

Apr 20 06:51:32 nas kernel: br-de4e767e968b: port 1(vethb723213) entered blocking state

Apr 20 06:51:32 nas kernel: br-de4e767e968b: port 1(vethb723213) entered disabled state

Apr 20 06:51:32 nas kernel: device vethb723213 entered promiscuous mode

Apr 20 06:51:32 nas kernel: br-de4e767e968b: port 1(vethb723213) entered blocking state

Apr 20 06:51:32 nas kernel: br-de4e767e968b: port 1(vethb723213) entered forwarding state

Apr 20 06:51:32 nas kernel: eth0: renamed from veth4fd5f6e

Apr 20 06:51:32 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb723213: link becomes ready

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered disabled state

Apr 20 06:53:58 nas kernel: veth04271b4: renamed from eth0

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered disabled state

Apr 20 06:53:58 nas kernel: device vethb7a7a0d left promiscuous mode

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(vethb7a7a0d) entered disabled state

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered blocking state

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered disabled state

Apr 20 06:53:58 nas kernel: device veth19ea5d3 entered promiscuous mode

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered blocking state

Apr 20 06:53:58 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered forwarding state

Apr 20 06:53:59 nas kernel: eth0: renamed from veth412205d

Apr 20 06:53:59 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth19ea5d3: link becomes ready

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered disabled state

Apr 20 06:53:59 nas kernel: veth412205d: renamed from eth0

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered disabled state

Apr 20 06:53:59 nas kernel: device veth19ea5d3 left promiscuous mode

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth19ea5d3) entered disabled state

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered blocking state

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered disabled state

Apr 20 06:53:59 nas kernel: device veth4f21a24 entered promiscuous mode

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered blocking state

Apr 20 06:53:59 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered forwarding state

Apr 20 06:54:00 nas kernel: eth0: renamed from veth332fb88

Apr 20 06:54:00 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4f21a24: link becomes ready

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered disabled state

Apr 20 06:54:00 nas kernel: veth332fb88: renamed from eth0

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered disabled state

Apr 20 06:54:00 nas kernel: device veth4f21a24 left promiscuous mode

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth4f21a24) entered disabled state

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered blocking state

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered disabled state

Apr 20 06:54:00 nas kernel: device veth7aa686c entered promiscuous mode

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered blocking state

Apr 20 06:54:00 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered forwarding state

Apr 20 06:54:01 nas kernel: eth0: renamed from vethbbce5ae

Apr 20 06:54:01 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7aa686c: link becomes ready

Apr 20 06:54:01 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered disabled state

Apr 20 06:54:01 nas kernel: vethbbce5ae: renamed from eth0

Apr 20 06:54:01 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered disabled state

Apr 20 06:54:01 nas kernel: device veth7aa686c left promiscuous mode

Apr 20 06:54:01 nas kernel: br-de4e767e968b: port 5(veth7aa686c) entered disabled state

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered blocking state

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered disabled state

Apr 20 06:54:02 nas kernel: device vethe5f5b66 entered promiscuous mode

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered blocking state

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered forwarding state

Apr 20 06:54:02 nas kernel: eth0: renamed from vethc225370

Apr 20 06:54:02 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe5f5b66: link becomes ready

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered disabled state

Apr 20 06:54:02 nas kernel: vethc225370: renamed from eth0

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered disabled state

Apr 20 06:54:02 nas kernel: device vethe5f5b66 left promiscuous mode

Apr 20 06:54:02 nas kernel: br-de4e767e968b: port 5(vethe5f5b66) entered disabled state

Apr 20 06:54:03 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered blocking state

Apr 20 06:54:03 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered disabled state

Apr 20 06:54:03 nas kernel: device vetha04a2ca entered promiscuous mode

Apr 20 06:54:03 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered blocking state

Apr 20 06:54:03 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered forwarding state

Apr 20 06:54:03 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered disabled state

Apr 20 06:54:04 nas kernel: eth0: renamed from veth757238d

Apr 20 06:54:04 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha04a2ca: link becomes ready

Apr 20 06:54:04 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered blocking state

Apr 20 06:54:04 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered forwarding state

Apr 20 06:54:04 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered disabled state

Apr 20 06:54:04 nas kernel: veth757238d: renamed from eth0

Apr 20 06:54:04 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered disabled state

Apr 20 06:54:04 nas kernel: device vetha04a2ca left promiscuous mode

Apr 20 06:54:04 nas kernel: br-de4e767e968b: port 5(vetha04a2ca) entered disabled state

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered blocking state

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered disabled state

Apr 20 06:54:06 nas kernel: device vethe6e2ad8 entered promiscuous mode

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered blocking state

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered forwarding state

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered disabled state

Apr 20 06:54:06 nas kernel: eth0: renamed from veth2a41ca1

Apr 20 06:54:06 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe6e2ad8: link becomes ready

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered blocking state

Apr 20 06:54:06 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered forwarding state

Apr 20 06:54:07 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered disabled state

Apr 20 06:54:07 nas kernel: veth2a41ca1: renamed from eth0

Apr 20 06:54:07 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered disabled state

Apr 20 06:54:07 nas kernel: device vethe6e2ad8 left promiscuous mode

Apr 20 06:54:07 nas kernel: br-de4e767e968b: port 5(vethe6e2ad8) entered disabled state

Apr 20 06:54:10 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered blocking state

Apr 20 06:54:10 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered disabled state

Apr 20 06:54:10 nas kernel: device veth712efe4 entered promiscuous mode

Apr 20 06:54:10 nas kernel: eth0: renamed from veth27d9f03

Apr 20 06:54:10 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth712efe4: link becomes ready

Apr 20 06:54:10 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered blocking state

Apr 20 06:54:10 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered forwarding state

Apr 20 06:54:11 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered disabled state

Apr 20 06:54:11 nas kernel: veth27d9f03: renamed from eth0

Apr 20 06:54:11 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered disabled state

Apr 20 06:54:11 nas kernel: device veth712efe4 left promiscuous mode

Apr 20 06:54:11 nas kernel: br-de4e767e968b: port 5(veth712efe4) entered disabled state

Apr 20 06:54:17 nas kernel: br-de4e767e968b: port 5(veth767b573) entered blocking state

Apr 20 06:54:17 nas kernel: br-de4e767e968b: port 5(veth767b573) entered disabled state

Apr 20 06:54:17 nas kernel: device veth767b573 entered promiscuous mode

Apr 20 06:54:17 nas kernel: eth0: renamed from veth269b709

Apr 20 06:54:17 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth767b573: link becomes ready

Apr 20 06:54:17 nas kernel: br-de4e767e968b: port 5(veth767b573) entered blocking state

Apr 20 06:54:17 nas kernel: br-de4e767e968b: port 5(veth767b573) entered forwarding state

Apr 20 06:54:18 nas kernel: br-de4e767e968b: port 5(veth767b573) entered disabled state

Apr 20 06:54:18 nas kernel: veth269b709: renamed from eth0

Apr 20 06:54:18 nas kernel: br-de4e767e968b: port 5(veth767b573) entered disabled state

Apr 20 06:54:18 nas kernel: device veth767b573 left promiscuous mode

Apr 20 06:54:18 nas kernel: br-de4e767e968b: port 5(veth767b573) entered disabled state

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered blocking state

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered disabled state

Apr 20 06:54:31 nas kernel: device vethcc49683 entered promiscuous mode

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered blocking state

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered forwarding state

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered disabled state

Apr 20 06:54:31 nas kernel: eth0: renamed from vethf2d927b

Apr 20 06:54:31 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcc49683: link becomes ready

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered blocking state

Apr 20 06:54:31 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered forwarding state

Apr 20 06:54:32 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered disabled state

Apr 20 06:54:32 nas kernel: vethf2d927b: renamed from eth0

Apr 20 06:54:32 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered disabled state

Apr 20 06:54:32 nas kernel: device vethcc49683 left promiscuous mode

Apr 20 06:54:32 nas kernel: br-de4e767e968b: port 5(vethcc49683) entered disabled state

Apr 20 06:54:57 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered blocking state

Apr 20 06:54:57 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered disabled state

Apr 20 06:54:57 nas kernel: device veth30c9524 entered promiscuous mode

Apr 20 06:54:58 nas kernel: eth0: renamed from veth9246f85

Apr 20 06:54:58 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth30c9524: link becomes ready

Apr 20 06:54:58 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered blocking state

Apr 20 06:54:58 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered forwarding state

Apr 20 06:54:58 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered disabled state

Apr 20 06:54:58 nas kernel: veth9246f85: renamed from eth0

Apr 20 06:54:58 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered disabled state

Apr 20 06:54:58 nas kernel: device veth30c9524 left promiscuous mode

Apr 20 06:54:58 nas kernel: br-de4e767e968b: port 5(veth30c9524) entered disabled state

Apr 20 06:55:49 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered blocking state

Apr 20 06:55:49 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered disabled state

Apr 20 06:55:49 nas kernel: device veth6d6613b entered promiscuous mode

Apr 20 06:55:49 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered blocking state

Apr 20 06:55:49 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered forwarding state

Apr 20 06:55:49 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered disabled state

Apr 20 06:55:50 nas kernel: eth0: renamed from veth197811e

Apr 20 06:55:50 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6d6613b: link becomes ready

Apr 20 06:55:50 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered blocking state

Apr 20 06:55:50 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered forwarding state

Apr 20 06:55:50 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered disabled state

Apr 20 06:55:50 nas kernel: veth197811e: renamed from eth0

Apr 20 06:55:50 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered disabled state

Apr 20 06:55:50 nas kernel: device veth6d6613b left promiscuous mode

Apr 20 06:55:50 nas kernel: br-de4e767e968b: port 5(veth6d6613b) entered disabled state

Apr 20 06:56:45 nas kernel: docker0: port 3(veth42be60c) entered disabled state

Apr 20 06:56:45 nas kernel: veth3f82378: renamed from eth0

Apr 20 06:56:45 nas kernel: docker0: port 3(veth42be60c) entered disabled state

Apr 20 06:56:45 nas kernel: device veth42be60c left promiscuous mode

Apr 20 06:56:45 nas kernel: docker0: port 3(veth42be60c) entered disabled state

Apr 20 06:56:45 nas kernel: docker0: port 3(veth88b1600) entered blocking state

Apr 20 06:56:45 nas kernel: docker0: port 3(veth88b1600) entered disabled state

Apr 20 06:56:45 nas kernel: device veth88b1600 entered promiscuous mode

Apr 20 06:56:45 nas kernel: docker0: port 3(veth88b1600) entered blocking state

Apr 20 06:56:45 nas kernel: docker0: port 3(veth88b1600) entered forwarding state

Apr 20 06:56:45 nas kernel: eth0: renamed from veth0c1271f

Apr 20 06:56:45 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth88b1600: link becomes ready

Apr 20 06:56:50 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered blocking state

Apr 20 06:56:50 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered disabled state

Apr 20 06:56:50 nas kernel: device vethb92446f entered promiscuous mode

Apr 20 06:56:50 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered blocking state

Apr 20 06:56:50 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered forwarding state

Apr 20 06:56:50 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered disabled state

Apr 20 06:56:51 nas kernel: eth0: renamed from vethbf006d6

Apr 20 06:56:51 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb92446f: link becomes ready

Apr 20 06:56:51 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered blocking state

Apr 20 06:56:51 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered forwarding state

Apr 20 06:56:51 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered disabled state

Apr 20 06:56:51 nas kernel: vethbf006d6: renamed from eth0

Apr 20 06:56:51 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered disabled state

Apr 20 06:56:51 nas kernel: device vethb92446f left promiscuous mode

Apr 20 06:56:51 nas kernel: br-de4e767e968b: port 5(vethb92446f) entered disabled state

Apr 20 06:57:21 nas kernel: docker0: port 3(veth88b1600) entered disabled state

Apr 20 06:57:21 nas kernel: veth0c1271f: renamed from eth0

Apr 20 06:57:21 nas kernel: docker0: port 3(veth88b1600) entered disabled state

Apr 20 06:57:21 nas kernel: device veth88b1600 left promiscuous mode

Apr 20 06:57:21 nas kernel: docker0: port 3(veth88b1600) entered disabled state

Apr 20 06:57:21 nas kernel: docker0: port 3(vethcb0af83) entered blocking state

Apr 20 06:57:21 nas kernel: docker0: port 3(vethcb0af83) entered disabled state

Apr 20 06:57:21 nas kernel: device vethcb0af83 entered promiscuous mode

Apr 20 06:57:21 nas kernel: docker0: port 3(vethcb0af83) entered blocking state

Apr 20 06:57:21 nas kernel: docker0: port 3(vethcb0af83) entered forwarding state

Apr 20 06:57:21 nas kernel: eth0: renamed from veth8e32929

Apr 20 06:57:21 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcb0af83: link becomes ready

Apr 20 06:57:44 nas kernel: br-de4e767e968b: port 1(vethb723213) entered disabled state

Apr 20 06:57:44 nas kernel: veth4fd5f6e: renamed from eth0

Apr 20 06:57:44 nas kernel: br-de4e767e968b: port 1(vethb723213) entered disabled state

Apr 20 06:57:44 nas kernel: device vethb723213 left promiscuous mode

Apr 20 06:57:44 nas kernel: br-de4e767e968b: port 1(vethb723213) entered disabled state

Apr 20 06:57:45 nas kernel: br-de4e767e968b: port 1(veth82d0a34) entered blocking state

Apr 20 06:57:45 nas kernel: br-de4e767e968b: port 1(veth82d0a34) entered disabled state

Apr 20 06:57:45 nas kernel: device veth82d0a34 entered promiscuous mode

Apr 20 06:57:46 nas kernel: eth0: renamed from veth1285969

Apr 20 06:57:46 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth82d0a34: link becomes ready

Apr 20 06:57:46 nas kernel: br-de4e767e968b: port 1(veth82d0a34) entered blocking state

Apr 20 06:57:46 nas kernel: br-de4e767e968b: port 1(veth82d0a34) entered forwarding state

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered blocking state

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered disabled state

Apr 20 06:59:16 nas kernel: device veth651ecd4 entered promiscuous mode

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered blocking state

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered forwarding state

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered disabled state

Apr 20 06:59:16 nas kernel: eth0: renamed from veth042048b

Apr 20 06:59:16 nas kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth651ecd4: link becomes ready

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered blocking state

Apr 20 06:59:16 nas kernel: docker0: port 4(veth651ecd4) entered forwarding state

Apr 20 07:00:05 nas emhttpd: read SMART /dev/sdc

Apr 20 07:03:39 nas kernel: docker0: port 4(veth651ecd4) entered disabled state

Apr 20 07:03:39 nas kernel: veth042048b: renamed from eth0

Apr 20 07:03:39 nas kernel: docker0: port 4(veth651ecd4) entered disabled state

Apr 20 07:03:39 nas kernel: device veth651ecd4 left promiscuous mode

Apr 20 07:03:39 nas kernel: docker0: port 4(veth651ecd4) entered disabled state

Apr 20 07:03:44 nas kernel: docker0: port 3(vethcb0af83) entered disabled state

Apr 20 07:03:44 nas kernel: veth8e32929: renamed from eth0

Apr 20 07:03:44 nas kernel: docker0: port 3(vethcb0af83) entered disabled state

Apr 20 07:03:44 nas kernel: device vethcb0af83 left promiscuous mode

Apr 20 07:03:44 nas kernel: docker0: port 3(vethcb0af83) entered disabled state

 

Verwendete Unraid Version: 6.9.2

Network Einstellungen: IPv4 only 

 

Hat jemand eine Idee was das zu bedeuten hat? 

Ist das normal?