CCU2 funktioniert nicht mehr [SOLVED]

[manfredh]

Nur, um jegliche Missverständnisse auszuschließen - das ist der Bildschirm nach einem Recovery (Taste festhalten und Netzgerät einstecken):

Clipboard01.jpg (9.62 KiB) 1868 mal betrachtet

Ist s/w weil aus der Bedienungsanleitung.

Wenn du da nach einem Factory reset schon Probleme mit einzelnen Screens hast, macht es überhaupt keinen Sinn, mit irgendwelchen Restores weiter zu machen. Dann muss du erst mal schauen, das die jungfräuliche CCU sauber läuft.

Kannst du dann mal einen anderen Rechner nehmen? Einen, der mit seinem Browser sicher noch nie Verbindung zu einer CCU hatte? Zur Not tut's da auch ein Smartphone oder Tablet.

Gruß
Manfred

[123ccu]

Tom und Manfred,
vielen Dank für Eure Antworten.
Ich hatte den alten Link gepostet. Der richtige ist: https://1drv.ms/f/s!Ar28cBhIzhFlgcxZSgImiZQZ3-B8JQ
Werde nach der Arbeit mal das mit der alten Firmware probieren.
Und ein tablet.
Grüsse
Kai

[123ccu]

Das Problem besteht leider weiterhin.
Ich hatte aber keine Zeit weitere Test auszuführen. Stattdessen die Schaltaktoren an den e-Heizkörpern überbrückt. (Damit die Familie nicht ganz so unter meinen Problemen leidet )
Hat vielleicht jemand ein boot-up messages log von einer funktionierenden CCU2? Dann könnte ich wenigstens mal nach möglichen Unterschieden suchen.
Gruss
Kai

[anli]

Wenn ich es richtig mitgekriegt habe, hast du doch jetzt zwei CCU2? Dann kannst du bei einer einen Werksreset machen und hast ein sauberes Log.

Ansonsten schau mal auf die Entwicklerkonsole im Browser, wenn du die Seite aufrufst, die grau bleibt (f12 im chrome). Steht da etwas in der Konsole?

[123ccu]

hallo amli
ja - 2 CCU2. Nachdem ich am ersten Abend keine Lösung mit der Ersten gefunden habe trotz Reset und allem, habe ich sofort eine neue bestellt. Gleiche Probleme dort. Beide verhalten sich gleich schlecht - also mit Sicherheit kein hardware-Fehler.
Interessanter Gedanke... problem mit client-seitigem script...
Werde übers WE checken
Gruss
Kai

[manfredh]

Das Problem besteht leider weiterhin.
Ich hatte aber keine Zeit weitere Test auszuführen....

Hast du wenigstens mal versucht, mit einem ganz anderen Gerät (Tablet?) auf das WEB-Ui der zurückgesetzten CCU zuzugreifen?

[TomT]

Auch wenn die Fragen im ersten Moment doof erscheinen :
1. Hast du den Browsercache geleert, dann den Browser geschlossen und dann neu gestartet?
2. Hast du ein Tab oder Handy oder irgendwas, was von aussen per APP auf die CCU zu greift?

Bei 1. Nein : Cache leeren, Browser neu starten
Bei 2. Ja, : Bitte das Teil stromlos machen, ausschalten oder sonst wie davon abhalten, auf die IP der CCU zu zugreifen....

Hier mein Log vom frischen Reset einer Test CCU2 mit Firmware Version 2.29.23:

Code: Alles auswählen

Dec  8 12:46:10 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2017-10-11 14:29:35 CEST)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Booting Linux on physical CPU 0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Initializing cgroup subsys cpu
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000] Linux version 3.4.11.ccu2 (hudson@entw-build-10) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 PREEMPT Wed Oct 11 14:58:54 CEST 2017
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.000000] CPU: VIVT data cache, VIVT instruction cache
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.000000] Machine: eQ-3 HomeMatic CCU2
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.000000] Memory policy: ECC disabled, Data cache writeback
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000] On node 0 totalpages: 65536
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c03c42ec, node_mem_map c03f8000
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 512 pages used for memmap
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000]   Normal zone: 65024 pages, LIFO batch:15
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000] Kernel command line: eQ3Mode=production console=ttyAMA0,115200 ubi.mtd=7 ubi.mtd=6 ro ip=none root=ubi0:root ubi.mtd=7 rootfstype=ubifs noinitrd mtdparts=gpmi-nand:1024k(fcb)ro,1024k(bbt),1024k(bootenv),1536k(boo
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] allocated 524288 bytes of page_cgroup
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Memory: 256MB = 256MB total
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000] Memory: 255276k/255276k available, 6868k reserved, 0K highmem
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000] Virtual kernel memory layout:
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]       .text : 0xc0008000 - 0xc037d000   (3540 kB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]       .init : 0xc037d000 - 0xc039a000   ( 116 kB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]       .data : 0xc039a000 - 0xc03c4a20   ( 171 kB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.000000]        .bss : 0xc03c4a44 - 0xc03f77dc   ( 204 kB)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] NR_IRQS:304
Dec  8 12:46:10 homematic-ccu2 user.err kernel: [    0.000000] saif0_clk_set_rate: clock is gated
Dec  8 12:46:10 homematic-ccu2 user.err kernel: [    0.000000] saif1_clk_set_rate: clock is gated
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Console: colour dummy device 80x30
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.000000] Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] pid_max: default: 32768 minimum: 301
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Mount-cache hash table entries: 512
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Initializing cgroup subsys cpuacct
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Initializing cgroup subsys memory
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Initializing cgroup subsys devices
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Initializing cgroup subsys freezer
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] CPU: Testing write buffer coherency: ok
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] Setting up static identity map for 0x402b1198 - 0x402b11f0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.080000] devtmpfs: initialized
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] dummy: 
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] NET: Registered protocol family 16
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] gpiochip_add: registered GPIOs 0 to 31 on device: gpio-mxs.0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] gpiochip_add: registered GPIOs 32 to 63 on device: gpio-mxs.1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] gpiochip_add: registered GPIOs 64 to 95 on device: gpio-mxs.2
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] gpiochip_add: registered GPIOs 96 to 127 on device: gpio-mxs.3
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.090000] gpiochip_add: registered GPIOs 128 to 159 on device: gpio-mxs.4
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.100000] Serial: AMBA PL011 UART driver
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.100000] duart: ttyAMA0 at MMIO 0x80074000 (irq = 47) is a PL011 rev2
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.110000] console [ttyAMA0] enabled
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.110000] mxs-usbphy mxs-usbphy.0: initialized usb phy
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.120000] mxs-usbphy mxs-usbphy.1: initialized usb phy
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.130000] bio: create slab <bio-0> at 0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.140000] mxs-dma mxs-dma-apbh: initialized
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.150000] mxs-dma mxs-dma-apbx: initialized
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.150000] REG-3V3: 3300 mV normal 
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.160000] REG-1V8: 1800 mV normal 
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.160000] USB 5V: 5000 mV normal 
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.160000] VDDIO-SD: 3300 mV normal 
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.170000] Switching to clocksource mxs_timer
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.210000] NET: Registered protocol family 2
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.210000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.220000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.230000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.230000] TCP: Hash tables configured (established 8192 bind 8192)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.240000] TCP: reno registered
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.240000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.250000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.260000] NET: Registered protocol family 1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.260000] RPC: Registered named UNIX socket transport module.
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.270000] RPC: Registered udp transport module.
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.270000] RPC: Registered tcp transport module.
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.280000] RPC: Registered tcp NFSv4.1 backchannel transport module.
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.290000] audit: initializing netlink socket (disabled)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.290000] type=2000 audit(0.290:1): initialized
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.500000] fuse init (API version 7.18)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.510000] msgmni has been set to 498
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.510000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.520000] io scheduler noop registered (default)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.530000] uart-pl011 duart: no DMA platform data
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.530000] mxs-auart.1: ttyAPP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.540000] mxs-auart mxs-auart.1: Found APPUART 3.1.0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.550000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    0.560000] Scanning device for bad blocks
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.560000] Bad eraseblock 16 at 0x000000200000
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.650000] Bad eraseblock 425 at 0x000003520000
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.860000] Bad eraseblock 1463 at 0x00000b6e0000
Dec  8 12:46:10 homematic-ccu2 user.warn kernel: [    0.960000] Bad eraseblock 1916 at 0x00000ef80000
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.990000] 8 cmdlinepart partitions found on MTD device gpmi-nand
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    0.990000] Creating 8 MTD partitions on "gpmi-nand":
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.000000] 0x000000000000-0x000000100000 : "fcb"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.010000] 0x000000100000-0x000000200000 : "bbt"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.010000] 0x000000200000-0x000000300000 : "bootenv"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.020000] 0x000000300000-0x000000480000 : "bootstream0"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.030000] 0x000000480000-0x000000a80000 : "bootstream1"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.040000] 0x000000a80000-0x000000e80000 : "kernel"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.050000] 0x000000e80000-0x000003e80000 : "user"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.060000] 0x000003e80000-0x000010000000 : "root"
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    1.060000] GPMI NAND driver registered. (IMX)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.070000] UBI: attaching mtd7 to ubi0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.070000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.080000] UBI: logical eraseblock size:    126976 bytes
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.090000] UBI: smallest flash I/O unit:    2048
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.090000] UBI: VID header offset:          2048 (aligned 2048)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    1.100000] UBI: data offset:                4096
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.800000] UBI: max. sequence number:       22
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.820000] UBI: attached mtd7 to ubi0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.830000] UBI: MTD device name:            "root"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.830000] UBI: MTD device size:            193 MiB
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.840000] UBI: number of good PEBs:        1546
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.840000] UBI: number of bad PEBs:         2
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.850000] UBI: number of corrupted PEBs:   0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.850000] UBI: max. allowed volumes:       128
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.860000] UBI: wear-leveling threshold:    4096
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.860000] UBI: number of internal volumes: 1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.870000] UBI: number of user volumes:     1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.870000] UBI: available PEBs:             0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.870000] UBI: total number of reserved PEBs: 1546
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.880000] UBI: number of PEBs reserved for bad PEB handling: 15
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.890000] UBI: max/mean erase counter: 143/30
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.890000] UBI: image sequence number:  296898662
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.890000] UBI: background thread "ubi_bgt0d" started, PID 32
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.900000] UBI: attaching mtd6 to ubi1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.900000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.910000] UBI: logical eraseblock size:    126976 bytes
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.920000] UBI: smallest flash I/O unit:    2048
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.920000] UBI: VID header offset:          2048 (aligned 2048)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    2.930000] UBI: data offset:                4096
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.350000] UBI: max. sequence number:       2
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.370000] UBI: attached mtd6 to ubi1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.370000] UBI: MTD device name:            "user"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.380000] UBI: MTD device size:            48 MiB
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.380000] UBI: number of good PEBs:        383
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.390000] UBI: number of bad PEBs:         1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.390000] UBI: number of corrupted PEBs:   0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.400000] UBI: max. allowed volumes:       128
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.400000] UBI: wear-leveling threshold:    4096
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.410000] UBI: number of internal volumes: 1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.410000] UBI: number of user volumes:     1
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.420000] UBI: available PEBs:             0
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.420000] UBI: total number of reserved PEBs: 383
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.430000] UBI: number of PEBs reserved for bad PEB handling: 3
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.430000] UBI: max/mean erase counter: 185/162
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.440000] UBI: image sequence number:  942934859
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.440000] UBI: background thread "ubi_bgt1d" started, PID 33
Dec  8 12:46:10 homematic-ccu2 user.err kernel: [    3.450000] UBI error: ubi_init: cannot attach mtd7
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.480000] fec_enet_mii_bus: probed
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.490000] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.500000] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.510000] stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.520000] watchdog watchdog0: watchdog initialized, 115 seconds remaining
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.530000] cpuidle: using governor ladder
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.530000] cpuidle: using governor menu
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    3.540000] Registered led device: power
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    3.540000] Registered led device: internet
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    3.540000] Registered led device: info
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.540000] NET: Registered protocol family 17
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.550000] registered taskstats version 1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.550000] rtc-rs5c372 0-0032: setting system clock to 2017-12-08 11:46:07 UTC (1512733567)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.680000] UBIFS: mounted UBI device 0, volume 0, name "root"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.690000] UBIFS: mounted read-only
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.690000] UBIFS: file system size:   192495616 bytes (187984 KiB, 183 MiB, 1516 LEBs)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.700000] UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.710000] UBIFS: media format:       w4/r0 (latest is w4/r0)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.710000] UBIFS: default compressor: lzo
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    3.720000] UBIFS: reserved for root:  0 bytes (0 KiB)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.730000] VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.740000] devtmpfs: mounted
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    3.740000] Freeing init memory: 116K
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.190000] UBIFS: default file-system created
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.300000] UBIFS: mounted UBI device 1, volume 0, name "user"
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.300000] UBIFS: file system size:   46600192 bytes (45508 KiB, 44 MiB, 367 LEBs)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.310000] UBIFS: journal size:       2285568 bytes (2232 KiB, 2 MiB, 18 LEBs)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.320000] UBIFS: media format:       w4/r0 (latest is w4/r0)
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.330000] UBIFS: default compressor: lzo
Dec  8 12:46:10 homematic-ccu2 user.notice kernel: [    4.330000] UBIFS: reserved for root:  2201041 bytes (2149 KiB)
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.040000] eq3spi eq3spi.0: master is unqueued, this is deprecated
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.110000] input: gpio-keys as /devices/platform/gpio-keys/input/input0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.160000] Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    5.170000] mxs-usbphy mxs-usbphy.0: enabling gadget mode
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.240000] usb0: MAC 00:1a:22:00:05:87
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.250000] usb0: HOST MAC 00:1a:22:00:05:86
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.260000] g_multi gadget: Mass Storage Function, version: 2009/09/11
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.260000] g_multi gadget: Number of LUNs=1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.270000]  lun0: LUN: read only CD-ROM file: /usr/share/eq3/install.iso
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.280000] g_multi gadget: Multifunction Composite Gadget
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.280000] g_multi gadget: g_multi ready
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.290000] fsl-usb2-udc: bind to driver g_multi
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.320000] tun: Universal TUN/TAP device driver, 1.6
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.320000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.400000] usbcore: registered new interface driver usbfs
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.410000] usbcore: registered new interface driver hub
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.410000] usbcore: registered new device driver usb
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.440000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.450000] mxs-ehci mxs-ehci.1: initializing i.MX USB Controller
Dec  8 12:46:10 homematic-ccu2 user.debug kernel: [    5.460000] mxs-usbphy mxs-usbphy.1: enabling host mode
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.480000] mxs-ehci mxs-ehci.1: using regulator to control VBUS
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.480000] mxs-ehci mxs-ehci.1: Freescale On-Chip EHCI Host Controller
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.490000] mxs-ehci mxs-ehci.1: new USB bus registered, assigned bus number 1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.530000] mxs-ehci mxs-ehci.1: irq 92, io mem 0x80090000
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.550000] mxs-ehci mxs-ehci.1: USB 2.0 started, EHCI 1.00
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.550000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.560000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.570000] usb usb1: Product: Freescale On-Chip EHCI Host Controller
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.570000] usb usb1: Manufacturer: Linux 3.4.11.ccu2 ehci_hcd
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.580000] usb usb1: SerialNumber: mxs-ehci.1
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.580000] hub 1-0:1.0: USB hub found
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.590000] hub 1-0:1.0: 1 port detected
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    5.620000] mxs-raw-auart mxs-raw-auart.0: Found raw APPUART 3.1.0
Dec  8 12:46:10 homematic-ccu2 user.info kernel: [    6.220000] ip_tables: (C) 2000-2006 Netfilter Core Team
Dec  8 12:46:10 homematic-ccu2 user.err kernel: 0>[    6.960000] udevd[125]: starting version 182
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'dialout' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'kmem' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'video' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'lp' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'floppy' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'cdrom' unknown
Dec  8 11:46:11 homematic-ccu2 daemon.err udevd[125]: specified group 'tape' unknown
Dec  8 12:46:12 homematic-ccu2 user.info kernel: [    8.230000] mxs-mmc mxs-mmc.0: using regulator to control VDDIO-SD
Dec  8 12:46:12 homematic-ccu2 user.info kernel: [    8.310000] mxs-mmc mxs-mmc.0: initialized
Dec  8 12:46:12 homematic-ccu2 daemon.info udhcpd[150]: udhcpd (v1.20.2) started
Dec  8 12:46:12 homematic-ccu2 daemon.err udhcpd[150]: can't open '/var/lib/misc/udhcpd.leases': No such file or directory
Dec  8 12:46:13 homematic-ccu2 user.info kernel: [    9.470000] eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=imx28-fec-1:00, irq=185)
Dec  8 12:46:15 homematic-ccu2 user.info kernel: [   11.470000] PHY: imx28-fec-1:00 - Link is Up - 100/Full
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: ifplugd 0.28 initializing.
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: Using interface eth0/00:1A:22:04:91:4F with driver <fec> (version: Revision: 1.0)
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: Using detection mode: SIOCETHTOOL
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: Initialization complete, link beat detected.
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Dec  8 11:47:41 homematic-ccu2 daemon.warn ifplugd(eth0)[264]: client: ifup: interface eth0 already configured
Dec  8 11:47:41 homematic-ccu2 daemon.info ifplugd(eth0)[264]: Program executed successfully.
Dec  8 12:48:21 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec  8 12:48:42 homematic-ccu2 user.debug setclock: Try to get time from 192.168.50.1
Dec  8 12:48:42 homematic-ccu2 user.debug setclock: Fri Dec 8 12:48:42 CET 2017
Dec  8 11:48:48 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Dec  8 11:48:49 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Dec  8 11:48:49 homematic-ccu2 user.debug update-coprocessor: No updatable gateways found in rfd.conf file.
Dec  8 11:48:49 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Dec  8 11:48:49 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Dec  8 11:48:49 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Dec  8 11:48:49 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Dec  8 12:48:54 homematic-ccu2 user.info update-coprocessor: Version: 2.8.5
Dec  8 12:48:54 homematic-ccu2 user.info update-coprocessor: No update necessary
Dec  8 12:48:55 homematic-ccu2 user.info kernel: [  171.910000] eq3loop: created slave ttyS0
Dec  8 12:48:55 homematic-ccu2 user.info kernel: [  171.920000] eq3loop: created slave mmd_bidcos
Dec  8 12:48:58 homematic-ccu2 user.info kernel: [  174.260000] eq3loop: eq3loop_open_slave() mmd_bidcos
Dec  8 12:49:42 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec  8 12:50:02 homematic-ccu2 user.debug setclock: Try to get time from 192.168.50.1
Dec  8 12:50:02 homematic-ccu2 user.debug setclock: Fri Dec 8 12:50:02 CET 2017
Dec  8 12:50:37 homematic-ccu2 user.info kernel: [  273.420000] eq3loop: eq3loop_open_slave() ttyS0
Dec  8 12:50:37 homematic-ccu2 user.info kernel: [  273.430000] eq3loop: eq3loop_close_slave() ttyS0
Dec  8 12:50:37 homematic-ccu2 user.info kernel: [  273.650000] eq3loop: eq3loop_open_slave() ttyS0
Dec  8 12:50:37 homematic-ccu2 user.info kernel: [  273.670000] eq3loop: eq3loop_close_slave() ttyS0
Dec  8 12:50:37 homematic-ccu2 user.info kernel: [  274.020000] eq3loop: eq3loop_open_slave() ttyS0
Dec  8 12:50:38 homematic-ccu2 user.notice kernel: [  274.060000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Dec  8 12:50:38 homematic-ccu2 user.notice kernel: [  274.070000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Dec  8 12:51:02 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec  8 12:51:22 homematic-ccu2 user.debug setclock: Try to get time from 192.168.50.1
Dec  8 12:51:23 homematic-ccu2 user.debug setclock: Fri Dec 8 12:51:23 CET 2017
Dec  8 12:51:58 homematic-ccu2 user.info : hss_lcd: Programm initialisiert.
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseDOM::LoadOM: original file not exists, so try load new file. [iseDOM.cpp:2608]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseDOM::LoadOM: new file not exists, so try load bak file. [iseDOM.cpp:2620]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IsePersist::LoadFromFile-> failed open file= /etc/config/homematic.regadom.bak [iseDOMpersist.cpp:78]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseObjectMap::Insert(202) failed! Already in map! [iseDOMobj.cpp:462]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseAddFavorite failed! ID=202 [iseDOM.cpp:644]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseObjectMap::Insert(203) failed! Already in map! [iseDOMobj.cpp:462]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseAddFavorite failed! ID=203 [iseDOM.cpp:644]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseObjectMap::Insert(204) failed! Already in map! [iseDOMobj.cpp:462]
Dec  8 12:51:58 homematic-ccu2 local0.err ReGaHss: Error: IseAddFavorite failed! ID=204 [iseDOM.cpp:644]
Dec  8 12:52:12 homematic-ccu2 user.info homematic: meine-homematic.de Versions - Upgrade auf 1.503
Dec  8 12:52:13 homematic-ccu2 user.info homematic: meine-homematic.de VPN Dienst und Autoupdate DEAKTIVIERT
Dec  8 11:52:13 homematic-ccu2 daemon.info init: starting pid 643, tty '/dev/ttyAMA0': '/sbin/getty -L ttyAMA0 115200 vt100 '
Dec  8 11:52:13 homematic-ccu2 daemon.info init: starting pid 644, tty '/dev/ttyGS0': '/sbin/getty -L ttyGS0 115200 vt100 '
Dec  8 12:52:23 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec  8 12:52:31 homematic-ccu2 user.err : node is empty
Dec  8 12:52:43 homematic-ccu2 user.debug setclock: Try to get time from 192.168.50.1
Dec  8 12:52:43 homematic-ccu2 user.debug setclock: Fri Dec 8 12:52:43 CET 2017

Und schließe mal auf deinem Rechner alle Programme, die du nicht benötigst und schalte eventuelle externe LogServer ab....

Grüße
Tom

[onkeltommy]

Vl auch sicherstellen, dass kein anderes Device bei Dir die selbe IP wie die CCU hat.
Sowas macht Mega Probleme

[123ccu]

Vielen Dank Tom,
zunächst

1. Hast du den Browsercache geleert, dann den Browser geschlossen und dann neu gestartet?
2. Hast du ein Tab oder Handy oder irgendwas, was von aussen per APP auf die CCU zu greift?

1.Ja und 2.Ja. Aber die Apps waren alle geschlossen und laufen nicht im Hintergrund. Werde dennoch mal ausschalten. (Wer wird schon gerne angerufen )

Das Log hat mir sehr geholfen, wenn auch nicht das Problem gelöst.
Unsere Logs sind fast identisch.
Der grosse Unterschied ist jedoch, dass gegen Ende meines Logs folgende Einträge sich wiederholend auftauchen:

Code: Alles auswählen

Dec  5 21:05:56 homematic-ccu2 user.err rfd: XmlRpc transport error calling [b]system.listMethods({"BidCos-RF"}) on binary://172.27.84.241:2099[/b]/RPC2:
Dec  5 21:06:59 homematic-ccu2 user.err rfd: XmlRpc transport error calling [b]listDevices({"BidCos-RF"}) on binary://172.27.84.241:2099[/b]/RPC2:

In Deinem Log sind keine vergleichbaren Einträge.

So wie ich das verstehe versucht meine CCU einen host mit IP 172.27.84.241 auf port 2099 zu erreichen, kann dies aber nicht.
Meine eigene interne IP range is 192.168.1.x.
Da diese Einträge bei Dir nicht vorkommen - und ich bei meiner CCU2 einen "Hard Reset (Knopf drücken)" und auch ein Zurückstellen auf Factory-Settings gemacht habe, kann es nichts werksseitiges sein.
Vermutungen:
a. Irgendwas scheint von aussen auf meine CCU zuzugreifen und sich als RPC-Partner anzubieten.
b. meine erste CCU wurde gehackt und der hack durch restore auf die neue übertragen, wo er sich resistent selbst bei reset hält. Dies scheint mir jedoch ziemlich unwahrscheinlich.

Für jede weitere Vermutung wäre ich dankbar.

@onkeltommy:

Vl auch sicherstellen, dass kein anderes Device bei Dir die selbe IP wie die CCU hat.
Sowas macht Mega Probleme

Da hast Du sehr recht. Bei dem Versuch die CCU direkt mit meinem Computer in einem kleinen Test-Netwerk zu testen, habe ich einen alten Router als Switch verwendet. Als ich später wieder mit WIFI auf mein Home-Netz zugegriffen habe, waren plötzlich alle LAN Geräte nicht mehr erreichbar. War eh alles umsonst, da ich es nicht geschafft habe in meinem Testnetzwerk irgendeine Verbindung zur CCU herzustellen (trotz spezieller Win10 driver und Setup.exe, und und und...).

Grüsse
Kai

[anli]

Wie sieht denn Deine /var/RFD.handlers aus? Die Ausgabe von

Code: Alles auswählen

ifconfig eth0

direkt per SSH auf der CCU2 aufgerufen wäre auch interessant.