Hi,
habe Probleme mit dem Start von knxd 0.14.16:85fe31e
Ein
knxd /etc/knxd.conf
funktioniert problemlos.
Mit
systemctl start knxd.service
bekomme ich folgende Fehler:
Meine /etc/knxd.conf
LG
mode
habe Probleme mit dem Start von knxd 0.14.16:85fe31e
Ein
knxd /etc/knxd.conf
funktioniert problemlos.
Mit
systemctl start knxd.service
bekomme ich folgende Fehler:
Code:
Aug 11 23:39:40 ubuntu systemd[1]: knxd.service: Ignoring invalid environment assignment 'trace-mask=0': /etc/knxd.conf Aug 11 23:39:40 ubuntu systemd[1]: knxd.service: Ignoring invalid environment assignment 'client-addrs=1.1.251:3': /etc/knxd.conf Aug 11 23:39:40 ubuntu systemd[1]: Starting KNX Daemon... -- Subject: Unit knxd.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit knxd.service has begun starting up. Aug 11 23:39:40 ubuntu knxd[8945]: Usage: knxd configfile [main_section] Aug 11 23:39:40 ubuntu knxd[8945]: Please consult /usr/share/doc/knxd/inifile.rst Aug 11 23:39:40 ubuntu systemd[1]: knxd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 11 23:39:40 ubuntu systemd[1]: Failed to start KNX Daemon. -- Subject: Unit knxd.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit knxd.service has failed. -- -- The result is failed. Aug 11 23:39:40 ubuntu systemd[1]: knxd.service: Unit entered failed state. Aug 11 23:39:40 ubuntu systemd[1]: knxd.service: Failed with result 'exit-code'. Aug 11 23:39:43 ubuntu polkitd(authority=local)[774]: Registered Authentication Agent for unix-process:8962:428532 (system bus name :1.25 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale Aug 11 23:39:43 ubuntu polkit-agent-helper-1[8968]: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory Aug 11 23:39:43 ubuntu polkit-agent-helper-1[8968]: PAM adding faulty module: pam_winbind.so Aug 11 23:39:47 ubuntu polkitd(authority=local)[774]: Operator of unix-process:8962:428532 successfully authenticated as unix-user:mode to gain ONE-SHOT authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.26 [systemctl Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Service hold-off time over, scheduling restart. Aug 11 23:39:50 ubuntu systemd[1]: Stopped KNX Daemon. -- Subject: Unit knxd.service has finished shutting down -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit knxd.service has finished shutting down. Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Ignoring invalid environment assignment 'trace-mask=0': /etc/knxd.conf Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Ignoring invalid environment assignment 'client-addrs=1.1.251:3': /etc/knxd.conf Aug 11 23:39:50 ubuntu systemd[1]: Starting KNX Daemon... -- Subject: Unit knxd.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit knxd.service has begun starting up. Aug 11 23:39:50 ubuntu knxd[8971]: Usage: knxd configfile [main_section] Aug 11 23:39:50 ubuntu knxd[8971]: Please consult /usr/share/doc/knxd/inifile.rst Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 11 23:39:50 ubuntu systemd[1]: Failed to start KNX Daemon. -- Subject: Unit knxd.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit knxd.service has failed. -- -- The result is failed. Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Unit entered failed state. Aug 11 23:39:50 ubuntu systemd[1]: knxd.service: Failed with result 'exit-code'. Aug 11 23:39:50 ubuntu polkitd(authority=local)[774]: Unregistered Authentication Agent for unix-process:8962:428532 (system bus name :1.25, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) (disconnected from bus)
Code:
[B.tpuarts] device = /dev/ttyUSB_KNX driver = tpuart [debug-server] name = mcast:knxd [debug-tunnel] trace-mask = 0 [main] addr = 1.1.251 client-addrs = 1.1.251:3 cache = A.cache connections = server,B.tpuarts systemd = systemd [server] debug = debug-server discover = true server = ets_router tunnel = tunnel [tunnel] debug = debug-tunnel # configuration for knxd.service #KNXD_OPTS=" -e 1.1.251 -t 0 -T -D -S -c tpuarts:/dev/ttyUSB_KNX" # 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:). # knxd's own bus address is 0.0.1; it will assign 0.0.2…0.0.9 to clients. # The knxd.socket file also tells knxd to listen to # /run/eib (socket activation via systemd) # TCP port 6720 (socket activation via systemd) # You *need* the -e option. Clients cannot connect without "-E". # You can read knxd's logs with # $ journalctl -u knxd --since "10 min ago" # (or whatever). See the manpage for details. # You need to be a member of the "adm" group. # Add "-f9 -t1023" to the beginning of the command line for extensive logging. # *** DO NOT use "-u" / "-u /run/knx" or "-i" / "-i 6720" here. # Systemd already does that on behalf of knxd, via 'knx.socket'. # *** DO NOT use both "-RS" and "-b ip:" (unless you specify a # different multicast address on one of them). You'd create a loop. # 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, for example "-e 7.0.99". # You should have a block of free addresses on your KNX bus which knxd can # assign to clients: "-E 7.0.100:28" will use 7.0.100 through 7.0.127. # If no such range is given, or if it's full, knxd uses its own address. # That mostly works, but separate addresses are much better. # 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 ## -p PIDFILE -- please use systemctl to control knxd ############################################################################### # This file is ignored when NOT using systemd: edit /etc/default/knxd instead # ###############################################################################
LG
mode
Kommentar