rfd startet, funktioniert aber nicht (hmconfig hängt mit "lade Daten") und fällt immer nach ~ 1 Minute wieder aus.
Auch beim Start im Vordergrund gibt es reproduzierbar dieses Ausgabe:
root@raspberrypi:~# sudo -u hmcon /opt/hmcon/bin/rfd -c -f /opt/hmcon/etc/rfd.conf
2017/01/28 09:57:08.317 BidCoS-Service started
2017/01/28 09:57:08.318 XmlRpc Server is listening on TCP port 2001
2017/01/28 09:57:08.320 Default interface is now GEQ0208083
2017/01/28 09:57:08.320 Current AES key=0, previous AES key=0
2017/01/28 09:57:10.452 Connected to Lan Interface GEQ0208083 at 10.10.10.48
2017/01/28 09:57:10.452 Event: GEQ0208083.CONNECTED=true
2017/01/28 09:57:18.467 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,00013506,0000,00
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
root@raspberrypi:~#
Konfiguration:
root@raspberrypi:/opt/hmcon/etc# cat rfd.conf
Listen Port = 2001
Log Destination = File
Log Filename = /opt/hmcon/var/log/rfd.log
Log Identifier = rfd
Log Level = 1
Persist Keys = 1
Device Description Dir = /opt/hmcon/firmware/rftypes
Device Files Dir = /opt/hmcon/var/rfd/devices
Key File = /opt/hmcon/var/rfd/keys
Address File = /opt/hmcon/etc/rfd/ids
Firmware Dir = /opt/hmcon/firmware
User Firmware Dir = /opt/hmcon/var/firmware
XmlRpcHandlersFile = /opt/hmcon/var/RFD.handlers
Replacemap File = /opt/hmcon/firmware/rftypes/replaceMap/rfReplaceMap.xml
[Interface 0]
Type = Lan Interface
Serial Number = GEQ0208083
Encryption Key =
root@raspberrypi:/opt/hmcon/etc#
!!!!!!! NACHTRAG: rfd alloziert in der Tat ~670MB (!) Speicher und crashed dann, der core-Dump ist 670MB groß ... bad.alloc ist also richtig.
Aber - warum verbraucht der Prozess soviel Speicher?
hmcon auf RPI3/Jessie mit HM-CFG-LAN f/w 0.965,
rfd startet, funktioniert aber nicht (hmconfig hängt mit "lade Daten") und fällt immer nach ~ 1 Minute wieder aus. Auch beim Start im Vordergrund gibt es reproduzierbar dieses Ausgabe:
root@raspberrypi:~# sudo -u hmcon /opt/hmcon/bin/rfd -c -f /opt/hmcon/etc/rfd.conf 2017/01/28 09:57:08.317 BidCoS-Service started
2017/01/28 09:57:08.318 XmlRpc Server is listening on TCP port 2001
2017/01/28 09:57:08.320 Default interface is now GEQ0208083
2017/01/28 09:57:08.320 Current AES key=0, previous AES key=0
2017/01/28 09:57:10.452 Connected to Lan Interface GEQ0208083 at 10.10.10.48
2017/01/28 09:57:10.452 Event: GEQ0208083.CONNECTED=true
2017/01/28 09:57:18.467 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,00013506,0000,00
2017/01/28 09:57:28.583 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,00015C8B,0000,00
2017/01/28 09:57:39.270 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,0001864C,0000,00
2017/01/28 09:57:49.805 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,0001AF74,0000,00
2017/01/28 09:58:00.589 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,0001D996,0000,00
2017/01/28 09:58:11.031 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,00020261,0000,00
2017/01/28 09:58:21.199 GEQ0208083 RX: HHM-LAN-IF,03C5,GEQ0208083,12FD7D,12FD7D,00022A1A,0000,00
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc root@raspberrypi:~#
Konfiguration:
root@raspberrypi:/opt/hmcon/etc# cat rfd.conf Listen Port = 2001 Log Destination = File Log Filename = /opt/hmcon/var/log/rfd.log Log Identifier = rfd Log Level = 1 Persist Keys = 1 Device Description Dir = /opt/hmcon/firmware/rftypes Device Files Dir = /opt/hmcon/var/rfd/devices Key File = /opt/hmcon/var/rfd/keys Address File = /opt/hmcon/etc/rfd/ids Firmware Dir = /opt/hmcon/firmware User Firmware Dir = /opt/hmcon/var/firmware XmlRpcHandlersFile = /opt/hmcon/var/RFD.handlers Replacemap File = /opt/hmcon/firmware/rftypes/replaceMap/rfReplaceMap.xml [Interface 0] Type = Lan Interface Serial Number = GEQ0208083 Encryption Key =
root@raspberrypi:/opt/hmcon/etc#
!!!!!!! NACHTRAG: rfd alloziert in der Tat ~670MB (!) Speicher und crashed dann, der core-Dump ist 670MB groß ... bad.alloc ist also richtig. Aber - warum verbraucht der Prozess soviel Speicher?