Jump to content

Kernel kill flow due to timeout? Affecting speeds.


MikeTHIS

Recommended Posts

Posted

first 5 test CPUs at 30/40 percent

and here my netduma stopped working (bug)page like at reboot but you do not hear the signal LEDs flash normally, rebot on the page does not work statement(Missing JSON response)

I disconnected from electricity it helped,

another 10 tests the processor once showed only a jump to 90 percent,the rest normally

 

and now only such messages

Fri May 17 16:56:02 2019 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)

Fri May 17 16:55:15 2019 daemon.info dnsmasq-dhcp[1182]: DHCPREQUEST(br-lan) 192.168.88.111 f0:76:6f:ab:2c:7b

Fri May 17 16:59:23 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Fri May 17 16:58:13 2019 kern.info kernel: [  979.336000] send: nf_ct_get failed
Fri May 17 16:58:13 2019 kern.info kernel: [  979.336000] recv: nf_ct_get failed
Fri May 17 16:57:53 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Fri May 17 16:57:53 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Fri May 17 16:57:44 2019 kern.info kernel: [  951.096000] send: nf_ct_get failed
Fri May 17 16:57:44 2019 kern.info kernel: [  951.096000] recv: nf_ct_get failed
Fri May 17 16:57:30 2019 kern.info kernel: [  936.996000] send: nf_ct_get failed
Fri May 17 16:57:30 2019 kern.info kernel: [  936.996000] recv: nf_ct_get failed
Fri May 17 16:57:23 2019 kern.info kernel: [  929.936000] send: nf_ct_get failed
Fri May 17 16:57:23 2019 kern.info kernel: [  929.936000] recv: nf_ct_get failed
Fri May 17 16:57:23 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Fri May 17 16:57:23 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Fri May 17 16:57:20 2019 kern.info kernel: [  926.404000] send: nf_ct_get failed

  • Replies 94
  • Created
  • Last Reply
Posted

a dzisiaj to 

Sat May 18 06:29:20 2019 kern.info dpiclass-daemon: Kill flow due to timeout
Sat May 18 06:28:43 2019 kern.info kernel: [49609.648000] send: nf_ct_get failed
Sat May 18 06:28:43 2019 kern.info kernel: [49609.648000] recv: nf_ct_get failed
Sat May 18 06:28:36 2019 kern.info kernel: [49602.356000] send: nf_ct_get failed
Sat May 18 06:28:36 2019 kern.info kernel: [49602.356000] recv: nf_ct_get failed
Sat May 18 06:28:36 2019 kern.info kernel: [49602.356000] send: nf_ct_get failed
Sat May 18 06:28:36 2019 kern.info kernel: [49602.356000] recv: nf_ct_get failed
Sat May 18 06:27:58 2019 kern.warn kernel: [49564.340000] HTB: quantum of class 10004 is big. Consider r2q change.
Sat May 18 06:27:57 2019 kern.warn kernel: [49564.216000] HTB: quantum of class 10001 is big. Consider r2q change.
Sat May 18 06:27:57 2019 user.info com.netdumasoftware.qos: applying qos for zone lan
Sat May 18 06:27:57 2019 user.info com.netdumasoftware.qos: applying qos for zone wan
Sat May 18 06:27:37 2019 kern.warn kernel: [49543.908000] HTB: quantum of class 10001 is big. Consider r2q change.
Sat May 18 06:27:37 2019 user.info com.netdumasoftware.qos: applying qos for zone lan
Sat May 18 06:27:32 2019 user.warn com.netdumasoftware.devicemanager: RPC call 'get_device_ips' exception 'ERROR: Nonexistent device
stack traceback:
    ?: in function '__new__'
    ?: in function '?'
    ?: in function <?:469>
    (tail call): ?
    ?: in function 'get_device'
    ?: in function <?:197>
    ?: in function <?:324>
    [C]: in function 'xpcall'
    ?: in function 'try'
    ?: in function <?:290>
    [C]: in function 'run'
    ?: in function <?:345>
    [C]: in function 'xpcall'
    ?: in function 'try'
    ?: in function <?:261>
    (taSat May 18 06:27:36 2019 user.info com.netdumasoftware.qos: applying qos for zone wan
Sat May 18 06:27:31 2019 kern.warn kernel: [49537.744000] HTB: quantum of class 10001 is big. Consider r2q change.
Sat May 18 06:27:31 2019 user.info com.netdumasoftware.qos: applying qos for zone lan
Sat May 18 06:27:30 2019 user.info com.netdumasoftware.qos: applying qos for zone wan
Sat May 18 06:27:29 2019 daemon.warn odhcpd[737]: Failed to send to ff02::1%br-lan (Operation not permitted)
Sat May 18 06:27:15 2019 kern.info kernel: [49521.704000] send: nf_ct_get failed
Sun May 19 10:25:35 2019 user.info com.netdumasoftware.systeminfo: Ubus object 'com.netdumasoftware.geofilter' added, attempting to bind pending
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7262]: Distance set to 1514
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7262]: User Engine 7
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7262]: Kernel thread started
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7262]: Set kernel thread to top FIFO priority
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: Disabled NETLINK returned 0
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: New buffer size is 262144
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: Default buffer size 163840
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: Setting queue buf size is enabled
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: Home coordinate set to (37,-98)
Sun May 19 10:25:35 2019 local5.info geoip-daemon[7261]: verdict marking: 1 shift: 19
Sun May 19 10:25:07 2019 user.info com.netdumasoftware.qos: Ubus object 'com.netdumasoftware.qos' added, attempting to bind pending
Sun May 19 10:25:07 2019 user.info com.netdumasoftware.qos: Ubus object 'com.netdumasoftware.hybridvpn' added, attempting to bind pending

  • Administrators
Posted

Thanks for this. We’ll need to check with a dev if these logs are indicative of anything. We’ll get back to you on Monday about this. 

  • Administrators
Posted

It looks like Google Translate may have changed the logs you posted. Could you post them again but unmodified?

Posted
4 hours ago, Netduma Alex said:

It looks like Google Translate may have changed the logs you posted. Could you post them again but unmodified?

ok, I've edited and improved

Posted

Reupgraded to Duma os

CPU keeps going to 100% and speeds are slow. 

Edit: Same issue, speeds are erratic. 

So now what? 

  • Administrators
Posted

Sorry it was a UK bank holiday yesterday, so nobody was in.

I'll check and see if any progress has been made.

Posted
10 hours ago, Netduma Alex said:

Sorry it was a UK bank holiday yesterday, so nobody was in.

I'll check and see if any progress has been made.

It’s to the point where I can’t use it right now unless it’s the old OS, but the caveat is that we have nat issues with two consoles 

Here is my current log:

log-1559077055178.txt

  • Administrators
Posted

I can't comment on the log so I'll wait for Alex to respond with feedback from devs. Are you using UPnP or Port Forwarding and do you have any luck if you use one over the other?

Posted
1 hour ago, Netduma Fraser said:

I can't comment on the log so I'll wait for Alex to respond with feedback from devs. Are you using UPnP or Port Forwarding and do you have any luck if you use one over the other?

UPNP on OS and the older software. 

Its fine on OS.

My speeds....no

Posted
15 hours ago, Netduma Fraser said:

Try to use port forwarding instead and forward 3074 for one and 3075 for the other

I’m sticking with the DumaOS for right now, it just works better with multiple consoles, but I’d REALLY like to help you guys nail down whatever the issue I’m seeing is. 

I went through all settings last night to make sure WiFi was off as I have a separate router for WiFi (the tick box was on, but it wasn’t “on” - strange)

I also noticed the VPN switch was on, but I have never used it.

I have the sliders set for 100% and ticked never - I’ll get max speeds SOMETIMES, but lower speeds often. During this, as suggested - watched the CPU and it hits 100% and the speeds slow down.

This happens wired, and wireless on every single device.

Log is above.

This is one of the first routers, I’m an early adopter, if that matters any.

Original firmware has functional QOS, as evidenced in this thread already.

Please help.

 

 

 

Posted
5 minutes ago, Netduma Alex said:

Devs still working on it

I'll check in tomorrow

Ok. Thanks for the update. 

  • Administrators
Posted

We're pretty sure that this is due to the age of your router, it certainly sounds like something caused by hardware.

Could you please email us at [email protected]

Posted
38 minutes ago, Netduma Alex said:

We're pretty sure that this is due to the age of your router, it certainly sounds like something caused by hardware.

Could you please email us at [email protected]

Sending now. 

Posted

Never heard anything via email from you guys. 

I wound up downgrading again because the speeds were too slow and erratic. 

 

 

  • Administrators
Posted

Ah sorry you emailed right before I left the office on Friday. I'll respond.

Posted

So are we not supposed to see these in our logs?  I tried searching for this months ago and found nothing.

image.png.562d9d07cadf967695b23242e9a1c038.png

I would love to have this fixed as well, or at the very least explained what it is that I'm reading.

  • Administrators
Posted
9 minutes ago, The0dark0one said:

So are we not supposed to see these in our logs?  I tried searching for this months ago and found nothing.

image.png.562d9d07cadf967695b23242e9a1c038.png

I would love to have this fixed as well, or at the very least explained what it is that I'm reading.

What's the effect that this is having on your connection?

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...