=== Lcawte is now known as Lcawte|Away | ||
ali1234 | Azelphur: the real question is why are you still using software centre? | 01:00 |
---|---|---|
Azelphur | ali1234: I'm not, but other new users are :P | 01:00 |
ali1234 | oh, them. | 01:00 |
=== Hornet- is now known as Hornet | ||
brobostigon | morning boys and girls. | 09:12 |
=== Lcawte|Away is now known as Lcawte | ||
=== Monotoko is now known as Guest27897 | ||
bashrc | looks like popey is on pump.io | 13:26 |
directhex | pope.io | 13:37 |
brobostigon | :) | 13:38 |
mapps | urgh | 14:10 |
mapps | mugged it again | 14:10 |
bashrc | I appear to have got my server into a condition of stability by stopping the oom-killer from killing mysql | 14:32 |
directhex | om nom nom oom | 14:46 |
directhex | the linux oom killer is unfit for purpose | 14:47 |
ali1234 | anyone got the link to that FAQ about how to write alsa applications properly so they work with pulseaudio? | 14:50 |
ali1234 | it was like "alsa best-practices" or something | 14:54 |
SuperEngineer | Dear work's laptop, I do recall I told you what would happen if your Outlook in box botred me to tears... I gave you fair warning... I warn you that I knew how to "delete all"... I did warn you that I knew where the off switch off was.... I did warn you that I Steam installed on my own pooter... ;) | 14:56 |
SuperEngineer | *bored | 14:57 |
* SuperEngineer kills work's laptop | 14:58 | |
SuperEngineer | [and laughs manically - movie style] | 14:58 |
bashrc | directhex: the oom-killer is just unintelligent and can't tell critical applications from non-critical ones | 15:19 |
directhex | bashrc, it also can't complete a kill op before getting invoked again, on a machine with a lot of ram, since it doesn't scale | 15:20 |
bashrc | with a lot of ram you can set swapiness to zero, but I'm only on a Beaglebone with limited system resources | 15:21 |
bashrc | the next kernel release for the Beaglebone should also include zram, which may help | 15:24 |
directhex | RamDoubler(tm) for Linux(tm)! | 15:31 |
=== lee1 is now known as Cueball | ||
andylockran | hey guys | 18:24 |
andylockran | any idea how to identify a process pinging tonnes of udp connections? | 18:25 |
andylockran | 19:24:40.561770 IP 220.241.62.169.49838 > 85.119.82.243.10320: UDP, length 172 | 18:25 |
penguin42 | that can be tricky | 18:31 |
andylockran | yeah, proving to be | 18:33 |
andylockran | have spent a few hours on it so far | 18:33 |
penguin42 | have you tried looking at the contents of the packets to see if they suggest anything? | 18:34 |
penguin42 | hmm I wonder if you can do it with perf's trace | 18:34 |
andylockran | the packets contents don't give me any clues | 18:35 |
penguin42 | andylockran: try perf trace -a -e sendmsg | 18:35 |
andylockran | though I can tell it looks like it's being used as a rtp relay | 18:35 |
penguin42 | says he guessing it's using sendmsg to send the packets | 18:36 |
andylockran | hmm, kinda buging me now | 18:40 |
penguin42 | andylockran: Try that perf command - it should show every process using the sendmsg syscall | 18:40 |
andylockran | merlin:/# perf | 18:42 |
andylockran | /usr/bin/perf: line 24: exec: perf_2.6.32: not found | 18:42 |
andylockran | E: linux-tools-2.6.32 is not installed. | 18:42 |
penguin42 | if you tab complete on perf_ do you have anything? | 18:42 |
penguin42 | hmm bit old, might not have trace | 18:42 |
penguin42 | andylockran: The other way that might work is creating an iptalbes rule to block them - not sure if that would show the process in the log? | 18:46 |
andylockran | Ok - blocking the process via ip seems to have blocked the data | 18:50 |
andylockran | but the process is still running | 18:50 |
penguin42 | but are you generating logs showing it? | 18:51 |
andylockran | all I've got at the moment is the tcpdump | 18:52 |
penguin42 | andylockran: I mean make the iptables log the rejects - I can't remember what info you get in the logs when you do that | 18:53 |
andylockran | ooh, ok | 18:53 |
andylockran | https://gist.github.com/anonymous/4dd0e8da0d82cfa8e63a | 18:55 |
penguin42 | andylockran: ah, external syslogging? | 18:55 |
penguin42 | what's pid 1881 then? | 18:56 |
andylockran | named | 18:56 |
penguin42 | so is that saying that named is sending zillions of moans to rsyslog for some reason? | 18:57 |
andylockran | still going strong with those proceses stoped | 18:57 |
penguin42 | did you check if you had perf_something installed ? | 18:58 |
andylockran | I've got perf_3.2 | 18:59 |
andylockran | perf: 'trace' is not a perf-command. See 'perf --help'. | 18:59 |
penguin42 | yeh probably too new a feature | 19:00 |
penguin42 | thing is if they were going to rsyslog I'd have expected some text in the packet - how are you capturing them with tcpdump? | 19:02 |
andylockran | https://gist.github.com/anonymous/793876c3889facf530c3 | 19:02 |
penguin42 | yeh what tcpdump command are you using? | 19:03 |
shauno | curious, do you have then coming inbound too? | 19:03 |
andylockran | I used wireshark | 19:03 |
MartijnVdS | ShireWark | 19:03 |
andylockran | inbound, nthing. | 19:03 |
penguin42 | andylockran: So with your wireshark, what's the contents of those packets - 200 bytes of something | 19:04 |
andylockran | https://gist.github.com/anonymous/a1c43dbb4ab4bea1f808 | 19:04 |
penguin42 | hmm, 200 bytes of not much | 19:05 |
andylockran | 22:43:39.533789 IP (tos 0x80, ttl 56, id 30442, offset 0, flags [DF], proto TCP (6), length 100) | 19:05 |
andylockran | 80.229.11.208.57889 > 85.119.82.243.22: Flags [P.], cksum 0x67c6 (correct), seq 192:240, ack 196913, win 8192, options [nop,nop,TS val 512981144 ecr 183589], length 48 | 19:05 |
andylockran | there are loads - lots of them each second | 19:06 |
penguin42 | andylockran: You could trace strace -p on every process one at a time until you find the victim | 19:07 |
penguin42 | andylockran: is something showing up in top as using cpu - if it's shifting that much you'd think it would be | 19:07 |
shauno | that last one I'd expect to see loads of | 19:08 |
andylockran | yeah - nothing is showing load | 19:08 |
penguin42 | if you just run perf top for a few seconds what's it showing? | 19:10 |
shauno | loads and loads. it's your ssh connection. so as you try to list the packets, it's creating more packets, so it lists more packets .. | 19:10 |
penguin42 | shauno: Oh yeh, that's not the UDP packets he was previously complaining of though | 19:11 |
shauno | right, just pointing out that the last one is a red herring :) | 19:11 |
penguin42 | andylockran: So the packet you grabbed the hex of - how did you select that, have you got the actual udp packets you're worrying about | 19:12 |
andylockran | Just randomly selected | 19:13 |
andylockran | they all seem v. similar at the top level | 19:14 |
andylockran | the IP that they're comunicating with is weird though | 19:14 |
andylockran | 220.241.62.169 | 19:14 |
andylockran | which comes up as a phone site - so I guess I'm relaying their calls for free | 19:15 |
shauno | hong kong. lovely. | 19:15 |
andylockran | even with inbound and outbound conns blocked to that ip, it continues. | 19:16 |
penguin42 | andylockran: iptraffic rule? | 19:16 |
penguin42 | iptables I mean | 19:16 |
penguin42 | andylockran: However, if your box has been owned it could have a hidden process that won't show up in top or anything | 19:17 |
andylockran | set https://gist.github.com/anonymous/ec3cb8a7cc08801ff1b0 | 19:17 |
andylockran | penguin42: scared it's the latter :( | 19:17 |
penguin42 | andylockran: so what does perf top show ? | 19:18 |
andylockran | penguin42: nowt | 19:19 |
penguin42 | andylockran: How do you mean nowt | 19:19 |
andylockran | it doesn't show anything. just says 0 cycles (not sure how to use it though) | 19:20 |
penguin42 | really? Oh never seen that | 19:20 |
penguin42 | andylockran: What distro? | 19:22 |
andylockran | debian wheezy | 19:23 |
penguin42 | the other possibility is it's just got something like an ipsec or other kernel level vpn enabled | 19:23 |
penguin42 | andylockran: if you do mount -t debugfs nodev /sys/kernel/debug does it mount it? | 19:24 |
andylockran | https://gist.github.com/anonymous/d594efb9b8523dc679b8 | 19:24 |
penguin42 | ok, what about ls /sys/kernel/debug/tracing ? | 19:25 |
andylockran | ls /sys/kernel/debug/tracing | 19:25 |
andylockran | available_events buffer_size_kb events per_cpu README set_event trace_clock trace_options tracing_cpumask tracing_on | 19:25 |
andylockran | available_tracers current_tracer options printk_formats saved_cmdlines trace trace_marker trace_pipe tracing_enabled | 19:25 |
penguin42 | ooh that's promising - now can I figure out ftrace | 19:25 |
andylockran | cheers for your time buddy - much appreciated | 19:25 |
penguin42 | andylockran: Can you install the trace-cmd package? | 19:26 |
andylockran | git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git? | 19:27 |
penguin42 | yes, although it should be packaged - it is on ubuntu, not sure about wheezy | 19:27 |
andylockran | installed | 19:28 |
penguin42 | andylockran: so hmm now the idea is to do trace-cmd record something to record something | 19:29 |
penguin42 | andylockran: Maybe all the syscalls | 19:29 |
andylockran | https://gist.github.com/anonymous/ae9c17f2124c3a77612c | 19:31 |
penguin42 | andylockran: how about trace-cmd record -e syscalls:sys_exit_sendmsg | 19:31 |
andylockran | https://gist.github.com/anonymous/7a07a716341c6ddc7368 | 19:32 |
penguin42 | andylockran: trace-cmd list |grep send | 19:32 |
andylockran | merlin:~/trace-cmd# trace-cmd list |grep send | 19:34 |
andylockran | sched:sched_signal_send | 19:34 |
penguin42 | hmm that's boring - it doesn't seem to have syscalls | 19:34 |
penguin42 | how about grep for net instead of send? | 19:35 |
penguin42 | if it has net_dev_xmit it would be good | 19:36 |
andylockran | nothing on net | 19:36 |
penguin42 | ok, that's just too old | 19:36 |
davmor2 | Well this seems to of worked. Server Upgrades FTW | 19:37 |
andylockran | perf_5.2 | 19:37 |
penguin42 | andylockran: Other than strace'ing every pid I can't think of much | 19:37 |
penguin42 | andylockran: Your kernel/perf is just too old for any of the funkier tools | 19:37 |
andylockran | aww . damnit :( | 19:38 |
penguin42 | andylockran: Tried running rkhunter? | 19:39 |
penguin42 | andylockran: Anything fun in dmesg? | 19:40 |
andylockran | nowt | 19:40 |
penguin42 | andylockran: well I'm out of ideas - it's not looking good for the machine though | 19:42 |
shauno | why do they always put blue LEDs in wifi dongles :/ if something's going on the side of my laptop, it shouldn't have a rescue strobe attached to it | 21:13 |
penguin42 | shauno: Because we've run out of other LED colours that are 'cool' | 21:44 |
shauno | I'm entirely in favour of no LEDs | 21:45 |
StevenR | hrrm. As far as I can tell, Ubuntu 14.04 LTS is released.... why doesn't do-release-upgrade see it? | 22:58 |
* penguin42 has half a memory that in 10.04 the update didn't happen until 12.04.1 was out, but I might be imagining that | 23:00 | |
StevenR | penguin42: you're right | 23:02 |
StevenR | Users of 12.04 LTS will be offered the automatic upgrade when 14.04.1 LTS is released, which is scheduled for July 24th | 23:02 |
StevenR | http://fridge.ubuntu.com/2014/04/17/ubuntu-14-04-trusty-tahr-released/ | 23:02 |
StevenR | thanks penguin42 | 23:03 |
penguin42 | still, I should probably upgrade my dad's 12.10 | 23:03 |
ging | is there an ubuntu ppa related channel? | 23:09 |
penguin42 | not that I'm aware of, there is #ubuntu-packaging if your problem is rying to package stuff | 23:16 |
ging | trying to find out if you can put a binary package you have no source for in a ppa | 23:25 |
penguin42 | I suspect that's technically doable, not sure if it's allowed under the rules or not | 23:30 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!