NEWS
KNX adapter?
-
Also:
-
ETS kann ich komplett ausschließen-> das läuft eigentlich auf einer anderen Maschine welche vom Netzwerk getrennt und heruntergefahren ist.
-
die knxd datei:
# Defaults for knxd initscript # sourced by /etc/init.d/knxd # installed at /etc/default/knxd by the maintainer scripts ######################################################################## # This file is ignored when using systemd: edit /etc/knxd.conf instead # ######################################################################## # start knxd when /etc/init.d/knxd start is run # by default knxd does NOT start. set to YES to enable START_KNXD=YES # Additional options that are passed to the Daemon. # # sane default: route between local KNX clients and multicast DAEMON_ARGS="-u /tmp/eib -u /var/run/knx -i -b ip:192.168.1.106" # Run `knxd --help` to get a complete list of available options and drivers. # If you have KNX hardware on a serial port or USB, add the appropriate # "-b TYPE:…" option. In this case, you probably want to set up a multicast # server, not a client (i.e. use "-D -T -R -S", not "-b ip:"). # DO NOT use both. # # If your KNX hardware is a KNX/IP gateway that doesn't do multicast, # use "-b ipt:192.168.1.2" (or its DNS name) to talk to it. # # KNX MUST NOT have more than one path between any two devices. Thus, # you need to make sure that the KNX/IP gateway does not route multicast # before you use both "-S" and "-b ipt:". # The default bus address of knxd is 0.0.1\. If that's in use in your KNX # network (or if you run more than one knxd on your network), set a # different address (-e 15.0.99).- knxd.conf:
# configuration for knxd.service KNXD_OPTS="-u /tmp/eib -i -DTRS -b ip:192.168.1.106" # The default options are "-u /tmp/eib -b ip:" # which tell knxd to route between all of # /tmp/eib (legacy socket (-u)) # multicast client (-b ip:). # The knxd.socket file also tells knxd to listen to # /run/eib (socket activation via systemd) # TCP port 6720 (socket activation via systemd) # *** DO NOT use "-u" / "-u /run/knx" or "-i" / "-i 6720" here. # Systemd already does that on behalf of knxd, via 'knx.socket'. # If you have KNX hardware on a serial port or USB, add the appropriate # "-b TYPE:…" option. In this case, you probably want to set up a multicast # server, not a client (i.e. use "-D -T -R -S", not "-b ip:"). # DO NOT use both. # # If your KNX hardware is a KNX/IP gateway that doesn't do multicast, # use "-b ipt:192.168.1.2" (or its DNS name) to talk to it. # # KNX MUST NOT have more than one path between any two devices. Thus, # you need to make sure that the KNX/IP gateway does not route multicast # before you use both "-S" and "-b ipt:". # The default bus address of knxd is 0.0.1\. If that's in use in your KNX # network (or if you run more than one knxd on your network), set a # different address (-e 15.0.99). # Run `knxd --help` to get a complete list of available options and drivers. ## DO NOT use the following options: ## -i -- /lib/systemd/system/knxd.socket does this for us ## -u /run/knx -- likewise ## -d -- /lib/systemd/system/knxd.service expects knxd to run in the foreground ############################################################################### # This file is ignored when NOT using systemd: edit /etc/default/knxd instead # ###############################################################################So 4)
Wenn ich knxd neustarte mit
/etc/init.d/knxd restartbekomme ich im Terminal die Fehlermeldung:
root@raspberrypi:~# /etc/init.d/knxd restart [....] Restarting knxd (via systemctl): knxd.serviceJob for knxd.service failed. See 'systemctl status knxd.service' and 'journalctl -xn' for details. failed!Wenn ich dann "systemctl status knxd.service" aufrufe bekomme ich das:
root@raspberrypi:~# systemctl status knxd.service ● knxd.service - KNX Daemon Loaded: loaded (/lib/systemd/system/knxd.service; enabled) Active: activating (auto-restart) (Result: exit-code) since Sa 2016-08-20 12:00:41 CEST; 6s ago Process: 1209 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=1/FAILURE) Main PID: 1209 (code=exited, status=1/FAILURE) Aug 20 12:00:41 raspberrypi systemd[1]: Failed to start KNX Daemon. Aug 20 12:00:41 raspberrypi systemd[1]: Unit knxd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full.So jetzt glaube ich hätte ich mal alle meldungen durch!! Hoffe das Hilft.
Danke für deine bemühungen!! :!:
Achja mein Interface ist ein Weinzierl KNX/IP 730
-
-
> Danke für deine bemühungen!! :!:Dafür gibts doch den "Danke" button. ;-)
Die gute Nachricht vorweg: Dein KNX/IP ist baugleiche mit meinem. Also kann es daran nicht liegen…
Was mir allerdings auffällt ist: In der Datei knxd.conf hast du: ip:192.168.1.106 stehen. Mach da mal ein ipt:192.168.1.106 draus.
Dannach ein "/etc/init.d/knxd restart" und schauen ob der daemon hoch kommt.
Gruß
-
HI!
Nein leider :
root@raspberrypi:~# systemctl status knxd.service ● knxd.service - KNX Daemon Loaded: loaded (/lib/systemd/system/knxd.service; enabled) Active: activating (auto-restart) (Result: exit-code) since Sa 2016-08-20 12:25:31 CEST; 7s ago Process: 2297 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=1/FAILURE) Main PID: 2297 (code=exited, status=1/FAILURE) Aug 20 12:25:31 raspberrypi systemd[1]: knxd.service: main process exited, c...E Aug 20 12:25:31 raspberrypi systemd[1]: Failed to start KNX Daemon. Aug 20 12:25:31 raspberrypi systemd[1]: Unit knxd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. -
Hmmm… was passiert denn wenn du:
sudo /usr/bin/knxd --eibaddr=0.0.230 -u /tmp/eib -u /var/run/knx -i -DTRS -b ipt:192.168.1.106abfeuerst?
-
Aha!
Was sagt:````
sudo netstat -tulpen|grep 6720 -
sudo ps aux |grep eibdund
sudo ps aux |grep knxd -
Ich bin verwirrt….
Warum ist den der socket offen?
Was sagt:
systemctl -all list-sockets |grep 6720 -
Aber trotzdem sagt systemd das der Dienst nicht startet…
Machmal:
> systemctl stop knxddannach nochmal schauen ob der socket zu ist:
systemctl -all list-sockets |grep 6720
-
Ich erinnere mich dunkel an einen cre podcast mit Lennart Poettering dem maintainer von systemd. Ein neues feature von systemd ist wohl, dass dienste "ondemand" gestartet werden können….
Das ist wohl hier der fall..
Versuch mal:
systemctl disable knxd -
Mal kein fehler:
Synchronizing state for knxd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d knxd defaults Executing /usr/sbin/update-rc.d knxd disable insserv: warning: current start runlevel(s) (empty) of script `knxd' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `knxd' overrides LSB defaults (0 1 6). Removed symlink /etc/systemd/system/sockets.target.wants/knxd.socket. -
Ok…
jetzt nochmal:
sudo /usr/bin/knxd --eibaddr=0.0.230 -u /tmp/eib -u /var/run/knx -i -DTRS -b ipt:192.168.1.106Wenn alles gut ist, meckert er wegen root… egal...
Gruß
-
Pfff.. Renitente Kiste…
Dann auf die harte nummer:
In "/etc/default/knxd" den daemon deaktivieren und neustarten (reboot).
also:
START_KNXD=YES -> START_KNXD=NO
reboot
dann nochmal:
sudo /usr/bin/knxd --eibaddr=0.0.230 -u /tmp/eib -u /var/run/knx -i -DTRS -b ipt:192.168.1.106
-
OK! Wieder was gelernt…
Also:
cd /etc/systemd/system/sockets.target.wants/ mv knxd.socket knxd.socket_tmp rebootProbieren ob es nun geht…
431
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge