Fragen zum Systemlog Raspberymatic

Einrichtung, Nutzung und Hilfe zu RaspberryMatic (OCCU auf Raspberry Pi)

Moderatoren: jmaus, Co-Administratoren

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Fragen zum Systemlog Raspberymatic

Beitrag von klana » 13.10.2017, 13:10

Hi,

seit heute habe ich den Raspi in Betrieb genommen und da sind mir im Systemlog so einige Stellen aufgefallen.
Wenn mir hier mal jemand auf die Sprünge helfen und die im Log markierten Stellen erklären könnte....
Die Stellen sind am Anfang der Zeile mit "FRAGE: " markiert.

Gruß und schon mal Vielen Dank im Vorraus.
Klana

Code: Alles auswählen

Oct 13 12:10:12 homematic-raspi syslog.info syslogd started: BusyBox v1.27.1
Oct 13 12:10:12 homematic-raspi user.notice kernel: klogd started: BusyBox v1.27.1 (2017-10-07 09:45:51 CEST)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000] Linux version 4.9.53-v7 (damato@bilbo) (gcc version 6.4.0 (Buildroot 2017.08-00656-gaa3e245-dirty) ) #1 SMP PREEMPT Sat Oct 7 10:10:03 CEST 2017
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] CPU: div instructions available: patching division code
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] cma: Reserved 8 MiB at 0x3ac00000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Memory policy: Data cache writealloc
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000] On node 0 totalpages: 242688
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat 80c6eb40, node_mem_map ba3a1000
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000]   Normal zone: 2133 pages used for memmap
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000]   Normal zone: 242688 pages, LIFO batch:31
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] percpu: Embedded 14 pages/cpu @ba35b000 s25804 r8192 d23348 u57344
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000] pcpu-alloc: s25804 r8192 d23348 u57344 alloc=14*4096
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 240555
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty2 root=PARTUUID=b6852070-02 ro noswap rootfstype=ext4 elevator=deadline fsck.repair=yes lapic sdhci_bcm2708.enable_llm=0 rootwait rootdelay=5 consoleblank=0 logo.nologo quiet
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Memory: 940376K/970752K available (7168K kernel code, 467K rwdata, 2016K rodata, 1024K init, 776K bss, 22184K reserved, 8192K cma-reserved)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000] Virtual kernel memory layout:
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]     vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]     lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]     modules : 0x7f000000 - 0x80000000   (  16 MB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]       .text : 0x80008000 - 0x80800000   (8160 kB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]       .init : 0x80b00000 - 0x80c00000   (1024 kB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]       .data : 0x80c00000 - 0x80c74cd0   ( 468 kB)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.000000]        .bss : 0x80c76000 - 0x80d383b4   ( 777 kB)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] Preemptible hierarchical RCU implementation.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] 	Build-time adjustment of leaf fanout to 32.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] NR_IRQS:16 nr_irqs:16 16
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000006] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000019] Switching to timer-based delay loop, resolution 52ns
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000283] Console: colour dummy device 80x30
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000301] console [tty2] enabled
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000325] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000344] pid_max: default: 32768 minimum: 301
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000655] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.000667] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.001658] Disabling memory control group subsystem
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.001734] CPU: Testing write buffer coherency: ok
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.001770] ftrace: allocating 22267 entries in 66 pages
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.049436] CPU0: update cpu_capacity 1024
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.049451] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.049489] Setting up static identity map for 0x100000 - 0x100034
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.219496] CPU1: update cpu_capacity 1024
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.219504] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.289604] CPU2: update cpu_capacity 1024
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.289611] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359733] CPU3: update cpu_capacity 1024
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359740] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359843] Brought up 4 CPUs
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359855] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359861] CPU: All CPU(s) started in HYP mode.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.359866] CPU: Virtualization extensions available.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.360728] devtmpfs: initialized
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.373524] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.373820] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.373838] futex hash table entries: 1024 (order: 4, 65536 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.374408] pinctrl core: initialized pinctrl subsystem
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.375403] NET: Registered protocol family 16
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.377963] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.387489] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.387497] hw-breakpoint: maximum watchpoint size is 8 bytes.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.389728] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    0.391097] irq: no irq domain found for /soc/aux@0x7e215000 !
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.481078] bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.483073] SCSI subsystem initialized
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.483247] usbcore: registered new interface driver usbfs
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.483331] usbcore: registered new interface driver hub
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.483437] usbcore: registered new device driver usb
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.489885] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-10-06 13:56
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.491518] clocksource: Switched to clocksource arch_sys_counter
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.546552] VFS: Disk quotas dquot_6.6.0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.546634] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.546865] FS-Cache: Loaded
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.547131] CacheFiles: Loaded
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.560771] NET: Registered protocol family 2
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.561788] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.561897] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562083] TCP: Hash tables configured (established 8192 bind 8192)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562174] UDP hash table entries: 512 (order: 2, 16384 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562218] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562445] NET: Registered protocol family 1
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562939] RPC: Registered named UNIX socket transport module.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562946] RPC: Registered udp transport module.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562951] RPC: Registered tcp transport module.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.562957] RPC: Registered tcp NFSv4.1 backchannel transport module.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.564145] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.566630] workingset: timestamp_bits=14 max_order=18 bucket_order=4
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.583611] FS-Cache: Netfs 'nfs' registered for caching
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.584659] NFS: Registering the id_resolver key type
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.584686] Key type id_resolver registered
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    0.584693] Key type id_legacy registered
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.587351] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.587475] io scheduler noop registered
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.587482] io scheduler deadline registered (default)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.587761] io scheduler cfq registered
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.593958] BCM2708FB: allocated DMA memory fad10000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.593985] BCM2708FB: allocated DMA channel 0 @ bb80f000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.602782] Console: switching to colour frame buffer device 80x30
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.608172] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Oct 13 12:10:12 homematic-raspi user.err kernel: [    0.609827] bcm2835-aux-uart 3f215040.serial: could not get clk: -517
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611145] bcm2835-rng 3f104000.rng: hwrng registered
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611280] vc-cma: Videocore CMA driver
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611287] vc-cma: vc_cma_base      = 0x00000000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611294] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611300] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.611589] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.612176] vc-sm: Videocore shared memory driver
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.628519] brd: module loaded
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.638006] loop: module loaded
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.638019] Loading iSCSI transport class v2.0-870.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.638584] usbcore: registered new interface driver smsc95xx
Oct 13 12:10:12 homematic-raspi user.info kernel: [    0.638600] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    0.866752] Core Release: 2.80a
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    0.866762] Setting default values for core params
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    0.866789] Finished setting default values for core params
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067183] Using Buffer DMA mode
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067189] Periodic Transfer Interrupt Enhancement - disabled
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067196] Multiprocessor Interrupt Enhancement - disabled
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067203] OTG VER PARAM: 0, OTG VER FLAG: 0
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067213] Dedicated Tx FIFOs mode
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067601] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbad04000 dma = 0xfad04000 len=9024
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067627] FIQ FSM acceleration enabled for :
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067627] Non-periodic Split Transactions
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067627] Periodic Split Transactions
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067627] High-Speed Isochronous Endpoints
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067627] Interrupt/Control Split Transaction hack enabled
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    1.067635] dwc_otg: Microframe scheduler enabled
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067687] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8059b900
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067698] WARN::hcd_init_fiq:460: FIQ ASM at 0x8059bc60 length 36
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067711] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.067778] dwc_otg 3f980000.usb: DWC OTG Controller
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.067814] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.067848] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067896] Init: Port Power? op_state=1
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.067902] Init: Power Port (0)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.068150] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.068162] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.068171] usb usb1: Product: DWC OTG Controller
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.068181] usb usb1: Manufacturer: Linux 4.9.53-v7 dwc_otg_hcd
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.068189] usb usb1: SerialNumber: 3f980000.usb
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.069103] hub 1-0:1.0: USB hub found
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.069151] hub 1-0:1.0: 1 port detected
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    1.069808] dwc_otg: FIQ enabled
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    1.069814] dwc_otg: NAK holdoff enabled
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    1.069819] dwc_otg: FIQ split-transaction FSM enabled
Oct 13 12:10:12 homematic-raspi user.debug kernel: [    1.069834] Module dwc_common_port init
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.070130] usbcore: registered new interface driver usb-storage
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.070372] mousedev: PS/2 mouse device common for all mice
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.071408] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.071745] bcm2835-cpufreq: min=600000 max=1200000
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.072263] sdhci: Secure Digital Host Controller Interface driver
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.072268] sdhci: Copyright(c) Pierre Ossman
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.072581] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.074804] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.074912] sdhci-pltfm: SDHCI platform and OF driver helper
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.078599] hidraw: raw HID events driver (C) Jiri Kosina
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.078702] usbcore: registered new interface driver usbhid
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.078705] usbhid: USB HID core driver
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.079272] vchiq: vchiq_init_state: slot_zero = 0xbad80000, is_master = 0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.081235] [vc_sm_connected_init]: start
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.089455] [vc_sm_connected_init]: end - returning 0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.089685] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.089722] Initializing XFRM netlink socket
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.089737] NET: Registered protocol family 17
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    1.089808] Key type dns_resolver registered
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    1.090098] Registering SWP/SWPB emulation handler
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.090502] registered taskstats version 1
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.095854] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 220, base_baud = 31250000) is a 16550
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.096290] sdhost: log_buf @ bad07000 (fad07000)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.171530] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.173571] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.173576] mmc-bcm2835 3f300000.mmc: DMA channel allocated
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.231569] of_cfs_init
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.231640] of_cfs_init: OK
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.232110] Waiting 5 sec before mounting root device...
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.244303] mmc0: host does not support reading read-only switch, assuming write-enable
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.246134] mmc0: new high speed SDHC card at address 0001
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.246556] mmcblk0: mmc0:0001 00000 29.8 GiB
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.247739]  mmcblk0: p1 p2 p3
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.251174] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.252685] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.254192] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.256901] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.281613] Indeed it is in host mode hprt0 = 00021501
Oct 13 12:10:12 homematic-raspi user.notice kernel: [    1.304080] random: fast init done
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.343832] mmc1: new high speed SDIO card at address 0001
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.481568] usb 1-1: new high-speed USB device number 2 using dwc_otg
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    1.481714] Indeed it is in host mode hprt0 = 00001101
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.711848] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.711861] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.712704] hub 1-1:1.0: USB hub found
Oct 13 12:10:12 homematic-raspi user.info kernel: [    1.712792] hub 1-1:1.0: 5 ports detected
Oct 13 12:10:12 homematic-raspi user.info kernel: [    2.031555] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Oct 13 12:10:12 homematic-raspi user.info kernel: [    2.161835] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Oct 13 12:10:12 homematic-raspi user.info kernel: [    2.161847] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    2.164641] smsc95xx v1.0.5
Oct 13 12:10:12 homematic-raspi user.info kernel: [    2.255500] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:fb:43:73
Oct 13 12:10:12 homematic-raspi user.info kernel: [    6.328349] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Oct 13 12:10:12 homematic-raspi user.info kernel: [    6.328396] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    6.331599] devtmpfs: mounted
Oct 13 12:10:12 homematic-raspi user.info kernel: [    6.333138] Freeing unused kernel memory: 1024K
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    7.097810] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.113372] EXT4-fs (mmcblk0p3): mounted filesystem with journalled data mode. Opts: data=journal
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.258493] i2c /dev entries driver
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.294242] rtc-ds1307 1-006f: rtc core: registered mcp7941x as rtc0
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.294267] rtc-ds1307 1-006f: 64 bytes nvram
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.294328] i2c i2c-1: new_device: Instantiated device mcp7941x at 0x6f
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.346678] tun: Universal TUN/TAP device driver, 1.6
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.346688] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 13 12:10:12 homematic-raspi user.warn kernel: [    7.360517] bcm2835_raw_uart: loading out-of-tree module taints kernel.
Oct 13 12:10:12 homematic-raspi user.info kernel: [    7.362431] bcm2835_raw_uart: Driver successfully loaded for uart0_base=0x3f201000, uart0_irq=87.
Oct 13 12:10:12 homematic-raspi daemon.info kernel: [   10.302962] udevd[223]: starting version 3.2.2
Oct 13 12:10:13 homematic-raspi daemon.info kernel: [   10.332184] udevd[224]: starting eudev-3.2.2
Oct 13 12:10:13 homematic-raspi user.info kernel: [   10.478905] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Oct 13 12:10:13 homematic-raspi user.info kernel: [   10.656047] usbcore: registered new interface driver brcmfmac
Oct 13 12:10:13 homematic-raspi user.info kernel: [   10.765034] brcmfmac: Firmware version = wl0: Aug 29 2016 20:48:16 version 7.45.41.26 (r640327) FWID 01-4527cfab
Oct 13 12:10:13 homematic-raspi user.err kernel: [   10.765701] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.6.3 Inc Compiler: 1.29.4 Inc ClmImport: 1.31.4 Creation: 2016-08-29 20:46:38 
Oct 13 12:10:13 homematic-raspi user.notice kernel: [   10.958057] random: crng init done
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402563] Bluetooth: Core ver 2.22
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402649] NET: Registered protocol family 31
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402656] Bluetooth: HCI device and connection manager initialized
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402678] Bluetooth: HCI socket layer initialized
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402693] Bluetooth: L2CAP socket layer initialized
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.402735] Bluetooth: SCO socket layer initialized
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.409727] Bluetooth: HCI UART driver ver 2.3
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.409740] Bluetooth: HCI UART protocol H4 registered
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.409747] Bluetooth: HCI UART protocol Three-wire (H5) registered
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.409946] Bluetooth: HCI UART protocol Broadcom registered
Oct 13 12:10:18 homematic-raspi daemon.info bluetoothd[304]: Bluetooth daemon 5.46
Oct 13 12:10:18 homematic-raspi daemon.info bluetoothd[304]: Starting SDP server
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.547780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.547802] Bluetooth: BNEP filters: protocol multicast
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.547831] Bluetooth: BNEP socket layer initialized
Oct 13 12:10:18 homematic-raspi daemon.info bluetoothd[304]: Bluetooth management interface 1.14 initialized
Oct 13 12:10:18 homematic-raspi daemon.err bluetoothd[304]: Failed to set privacy: Rejected (0x0b)
Oct 13 12:10:18 homematic-raspi user.info kernel: [   15.684138] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Oct 13 12:10:19 homematic-raspi user.info kernel: [   17.192072] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Oct 13 12:10:23 homematic-raspi daemon.err udhcpc[343]: started, v1.27.1
Oct 13 12:10:23 homematic-raspi daemon.err udhcpc[343]: sending discover
Oct 13 12:10:23 homematic-raspi daemon.err udhcpc[343]: sending select for 192.168.178.20
Oct 13 12:10:23 homematic-raspi daemon.err udhcpc[343]: lease of 192.168.178.20 obtained, lease time 864000
Oct 13 12:10:23 homematic-raspi user.info kernel: [   21.186985] NET: Registered protocol family 10
Oct 13 12:10:24 homematic-raspi user.info kernel: [   21.372177] ip6_tables: (C) 2000-2006 Netfilter Core Team
Oct 13 12:10:24 homematic-raspi user.info firewall: configuration set
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: ifplugd 0.28 initializing.
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: Using interface eth0/B8:27:EB:FB:43:73 with driver <smsc95xx> (version: 22-Aug-2005)
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: Using detection mode: SIOCETHTOOL
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: Initialization complete, link beat detected.
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(wlan0)[411]: ifplugd 0.28 initializing, using NETLINK device monitoring.
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(wlan0)[411]: Using interface wlan0/B8:27:EB:AE:16:26 with driver <brcmfmac> (version: 7.45.41.26)
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(wlan0)[411]: Using detection mode: wireless extension
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(wlan0)[411]: Initialization complete, link beat not detected, interface enabled.
Oct 13 12:10:24 homematic-raspi user.info kernel: [   21.599445] brcmfmac: power management disabled
Oct 13 12:10:24 homematic-raspi user.info kernel: [   21.599867] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Oct 13 12:10:24 homematic-raspi daemon.warn ifplugd(eth0)[407]: client: ifup: interface eth0 already configured


FRAGE: <<== Was ist das?  Fehler?==>>>

Oct 13 12:10:24 homematic-raspi daemon.err ifplugd(wlan0)[411]: NLAPI: Packet too small or truncated!					

Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(wlan0)[411]: Exiting.
Oct 13 12:10:24 homematic-raspi daemon.info ifplugd(eth0)[407]: Program executed successfully.
Oct 13 12:10:29 homematic-raspi daemon.notice ntpdate[419]: step time server 81.14.202.21 offset -1.061376 sec
Oct 13 12:10:29 homematic-raspi daemon.notice ntpd[421]: ntpd 4.2.8p10@1.3728-o Sat Oct  7 07:59:24 UTC 2017 (1): Starting
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[421]: Command line: /usr/sbin/ntpd -g ntp.homematic.com
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: proto: precision = 0.989 usec (-20)
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen and drop on 0 v6wildcard [::]:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen normally on 2 lo 127.0.0.1:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen normally on 3 eth0 192.168.178.20:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen normally on 4 lo [::1]:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listen normally on 5 eth0 [fe80::ba27:ebff:fefb:4373%2]:123
Oct 13 12:10:29 homematic-raspi daemon.info ntpd[423]: Listening on routing socket on fd #22 for interface updates


FRAGE: <<== Was ist das? Fehlt da was? ==>>>

Oct 13 12:10:29 homematic-raspi daemon.err xinetd[444]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]    

Oct 13 12:10:29 homematic-raspi daemon.crit xinetd[444]: 444 {init_services} no services. Exiting...

FRAGE: <<== Was ist das? Fehlt da was? ==>>>

Oct 13 12:10:29 homematic-raspi user.err : Could not read serial number                                 

Oct 13 12:10:29 homematic-raspi auth.info sshd[467]: Server listening on 0.0.0.0 port 22.
Oct 13 12:10:29 homematic-raspi auth.info sshd[467]: Server listening on :: port 22.
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: write_pid /var/run/cuxd.pid [506]
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: CUx-Daemon(1.11a) on CCU(2.29.22.20171007) start PID:506
Oct 13 12:10:30 homematic-raspi user.info homematic: started cux-daemon
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:1045 update(-51s):Fri Oct 13 12:09:39 2017
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: write_proxy /var/cache/cuxd_proxy.ini (506 /usr/local/addons/cuxd/ 1.11a 2.29.22.20171007 0)
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: add interface 'CUxD'
Oct 13 12:10:30 homematic-raspi daemon.info cuxd[506]: write 4 interfaces to /usr/local/etc/config/InterfacesList.xml
Oct 13 12:10:30 homematic-raspi user.info root: Updating RF Lan Gateway Coprocessor Firmware
Oct 13 12:10:30 homematic-raspi user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Oct 13 12:10:30 homematic-raspi user.info root: Updating RF Lan Gateway Firmware
Oct 13 12:10:30 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Oct 13 12:10:30 homematic-raspi user.info root: Updating Wired Lan Gateway Firmware
Oct 13 12:10:30 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Oct 13 12:10:31 homematic-raspi daemon.info snmpd[553]: Created directory: /var/lib/snmp
Oct 13 12:10:31 homematic-raspi daemon.info snmpd[553]: Created directory: /var/lib/snmp/cert_indexes
Oct 13 12:10:31 homematic-raspi daemon.info snmpd[553]: Created directory: /var/lib/snmp/mib_indexes
Oct 13 12:10:31 homematic-raspi daemon.info snmpd[553]: Turning on AgentX master support.
Oct 13 12:10:31 homematic-raspi daemon.info snmpd[555]: NET-SNMP version 5.7.3
Oct 13 12:10:31 homematic-raspi user.info kernel: [   30.127406] eq3loop: created slave ttyS0
Oct 13 12:10:31 homematic-raspi user.info kernel: [   30.129122] eq3loop: created slave mmd_bidcos
Oct 13 12:10:35 homematic-raspi user.info kernel: [   34.333214] eq3loop: eq3loop_open_slave() mmd_bidcos
Oct 13 12:10:48 homematic-raspi user.info kernel: [   46.601378] eq3loop: eq3loop_open_slave() ttyS0
Oct 13 12:10:48 homematic-raspi user.info kernel: [   46.601725] eq3loop: eq3loop_close_slave() ttyS0
Oct 13 12:10:48 homematic-raspi user.info kernel: [   46.619628] eq3loop: eq3loop_open_slave() ttyS0
Oct 13 12:10:48 homematic-raspi user.info kernel: [   46.619915] eq3loop: eq3loop_close_slave() ttyS0
Oct 13 12:10:48 homematic-raspi user.info kernel: [   46.648419] eq3loop: eq3loop_open_slave() ttyS0
Oct 13 12:10:48 homematic-raspi user.notice kernel: [   46.652221] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Oct 13 12:10:48 homematic-raspi user.notice kernel: [   46.652242] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Oct 13 12:10:54 homematic-raspi daemon.warn cuxd[506]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
Oct 13 12:10:56 homematic-raspi daemon.warn cuxd[506]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
Oct 13 12:11:00 homematic-raspi user.info homematic: meine-homematic.de loophammer startet openvpn.

FRAGE: <<== Was ist das? ==>>

Oct 13 12:11:00 homematic-raspi daemon.warn openvpn[779]: WARNING: file '/usr/local/etc/config/addons/mh/client.key' is group or others accessible 
Oct 13 12:11:00 homematic-raspi daemon.warn openvpn[780]: WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.					


FRAGE: <<== Was ist das? ==>>

Oct 13 12:11:03 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 13 12:11:03 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.


FRAGE: <<<< Unsicher?? >>>>

Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: cipher with small block size in use, reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
Oct 13 12:11:05 homematic-raspi daemon.notice openvpn[780]: do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: ERROR: Linux route add command failed: external program exited with error status: 2
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this


Oct 13 12:11:07 homematic-raspi daemon.info ntpd[423]: Listen normally on 6 tun0 10.194.59.92:123
Oct 13 12:11:07 homematic-raspi daemon.info ntpd[423]: Listen normally on 7 tun0 [fe80::cb3b:b387:74be:4f8d%4]:123


FRAGE: <<== Was ist das? Warum kommt das immer beim Reboot? =====>>

Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:10 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:10 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:10 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:11 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:11 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:11 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:11 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [iseXmlRpc.cpp:1440]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [iseXmlRpc.cpp:1440]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [iseXmlRpc.cpp:1440]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [iseXmlRpc.cpp:1440]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]


FRAGE: <<== Warum werden immer verschiedne Geräte angemeckert? Warum kommt das immer beim Reboot? =====>>

Oct 13 12:11:17 homematic-raspi user.err rfd: HSSParameter::GetValue() id=LUX failed getting physical value.
Oct 13 12:11:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"NEQ1357311:1","LUX"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Oct 13 12:11:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 13 12:11:17 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Oct 13 12:11:26 homematic-raspi daemon.info cuxd[506]: INIT 'xmlrpc_bin://127.0.0.1:1999' '1238'
Oct 13 12:11:34 homematic-raspi user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Oct 13 12:11:34 homematic-raspi user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Oct 13 12:11:34 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0499379:4","STATE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Oct 13 12:11:34 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 13 12:11:34 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 13 12:11:47 homematic-raspi user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Oct 13 12:11:47 homematic-raspi user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Oct 13 12:12:06 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0412633:1","BRIGHTNESS"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 13 12:12:06 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"LEQ0412783:1","BRIGHTNESS"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Oct 13 12:12:06 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Oct 13 12:12:08 homematic-raspi user.err rfd: HSSParameter::GetValue() id=LUX failed getting physical value.


<<=== Ab hier werden eigene Programme beim Reboot abgearbeitet ===>>

Oct 13 12:15:48 homematic-raspi user.debug script: [LED16 per Hand resettet]
Oct 13 12:15:57 homematic-raspi user.debug script: [StandardOffsets Astro setzen bei Reboot]
Oct 13 12:16:17 homematic-raspi user.debug script: [Heizung auf Winterbetrieb stellen bei Reboot]

FRAGE: <<<== Dieses Gerät gibt es nicht! == >> 
Oct 13 12:16:33 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= OEQ0305956 [iseXmlRpc.cpp:2157]
Oct 13 12:16:37 homematic-raspi user.debug script: [REBOOT ABGESCHLOSSEN]
Oct 13 12:30:00 homematic-raspi cron.info crond[208]: USER root pid 867 cmd /bin/SetInterfaceClock 127.0.0.1:2001
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Benutzeravatar
jmaus
Beiträge: 9862
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 464 Mal
Danksagung erhalten: 1880 Mal
Kontaktdaten:

Re: Fragen zum Systemlog Raspberymatic

Beitrag von jmaus » 13.10.2017, 13:51

klana hat geschrieben: seit heute habe ich den Raspi in Betrieb genommen und da sind mir im Systemlog so einige Stellen aufgefallen.
Wenn mir hier mal jemand auf die Sprünge helfen und die im Log markierten Stellen erklären könnte....
Hatten wir nicht schon in der Vergangenheit bzgl. deiner Motivation dauernd Logfiles zu studieren kontakt? :)

Ich würde dir wirklich raten besser nach dem Prinzip vorzugehen wenn praktische Fehler auftreten die Ursache dafür zu finden und nicht irgendwelche vermeintlichen Fehlermeldungen in verschiedensten Logfiles aktiv zu suchen mit der Motivation ergründen zu wollen was denn da der Grund ist und ob du da ein passendes Problem dazu finden kannst. Ich hatte dir ja bereits gesagt, das nicht alle Meldungen die so rausgeschrieben werden auch wirklich aktive Fehler sind sondern mitunter auch einfach aus debugging Gründen eine Fehlerausgabe erzeugt wird, aber eben nicht bedeutet das du praktisch damit ein Problem hast. Du wirst also niemals dazu kommen ein leeres Fehlerlog vorzufinden so sehr du dich auch bemühst dieses zu bereinigen. Auch postest du IMHO etwas zuviel und zu exzessiv an verschiedensten Stellen im Forum oftmals auch den kompletten Inhalt deiner Logfiles auch wenn >90% davon komplett irrelevant sind. Es wäre daher wirklich besser/hilfreich du würdest dich darauf konzentrieren lediglich bei einem aktiv auftretenden Problem im Logfile die Ursache dafür zu finden und eben nicht umgedreht.

Und wenn du schon Inhalte von Logfiles postest, dann bitte auch nur die zur Frage stehenden Stellen und nicht ganze boot logs mit kernel ausgaben die vollkommen normal sind.

Aber um dich nicht ganz enttäuschen zu wollen gehe ich mal auf ein paar Dinge in deinem Logfile ein:

Code: Alles auswählen

FRAGE: <<== Was ist das?  Fehler?==>>>
Oct 13 12:10:24 homematic-raspi daemon.err ifplugd(wlan0)[411]: NLAPI: Packet too small or truncated!               
Keine Ahnung, hast du ein Problem? Wenn nicht, irrelevant. Ansonsten googeln und rausfinden.

Code: Alles auswählen

FRAGE: <<== Was ist das? Fehlt da was? ==>>>
Oct 13 12:10:29 homematic-raspi daemon.err xinetd[444]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]    
Definitiv kein Fehler. Also irrelevant

Code: Alles auswählen

FRAGE: <<== Was ist das? Fehlt da was? ==>>>
Oct 13 12:10:29 homematic-raspi user.err : Could not read serial number                                 
Keine Ahnung, hast du ein Problem? Wenn nicht ignorieren.

Code: Alles auswählen

FRAGE: <<== Was ist das? ==>>
Oct 13 12:11:00 homematic-raspi daemon.warn openvpn[779]: WARNING: file '/usr/local/etc/config/addons/mh/client.key' is group or others accessible 
Oct 13 12:11:00 homematic-raspi daemon.warn openvpn[780]: WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.               
Das was es ist: Eine Warnung. Ergo, wenn es kein problem mit CloudMatic gibt, ignorieren.

Code: Alles auswählen

FRAGE: <<== Was ist das? ==>>
Oct 13 12:11:03 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Oct 13 12:11:03 homematic-raspi user.err rfd: HSSParameter::GetValue() id=BRIGHTNESS failed getting physical value.
Eine Mitteilung vom rfd daemon das er aus irgendwelchen Gründen den BRIGHTNESS wert eines Gerätes nicht erhalten kann. (Temporär) nicht erreichbar, etc.?!? Wenn es kein Problem gibt, ignorieren.

Code: Alles auswählen

FRAGE: <<<< Unsicher?? >>>>
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).
Potentiell unsicher, ja. Aber nur von den CloudMatic Machern zu beheben (müssen in ihrem Server eine andere Verschlüsselung wählen). Würde es aber als "minor" einstufen, trotzdem aber den CloudMatic Machern melden (was denen eigentlich schon bekannt sein sollte.

Code: Alles auswählen

FRAGE: <<== Was ist das? Warum kommt das immer beim Reboot? =====>>
Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:10 homematic-raspi user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [iseXmlRpc.cpp:1440]
Oct 13 12:11:15 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal =  [iseDOMdpHSS.cpp:130]
FRAGE: <<== Warum werden immer verschiedne Geräte angemeckert? Warum kommt das immer beim Reboot? =====>>
Oct 13 12:11:17 homematic-raspi user.err rfd: HSSParameter::GetValue() id=LUX failed getting physical value.
Oct 13 12:11:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"NEQ1357311:1","LUX"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Oct 13 12:11:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
So ist das eben :) Geräte sind manchmal nicht erreichbar, nicht in dem Modus das man sie abfragen kann, etc. etc. Aber dann wird es eben später nochmal abgefragt und gut ist. Auch hier gilt: Hast du kein praktisches Problem: ignorieren.

Code: Alles auswählen

FRAGE: <<<== Dieses Gerät gibt es nicht! == >> 
Oct 13 12:16:33 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= OEQ0305956 [iseXmlRpc.cpp:2157]
Na dann schau mal welche ID dein Funkmodul hast. Würde mich nicht überraschen wenn das die Adresse des Funkmoduls ist :)

Zusammenfassen also nochmal bitte im Hinterkopf behalten das nicht jede Meldung im Syslog (auch wenn sie den Terminus 'ERROR' trägt) kritisch ist oder man sich sorgen machen muss. Du solltest also bitte aufhören dauernd bzw. täglich dein Logfile lesen zu wollen sondern dich zurücklehnen, und wenn ein Problem auftritt dann das Logfile zu rate ziehen.
RaspberryMatic 3.75.7.20240420 @ ProxmoxVE – ~200 Hm-RF/HmIP-RF/HmIPW Geräte + ioBroker + HomeAssistant – GitHub / Sponsors / PayPal / ☕️

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von klana » 13.10.2017, 14:06

Hallo Jens,

erst einmal vielen Dank, dass du dich trotzdem erbarmt hast :mrgreen:

Die Meldung werde ich an CloudMatic melden..gefällt mir gar nicht...

Ich lese natürlich nicht immer die Systemlogs, aber nachdem ich den Raspi jetzt in den Produktivbetrieb genommen habe gucke ich natürlich da auch mal rein.

Auf dem Funkmodul kann ich die Nummer nicht finden



Gruß
Klana
Zuletzt geändert von klana am 13.10.2017, 14:29, insgesamt 1-mal geändert.
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Xel66
Beiträge: 14164
Registriert: 08.05.2013, 23:33
System: Alternative CCU (auf Basis OCCU)
Wohnort: Nordwürttemberg
Hat sich bedankt: 585 Mal
Danksagung erhalten: 1499 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von Xel66 » 13.10.2017, 14:08

klana hat geschrieben:Auf dem Funkmodul kann ich die Nummer nicht finden
Aber ich. Der mittlere große QR-COde ist es. Nur weil man etwas nicht sieht, heißt es nicht, dass es nicht da ist. :-)

Gruß Xel66
-------------------------------------------------------------------------------------------
524 Kanäle in 146 Geräten und 267 CUxD-Kanäle in 34 CUxD-Geräten:
343 Programme, 334 Systemvariablen und 183 Direktverknüpfungen,
RaspberryMatic Version: 3.65.11.20221005 + Testsystem: CCU2 2.61.7
-------------------------------------------------------------------------------------------
Einsteigerthread, Programmlogik-Thread, WebUI-Handbuch

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von klana » 13.10.2017, 14:10

Oh Mann, da soll man aber drauf kommen....
Und ja es ist das Funkmodul....
Danke!
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Benutzeravatar
JRiemann
Beiträge: 3903
Registriert: 12.11.2015, 21:05
Wohnort: Aurich
Danksagung erhalten: 3 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von JRiemann » 13.10.2017, 14:14

- auf Wunsch gelöscht -
Konnte sogar am Monitor eingelesen werden.
Zuletzt geändert von JRiemann am 13.10.2017, 14:34, insgesamt 1-mal geändert.
Viele Grüße!
Jörg

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von klana » 13.10.2017, 14:16

JRiemann hat geschrieben: Konnte sogar am Monitor eingelesen werden.
Genau das habe ich auch gemacht....endlich hab ich mal die QR-Code App gebraucht...
Zuletzt geändert von klana am 13.10.2017, 14:29, insgesamt 1-mal geändert.
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Benutzeravatar
jmaus
Beiträge: 9862
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 464 Mal
Danksagung erhalten: 1880 Mal
Kontaktdaten:

Re: Fragen zum Systemlog Raspberymatic

Beitrag von jmaus » 13.10.2017, 14:18

klana hat geschrieben: Die Meldung werde ich an CloudMatic melden..gefällt mir gar nicht...
Wie gesagt, dramatisier das nicht zu sehr. Wenn das kritisch wäre würde openvpn schon gar keine Verbindung zulassen. Ist halt die theoretische Möglichkeit das die VPN Verbindung mittels SWEET32 Attacke angegriffen werden kann (wer auch immer das bei dir am ende gerne möchte/kann)...
klana hat geschrieben: Ich lese natürlich nicht immer die Systemlogs, aber nachdem ich den Raspi jetzt in den Produktivbetrieb genommen habe gucke ich natürlich da auch mal rein.
Dann hast du jetzt ja reingeschaut und gut ist. Denn wenn du kein praktisches Problem hast dann solltest du dich ab jetzt zurücklehnen und die Show genießen statt dir dauernd sorgen zu machen ob denn ggf. im Logfile Fehler sind die du nicht nachvollziehen kannst.
klana hat geschrieben: Auf dem Funkmodul kann ich die Nummer nicht finden
Na spätestens jetzt weiss jeder durch das Bild mit dem QR Code die Seriennummer deines Funkmoduls und kann zu deinem Haus fahren und feine Attacken starten :) Du solltest wirklich vermeiden die Seriennummern deiner Geräte und Funkmodule öffentlich Preis zu geben denn wenn du keinen eigenen Sicherheitsschlüssel verwendest fliesst diese Information zusammen mit dem Standard-Sicherheitsschlüssel in die verschlüsselte Kommunikation ein :) Wenn du aber die Seriennummer deines Funkmoduls rausbekommen willst dann Klick in der WebUI einfach mal auf "Hilfe", dann wird die in dem Aboutteil dort normalerweise dargestellt.
RaspberryMatic 3.75.7.20240420 @ ProxmoxVE – ~200 Hm-RF/HmIP-RF/HmIPW Geräte + ioBroker + HomeAssistant – GitHub / Sponsors / PayPal / ☕️

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von klana » 13.10.2017, 14:35

jmaus hat geschrieben: Na spätestens jetzt weiss jeder durch das Bild mit dem QR Code die Seriennummer deines Funkmoduls und kann zu deinem Haus fahren und feine Attacken starten :) Du solltest wirklich vermeiden die Seriennummern deiner Geräte und Funkmodule öffentlich Preis zu geben denn wenn du keinen eigenen Sicherheitsschlüssel verwendest fliesst diese Information zusammen mit dem Standard-Sicherheitsschlüssel in die verschlüsselte Kommunikation ein :) Wenn du aber die Seriennummer deines Funkmoduls rausbekommen willst dann Klick in der WebUI einfach mal auf "Hilfe", dann wird die in dem Aboutteil dort normalerweise dargestellt.

Ich hatte vorher die Ortsdaten aus dem Bild herausgenommen....
Ok, dann lehne ich mich jetzt zurück und hoffe das ich nie, nie, nie wieder Fehler bekommen :mrgreen:

Nochmals Danke
Klana
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Benutzeravatar
klana
Beiträge: 1099
Registriert: 08.02.2015, 08:37
System: Alternative CCU (auf Basis OCCU)
Hat sich bedankt: 66 Mal
Danksagung erhalten: 27 Mal

Re: Fragen zum Systemlog Raspberymatic

Beitrag von klana » 18.10.2017, 09:39

Hi,

nur zur Info zu der folgenden Meldung von Cloudmatic

Code: Alles auswählen

Oct 13 12:11:05 homematic-raspi daemon.warn openvpn[780]: WARNING: INSECURE cipher with block size less than 128 bit (64 bit).  This allows attacks like SWEET32.  Mitigate by using a --cipher with a larger block size (e.g. AES-256-CBC).

Der Support von Cloudmatic hat mir geschrieben, dass der Fehler bekannt ist und es im 4. Quartal dazu ein Update geben wird.

Gruß
Klana
Gruß Klana
Es ist nett, wichtig zu sein. Aber es ist wichtiger, nett zu sein.

Antworten

Zurück zu „RaspberryMatic“