Network statistics widget causes error message

[tariqbuilds]

Network statistics widget causes error message

[arnaudbey]

what does this command tell, in a shell ?

/bin/netstat -ntu | awk 'NR>2{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr

[lgaetz]

Load the dashboard, get the error message and this:

root@pbx2:/ $ /bin/netstat -ntu | awk 'NR>2{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr
     18
      2 127.0.0.1
      2 10.41.2.126
      1 208.113.219.101
      1 146.255.36.1
      1 10.41.2.6

[arnaudbey]

i suspect that address to begin with a ":" or something wrong with the cut

could you try without the cut ?
/bin/netstat -ntu | awk 'NR>2{print $5}' | sort | uniq -c | sort -rk 1

by the way, this command should be the one used (if it fixes your pb obviously), cause it may the result more precise, keeping port distinction beetween connections.

[lgaetz]

Confirmed.

root@pbx2:/ $ /bin/netstat -ntu | awk 'NR>2{print $5}' | sort | uniq -c | sort -rk 1
      1 ::ffff:10.41.2.6:38329
      1 ::ffff:10.41.2.126:62136
      1 ::ffff:10.41.2.126:62135
      1 ::ffff:10.41.2.126:62134
      1 ::ffff:10.41.2.126:62133
      1 ::ffff:10.41.2.126:62132
      1 ::ffff:10.41.2.126:62131
      1 ::ffff:10.41.2.126:62130
      1 ::ffff:10.41.2.126:62129
      1 ::ffff:10.41.2.126:62128
      1 ::ffff:10.41.2.126:62127
      1 ::ffff:10.41.2.126:62126
      1 ::ffff:10.41.2.126:62125
      1 ::ffff:10.41.2.126:62124
      1 ::ffff:10.41.2.126:62123
      1 ::ffff:10.41.2.126:62122
      1 ::ffff:10.41.2.126:62121
      1 ::ffff:10.41.2.126:62120
      1 ::ffff:10.41.2.126:62119
      1 208.113.219.101:80
      1 127.0.0.1:56565
      1 127.0.0.1:5038
      1 10.41.2.126:61511
      1 10.41.2.126:60640
      1 10.10.0.17:53

[arnaudbey]

And how about this one ?
/bin/netstat -ntu | awk 'NR>2 {sub(/:[^:]+?$/, ""); print $5}' | sort | uniq -c | sort -rk 1

[lgaetz]

root@pbx2:/ $ /bin/netstat -ntu | awk 'NR>2 {sub(/:[^:]+?$/, ""); print $5}' | sort | uniq -c | sort -rk 1
      2 127.0.0.1
      2 10.41.2.126
     20 ::ffff:10.41.2.126
      1 208.113.219.101
      1 146.255.36.1
      1 10.41.2.6

[arnaudbey]

hmm, it solves (partially) the problem. This one should be ok :
/bin/netstat -ntu | awk 'NR>2 {sub(/:[^:]+?$/, ""); print $5}' | sort | uniq -c | sort -nrk 1

[lgaetz]

root@pbx2:/ $ /bin/netstat -ntu | awk 'NR>2 {sub(/:[^:]+?$/, ""); print $5}' | sort | uniq -c | sort -nrk 1
     31 ::ffff:10.41.2.126
      2 127.0.0.1
      2 10.41.2.126
      1 208.113.219.101
      1 146.255.36.1

[commonquail]

The port will only be a number; sub(/:[^:]+?$/, ""); can be changed to sub(/:[0-9]+$/, "");.
Is the first call to sort necessary?
The k argument to the second sort call can be omitted.

[arnaudbey]

yep, first sort is necessary. Removing it cause the uniq to not work completly. Dunbno exactkly why, i'm not a unix expert, not yet :)

And about regexp, it's not a bug, it's a feature 💃
I just wanted to be more generic, that's why I also make the quantifior less greedy (to handle weird client address)

And I agree about the k argument.

[arnaudbey]

second sort is even fully useless since it's javascript sorted

[commonquail]

I figured that was the cause for the pattern. I personally prefer explicitness when possible and I'd rather tackle specific issues as they arise, but I'm not going to insist either way.

I do think we should probably drop the second call to sort, though.

[arnaudbey]

I'm ok with that too, i'll change it in that way !