An earnest appeal - please do fix APINGER in 2.2
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
This is a production unit. While I followed the 2.1 beta series, I haven't yet moved to 2.2 beta.
-
@KOM:
You must be new to a support role ;D
People are utterly fantastic at complaining about this, that and the other thing. The moment that they have to wiggle their little finger to help themselves, though, suddenly their problem is not quite so urgent or they just never quite get around to it. But they keep complaining…
Dude.
-
@ermal:
How difficult is to post logs after activating debug knob available on latest snapshots and post it here?
I attached my logs on reply 54, then when you asked for them in reply 55, I replied in reply 56 that they were attached to my previous post. You didn't respond asking for anything else, I do not know what else you want…
The gateway logs are on post 54. If you need other logs let me know and I will be glad to provide.
-
i need to see at least two logs since so many people complain about it.
That will give clues for the proper problem here. -
test
Why cant I copy/paste anything into this…
I write test and get no server error, but copy the log and I get unavailable/Nginx error.
-
The website cannot display the page
HTTP 500
Most likely causes:
•The website is under maintenance.
•The website has a programming error.What you can try:
Refresh the page.
Go back to the previous page.
More information More information
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.
-
Put it on gist.github.com and post the link?
-
https://gist.github.com/anonymous/7f15078fbe6c76e91502
-
i do not see issues from the log do you really have issues?
-
are you sure your system time is on sync and not running backward?
-
I also put a fix on apinger to recover from strange delay values on new snapshots.
-
Yes. It starts to show latency and packetloss. Then I manually restart the Apinger service and it runs again no issues.
It gets worse when the alarms are triggered and after a restart then no problem again for some time.
-
@ermal:
are you sure your system time is on sync and not running backward?
It was set to sync through hyper-v…I just disabled that in case it was causing issues. Also, I just updated to the latest snapshot. Will post update soon.
-
Update: All looks good.
It looks like ermal's fixes have made a huge difference. No more weird latency issues. I am at almost 2 days uptime, rrd graphs and gateway status is spot on.
I am on the Monday snapshot.
-
Still got a offline opt1 on latest Thu Oct 09 15:04:15 bulid.
-
can you explain the offline nic?
Put more detail on what you mean by that. -
@ermal:
can you explain the offline nic?
Put more detail on what you mean by that.I meant apinger showed me a opt1 offline status after a system upgrade in some snapshots, but in fact two pppoe lines are connected and up.
I got it today after upgraded to Oct 14 17:37:25 build on the first reboot, but it's disappeared after another reboot.
-
My HE IPv6 tunnel has been stuck at 14% packetloss - exactly - for days. Even though it's working fine. (2.1.5). As far as I'm concerned, apinger should be all hands on deck at ESF. for 2.1.6 and 2.2. It's completely broken and the ramifications are pretty extreme.
I am, right now, going to go add debugging to my 2.1.5 and restart apinger.
ETA: I would concentrate my efforts in the logic that calculates what's debug logged as "Recently lost packets". Something is not properly decrementing that variable.
-
put apinger in debug mode and give me the logs.
-
My HE IPv6 tunnel has been stuck at 14% packetloss - exactly - for days. Even though it's working fine. (2.1.5). As far as I'm concerned, apinger should be all hands on deck at ESF. for 2.1.6 and 2.2. It's completely broken and the ramifications are pretty extreme.
I am, right now, going to go add debugging to my 2.1.5 and restart apinger.
ETA: I would concentrate my efforts in the logic that calculates what's debug logged as "Recently lost packets". Something is not properly decrementing that variable.
It needs to be replaced but when i come to it.
There is some statistical calculation that is wrong there especially after reloading the config.
Though i should have fixed most of them by now.