Deco P9 error: daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 20 ??
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi All,
Looking for some assistance from other Deco P9 users.
I've noticed my P9 is reporting the following error "daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 20", approximately 20+ times per minute. I've also noticed the P9 is repeatedly experiencing 100% CPU utilisation (load), and am wondering if the two could be related. I've contacted tp-link support, who've advised they can't see any issue with the device.
However, I'd be grateful if other Deco P9 users could check and advise if the same / similar error is being reported by their P9 systems in the (Notice, Error, Warning) logs?
Thank for the assistance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@FireDZ Same thing, multiple disconnects from internet in the logs, multiple restarts of daemons.
The interface appears to change, mine is 24.
Tried both as router and access point.
Odd thing - as access point you can see the dhcp daemon start up and attempt to dish out addresses which it SHOULD NOT DO! i.e. udhcpd[8797] clear ip c0a80064
Which basically tries to clear 192.168.0.100.
It attempts to own the range 192.168.0.100 to 192.168.0.250 My main router is 192.168.0.1/8 so it takes the top half.
It goes ( *** are my comments from entries in the logs ).
AP Online status changed (ONLINE --> OFFLINE) *** basically internet down for anything attached to Deco.
route del default dev br-lan *** let's start again and try to get you back online.
smartipd restart udhcpd *** why would it want to restart this when you are an Access Point and not responsible for IP address allocation?
kill process udhcpd *** after restart? Huh?
Received SIGTERM *** the udhcpd goes down.
udhcp (v1.22.1) started *** OK - we're going to allocate IP addresses soon, no idea why since we're an access point.
Sending Discover *** dhcp is trrying to find out stuff about the network, presumably to grab a range it thinks it can use.
config IP: ifconfig br-lan 192.168.0.30 netmask 255.255.255.0 *** this is the Deco setting up it's network interface port, proof that it has completely gone off the grid.
then what follows are gateway configurations for the br-lan port with the miniupnpd being restarted (universal plug and play).
Now the apsd errors show up again although we do go back to being ONLINE.
Logs then show other deco units connecting and an apsd around once per second.
Followed by an OFFLINE on the connection and it going back round again.
Overall, exactly 60 seconds passed between ONLINE and OFFLINE. 30 seconds to get back ONLINE again. 60 seconds, back OFFLINE.
Rince, repeat, annoyingly poor internet.
One of two things, the apsd is a symptom of the problem and might help it be tracked down or ...
There's a race condition, something hasn't happened within 60 seconds and so the OS assumes there's a need to reboot.
My money is on the race condition against a watchdog.
Either way, tp-link are the only ones who can resolve this unless their source code is public domain. In that case (quite possible as it's a linux base) other users can fix it for them.
- Copy Link
- Report Inappropriate Content
I've turned off 5ghz wifi and everything (connections) are much more stable now, now more disconnects, but off course this should not be the way to fix this, as I want to use 5ghz option as well.....
TP-Link, please fix this ASAP!!!
- Copy Link
- Report Inappropriate Content
Below is a sample of the logs I'm getting. It just keeps doing it over and over and over. At this point I would rather be given the option to downgrade to the last stable firmware version.
Sat Jul 4 01:03:23 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff62:3cce is link-local multicast address
Sat Jul 4 01:03:23 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff62:3cce is link-local multicast address
Sat Jul 4 01:03:24 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::fb is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:25 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::1:ff00:0 is link-local multicast address
Sat Jul 4 01:03:28 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::fb is link-local multicast address
Sat Jul 4 01:03:28 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::fb is link-local multicast address
Sat Jul 4 01:03:29 2020 user.warn IMPROXY: WARNING[imp_verify_multicast_addr@206]: Group address ff02::c is link-local multicast address
Sat Jul 4 01:03:30 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sat Jul 4 01:03:33 2020 user.notice IMPROXY: INFO[imp_verify_multicast_addr@245]: Group address 224.0.0.251 is Local Network Control Block
Sat Jul 4 01:03:42 2020 user.warn IMPROXY: WARNING[mcast_recv_igmp@753]: Don't exist this Downstream VIF
Sat Jul 4 01:03:46 2020 daemon.err uhttpd[7340]: ath22 no frequency information.
Sat Jul 4 01:03:46 2020 daemon.err uhttpd[7340]:
- Copy Link
- Report Inappropriate Content
@TP-Link_Deco would love to here from you guys :) I emailed TP-Link Germany on 25th June and still no reply and as you can see, many users are having some problems.
- Copy Link
- Report Inappropriate Content
Had another response from tp-link support; they're gathering data to investigate the disconnection issues in more detail.
Additionally, tp-link is also working on an updated firmware to address the various erroneous errors being seen in the logs (No details or potential timescales for release of the updated firmware).
- Copy Link
- Report Inappropriate Content
@FireDZ Thank you for the update. Can you please let us know if/when they post an updated firmware? Much appreciated!
- Copy Link
- Report Inappropriate Content
I haven't received any updates from TP-Link Germany regarding my ticket what so ever from 25th of June. I cannot believe this.
- Copy Link
- Report Inappropriate Content
Hello all, sorry to respond late.
For the daemon.err display issue, we have received your feedback and will ask our developers to speed up analyzing it, please be more patient, thanks.
For the CPU shows 100% issue, as far as we can tell it will only appear when you just entered the web UI of the Deco P9 and it will be back normal after a while. This is also forwarded to the engineers and we will update here.
However, neither the daemon.err display issue nor the 100% CPU issue will cause the P9 crash or disconnecting from the internet, so if anyone encounters a disconnection issue with the Deco P9 network, please confirm some basic info so that we can speed up the whole process and offer a solution:
1. Refer to the troubleshooting guide to narrow down the issue and confirm if the whole system is unstable or just the satellite P9 is disconnecting from the main P9:
2. What is the detailed network diagram and how Deco P9s connected, is the main P9 a Router or an Access Point? What is the LED status on each Deco P9 when the network disconnects?
3. How often does the disconnection issue happen and how do you make it back to work?
4. Are all clients disconnecting from the network or just some of them? Is the wireless still connected but showing no internet access or it got disconnected from the network?
Thanks for your cooperation and look forward to your reply.
- Copy Link
- Report Inappropriate Content
Hi everyone,
If you are getting issues where your DECO P9 goes red and or internet access just dies. I found a "fix".
I purchase 3 DECO P9s and since the purchase I would get a day or more usage before the connection would go red
To troubleshoot, over 7 days ago I unplugged one of the P9s (not the master) and just ran with 2x DECO p9s. Since then it has been pretty reliable with no failure to internet access.
Still getting the following in the logs though.
Tue Jul 7 14:08:12 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
Tue Jul 7 14:08:15 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
Tue Jul 7 14:08:18 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
Tue Jul 7 14:08:21 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
Tue Jul 7 14:08:24 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
Tue Jul 7 14:08:27 2020 daemon.err /usr/bin/apsd: apsd_get_active_ports:214: Error: No such interface 24
- Copy Link
- Report Inappropriate Content
@Rho I can confirm the network stays stable with 2 deco units(1 router, 1 AP).
Last week I added the third one again and all was great for hours.
But then suddenly the system started to mallfunction again. Stalling while loading complex websites and my Samsung Galaxy Note 8 got the message 'internet may not be available' again. Now 3 days great performance with 2 units.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 24357
Replies: 94
Voters 0
No one has voted for it yet.