Jump to content
  • 0

KN-1810 sometimes stops working. Fw 3.9.3


Question

Posted

Hi all.

After updating FW to 3.9.3 (stable) my Keenetic Ultra starts to completely stop working.

I have some error messages in log (located on syslog server).

After that I can see all services become unavailable: first of all WUI and cli than DHCP than Wifi than Internet access completely.

I tried to remove entware USB-flash and change Ping checker config, but without any success.

Reboot fix the problem for some time: it works good from dozen minutes to several hours and than stops again.

Any ideas?

PS. I haven't tried to reset to factory settings yet.

Log extract is here:

Feb 17 18:45:07 Keenetic-2918 ndm: Timer: unable to alarm "Network::Interface::LinkDetector" for 60 seconds.
Feb 17 18:45:08 Keenetic-2918 ndm: Timer: "Ping-check profile queue" (2938) backtrace:
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   <unknown>()+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Io::Pollable::SetPollState(ReturnT const&)+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Io::TcpSocketBase::CreateSslConnection_(int, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&)+0x308
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Io::TcpSocketBase::Connect(PVector<Io::SocketAddress> const&, Io::TcpSocketBase::TypeT, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&, int, unsigned int&, Io::SocketAddress&)+0xd84
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Io::TcpSocket::Connect(Array<Network::IpAddress> const&, unsigned short, Io::TcpSocketBase::TypeT const&, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&, int)+0x208
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   PingCheck::Profile::Task_::Run()+0x26c4
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Task::Thread::Run_()+0x488
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Task::Thread::Run()+0x38
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   Thread::StartRoutine_(void*)+0x42c
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   start()+0xc8
Feb 17 18:45:08 Keenetic-2918 ndm: Timer:   __clone()+0x6c
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog: Ping-check profile queue holds INTERFACE_REPO (62) lock 60 seconds acquired Feb 17 18:44:08.
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog: "Ping-check profile queue" (2938) backtrace:
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog:   <unknown>()+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog:   __cp_end()+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog:   __syscall_cp_c()+0xcc
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog:   read()+0x3c
Feb 17 18:45:08 Keenetic-2918 ndm: Core::Watchdog:   BIO_accept()+0x10d0
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder: unable to send "Event::Type::Neighbour" to "Network::Interface::AccessPoint" for 60 seconds.
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder: "Ping-check profile queue" (2938) backtrace:
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder:   <unknown>()+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder:   __cp_end()+0x0
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder:   __syscall_cp_c()+0xcc
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder:   read()+0x3c
Feb 17 18:45:08 Keenetic-2918 ndm: Event::Forwarder:   BIO_accept()+0x10d0
Feb 17 18:45:11 Keenetic-2918 ndm: Network::Interface::Rtx::WifiMonitor: "WifiMaster1/AccessPoint0": STA(04:39:26:55:2e:36) had associated successfully.
Feb 17 18:45:11 Keenetic-2918 ndm: Network::Interface::Rtx::WifiMonitor: "WifiMaster1/AccessPoint0": STA(04:39:26:55:2e:36) set key done in WPA2/WPA2PSK.
Feb 17 18:45:12 Keenetic-2918 ndhcps: DHCPDISCOVER received for 172.16.25.45 from 04:39:26:55:2e:36.
Feb 17 18:45:12 Keenetic-2918 ndhcps: making OFFER of 192.168.2.10 to 04:39:26:55:2e:36.
Feb 17 18:45:12 Keenetic-2918 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 192.168.2.10 from 04:39:26:55:2e:36.
Feb 17 18:45:13 Keenetic-2918 ndhcps: sending ACK of 192.168.2.10 to 04:39:26:55:2e:36.
Feb 17 18:45:13 Keenetic-2918 upnp: getifstats: NDM request failed (Operation timed out)
Feb 17 18:45:13 Keenetic-2918 upnp: getifstats: NDM response not valid (interface: GigabitEthernet1)
Feb 17 18:45:26 Keenetic-2918 telnetd: ::ffff:192.168.2.6 client disconnected.
Feb 17 18:45:28 Keenetic-2918 upnp: getifaddr: NDM request failed (Operation timed out)
Feb 17 18:45:28 Keenetic-2918 upnp: Failed to get ip address for interface GigabitEthernet1
Feb 17 18:45:37 Keenetic-2918 ndm: Timer: unable to alarm "Network::Interface::LinkDetector" for 90 seconds.
Feb 17 18:45:38 Keenetic-2918 ndm: Timer: "Ping-check profile queue" (2938) backtrace:
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   <unknown>()+0x0
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Io::Pollable::SetPollState(ReturnT const&)+0x0
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Io::TcpSocketBase::CreateSslConnection_(int, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&)+0x308
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Io::TcpSocketBase::Connect(PVector<Io::SocketAddress> const&, Io::TcpSocketBase::TypeT, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&, int, unsigned int&, Io::SocketAddress&)+0xd84
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Io::TcpSocket::Connect(Array<Network::IpAddress> const&, unsigned short, Io::TcpSocketBase::TypeT const&, Io::TcpSocketBase::CertVerificationT, CString const&, CString const&, int)+0x208
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   PingCheck::Profile::Task_::Run()+0x26c4
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Task::Thread::Run_()+0x488
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Task::Thread::Run()+0x38
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   Thread::StartRoutine_(void*)+0x42c
Feb 17 18:45:38 Keenetic-2918 ndm: Timer:   start()+0xc8

 

3 answers to this question

Recommended Posts

  • 0
Posted
2 часа назад, TSergey сказал:

Is there any workarounds to avoid the issue?

You may reduce the effect if you will exclude https and TLS protocols from your ping check profile mode setting. 

  • Thanks 1
  • 0
Posted
4 minutes ago, sergeyk said:

It is known issue and it will be fixed in 3.9.4.

Thanks a lot.

Is there any workarounds to avoid the issue?

Probably to disable any services or change config...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...