IP Geräte werden nicht gefunden

Einrichtung, Nutzung und Hilfe zu YAHM

Moderator: Co-Administratoren

tenorb
Beiträge: 25
Registriert: 09.02.2017, 07:50
Hat sich bedankt: 1 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von tenorb » 12.12.2017, 14:07

Hi,

ja, ich hatte eine frische Installation genommen und dann das Backup eingespielt.
Die Installation des pivccu-drives hatte ich schon erneut durchgeführt - keine Änderung.

Hier die beiden Ausgaben:

Code: Alles auswählen

# ls -al /dev
total 24
drwxr-xr-x    6 root     root          4096 Dec 12 08:39 .
drwxr-xr-x   20 root     root          4096 Dec 12 08:38 ..
drwxr-xr-x    2 root     root          4096 Dec 11 21:44 char
c--x--x--x    1 root     tty       136,   0 Dec 12 08:39 console
crw-------    1 root     root      245,   0 Dec 12 08:39 eq3loop
lrwxrwxrwx    1 root     root            13 Dec 12 08:39 fd -> /proc/self/fd
-rw-r--r--    1 root     root            36 Dec 12 08:39 kmsg
lrwxrwxrwx    1 root     root            10 Dec 10 18:47 log -> ../tmp/log
crw-------    1 root     root      245,   2 Dec 12 08:39 mmd_bidcos
crw-rw-rw-    1 root     root      243,   0 Dec 12 08:38 mxs_auart_raw.0
drwxr-xr-x    2 root     root          4096 Dec 10 18:49 net
crw-rw-rw-    1 root     root        1,   3 Dec 12 08:39 null
lrwxrwxrwx    1 root     root            13 Dec 10 18:47 ptmx -> /dev/pts/ptmx
drwxr-xr-x    2 root     root             0 Dec 12 08:38 pts
crw-rw-rw-    1 root     root        1,   8 Dec 12 08:39 random
drwxr-xr-x    2 root     root          4096 Dec 10 18:47 shm
lrwxrwxrwx    1 root     root            15 Dec 12 08:39 stderr -> /proc/self/fd                                                  /2
lrwxrwxrwx    1 root     root            15 Dec 12 08:39 stdin -> /proc/self/fd/                                                  0
lrwxrwxrwx    1 root     root            15 Dec 12 08:39 stdout -> /proc/self/fd                                                  /1
crw-rw-rw-    1 root     tty         5,   0 Dec 12 08:39 tty
crw--w----    1 root     tty         4,   0 Dec 12 08:39 tty0
crw--w----    1 root     root      136,   0 Dec 12 08:39 tty1
crw-------    1 root     root      245,   1 Dec 12 08:39 ttyS0
crw-rw-rw-    1 root     root        1,   9 Dec 12 08:39 urandom
crw-rw-rw-    1 root     root        1,   5 Dec 12 08:39 zero

Code: Alles auswählen

# ps aux
PID   USER     COMMAND
    1 root     init
   85 root     /usr/sbin/crond
   89 root     /sbin/syslogd -m 0
   91 root     /sbin/klogd
   94 root     /lib/udev/udevd -d
  178 root     /lib/udev/udevd -d
  179 root     /lib/udev/udevd -d
  231 root     /usr/sbin/ifplugd -i eth0 -fI -u0 -d10
  275 root     /bin/eq3configd
  291 root     /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
  294 root     /usr/sbin/sshd
  312 root     /usr/local/addons/cuxd/cuxd
  341 root     udhcpc -x hostname Homematic-ccu -V eQ3-CCU2 -b -s /bin/dhcp.script
  371 root     /bin/hs485dLoader -l 5 -dw /etc/config/hs485d.conf
  373 root     /bin/hs485d -l 5 -g -i 0
  393 root     /bin/multimacd -f /etc/config/multimacd.conf -l 5
  411 root     java -Xmx32m -Dlog4j.configuration=file:///etc/config/log4j.xml -Dfile.encoding=ISO-8859-1 -jar /opt/HMServer/HMSe
  454 root     /bin/rfd -f /etc/config/rfd.conf -l 5
  474 root     /bin/ReGaHss.normal -f /etc/rega.conf -l 2
  505 root     /sbin/getty -L tty1 115200 linux
  567 root     ntpclient -h ntp.homematic.com -l
  886 root     [ReGaHss.normal]
 1117 root     [ReGaHss.normal]
 1175 root     {sshd} sshd: root@pts/1
 1177 root     -sh
 1183 root     ps aux
#

leonsio
Beiträge: 1107
Registriert: 07.01.2012, 14:06
Danksagung erhalten: 6 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von leonsio » 12.12.2017, 21:36

von den Geräten sieht alles gut aus

schau mal ob deine /etc/crRDF.conf ähnlich aussieht. bzw. poste diese hier

Code: Alles auswählen

cat /etc/crRFD.conf 
# USB HM/IP TRX Adapter Configuration
Adapter.1.Type=HMIP_CCU2
Adapter.1.Port=/dev/ttyS0

Config.Dir=/etc/config/crRFD
Config.Include=hmip_user.conf

# Directory Configuration
Persistence.Home=/etc/config/crRFD/data
FirmwareUpdate.BG.OTAU.Home=/etc/config/firmware

# Legacy API Configuration
API.1.Type=XML-RPC
Legacy.Encoding=ISO-8859-1
Legacy.ResponseTimeout=20
Legacy.ReplacementURL=127.0.0.1
Legacy.Parameter.Definition.File=/opt/HmIP/legacy-parameter-definition.config
# Legacy.RemoveUnreachableClients=false
Legacy.AddressPrefix=3014F711A0
Legacy.SwitchTypeAndSubtype=true
Legacy.HandlersFilename=/var/LegacyService.handlers
Legacy.DiscardDutyCycleEvents=true
Legacy.SendUDPServiceMessages=true

# Miscellaneous Configuration
CyclicTimeout.TimerStartMaxDelay=90
CyclicTimeout.TimerCycleTime=600
Legacy.Parameter.ReplaceEnumValueWithOrdinal=true

### Configuration for Inclusion with key server (internet) or local key (offline)
KeyServer.Mode=KEYSERVER_LOCAL
KeyServer.Gateway.URL=secgtw.homematic.com


tenorb
Beiträge: 25
Registriert: 09.02.2017, 07:50
Hat sich bedankt: 1 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von tenorb » 12.12.2017, 22:41

Schon mal danke für deine Hilfe!

Die Datei scheint gleich zu sein:

Code: Alles auswählen

# cat /etc/crRFD.conf
# USB HM/IP TRX Adapter Configuration
Adapter.1.Type=HMIP_CCU2
Adapter.1.Port=/dev/ttyS0

Config.Dir=/etc/config/crRFD
Config.Include=hmip_user.conf

# Directory Configuration
Persistence.Home=/etc/config/crRFD/data
FirmwareUpdate.BG.OTAU.Home=/etc/config/firmware

# Legacy API Configuration
API.1.Type=XML-RPC
Legacy.Encoding=ISO-8859-1
Legacy.ResponseTimeout=20
Legacy.ReplacementURL=127.0.0.1
Legacy.Parameter.Definition.File=/opt/HmIP/legacy-parameter-definition.config
# Legacy.RemoveUnreachableClients=false
Legacy.AddressPrefix=3014F711A0
Legacy.SwitchTypeAndSubtype=true
Legacy.HandlersFilename=/var/LegacyService.handlers
Legacy.DiscardDutyCycleEvents=true
Legacy.SendUDPServiceMessages=true

# Miscellaneous Configuration
CyclicTimeout.TimerStartMaxDelay=90
CyclicTimeout.TimerCycleTime=600
Legacy.Parameter.ReplaceEnumValueWithOrdinal=true

### Configuration for Inclusion with key server (internet) or local key (offline)
KeyServer.Mode=KEYSERVER_LOCAL
KeyServer.Gateway.URL=secgtw.homematic.com

leonsio
Beiträge: 1107
Registriert: 07.01.2012, 14:06
Danksagung erhalten: 6 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von leonsio » 14.12.2017, 11:31

hmm sorry da bin ich mit meinem Latein am ende
eigentlich müsste es laufen :(

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: IP Geräte werden nicht gefunden

Beitrag von deimos » 14.12.2017, 15:53

Hi,

ich hätte noch eine Idee: Wie sieht deine /etc/config/InterfacesList.xml aus?

Viele Grüße
Alex

tenorb
Beiträge: 25
Registriert: 09.02.2017, 07:50
Hat sich bedankt: 1 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von tenorb » 14.12.2017, 21:16

So sieht sie aus:

Code: Alles auswählen

# cat /etc/config/InterfacesList.xml
<?xml version="1.0" encoding="utf-8" ?>
<interfaces v="1.0">
        <ipc>
                <name>BidCos-RF</name>
                <url>xmlrpc_bin://127.0.0.1:2001</url>
                <info>BidCos-RF</info>
        </ipc>
        <ipc>
                <name>VirtualDevices</name>
                <url>xmlrpc://127.0.0.1:9292/groups</url>
                <info>Virtual Devices</info>
        </ipc>
        <ipc>
                <name>BidCos-Wired</name>
                <url>xmlrpc_bin://127.0.0.1:2000</url>
                <info>BidCoS-Wired</info>
        </ipc>
        <ipc>
                <name>CUxD</name>
                <url>xmlrpc_bin://127.0.0.1:8701</url>
                <info>CUxD</info>
        </ipc>
</interfaces>
#

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: IP Geräte werden nicht gefunden

Beitrag von deimos » 14.12.2017, 21:30

Dann haben wir da schonmal ein Problem gefunden. Da fehlt der Block für HmIP:

Code: Alles auswählen

        <ipc>
                <name>HmIP-RF</name>
                <url>xmlrpc://127.0.0.1:2010</url>
                <info>HmIP-RF</info>
        </ipc>
Füg den mal ein, mach einen Neustart und schau, wie es dann aussieht.

Viele Grüße
Alex

tenorb
Beiträge: 25
Registriert: 09.02.2017, 07:50
Hat sich bedankt: 1 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von tenorb » 14.12.2017, 21:46

Habe ich gemacht. Nun bekomme ich jedoch im Webinterface die Meldung:

Code: Alles auswählen

HmIP-RF
Eine Komponente der HomeMatic Zentrale reagiert nicht mehr.

Hierfür kann es eine Reihe von Ursachen geben:

    es besteht keine Netzwerk-Verbindung
    die Stromversorung der HomeMatic Zentrale wurde unterbrochen
    mindestens eine Komponente der HomeMatic Zentrale ist abgestürzt

Überprüfen Sie die Netzwerk-Verbindung und die Stromversorgung der HomeMatic Zentrale. Starten Sie ggf. die HomeMatic Zentrale neu.

Benutzeravatar
deimos
Beiträge: 5396
Registriert: 20.06.2017, 10:38
System: Alternative CCU (auf Basis OCCU)
Wohnort: Leimersheim
Hat sich bedankt: 121 Mal
Danksagung erhalten: 957 Mal
Kontaktdaten:

Re: IP Geräte werden nicht gefunden

Beitrag von deimos » 14.12.2017, 21:51

Dann poste mal bitte deine /var/log/messages und die /var/log/hmserver.log

Beides ca. 1 Minute nach dem Start.

Viele Grüße
Alex

tenorb
Beiträge: 25
Registriert: 09.02.2017, 07:50
Hat sich bedankt: 1 Mal

Re: IP Geräte werden nicht gefunden

Beitrag von tenorb » 14.12.2017, 21:58

Hier die Logs:

Code: Alles auswählen

# cat /var/log/messages
Dec 14 21:53:39 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Dec 14 21:53:39 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2017-10-11 14:29:35 CEST)
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'dialout' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'kmem' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'video' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'lp' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'floppy' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'cdrom' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[98]: specified group 'tape' unknown
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[100]: inotify_add_watch(6, /dev/mmcblk0, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/mmcblk0p2, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[100]: inotify_add_watch(6, /dev/mmcblk0p1, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/loop0, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/loop1, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[116]: inotify_add_watch(6, /dev/ram12, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[105]: inotify_add_watch(6, /dev/loop2, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram14, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram15, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[100]: inotify_add_watch(6, /dev/ram13, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram2, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram4, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram5, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[100]: inotify_add_watch(6, /dev/ram3, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[105]: inotify_add_watch(6, /dev/ram8, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[100]: inotify_add_watch(6, /dev/ram7, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[107]: inotify_add_watch(6, /dev/loop3, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[109]: inotify_add_watch(6, /dev/loop5, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[105]: inotify_add_watch(6, /dev/ram9, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[108]: inotify_add_watch(6, /dev/loop4, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[110]: inotify_add_watch(6, /dev/loop6, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[113]: inotify_add_watch(6, /dev/ram1, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[111]: inotify_add_watch(6, /dev/loop7, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[115]: inotify_add_watch(6, /dev/ram11, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[114]: inotify_add_watch(6, /dev/ram10, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[104]: inotify_add_watch(6, /dev/ram6, 10) failed: No such file or directory
Dec 14 20:53:39 homematic-ccu2 daemon.err udevd[112]: inotify_add_watch(6, /dev/ram0, 10) failed: No such file or directory
Dec 14 20:53:40 homematic-ccu2 daemon.info ifplugd(eth0)[200]: ifplugd 0.28 initializing.
Dec 14 20:53:40 homematic-ccu2 daemon.info ifplugd(eth0)[200]: Using interface eth0/4A:49:43:49:79:D2 with driver <veth> (version: 1.0)
Dec 14 20:53:40 homematic-ccu2 daemon.info ifplugd(eth0)[200]: Using detection mode: SIOCETHTOOL
Dec 14 20:53:40 homematic-ccu2 daemon.info ifplugd(eth0)[200]: Initialization complete, link beat detected.
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: Beep failure, disabled.
Dec 14 20:53:40 homematic-ccu2 daemon.info ifplugd(eth0)[200]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: sysctl: error: 'net.ipv4.tcp_timestamps' is an unknown key
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: udhcpc (v1.20.2) started
Dec 14 21:53:40 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec 14 21:53:40 homematic-ccu2 user.debug setclock: Thu Dec 14 21:53:40 CET 2017
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Sending discover...
Dec 14 20:53:40 homematic-ccu2 auth.info sshd[263]: Server listening on 0.0.0.0 port 22.
Dec 14 20:53:40 homematic-ccu2 auth.info sshd[263]: Server listening on :: port 22.
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: write_pid /var/run/cuxd.pid [275]
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: CUx-Daemon(1.11a) on CCU(2.29.23) start PID:275
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:1947 update(-15s):Thu Dec 14 21:53:25 2017
Dec 14 21:53:40 homematic-ccu2 user.info homematic: started cux-daemon
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: write_proxy /var/cache/cuxd_proxy.ini (275 /usr/local/addons/cuxd/ 1.11a 2.29.23 0)
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: add interface 'CUxD'
Dec 14 21:53:40 homematic-ccu2 daemon.info cuxd[275]: write 5 interfaces to /usr/local/etc/config/InterfacesList.xml
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Sending select for 192.168.2.8...
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Lease of 192.168.2.8 obtained, lease time 864000
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: rm: can't remove '/var/etc/resolv.conf': No such file or directory
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: udhcpc (v1.20.2) started
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Sending discover...
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Sending select for 192.168.2.8...
Dec 14 20:53:40 homematic-ccu2 daemon.warn ifplugd(eth0)[200]: client: Lease of 192.168.2.8 obtained, lease time 864000
Dec 14 20:53:41 homematic-ccu2 daemon.info ifplugd(eth0)[200]: Program executed successfully.
Dec 14 20:53:41 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Dec 14 20:53:41 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Dec 14 20:53:41 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Dec 14 20:53:41 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Dec 14 20:53:41 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Dec 14 20:53:41 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update...
Dec 14 20:53:41 homematic-ccu2 user.info update-lgw-firmware: Gateway LEQ0636904
Dec 14 20:53:43 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HMW-LGW-App
Dec 14 20:53:43 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version:   1.0.5
Dec 14 20:53:43 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.0.5
Dec 14 20:53:43 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
Dec 14 20:53:44 homematic-ccu2 auth.info sshd[343]: Did not receive identification string from 192.168.2.4
Dec 14 21:53:53 homematic-ccu2 daemon.warn cuxd[275]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
Dec 14 20:53:54 homematic-ccu2 auth.info sshd[378]: Accepted password for root from 192.168.2.4 port 54769 ssh2
Dec 14 20:54:03 homematic-ccu2 daemon.info init: starting pid 473, tty '/dev/tty1': '/sbin/getty -L tty1 115200 linux'
Dec 14 21:54:04 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Dec 14 21:54:11 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DECISION_VALUE failed getting physical value.
Dec 14 21:54:11 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"MEQ0478501:7","DECISION_VALUE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2641]
Dec 14 21:54:11 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1455]
Dec 14 21:54:11 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Dec 14 21:54:21 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Dec 14 21:54:21 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","6170"} result= nil [iseXmlRpc.cpp:2635]
Dec 14 21:54:21 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1227]
Dec 14 21:54:21 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=HmIP-RF [iseRTHss.cpp:163]
Dec 14 21:54:21 homematic-ccu2 daemon.info cuxd[275]: INIT 'xmlrpc_bin://127.0.0.1:1999' '16110'
Dec 14 21:54:40 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Dec 14 21:54:40 homematic-ccu2 user.debug setclock: Thu Dec 14 21:54:40 CET 2017
#
und

Code: Alles auswählen

# cat /var/log/hmserver.log
Dec 14 21:53:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Dec 14 21:53:50 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor
Dec 14 21:53:50 de.eq3.ccu.server.HMServer INFO  [main] Creating instance of HMServer...
Dec 14 21:53:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [main] SYSTEM: added for deployment [BackendWorker] (1) *worker
Dec 14 21:53:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [main] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker
Dec 14 21:53:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [main] SYSTEM: deploying 2 classes to Vert.x
Dec 14 21:53:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [main] SYSTEM: 2 VertxDeployers initialized
Dec 14 21:53:50 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of BackendWorker succeeded (deployment-5581ade7-c8cf-4cd3-956c-6e2d65712a21)
Dec 14 21:53:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupRequestWorker succeeded (deployment-9b8e8ccc-ac8d-49cc-97a3-6cb07948b58e)
Dec 14 21:53:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [main] SYSTEM: initial deployment complete _____________________________________________________
Dec 14 21:53:51 de.eq3.ccu.server.HMServer INFO  [main] Starting HMServer at 127.0.0.1:9292
Dec 14 21:53:51 de.eq3.ccu.server.HMServer INFO  [main] Read Configuration
Dec 14 21:53:51 de.eq3.ccu.server.HMServer INFO  [main] Create Bidcos Dispatcher
Dec 14 21:53:51 de.eq3.ccu.server.HMServer INFO  [main] InitBidCosCache
Dec 14 21:53:52 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [main] BidCosCache could not be initialized
Dec 14 21:53:52 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [main] org.apache.http.conn.HttpHostConnectException: Connection to http://127.0.0.1:2001 refused
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create groupDefinitionProvider
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create VirtualDeviceHolder
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create VirtualDeviceHandlerRega
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create GroupAdministrationService
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create GroupDeviceDispatcher
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create GroupDeviceHandler
Dec 14 21:53:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [main] @GroupDeviceHandler - initializing...
Dec 14 21:53:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [main] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
Dec 14 21:53:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [main] --> created virtualDeviceHandler (GroupDeviceService to ReGa)
Dec 14 21:53:52 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [main] --> got groupDefinitionProvider
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Create BidCosGroupMemberProvider
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Init groupAdministrationService
Dec 14 21:53:52 de.eq3.ccu.server.HMServer INFO  [main] Init ESHLight Bridge
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Create RrdDatalogging
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Create MeasurementService
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Init MeasurementService
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Create HTTP Server
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Create BidCos context and start handler
Dec 14 21:53:53 de.eq3.ccu.server.HMServer INFO  [main] Create group context and start handler
Dec 14 21:53:53 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-1] Could not register BidCos-RF_java
Dec 14 21:53:53 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:53:54 de.eq3.ccu.server.HMServer INFO  [main] Starting HMServer done
Dec 14 21:53:58 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-1] Could not register BidCos-RF_java
Dec 14 21:53:58 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:03 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:08 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:11 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999
Dec 14 21:54:11 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-1] Added InterfaceId: 1236
Dec 14 21:54:11 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-4] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
Dec 14 21:54:13 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:18 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:23 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:28 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:33 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:38 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:43 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:48 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:53 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:54:58 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:03 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:08 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:13 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:18 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:23 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:28 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:33 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:38 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:43 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:48 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:53 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:55:58 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:56:03 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:56:08 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:56:13 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:56:18 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
Dec 14 21:56:23 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register HmIP-RF_java
#

Antworten

Zurück zu „YAHM“