Yesterday i startetd testing the AmazonDashButton.
Its working but since that my log is full with lines like the following:
…
2017-02-12 09:09:05.532 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:07.571 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:09.672 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:11.392 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:13.422 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:15.492 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:17.450 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 09:09:19.500 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
…andSoOn
Thats just a small Part of the log.
As you see, there are many lines within a few seconds…i think thats killing the SD card over the time (raspberry pi 3).
Concerning the binding-doc at
i installed pcap4j on my raspberry (linux jessy or so) and did every setcap step of the doc.
Now (cause of the log problem) i removed pcap4j again with
sudo apt-get remove libpcap-dev
but still got the log entries.
Then i executed
sudo setcap -r realpath /usr/bin/java to remove them also.
And now openhab.log looks like this when i try to detect my dashbutton in paperUI:
...
2017-02-12 10:01:59.553 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 10:02:01.561 [WARN ] [org.pcap4j.core.PcapNetworkInterface] - Empty pcap_addr on tun0 (null). Ignore it.
2017-02-12 10:02:03.350 [ERROR] [nal.capturing.PacketCapturingService] - Capturing packets on device lo failed.
org.pcap4j.core.PcapNativeException: lo: You don't have permission to capture on that device (socket: Operation not permitted)
...
So now there are still these lines with “…Empty pcap_addr on tun0 (null)…”.
After that i removed the Binding itself again.
The log is clear now…so it seems that the binding is the ultimate reason for the entries.
FYI:
I also use the RPI as vpn server so this tun0 interface maybe comes from that side…
I would like to use the dashbutton but i dont want to kill my sd card with that amount of write access.
Nevertheless i uninstalled the dashbutton binding, i see the thing at paperui-config.things.
its always “offline” and after a click on remove its “removing”.
after a reboot its again offline.
So i am not able to delete this thing.
It seems that it got installed by adding the rule according to the dashbinding-doc (see link in 1st post).
Having exact same issue with openvpn set up on rpi3 and getting this on the openhab.log every 2 seconds.
I notice it is a “logger.warn” message on org.pcap4j.core.PcapNetworkInterface, but not sure how to filter out warning messages.
tun0 and tun1 do have ip-address associated but are used for VPN
imq0 and imq1 are used for QOS and have no ip-address
These come automatically when enabling the VPN and QOS modules on ClearOs (and other distros too I would expect)…
I know the subnet the dashbuttons are on, wouldn’t it make sense to limit to that interface only (or at least make it possible to configure the interfaces)…
I think this is related to those interfaces and the application is polluting the logs with this. Not sure if there are a lot of things you can do apart from ignoring it. Maybe you can turn on only ‘error’ logging and filter out ‘warn’ logs?
